Some suggestions for new options...

[alex]

Suggestions:
1) There are many constraints of the type "Max hours daily for all teachers" or "Max hours daily for all students", etc. I think that it would be very useful to have options such as "Default max hours daily for all teachers". For example, a constraint of this type would be like this:
Default max hours daily for all teachers: 5
and would add this constraint to all teachers unless some of them are given individually the constraint "Max hours daily for a teacher". So, all teachers who are not given the constraint "Max hours daily for a teacher" would have the maximum of 5 hours daily.
2) I think that adding the constraints "Min gaps per week for a teacher/all teachers", "Min gaps per day for a teacher/all teachers" (and why not "default max gaps per week for all teachers" and "default max gaps per day for all teachers") would give more options for a just timetable.
3) When adding activities, and if one has added more than one teachers/students sets/tags for the same activity, it's impossible to remove for example just one of the tags or just one of the teachers. Instead, one has to press the "clear" button, remove all the contains of the specific field and import one by one the information he needs. So, it would be very useful for example to add a "remove" option (for example by pressing the right button of the mouse) exactly on the selected (specific) information (for example: tag) that needs to be removed.
4) When adding an activity (which is split in 2 days or more), I think that there should be more options for defining more exactly the "distance" between each one of the "splits" (actually between each one of the sub-activities). So, I think one more option should be added. The option "min days" with its weight is OK. I suggest that if the weight here is not 100% (for example if it is 95%), an additional option of defining the actual min days (with a 100% weight) would be very useful. For example: An activity is split in 3 parts (sub-activities) per week (a five-day week). If we give
min days = 2, weight 100%,
the algorithm will result in a timetable with this activity placed on Monday, Wednesday and Friday. If we give min days = 2, weight 95%,
the algorithm might place the activities for example on Monday, Wednesday and Thursday, or the 1st sub-activity on Monday, and the 2nd and 3rd in the same day (Wednesday). If there is the additional option for defining the actual min days between the activities (with a 100% weight), the algorithm would give different results. For example, if we give
min days = 2 weight 95% AND
min days = 1 weight 100%,
the algorithm should never give the result with the sub-activities places on Monday (the 1st sub-activity) and Wednesday (the 2nd and 3rd sub-activities).
5) In the same window (adding an activity), I think that the additional option of defining if a sub-activity (with 2 hours duration for example) should be with the two hours consecutive or not, would be really useful.
Thanks a lot!

[Volker Dirr]

3) When adding activities, and if one has added more than one teachers/students sets/tags for the same activity, it's impossible to remove for example just one of the tags or just one of the teachers. Instead, one has to press the "clear" button, remove all the contains of the specific field and import one by one the information he needs. So, it would be very useful for example to add a "remove" option (for example by pressing the right button of the mouse) exactly on the selected (specific) information (for example: tag) that needs to be removed.

You can remove just one by double clicking on that name. So this feature request already exists.

[alex]

Thanks a lot! I didn't know it!

[Volker Dirr]

About the other requests:
Thank you for report. Of course Liviu is in charge to decide.
My personal opinion:
a) the activity window is already very full. no problems to guys with a full HD 27 inch display. but a problem to guys with a small resolution 14 inch laptop display. so i am not sure if it's possible to add that request.
b) about the "default" stuff: in my opinion the windows are not very good for a user. the current way how constraints are stored are wonderful if you read that as a coder or as you enter them the first time as a user. But as soon as you reuse the date one year later, it is sometimes confusing and complicated. The current version use only little memory and only needed constraints are added. that is fine. but they are "bad" for users, because it's sometimes pretty confusing. a table view would be smater for a user (but more worse out of coders view). In fact my suggestion is to totally redesign that teachers and students constraints view windows; more like a classic database. but i sadly don't have enough time to code that. so i fear it will take some time until we get a new design.
one guy already started that. please view:
http://mieszkowski.eu/genfet/
i am not sure when we will start redesigning that. it is much work and there are still a lot of other TODOs.

Thank you for report.

[Liviu Lalescu]

I was away with no internet. I'll answer soon.

[Liviu Lalescu]

Suggestions:
1) There are many constraints of the type "Max hours daily for all teachers" or "Max hours daily for all students", etc. I think that it would be very useful to have options such as "Default max hours daily for all teachers". For example, a constraint of this type would be like this:
Default max hours daily for all teachers: 5
and would add this constraint to all teachers unless some of them are given individually the constraint "Max hours daily for a teacher". So, all teachers who are not given the constraint "Max hours daily for a teacher" would have the maximum of 5 hours daily.

In FET, all constraints are respected. You can add more constraints to a teacher, and the stronger one wins. This is not pleasant for min hours daily, but is convenient for max hours constraints. I know it is not the best approach.

2) I think that adding the constraints "Min gaps per week for a teacher/all teachers", "Min gaps per day for a teacher/all teachers" (and why not "default max gaps per week for all teachers" and "default max gaps per day for all teachers") would give more options for a just timetable.

Min gaps per week/day is too difficult for me.

3) When adding activities, and if one has added more than one teachers/students sets/tags for the same activity, it's impossible to remove for example just one of the tags or just one of the teachers. Instead, one has to press the "clear" button, remove all the contains of the specific field and import one by one the information he needs. So, it would be very useful for example to add a "remove" option (for example by pressing the right button of the mouse) exactly on the selected (specific) information (for example: tag) that needs to be removed.

This was answered by Volker.

4) When adding an activity (which is split in 2 days or more), I think that there should be more options for defining more exactly the "distance" between each one of the "splits" (actually between each one of the sub-activities). So, I think one more option should be added. The option "min days" with its weight is OK. I suggest that if the weight here is not 100% (for example if it is 95%), an additional option of defining the actual min days (with a 100% weight) would be very useful. For example: An activity is split in 3 parts (sub-activities) per week (a five-day week). If we give
min days = 2, weight 100%,
the algorithm will result in a timetable with this activity placed on Monday, Wednesday and Friday. If we give min days = 2, weight 95%,
the algorithm might place the activities for example on Monday, Wednesday and Thursday, or the 1st sub-activity on Monday, and the 2nd and 3rd in the same day (Wednesday). If there is the additional option for defining the actual min days between the activities (with a 100% weight), the algorithm would give different results. For example, if we give
min days = 2 weight 95% AND
min days = 1 weight 100%,
the algorithm should never give the result with the sub-activities places on Monday (the 1st sub-activity) and Wednesday (the 2nd and 3rd sub-activities).

After adding all the activities, please see the "Spread activities evenly over the week" option.

5) In the same window (adding an activity), I think that the additional option of defining if a sub-activity (with 2 hours duration for example) should be with the two hours consecutive or not, would be really useful.
Thanks a lot!

You could divide into more components and take care of the min days between activities constraints.