FET - edit & print

[Liviu Lalescu]

Thank you, g.theodoroy!

You corrected the minor problems which I reported.

I found a possible typo in your source code:

"existingElenents" -> should be Elements, with m instead of n?

Please forgive me for something: I forgot to add your name in the THANKS and Help/About/Thanks. I just released the new version without it . I will add your name in the next version.

[Liviu Lalescu]

@g.theodoroy ,

Vangelis just sent me a file saved file by your program and we found a bug: in the constraints activity preferred starting time, you write 1..n instead of hour_name[1],..,hour_name[n]. The fet file cannot be opened by FET.

[Liviu Lalescu]

@g.theodoroy ,

Vangelis gave me the attached file which if you load in your program shows nothing (empty). Is this a bug?

[g.theodoroy]

Obviously it needs debugging


 

[Liviu Lalescu]

Vangelis puts your program to work/test!

[g.theodoroy]

The problem in Mytest-for-conflicts... is that in one activity there are no teachers.

if i put teachers it works

I will check it.

Of course this "program" cannot fulfill all the abilities of real FET


As for the hours in my fet files i used "numbers" for hour names.

I will check both bugs

[Liviu Lalescu]

Don't worry, even I make a lot of bugs.

[g.theodoroy]

Fixed

• Hour names fixed
• If no teacher in Activity a new empty row is added with 'no teacher'

I don't understand something

When i open with FET the modified fet file from html some times the first generation stucks at one Activity ( one of activities that have been moved )

[Liviu Lalescu]

Thank you!

It is normal, because the fixed activities are scheduled first, and they are possible, but the last unscheduled activities will be impossible to place. To be able to schedule all, deactivate all the time and space constraints of type other than the locking time and space constraints: activity preferred starting time and activity preferred room.

[Liviu Lalescu]

Thank you!

I checked and now it behaves correct. I like the program, because it is so short and does so many things! Unfortunately, I don't understand the code, because it is so different from C++

I would recommend you to maybe:

1) Write your name+contact in the source file.

2) Write the license type and conditions in the source file.

3) Write your name+contact in something like Help/About when running the file. This is maybe. See how I did in FET Help/About, but I am not sure you can do this in HTML... As you consider best.

4) Write the license type (short) when running the file. Again this is maybe.

[Vangelis Karafillidis]

Thank you!

It is normal, because the fixed activities are scheduled first, and they are possible, but the last unscheduled activities will be impossible to place. To be able to schedule all, deactivate all the time and space constraints of type other than the locking time and space constraints: activity preferred starting time and activity preferred room.

@Liviu Lalescu and @g.theodoroy,

I think that this html file should have a specific behavior. When the user has modified an existing timetable, they need to save the new timetable as a .fet file in order to generate all the other forms (views) of the timetable. The constraints (for example teacher - min hours daily) are not needed anymore. So, since a) the user is sure about the new (modified) timetable, and b) this timetable is a temporary one (i.e. it is going to be used for the next day), only the locking time and space constraints are needed. All the other constraints could be omitted. I don't know if this easier regarding the coding part, but in my opinion if this possible (this "cleaning-up" of the constraints), it might simplify things...

Vangelis.

P.S. I am going to test the new file in more detail soon...
I really like this idea by @g.theodoroy !!!

[Liviu Lalescu]

@g.theodoroy ,

I had a consultation with Volker and, if you want, we could make a board for your program here on the forum, and make you moderator on this board. It will be similar to Volker's TiTiTo, StElTo, and TSC boards on the FET Tools section.

Please let me know if you would like this.

[g.theodoroy]

Let first decide that it is robust enough and deserves to be there.

Thank you very much.

[Liviu Lalescu]

Sure, sorry!

[g.theodoroy]

Added

• name+contact is written in the source file.
• license type and conditions is written in the source file.
• "Help/About modal" on button press
• Name, license type, mail to, at bottom of page
• "Error modal" in case of read-load error of fet file to catch program collapse

Thank you Liviu for your advices!