reports_update
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
reports_update [2023/03/02 19:49] – yetidi | reports_update [2023/03/05 19:06] (current) – yetidi | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== reports update ====== | ====== reports update ====== | ||
+ | ===== upd 05-mar-23 ===== | ||
+ | *having working php gbod_report as a pair html + xlsx | ||
+ | *works by 2-3 faster than old c# analog, fixed bug with overlapping preview admissions | ||
+ | *will re-make reports on new engine one-by-one as second fdm instance... | ||
+ | |||
+ | ===== prev comments ===== | ||
+ | |||
I think the database is enough ok for continue; may be some things will be later added to the database, but now it's ok | I think the database is enough ok for continue; may be some things will be later added to the database, but now it's ok | ||
Line 6: | Line 13: | ||
First things which cause troubles -- gbod and dgbos reports | First things which cause troubles -- gbod and dgbos reports | ||
- | HTML version of the gbod report is partially working here -- http:// | + | HTML version of the gbod report is partially working here -- http:// |
- | (here 694 -- id of the film AVATAR 2 in the datavase) | + | (where 694 -- the id of the film AVATAR 2 in the database) |
To generate XLSX files this time I wanna try to use Javascript library being running on the client side. | To generate XLSX files this time I wanna try to use Javascript library being running on the client side. | ||
- | I think this way should leave our server to be highlu loading during reports generation, Also we not sure why bugs coming, may be server | + | Last years users computers became |
+ | Or use another server to generate such reports | ||
So, now our plan the next | So, now our plan the next | ||
*we use PHP instead of c# for updated fdm reports | *we use PHP instead of c# for updated fdm reports | ||
*we use Javascript to generate Excel reports instead of c# NPOI library (which eat a lot of server resources) | *we use Javascript to generate Excel reports instead of c# NPOI library (which eat a lot of server resources) | ||
- | *we leave old database structure | + | *continue to use old database structure |
- | *we leave old c# UI to add / edit data | + | *continue to use old c# UI to add / edit data |
Ok, I think when most reports will look and work ok our next step will be to move to php forms instead of c#, of course in the case if the speed / usability will be better. | Ok, I think when most reports will look and work ok our next step will be to move to php forms instead of c#, of course in the case if the speed / usability will be better. |
reports_update.1677786543.txt.gz · Last modified: 2023/03/02 19:49 by yetidi