Natural way to develop UI

| | Comments (0) | TrackBacks (0)

As a part of "too late" discussion Ed Merks pointed to Intentional UI Modeling approach from Jim van Dam's EclipseCon 2008 talk. Ed named it compelling, and I'd like to add: it is not only compelling, it's natural aproach to UI development and similar to JavaFX/UI. The devil of course in details...

Important detail is how we will transform higher level UI abstractrions into a final representation. Atomic block in "old UI" composition is a widget. Atomic block in JavaFX/WPF is a 2D graphic primitive. These technologies treat Classical Widget as a composite of lower-level primitives, and these primitives available on every platform (which is not true for Widget-based approach) - just to support Jim van Dam's run everywhere point. This is not conceptual shift, but

  • Few years ago we were not able to develop such UIs due to CPU/GPU performance limitations (and this was the main reason why SWT was born).
  • Now, scaling down to lower-level primitives gives new very attractive possibilities like: run everywhere (if something can provide adequate CPU/GPU power and runtime), clean separation of UI represenation and UI logic (we may expect designers working on desktop designs in the near future like we see in Web design market), flexible UI customization at run time and at any level (in WPF I can override Button look-and-feel for example adding rotate and scale transorm, adding few lines around caption, etc... I can completely replace look-and-feel of my button at application or window level - and all these will be vector graphics - just forget about pixels)! This is also very attractive from UI components reusing and representation inheritance standpoints, etc. Of course there are much more benefits we can figure out...

So regarding buzz - I do not think this is a buzz, but natural evolution of UI started with SVG and Flash; higher-level technologies like Flex; and continued with JavaFX/WPF. It is constantly running evolution during last years, and finally we have these technologies ready for end-users, and end-users have PCs powerful enough to run such UIs. So there is a trend to decomposite UI down to 2D (3D? :)) primitives. And such decomposition rules will be fully controled/defined by application, which is contrary to original SWT idea and goal.

0 TrackBacks

Listed below are links to blogs that reference this entry: Natural way to develop UI.

TrackBack URL for this entry: http://blogs.xored.com/mt-tb.cgi/8

Leave a comment

About this Entry

This page contains a single entry by Andrey Platov published on April 13, 2008 6:41 PM.

Is E4 overfocusing on Declarative UI and Scripting? was the previous entry in this blog.

Looking at WPF and JavaFX, thinking on SWT is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.