My experience is still somewhat limited but I'll try to address what you listed, and ask more questions:
On Mon, Jan 26, 2009 at 10:57 AM, Oleh Kovalchuke <[email protected]> wrote: > It is for several different applications. One of them queries and sorts data > in hundreds of thousands of rows and a few dozens of columns. Are you really shipping hundreds of thousands of rows to the client? Are you doing sorts on the client or on the server? Do you have some kind of grouping or pagination UI available for people who see such large result sets? > The immediate concerns I have about building entire application in Flex are: > > - presentation of inline error correction messages; What is your concern here? I've seen several methods for doing this in Flex and all seem as good or better than the traditional Web (HTML/JavaScript) methods. > - writing and editing contextual help messages; Again I'm not understanding what the issue is here. We have two kinds of error messages - one is a type that is fully preloaded into the client and displayed when appropriate. The other is constructed on the fly and may require retrieval from the back end. This is done roughly as one would do an xmlhttp request in a page made with HTML/JS. > - scrolling for dynamic, expandable content (this could be a non-issue); Are you concerned with the speed of scrolling? As in render speed on the browser? We had some issues with this that I can discuss a bit if that's relevant. > - presentation consistency across different development teams (this > includes layout consistency (padding, margins, grids -- Flex CSS should help > here). As with distributed development of a Web site, use of good CSS styles and standardization seems to be the way to go. > - propagation of updates to UI components across application. What sorts of updates do you mean? Do you mean the components changing or data content within a component changing? Or something else? > - will entire application go bust, once new version of Flash player is > released and automatically installed on client's machine (a very plausible > scenario)? Can this mishap be prevented? Yes and no. Since the Flash player is made by Adobe one would expect them not to distribute a player that will immediately break all the existing Flex applications. Of course, problems always happen, but again this seems roughly the same problem as a browser coming out with a new JavaScript engine that breaks your existing JS code. Best regards, --Alan ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [email protected] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
