Re: Impressions of EGL - Part Duex

I'll look at it. But, I am still learning the UI. It looks like most of the functionality is in the js and css though, so I am not sure how EGL would do this more efficiently. Was this all drag and drop or did you code the js and css by hand (I expect so).

The stuff that has impressed me so far is the "plumbing" that is connecting the page elements to the underlying application code. Particularly the DB. If this example was retrieving the information from a DB, then I might be in a better position to compare. The UI stuff, well, that is the next step for me.

Pete

Nathan Andelin wrote:

Pete Helgren wrote:
My interest is ... to find something I can use efficiently.

Of course. We use tools because they enhance our productivity. How about you taking a stab at duplicating the radio group example by using EGL, so we can compare notes.

http://www.radile.com/rdweb/temp/rg.html

Right click on the page to view the complete source. Right click on the images to download them.

Open the source in a WYSIWYG editor. The editor design view ought to give you a good idea of how I initially envisioned the radio group component to look. Toggle over to source view and read from top to bottom to get a good idea of my thought process as I implemented it. If you don't understand something in the page source, I'd be happy to assist. All basic HTML, CSS, and JavaScript.

It would be interesting to compare my development process to one implemented in EGL, and to compare source code as well.

It would disappoint me if the EGL way of doing it was essentially the same as the way I did it, because we've been led to believe that EGL is more productive.

If it would help, I could interface the page with an RPG program that updates a database table according to changes made on the screen when a radio button is clicked, and visa versa. We could compare that too.

This would give us a chance to see if EGL is more productive, with something fairly trivial.

Nathan.