Re: Impressions of EGL - Part Duex

In the example of the radio group, I embedded the style and JavaScript elements in the page so folks could understand my thought process, and so we could compare with an EGL equivalent. Perhaps Joe will step in and create an EGL equivalent, since it's pretty trivial, and he was the first to mention how easy it is to handle radio groups in EGL.

I inserted a radio group on the page using point and click methods, and filled in the property sheet prompts for button labels and values.

The idea of a visual image of a Dog, Cat, Bird, and Iquana struck me, to emphasize the choice. Then came the idea of placing the four radio buttons on each corner of a box, with an image in the middle.

I inserted the table using point and click methods, then switched to code view and cut and pasted the radio buttons into table cells and played with the formatting, a little.

From that point on, I worked in code view. Dreamweaver supports writing HTML and style elements via intellisense prompting, and supports JavaScript with automatic code coloring. On-line help is packaged.

I normally prototype an application fairly completely with HTML, style, and JavaScript elements. Then later write server code for DB I/O and UI support.

For comparison purposes, I think it would be good to store the user's radio button choice in a table and show the stored choice when the page is initially requested. And update the database when a new choice is selected. And display an applicable completion message. Ajax could help with this.

To stress test the server request & response cycle we could press and hold down an arrow key to select each button and fire the onClick event VERY rapidly in succession.

We compare UI code, server code, development approach, and performance. Sound good?