Upcoming Stuff:

Ideas for Actions that are either in-progress or are on my Action coding plate to look into soon. Arranged roughly in order of precedence.
 

Voice your opinion. Send me suggestions or feedback. Your input is valued, and is one of the few ways to gauge the community's needs. You may use the the email address provided in the graphic at the top/left of the page.
 

General Action Ideas (Read: Rough thoughts):
- Ability to have a text link change its text to match the 'title' (or optionally other attributes) of the linked page.
- Modularized Action creation and installation, central hub with independant library spokes that all developers can use.
[[This is proceeding quite well and I am almost ready to post some notes and points about usages. Any inquiries are welcome, as this will be a toolset released to the generl Action Development community, likely without restriction]]
- Update of some older Actions to utilize recent improvements to FW.
- Action to gather and exernalize any found JS code found in the document <head>
Mootools Suite Improvements- Suite Description Page
Mootools Suite has been released. I plan improvements and additions to the Suite.

CURRENT SUITE CONTENTS:
> Lightbox/Slimbox
> Accordion - FAQ Show/Hide Text Block
> Effect on Load - Plan to grow with more options, but code structure is present.
> Smooth Scrolling to Anchors
> Slideshow/Gallery - Fading slideshow control with integrated Slimbox popups

Possible inclusions in the future:
? Easy convertion of Spawn New Window Actions to Thickbox/Moodalbox for convenience. (maybe even a page/chain-based soultion to universally convert)
? Customizable fallbacks for non-JS enabled browsers.
? Template based galleries
+ Integration of current Fading Slideshow into mootools Suite.
+ Gathering the 'essence' of many of the Misc. Actions into one larger suite all using the same JS library and coding conventions.
+ Draggables
? Rounded Corners - script not compatible with current mootools version
+ Tooltips - Simpe first, then more complex later.

Rewrite of Input Item Label -
Input Item Label needs to be readdressed for update to FW4. Only FULL version affected, and then only specific features
Should also include some neat labeling features found on AListApart as well
 
OverLib/DHTML Tooltips - Probably rolled into the mootools Suite to prevent 'another' library from having to be added.
Ultimately, I would like to revisit the OverLib action and see if can get that working well for FW4. I haven't decided which one I will use. Nor, have I settled on a path for implementation. Please send any suggestions to the address noted at the top of the page.
Planned / Ideal Features:
- Use a DIV layer on the design page as the tooltip content
-(Option to type in HTML content as well)
- Totally hands-free operation for the visual appearance of the tooltip
-Options for all known features
- Area to add custom code for unforeseen coding requirements
DON'T EXPECT TOO SOON - DELAYED INDEFINITELY
Could be part of the mootools suite as this is a plugin of that library
 
Possible Interface options:
-Advanced: Use a layer item on the page for the source of the 'popup'
-Simple: Accept simple textual input with some Class styling
Generals:
-Height/Width/Position/Delay/Sticky
-Master/Slave Settings
Options quickly become overwhelming to Author and User alike
 
hexheader02
mail

Updated:
7/4/08

Upcoming Stuff
item1aitem2item2