On our to-do list, which didn't get done, was a spark StatusIndicator. The StatusIndicator is a skinnable component used to show one of three statuses:
* Busy * Non-Busy * Error This is an extension of the BusyIndicator on mobile which is not skinnable. This component could be used to show the status of loading data. The developer would set the status to "busy" when loading the data is loading. When the date is loaded, the status would be set to "non-busy". If there was an error loading the data the status would be set "error". The error status could be set in the component and used as a tooltip on the error icon. Carol On 3/8/12 8 :59AM, "Tink" <f...@tink.ws> wrote: >In a way I agree, although it doesn't fit the spark skinning model and >therefore its difficult to change the look and feel. I think we could >come up with something better. > >Tink > >Duane Nickull <du...@uberity.com> wrote: > >>Justin: >> >>As usual, your proposals are clearly logical and make sense. >> >>+1 >> >>If anyone can think of a single reason why not, please speak now (and be >>concise) or please consent by silence. >> >>Synopsis: >> >>The Busy indicator is current bundled to be with the mobile SWC. A lot >>of >>end users like to have consistency across bot mobile and desktop >>experiences. The busy cursor is a brilliant feedback mechanism that >>tells >>users "something is happening" rather than "I hit a button and I am not >>sure what is happening". >> >>Work required would be minimal in my estimation (see Justin's notes >>below). >> >>It makes sense, serves the populace. >> >>Duane >>---------------- >>President/COO Überity Technology Corporation >>Adobe LiveCycle ES & Enterprise Specialist >>Blog | http://technoracle.blogspot.com >>Twitter | @Uberity @duanechaos >> >> >> >> >> >> >>On 12-03-08 2:47 AM, "Justin Mclean" <jus...@classsoftware.com> wrote: >> >>>Hi, >>> >>>I'm seen a number of Flex desktop applications include the mobile swc >>>just to use the busy indicator component. While Flex desktop application >>>are generally asynchronous in nature there are occasion where it is >>>useful to display a busy indicator. >>> >>>So I like to suggest we move BusyIndicator.as out of the mobile >>>components/project. and into the spark components/project. I believe >>>this >>>change can be made so that no existing code would need to be changed (as >>>the BusyIndicator's package spark.components is still the same) >>> >>>This has come up a few times on various lists and is in the Adobe bug >>>base so I'll not add an apache JIRA entry just yet. >>>https://bugs.adobe.com/jira/browse/SDK-29960 (closed and deferred) >>> >>>Thanks, >>>Justin >> >>
