using plugin variables as sources for other variab

[Wormopolis]

clarification:
Lets say I had an autoform setup.  would it be plausible to link the autoform id, to be the source of a dropdown outside of the autoform?

example: 
lets say I used an autoform to setup a bunch of different kinds of pets.  then in a different autoform, or just outside of the autoform, I had a dropdown that was populated with a list of one of the autoforms members.  such as "type".  essentially a dynamic dropdown.

[Chris]

Seconding this.

[Chris]

That could be accomplished if my suggested custom events were implemented but alas I doubt if it even gets serious consideration it would be attempted so close to release...
The Settings UI does offer a consistent familiar interface that even the most green user can follow and I understand the reasoning behind not allowing scripts that could undermine that uniformity, however, like the WYSIWYG editor, a more advanced (bbcode) option is desirable to those of us who value efficiency just as much as (or more than) simplicity. The limitations are rubbing my wrists raw and makes it difficult to type with both hands tied behind my back <insert grin here>

Dec 9, 2012 9:00:05 GMT -8 Chris said:

• Richer Setting UI Suggestions (that don't belong in this thread)
  
  • onBeforeSetup - custom event that allows a plugin to add default values if none present, check for additional required libraries, etc.
  • onSetupFieldChange - custom event to implement more complex conditional field validations with context-sensitive guidance as well as ability to dynamically hide/show fields based on relevance to choice just made
  • onAfterSetup - opportunity to validate final choices, alert to further actions that may need to be taken (e.g. - actions that would be considered unsanctioned AJAX calls)