I wonder how a 'designer' works when you might have so many possible screen 
dimensions?

It always irked me that so many dialogue boxes were hard-wired to 640x480 (or 
smaller), because that ensured they would always fit.  Same thing with having 
to 2x iPhone apps for the iPad.

It seems to me with a procedural (or declarative, i.e., LZX) UI, you are more 
future proof.  You think about your UI in vectors and percentages, not in 
pixels.

Another box that 'designer's force you into is that your 'actions' are 
predicate on location not content.  The designer ends up associating gestures 
and actions with a location on the screen, rather than the content of that 
location (contrast with "data detectors" and "smart objects").

Something that I'd like to do with LZX is generalize the presentation-type 
system, so that you can associate actions with types.  Think of it this way:  
in the debugger, every representation that has an underlying object is 
inspectable.  It's like we've said that there is a general action (inspect) on 
the type Object, invoked by the gesture click-left.  You could have more 
specific actions:  for instance, I might write an "inspectColor" action that 
displays a color in a color-picker style and make the association click-left on 
Color -> inspectColor.  The system should choose the 'most applicable' action 
when I make an overloaded gesture (you could present the overridden actions in 
the click-right menu).

Ok, I strayed way off topic...  it's a dream I have.

On 2010-06-21, at 11:00, Sarah Allen wrote:

> I saw a presentation on this last week.  It runs on Android and iPhone for 
> mobile.  It's a very procedural approach.  They have a designer app for Ext 
> JS, but it doesn't seem to have been updated for mobile and either the app is 
> really flakey or I haven't figured out how to use it in 5 mins :)
> 
> Having jQTouch run on Android is pretty compelling for mobile developers.  
> Apparently developers are seeing incompatibility in webkit versions across 
> Android devices.  I've only done Android on my Nexus One and not any fancy 
> apps, so I haven't seen that personally.
> 
> My $.02
> Sarah
> 
> On Jun 21, 2010, at 7:45 AM, P T Withington wrote:
> 
>> Ext JS + jQTouch + Raphaël = Sencha — Sencha Blog — JavaScript Framework and 
>> RIA Platform http://bit.ly/acgHmO
>> Source: http://www.sencha.com/blog/2010/06/14/ext-js-jqtouch-raphael-sencha/
>> See who is talking about this page: http://bit.ly/acgHmO+
>> Brought to you via http://bit.ly
> 
> 


Reply via email to