Differences

This shows you the differences between two versions of the page.

--- reports_update [2023/03/02 19:44] – created yetidi
+++ reports_update [2023/03/05 19:06] (current) – yetidi
@@ Line 1: / Line 1: @@
 ====== 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
@@ Line 6: / Line 13: @@
 First things which cause troubles -- gbod and dgbos reports
-HTML version of the gbod report is partially working here -- http://filmdistributionmanager.com/fdm/index.php/reviewer/gbod_data/694  //
+HTML version of the gbod report is partially working here -- http://filmdistributionmanager.com/fdm/index.php/reviewer/gbod_data/694  \\
-(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.
+Last years users computers became so much powerful so we have an opportunity to leave heavy report generation from our server.
+Or use another server to generate such reports for example using some browser on them (hetzner vps with 4gb ram).
+So, now our plan the next
+  *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)
+  *continue to use old database structure
+  *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.
+To be continued