Alright Paul, let's talk about assuming that the best way is YOUR way. Without knowing the actual use case, comments like "bad design", "accomplice", and "horrors" are a bit arrogant, when it comes to helping someone solve a problem. Javier didn't ask, "What would be the best design choice?". He asked, "Can someone help me?". Without more information, criticism is pointless. There may be a very good reason for developing a solution that uses a TabNavigator this way. When you judge people without knowing all of the facts, you better not live in a glass house.
By the way, isn't an accordion just a view stack with buttons; in a slightly different visual representation than a TabNavigator? So, it's OK one way, in a perfect design theory oriented approach, but not the other? Not so impressed with the quality of response. When you berate someone for asking a perfectly good question, it serves no-one. Anyway, not trying to make you into an enemy, but compassion is one of the true indicators that we are more than just animals. End of sermon. :) -TH --- In flexcoders@yahoogroups.com, "Paul Andrews" <[EMAIL PROTECTED]> wrote: > > Ultimately what determines if it is a good design is whether it works for > the user rather than confuses them. People looking at tabs expect to be able > to click on them. > > I've been quite critical of the notion of forcing people through the tabs > because it's breaking the tab metaphor. Personally I think that if you are > going to use tabs to capture this information, you should let people fill in > the tabs in the order they want and have a final 'submit' type control > (outside the tabs) that only gets enabled when all of the requisite data has > been set (perhaps an indicator on the tab to show which have been > completed). I have great difficullty understanding how you can adopt a tab > metaphor and force navigation through it with buttons and expect the user to > understand it. If you have to do this kind of behaviour use a viewstack and > use the buttons to move through that. > > You've already mentioned using an accordion and that can work well. I wonder > if the OP has considered using that? > > Paul > ----- Original Message ----- > From: "Tim Hoff" <[EMAIL PROTECTED]> > To: <flexcoders@yahoogroups.com> > Sent: Tuesday, September 19, 2006 12:47 AM > Subject: [flexcoders] Re: How can I block a TabNavigator ? > > > > It's only bad design if it doesn't solve the individual use case. > > It's possible that Javier wants the same functionality as a self- > > guilded checkout, that uses an accordion control, but only allows > > the user to proceed to the next step after the current step has been > > successfully completed. If that's the case Deepa, your earlier > > solution would fit the bill. > > > > -TH > > > > --- In flexcoders@yahoogroups.com, "Deepa Subramaniam" > > <dsubrama@> wrote: > >> > >> Yes, I agree, its bad design. The benefits of exposing tabs for > > browsing > >> and then disabling them and forcing the user to follow some other > > route > >> to navigate through the container makes no sense to me but I was > > just > >> answering the poster's initial question :-) > >> > >> > >> > >> ________________________________ > >> > >> From: flexcoders@yahoogroups.com > > [mailto:[EMAIL PROTECTED] On > >> Behalf Of Paul Andrews > >> Sent: Monday, September 18, 2006 12:45 PM > >> To: flexcoders@yahoogroups.com > >> Subject: Re: [flexcoders] How can I block a TabNavigator ? > >> > >> > >> > >> ----- Original Message ----- > >> From: "Deepa Subramaniam" <dsubrama@ > >> <mailto:dsubrama%40adobe.com> > > >> To: <flexcoders@yahoogroups.com <mailto:flexcoders% > > 40yahoogroups.com> > > >> Sent: Monday, September 18, 2006 6:52 PM > >> Subject: RE: [flexcoders] How can I block a TabNavigator ? > >> > >> > What you can do is iterate through the TabNavigator's tabs and > > disable > >> > each of them. By disabling them, the change event will not get > >> emitted. > >> > Use TabNavigator.getTabAt() and set the enabled property to > > false for > >> > each Tab. > >> > > >> > Now, when you disable a Tab, the Tab will assume the look of its > >> > disabled state (grayed out, etc). You probably want the Tab to > > look > >> > enabled even if it is disabled - in which case you'll have to > > change > >> the > >> > Tab's disabledSkin. > >> > > >> > HTH - > >> > deepa > >> > >> Horrors. It's really good making the user think (s)he can navigate > > the > >> tabs, > >> then discover they can't. Is this really good practice? > >> Even with the disabled tabs - hey I completed the info, now it's > > become > >> invalid.. > >> > >> Paul > >> > > > > > > > > > > > > > > > > -- > > Flexcoders Mailing List > > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > > Search Archives: http://www.mail-archive.com/flexcoders% 40yahoogroups.com > > Yahoo! Groups Links > > > > > > > > > > > > > > > > > > > > > > > -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/flexcoders/join (Yahoo! ID required) <*> To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
