TEACHERS NAMES & CODES

[Liviu Lalescu]

This will be easy and we'll try to do it. There will be 4 fields in a teacher:

- Name (short name), unique and nonempty, used as an ID.

- Long name (in the future).

- Code (in the future).

- Comments (already existing).

All these will be strings. Are they enough for your necessities? We could add one of them in the header for teachers' timetables, and I am thinking of the comments. It will be an option with a check box. OK?

[Cyrus Ireri]

From your options,i i want teacher 1 to be in science department,teacher 2 humanity department where shall i indicate their offices?

[Liviu Lalescu]

I think the best is in the Comments, and the teachers' timetables days horizontal/vertical will contain for each teacher the comments as the table heading.

[Cyrus Ireri]

Thats fine

[Cyrus Ireri]

Encouraged by my mother to try it, and by a nice idea of simplifying things by Volker, I began something. It might work, and it might be made much faster than I thought. I'll let you know.

The interface will have mostly only the short names, but internally FET will also contain long names and codes, and I intend to make these selectable in the HTML timetables, I mean which one to print in which timetable.

We should expect something nice soon?

[Liviu Lalescu]

I hope. I did the long name and code internally and modifiable in the interface for everything needed. Now a big work is making the HTML timetables, which is more Volker's code and I am not sure he can work very fast now. I will try to present working snapshots soon.

[Cyrus Ireri]

I can't wait for this.It will be great

[Liviu Lalescu]

Me too!

It was a good suggestion.

[Liviu Lalescu]

Hello, Cyrus! I hope I have good news: the main parts seem to work. I need a bit more work to finish it up, and testing a bit, and then I'll be able to put a snapshot.

It was much easier than I thought.

[Liviu Lalescu]

I must apologize for hugely overestimating the needed work time. But with Volker's advice and some tricks it was possible fast.

It is not ready yet, we need now to add the optional comments as table heading in each days horizontal/vertical timetables and the options about the hours'/days' names. But the main part is done.

[Cyrus Ireri]

Hello, Cyrus! I hope I have good news: the main parts seem to work. I need a bit more work to finish it up, and testing a bit, and then I'll be able to put a snapshot.

It was much easier than I thought.

Keep the good news coming.We are chilling to enjoy the upgrade

[Cyrus Ireri]

I must apologize for hugely overestimating the needed work time. But with Volker's advice and some tricks it was possible fast.

It is not ready yet, we need now to add the optional comments as table heading in each days horizontal/vertical timetables and the options about the hours'/days' names. But the main part is done.

Thats quite commendable👌

[Volker Dirr]

Well, it was only fast, since we (or better you) didn't change the GUI. That is still old (short) only; but I think that is very fine. We changed only html-timetables and print; so tables that are for other users. So for example also not the statistics, but I think that is also fine)
And also because you are working without a break. Other guys work only max. 10 hours per day. I hope a few guys will donate for this work.

[Cyrus Ireri]

Well, it was only fast, since we (or better you) didn't change the GUI. That is still old (short) only; but I think that is very fine. We changed only html-timetables and print; so tables that are for other users. So for example also not the statistics, but I think that is also fine)
And also because you are working without a break. Other guys work only max. 10 hours per day. I hope a few guys will donate for this work.

We shall come in handy

[Liviu Lalescu]

Hello, Cyrus, Volker, and users,

It is ready! I just released a snapshot: https://lalescu.ro/liviu/fet/download/test/

It implements the suggested options. Please test. I might release on 17 June the final version.

Thank you, Cyrus, for the good suggestions!