Brian_Farn's Profile

  • Name: Brian Farn
  • Email: (Private)
  • Member Since: Apr 8, 2009
  • Last Logged In: Jul 2, 2009 7:00 AM
  • Status Level:  
  • Location: Markham, Ontario, Canada
  • Occupation: Software Developer
  • Expertise: Visual Editors for Programming Languages

Brian_Farn's Latest Content

The way a web browser arranges artifacts on a web page is sometimes confusing. By default, a web page arranges its artifacts in a top-down, left to right order. This is also true of EGL Rich UI widgets. Fortunately, EGL gives you an easily understood layout container widget, in the form of a Box widget, which arranges its child widgets in rows and columns. Boxes may also contain other Boxes as children. When Boxes are used, a web page consists of a hierarchy, or tree of EGL widgets.

This becomes apparent as you decide to move an existing widget to another location by dragging the widget in the Design page. When you begin to drag, a set of colored indicators (yellow by default) appear, where each indicator denotes a potential drop location. As you drag your mouse close to one of these potential drop indicators, the indicator will change color (to green by default) which indicates where the widget will be placed if the mouse is released. The term "placed" needs to be clarified. Since widgets exist in a hierarchy, potential drop indicators reflect a new hierarchical location, and not necessarily a physical location. To help you in visualizing the new widget location in the hierarchy, as the widget is dragged over a potential drop indicator, a small diagram of your EGL widget hierarchy appears. This diagram displays where in the hierarchy your widget will be placed when you release the mouse button.

In the image below, the Configure button is being dragged to a new location between the MyTextLabel label and the MyTextField field. The hierarchy diagram displays where the Configure button is currently located as indicated with the dotted rectangle, and its new location as indicated by the green line. The color of the line matches the color of the potential drop indicator in the design area. Indicator colors are configurable in the tool's preference page. Potential drop indicators that are dotted on one side represent a location that is either before or after a Box. The large rectangular area at the bottom represents the area below all other widgets.


movingwidget.gif

Widgets, whose positions are set to either absolute or relative, have positions that are independent of the widget hierarchy. When these widgets are dragged to a new position, the potential drop indicators and hierarchy diagram do not appear, and the widget's x and y attributes are set to new values when the widget is dropped.

After moving widgets, you can view what changes were made in your EGL source code.

0 Comments Permalink

In an article that Joe Pluta wrote entitled "Welcome to the New RDi-SOA", he talks at length about the EGL Rich UI editor and states that "The WYSIWYG designer is the only one of its kind". As the user interface designer and developer of the first version of this editor, my primary consideration was to maximize the tool's visual accuracy, so that you the designer will have the most real and accurate representation of your web page. As Joe has stated, its because of its "what you see is what you get" ability that gives this tool an edge.

When you use the EGL Rich UI editor for the first time, you will notice that the editor has the usual Design page for arranging EGL widgets in a web page, a Source page for viewing and modifying your EGL code, and a Preview page for seeing what the web page will look like and how well your EGL code responds to some user interface events.

When using the Design page, the web page that you are working on always reflects what the web page will initially look like when your application is run. Not only does this include the layout arrangment of EGL widgets, but also the web page's associated style sheet contributions. In fact, due to the way the Design page was architected, it will always do so even as web standards such as HTML and CSS are enhanced. You will always know whether visual changes that you made to your EGL code has the expected result, reducing the need to refer to the Preview page.

designer.gif

The EGL Rich UI editor was architected with a unique Design page that does not simulate the visual content of a web browser and its constantly changing standards, but instead always shows what the web page actually looks like. Combined with its Preview page, and a Source page for those who enjoy specifying concise EGL code, this one tool gives you the flexibility of a few useful working modes to help you craft your EGL Rich UI applications.

Stay tuned for a future post, in which I will describe how to visually arrange widgets on your web page.

1 Comments Permalink

Write your own drafts, invite selected collaborators, or leave it open for all to pitch in.

Brian_Farn's Blogs

Brian_Farn's Commonly Used Tags