Hey, sorry for not pointing you in the right direction, that was kinda douche-like of me :)
Here's where you want to be: https://bugs.adobe.com/flex/ You can file bug reports and change requests, and vote on things that other people have reported as well. If you want to mess with the focusing, I'd say the place to jump in is mx.managers.FocusManager. Find out where it's being used, if you can subclass it and replace the base FocusManager for your Application, or something else along those lines. -Josh On Wed, Sep 17, 2008 at 12:40 PM, aceoohay <[EMAIL PROTECTED]> wrote: > Josh: > > In my original post, I asked "how I can get this in front of someone > who could make it hap(p)en." Alex could have easily pointed me to the > url that I could use to post it as a feature request (which I still > don't have). > > Alex has helped me in the past, but on two occassions, I have pointed > out what I consider behavior that if given the opportunity to enhance > I would (one is a flat out bug), and I laid out what I felt was a > strong case to have the change made. On neither occassion was I > pointed to a more appropriate place to make these requests, and I > felt my request was brushed aside without much thought. > > I am not sure why you take offense to the expression "run it up the > flag pole," where I come from it means to "air it out", basically let > some other folks look at it, and see if it generates any interest. > While not uplifting it certainly was not meant as a perjorative. > > Why do I feel strongly about having developer definable tab loop > regions? We are developing quite a number of modules that can be > brought onto the stage by the user in any combination. Each module > has its own separate and distinct purpose such as a table > maintenance, or business process function, etc. When the user is > doing one of these functions tabbing outside of the module makes for > a very confusing experience. > > What I believe would be useful is the ability to define a tab loop > region at a container level such as a Panel, or Canvas that will > preclude tabbing out of that region while allowing tabbing to all > objects in the container and its children. > > Instead of considering the flash player stage a single window, > consider it a container that holds many little windows. In one little > window you might have a vendor table maintenance open, in another you > might have order entry, in another shipping, etc. We are trying to > effectively use the flash player as a mini OS where the user can run > multiple "programs" simultaneously. These program interact with one > another in a collaborative manner, but are distinct entities. You > wouldn't want the user tabbing out of one "program" into another > would you? > > If you consider Windows (or linux) just another stage, analagous to > the Flash Player you can see the functionality in action, just bring > up any two applications, and set focus to one application, and use > the tab key. It will not jump to the other application. I am not > suggesting changing the default behavior BTW, just adding > functionality. > > I do appreciate Alex's help. This may be the wrong place to discuss > enhancements, but I hate being brushed off, hence my temper tantrum. > I apologize for any ill will that may have been created. > > BTW, I do not fear changing how flex works, but again, I need a > starting point, if you would kindly point the way I will look into > it. Don't need a detailed map, just a starting point. > > Paul > > > --- In flexcoders@yahoogroups.com, "Josh McDonald" <[EMAIL PROTECTED]> wrote: > > > > Aw cummon, don't say things like "run it up the flagpole" dude, > that's > > painful. > > > > If you think it should change, file a feature request and ask > people who > > agree with you to vote on it. We have a system for this sort of > thing and > > it's not "get cranky with people from Adobe who're helping us all > out on the > > mailing list". > > > > As for the tabbing thing, that would annoy the *hell* out of me if > I were > > trying to use an app. I don't know what "standard" you're seeing > where you > > can only tab between controls within one section of a window, but > doesn't > > sound pleasant to me. You're perfectly free to write some funky tab > code > > that does what you want, and offer it up for anybody else who wants > the same > > thing. If Flex is keeping popups out of the tab loop, that means > the tabbing > > code is in Flex (not Player) and you can change it how you please > and offer > > a patch on Adobe's Jira (ie, run it up your own flagpole), or hook > into > > whatever mx_internal voodoo it's probably using and simply have it > as a > > library. > > > > Cheers, > > -Josh > > > > On Wed, Sep 17, 2008 at 11:04 AM, aceoohay <[EMAIL PROTECTED]> wrote: > > > > > Alex: > > > > > > How does this work against accessibility rules? > > > > > > First, I am suggesting something that enhances flexibility while > > > leaving the default behavior alone. Second, the current default > > > behavior irrespective of accessibility rules is counter intuitive. > > > > > > Over time I have made two suggestions regarding how Flex should > > > behave, both of which would make Flex a substantially better > product > > > and in both cases you shot them down because you "won't have > time." > > > Neither of the suggestions are difficult to implement, and both > would > > > provide more control for folks who want to make real business > > > applications. > > > > > > The two suggestions are; > > > > > > 1) Fix the bug that causes dataGrid sorting to ralph on it's shoes > > > when a date or number column has a null value in a cell. In this > case > > > I suggested that a "data type" be definable for colums in a > dataGrid > > > and null's be handled predictably (either sort high or low). > > > > > > 2) Fix the bug where tabbing through objects is counter intuitive > and > > > behaves irrationally. Here I suggest that a tab loop "Region" be > > > definable at a container level. > > > > > > In both cases the "workarounds" are cumbersome and make the > resultant > > > code look like a 2nd year programmer's hack job. I would think > that > > > Adobe would want a product that attracts business application > > > developers, not just web designers. When Adobe's folks (I assume > that > > > you are a member of this group) refuse to even look at changes > that > > > would make it easier for someone doing this kind of development to > > > make professional looking applications, it makes looking into > > > Silverlight ever so much more attractive. If Microsoft won't pay > > > attention at least you can blame it on them being so big. > > > > > > Why don't you run it up the flag pole, take a look at how much > time > > > it would actually take to implement, and see if anyone else would > > > find it a useful feature befor dismissing it out of hand. > > > > > > Paul > > > > > > --- In flexcoders@yahoogroups.com, Alex Harui <aharui@> wrote: > > > > > > > > No advantages using non-modal popups, just a way to get what you > > > want. I doubt we'll have time to provide more control over > tabbing, > > > especially in a way that sort of works against accessibility > rules. > > > > > > > > If you are using ModuleLoader today, you can probably pass the > > > ModuleLoader to PopUpManager. There'll probably be some other > stuff > > > that needs to be fixed up, but that's what I'd try first. > > > > > > > > From: flexcoders@yahoogroups.com > > > [mailto:[EMAIL PROTECTED] On Behalf Of aceoohay > > > > Sent: Tuesday, September 16, 2008 12:13 PM > > > > To: flexcoders@yahoogroups.com > > > > Subject: [flexcoders] Re: Flex Enhancement, TabIndex > > > > > > > > > > > > Alex: > > > > > > > > I am not sure precisely how to do what you are suggesting. > > > > > > > > What I currently do is to create modules for each panel, and use > > > > moduleloader to add them to the stage. Are you suggesting that > > > > instead I use PopUpManager instead of moduleLoader? > > > > > > > > For my existing application it seems like a lot of work, and > just > > > > investigating the ramifications regarding intermodule > communications > > > > and so on may be challenging. > > > > > > > > Are there any benefits/drawbacks of using non modal popups vs > module > > > > loader other than the tab loop? > > > > > > > > Paul > > > > > > > > --- In flexcoders@yahoogroups.com<mailto:flexcoders% <flexcoders%25> > <flexcoders%25> > > > 40yahoogroups.com>, Alex Harui <aharui@> wrote: > > > > > > > > > > Why not just tile the application with non-modal popups? > Wouldn't > > > > that get you what you want? > > > > > > > > > > From: flexcoders@yahoogroups.com<mailto:flexcoders%<flexcoders%25> > <flexcoders%25> > > > 40yahoogroups.com> > > > > [mailto:flexcoders@yahoogroups.com<mailto:flexcoders%<flexcoders%25> > <flexcoders%25> > > > 40yahoogroups.com>] On Behalf Of aceoohay > > > > > Sent: Tuesday, September 16, 2008 6:26 AM > > > > > To: flexcoders@yahoogroups.com<mailto:flexcoders% > > > > > <flexcoders%25><flexcoders% > 25> > > > 40yahoogroups.com> > > > > > Subject: [flexcoders] Flex Enhancement, TabIndex > > > > > > > > > > > > > > > We write Client Server replacement applications using Flex. > One > > > > > thing that is problematic is the handling of tabIndexing using > > > > Flex. > > > > > The problem; > > > > > > > > > > Flex use a Tab Loop for the entire application except popups. > This > > > > > means if you are in panel A, reach the end using tab, it will > move > > > > > to panel B, or elsewhere in your application. This is not the > same > > > > > behavior that standard Client Server applications exhibit, > and is > > > > > undesireable. Adding tab indexes makes the problem worse > because > > > if > > > > > you have multiple panels with overlapping tab indexes, it will > > > > > bounce back and forth between panels. > > > > > > > > > > A Solution; > > > > > > > > > > On any container object such as panel, canvas, tabnavigator, > hbox, > > > > > vbox, etc. allow a new boolean attribute "tabLoopContainer" > with > > > > > true and false as the allowable values. This would then cause > a > > > > > local tab loop that would encompass only the objects within > that > > > > > container. The default would be false, leaving the behavior > as it > > > > > currently exists. Any object with a separate tab loop would > only > > > be > > > > > accessible by mouse click or programatically via set focus. > > > > > > > > > > I would like some feedback as to whether this seems > reasonable, > > > and > > > > > how I can get this in front of someone who could make it > hapen. > > > > > > > > > > Paul > > > > > > > > > > > > > > > > > > > > > ------------------------------------ > > > > > > -- > > > Flexcoders Mailing List > > > FAQ: > http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > > > Alternative FAQ location: > > > https://share.acrobat.com/adc/document.do?docid=942dbdc8-e469- > 446f-b4cf-1e62079f6847<https://share.acrobat.com/adc/document.do?docid=942dbdc8-e469-446f-b4cf-1e62079f6847> > > > Search Archives: > > > http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! > Groups > > > Links > > > > > > > > > > > > > > > > > > -- > > "Therefore, send not to know For whom the bell tolls. It tolls for > thee." > > > > http://flex.joshmcdonald.info/ > > > > :: Josh 'G-Funk' McDonald > > :: 0437 221 380 :: [EMAIL PROTECTED] > > > > > > ------------------------------------ > > -- > Flexcoders Mailing List > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > Alternative FAQ location: > https://share.acrobat.com/adc/document.do?docid=942dbdc8-e469-446f-b4cf-1e62079f6847 > Search Archives: > http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups > Links > > > > -- "Therefore, send not to know For whom the bell tolls. It tolls for thee." http://flex.joshmcdonald.info/ :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED]
