Howto:Processing legacy PUI dialogs using Canvas: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 23: Line 23:
   |script_version = 0.40  
   |script_version = 0.40  
   }}</ref>
   }}</ref>
Improving the frame-rate and modernised 3D rendering, can’t be worked on until the PUI code, 2D panels and Shiva are removed, but doing so is a frustrating slow path<ref>{{cite web
  |url    =  https://sourceforge.net/p/flightgear/mailman/message/35623408/
  |title  =  <nowiki> Re: [Flightgear-devel] canvas non svg-elements broken </nowiki>
  |author =  <nowiki> James Turner </nowiki>
  |date  =  Jan 24th, 2017
  |added  =  Jan 24th, 2017
  |script_version = 0.40
  }}</ref>
Most people seem to agree PUI needs to be replaced, it sounds as if the fallout from doing so would be more painful (cumulatively) than the pain its existence causes.<ref>{{cite web
  |url    =  https://sourceforge.net/p/flightgear/mailman/message/35623408/
  |title  =  <nowiki> Re: [Flightgear-devel] canvas non svg-elements broken </nowiki>
  |author =  <nowiki> James Turner </nowiki>
  |date  =  Jan 24th, 2017
  |added  =  Jan 24th, 2017
  |script_version = 0.40
  }}</ref>


pui2canvas.nas is a viable replacement - once finished, it will render every existing dialog, not pretty but working - 95% of the pain for maintainers is gone because no immediate action is required, everything still works, PUI can go<ref>{{cite web
pui2canvas.nas is a viable replacement - once finished, it will render every existing dialog, not pretty but working - 95% of the pain for maintainers is gone because no immediate action is required, everything still works, PUI can go<ref>{{cite web

Navigation menu