Re: Gnoga current status

[Olivier Henley <olivier.henley@gmail.com>]

On Thursday, July 7, 2016 at 9:02:10 AM UTC-4, tonyg wrote:
> I'm having real problems finding an editor with all the buttons / selection boxes etc 
> 
> Do I need the editor to be using the same javascript being used for Gnoga, I am using  boot.js and jquerymin.js in my gnoga project/js directory?

1. For the editor part, check into Maqetta. To give you an idea of the depth of this editor listen to this: https://www.youtube.com/watch?v=J0LneuYl280&list=PL821DA1C6573FC973

2. You do not need/nor want the editor to use boot.js. The editor should only be used to "build your graphical components". Once you are done with those (you will get html and ccs code), you are left with two choices, or a combination of these choices:

a. You c&p those html and css snippets into boot.html and app.css (the css file that you link in the boot.html of your app) These will be served at page request, static.
b. You make Gnoga code to generate those html/css structures; code that is injected into the DOM when you need it.


IMO, the faster way and cleaner way to work is to first define the static and dynamic parts of your application. E.g, Your app logo placement, the navigation toolbar, the overall structure of the app etc should be STATIC and therefore can be just served in your boot.html file. Second all the widgets that will be created by users interactions, e.g new blog posts should be transformed into 'Gnoga code' for proper DYNAMIC creation/destruction.