I don't seen any reason to hold it back.  My only question would be for the
submission I made.  I submitted two methods for doing modal dialogs:
gnoga.gui.modal_dialog and gnoga.gui.view.modal_dialog.  It probably isn't
good to have both methods as it might be confusing.  Should we axe one?  I
was hoping people would have a chance to use it and provide feedback on
which method they prefer

Either way, I think it is stable enough for beta

On Wed, Jul 31, 2019 at 10:24 PM Pascal via Gnoga-list <
gnoga-list@lists.sourceforge.net> wrote:

> Hello,
>
> Up to now here is the list of new features of GNOGA V1.5 alpha (versus
> 1.4):
> - Update Jeff Carter's Pragmarc and demos from Github
> - Upgrade to Simple Components 4.40
> - Canvas: add additional binding to drawImage
> - PIXI.Sprite: recursive rendering of sprite's children.
> - PIXI.Sprite: modification for finalizing children
> - Add log of user agent and platform client browser in case of suspicious
> connections
> - Make favicon customization available by the application.
> - Add an exception handler when a requested file is non existent on the
> server side
> - Support multi-part bodies for POST forms
> - Add Profile build mode and tidy some GPR project files.
> - Fix POST UTF-8 key, UTF-8 to Latin-1 translation, UTF8 incoming message.
> - Console_IO: improve responsiveness of Get_Line
> - Canvas_2D: add Polygon_To; Plotting_2D: use Polygon_To
>
> There are available on Gnoga SF repo:
> https://sourceforge.net/p/gnoga/code/ci/dev_1.5/tree/
>
> I propose to move in beta status for more testing unless you propose some
> additional features to add.
> What is your feedback?
>
> Thanks, Pascal.
> http://blady.pagesperso-orange.fr
>
>
>
>
> _______________________________________________
> Gnoga-list mailing list
> Gnoga-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gnoga-list
>
_______________________________________________
Gnoga-list mailing list
Gnoga-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gnoga-list

Reply via email to