FET as program library

[gradgrind]

OK, while I'm making suggestions ...

I guess this one might be quite a bit more work (so I could understand you wanting sponsorship for something like this), but I think it might be a good idea for those cold, dark winter days ...

My suggestion is to make a library version of FET, rather like the command-line version, but interfacing via some communication mechanism (callbacks, messaging, whatever, ...). Or it could be an HTML server, using JSON messages for example ...

Anyway, this FET version would create no files, but pass all generated data and progress information back to the client, which could do with it whatever it wanted. Control of the processes, setting of options, etc., would be done by messages from the client.

[Liviu Lalescu]

Dear Michael,

Indeed, lack of financial support is the big problem. Also, I don't have much knowledge with these (I don't even know what "callbacks" mean), but I would be willing to learn and collaborate.

But I will add your words in the TODO list.

[Volker Dirr]

I guess the "best" variant for this is using a REST api. But I fear both (your and also my idea) will be very difficult, since you don't need to write only the api, you also need to care that fet will run all request on the same time. So internally it must be able to generate 2 and more different timetables at the same time. I fear timetabling is much too difficult for this, since it is not a "static" database. The generating part is highly dynamic and all guys want to start and stop their own generating at the same time.