Ken Ferguson wrote: > So, in regards to the back button I've been thinking that a really > quality, well-done web2-type application would be one where your back > button wouldn't work, but one where you'd also not ever think of using > it. I mean, the application should flow such that the back button > doesn't really mean anything.
Checking: The document browser's 'Back' button should still take you back to the previous document, right? For handling application state, something like an accordion control is useful... there's really no "undo" (or "back") because everything remains inspectable, editable, reversible. (For other types of application interfaces, a History structure or "Undo" button might make sense.) Brendan Baldwin wrote, in part: > IMHO Flex is not about pushing that vision at all. Flex is just Macromedia > trying to leverage ColdFusion to promote the adoption of Flash as an > application platform, essentially reducing the "webbiness" of the web by > closing the standards discussion for web resources as usable, mungible > things. .... "mungible"... I like that one... "webbiness of the web" comes close, though.... ;-) It would go uselessly off-topic to counter each assertion. ColdFusion successfully showed how to efficiently handle server-side processing. Flex handles the presentation layer, with similar efficiencies. (You could view PHP-coding vs CF as JS-coding vs Flex, if you'd like.) Interfaces need to be less hardwired, more approachable... I hope everyone could agree on this part...? The JavaScript-supremacist crowd will have to develop against, maintain against, and support each of the various branded renderers out there (the "MSIE" brand, the "FF/Win" brand, the "FF/Mac" brand and so on). The features they offer will be bound by the intersection of what their audience's browsers will support. This is slow progress. The Adobe Flash Player is *part* of all these browsers, by taking advantage of the browsers' established extension mechanisms. Because it's a single engine you'll see new features faster; because it's an inclusive engine you'll see wider audience faster. Webwork is indeed moving on, I agree with you there. I don't think that evolution is only in serverside technology, however... I think it's more about making servers and clients work together more smoothly, with greater expressive abilities, and in more environments. The revolution will not occur *only* on the server, imho. jd -- John Dowdell . Adobe Developer Support . San Francisco CA USA Weblog: http://weblogs.macromedia.com/jd Aggregator: http://weblogs.macromedia.com/mxna Technotes: http://www.macromedia.com/support/ Spam killed my private email -- public record is best, thanks. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:240600 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
