I have been thinking about this a bit over the last couple of days. Although I think that, in general, a spreadsheet is not a good way to present the output from FET (why would you want to do this?), I did have some code for reading FET results lying around. Adding a bit of code to produce spreadsheets should not be too difficult, I thought ...
Well, a quick search of the forum brought up a few posts from the past, and it seems that there are at least two reasons for wanting Excel files:
1) To print the results in some sort of customized way.
2) Because some other administrative software accepts only Excel files.
Both of these will probably require tables structured in very particular ways, and be very dependent on the nature of the timetable data. They seem very fragile, in the sense that a different set of input data could break the layout assumptions. Each institution might need its own customized version of the converter. That is not an encouraging basis for a developer to work on.
There are certainly better solutions for printing – all the data is available in the XML, so why convert it to Excel before working on it? I have done some work on printing timetables. Because of the extreme flexibility of FET, it is very difficult (impossible?) to find a layout/structure which will satisfy all requirements, in general. If certain limits can be imposed on the data, quite nice results can be obtained – I have had some success with Typst, but it requires quite a lot of programming.
For providing input to other software, it would certainly be better to consult with the designers of that software, in the hope of getting them to provide a better input interface! Of course, that is not always possible ...
Anyway, for anyone who really wants Excel documents, I have put up a little "proof of concept" at fet2xlsx. It should work roughly like FETtoExcelExporter, but it uses different input files (the "..._data_and_timetable.fet" ones) and is cross-platform. I have posted runnable files for Windows and Linux.
Well, a quick search of the forum brought up a few posts from the past, and it seems that there are at least two reasons for wanting Excel files:
1) To print the results in some sort of customized way.
2) Because some other administrative software accepts only Excel files.
Both of these will probably require tables structured in very particular ways, and be very dependent on the nature of the timetable data. They seem very fragile, in the sense that a different set of input data could break the layout assumptions. Each institution might need its own customized version of the converter. That is not an encouraging basis for a developer to work on.
There are certainly better solutions for printing – all the data is available in the XML, so why convert it to Excel before working on it? I have done some work on printing timetables. Because of the extreme flexibility of FET, it is very difficult (impossible?) to find a layout/structure which will satisfy all requirements, in general. If certain limits can be imposed on the data, quite nice results can be obtained – I have had some success with Typst, but it requires quite a lot of programming.
For providing input to other software, it would certainly be better to consult with the designers of that software, in the hope of getting them to provide a better input interface! Of course, that is not always possible ...
Anyway, for anyone who really wants Excel documents, I have put up a little "proof of concept" at fet2xlsx. It should work roughly like FETtoExcelExporter, but it uses different input files (the "..._data_and_timetable.fet" ones) and is cross-platform. I have posted runnable files for Windows and Linux.