Show/Hide Text Block - Change-Log Weaver Using JS library from: http://moofx.mad4milk.net/ ----- + New feature * Changed feature - Removed feature > Notice/Event (internal note to me) ! Bugfix ~ Outstanding item to complete before release ----- Known Issues to be resolved: (starting from 10/11/06) ------------------ ! User must set container overflow to Hidden via the Inspector. This cannot be done via the Action except in the html output. Limitation of Action environment. ! Compounding of opacity does not show correctly in IE6, will need to look into IE7 and report back. Hopefully IE7 fixes this problem and it will become a non-issue. (example, using opacity fade with Show/Hide which is show/hide'ing a semitransparent item. Colors are strangely/slightly inverted) ! v2.2.4 and previous can potentially prompt user for missing resources under these circumstances: >Same behavior can be noted with any Action that programatically assigns files to upload Resources have been removed manually outside FW, and affected pages are themselves never 'dirtied' A non-layer item has been moved to the pasteboard after previously publishing -At best, the user should only be prompted once +Fixed in v2.2.5 Workarounds: -Republish everything by holding control and accessing the File menu -Turn the pasteboard item into a layer item, or better still -Toggle off 'Publish' in the Inspector for the item Known Issues that cannot be resolved via the Action: ------------------ > Opacity has issues with ClearType in Win-XP, this is a limitation of Win-XP Workaround involves turing off opacity or defining a BG color for the Stretcher, both options possible inside Action > Issue with JS Library/CSS interaction beyond my control. If user is to have only an accordion made up of items with a Style that includes a BG Image, then the Accordions won;t work at all. The solution is to have at least one member of the Accordion group be without a defined BG Image. This can be done by having a 'dummy' member off in a corner somewhere. Again, this is not an issue with the Action, but rather with JS/CSS/DOM Non-grouped moo show/hides are not affected > FW Issue, if the Resources of the output folder are manually deleted, the user will be alerted to a missing resource for this Action. the Action publishes fine, and everything is OK. Logic has been added to clear out this 'dead-wood' to prevent user annoyance. But it does take one publish cycle to clear this. > Notice to user about missing resources in FW when user manually removes source files >Solution: Force republish of everything by holding 'Control' and accessing 'Republish Everything' command under the File Menu. User should only be alerted once more about missing resources. > Opera has some rendering artifacts when using an Accordion system. This is mainly exhibited as minor breaks in the graphical appearance of the page. Scrolling the content off the page and back causes Opera to redraw that section of page. This is an issue with Opera itself, and not with the Action or JS libraries. It is added to be as complete as possible with the expected and known behavior of the FAW Show/Hide setup. Any operation that changes sizes within the browser would be just as susceptible to this appearance. Potential Items (standing ideas) ------------------ + Close accordion/show/hide inline item, remote trigger (so it could be embedded inside the content of the show/hide, ÀfwParent? property) position marked in JS code, just need to implement method to ask for user input and create + Close item link at bottom of Stretcher see above + Externalize Custom JS to separate file, common JS already moved out of html page. + Ability to look at the code of the parent and change overflow to hidden in the HTML code. Experimental. + Notice to user about collapsible parent, and maybe about opacity and ClearType issues; conditional of course + Option for rotating graphic with header for further customization position marked for use in such a situation + Ability to define CLASS for all text inserted by the Action, currently inherit adjacent CSS >Need to re-tweak moo.smk.js file and add appropriate controls in Interface + Add coding to hide only opacity driven items on page load, requires some CSS kludges, so may avoid + Option to clear Files from Actions to prevent 'Missing Resource' Notices (house keeping operation like re-sync group) Should never need, but will prevent headaches if a user falls into a situation where they are perpetually prompted for missing resources. + Master/Slave Groups + Add custom code to set style to flexible height in case of such situations to allow growth if changing the browser text size, as well as allowing nested moo show/hides + Option of cookies to remember height/closure options + alwaysHide: boolean, if you want the ability to close your only-open item. defaults to false. Turn accordion into pseudo toggler, add like 'open this item' and 'open accordion on page load' To Do: ------------------ v 2.3 stuff, a lot of the potential ideas to be incorporated. !! Change method from prototype to single mootools.js file. Save me some headaches and such !! Change fwParam names for current var to eliminate missing resource notices. !! Update to moo.js v2.0 ++ Add option for 'open-first' (slides open on load), or 'first-open' just loads tray as open. May interfere with CSS JS in loading, may need to work out the issues between the two, may just remove class from 'open on load item http://docs.mootools.net/files/Plugins/Accordion-js.html#Fx.Accordion + add check and variable for mootools version, need to replace older versions page publish !! work on add markup as file as I am having multiple Actions writing to the same file location. Need to add logic to ignore looking if the file version is up to date. Required packages: Accordion Dom Transitions(for special transition effects) fxUtils fxPack (may need for scrollin Action, but not for Show/Hide); simply added full mootools functionality as it can then be called by common actions. combo has been replaced by: (need to buld by hand instead of single object call) var effect1 = new Fx.Opacity('Div', {duration: 300}); var effect2 = new Fx.Height('Div', {duration: 300}); $('submit').addEvent('click', function(){ effect1.toggle(); effect2.toggle(); }); ****************** Revision Log: [Ver.] [Release Date] [Main Notice to User] ****************** 2.3 (no eta at present) > Moo Libraries v2.0; Close links; CSS Styling ------------------ + Interface: Integrated Close Link Interface items (no backend yet) > Interface: Integrated Text CLASS (no backend yet) > Need to work on smk function to build correctly >> Hidden until it can be worked out the exact method to be used

vs etc... + Int: Addon Link Text Class backend ! Int: Moved Addon Text box adjacent to disclosure to condense overall interface footprint + Transitions options list for moo items ! Fixed
addition. no longer part of Addon text, separate entity, eliminates some possible display quirks with tags ! Single tag situations would cause incorrect publish, ie if only using an image as the header. - Removed some unneceesary code for DOM inspection, part of moo file - Remove prototype dependancy + Added 'wait:true' to syntax to force completion of transition before starting another + Added onComplete syntax to allow height:auto to be added to open accordion and combo items, allows nesting if moo Show/Hides ! Changed to include the FULL mootools library, this will allow implementation with other ACtions that I create. - Removed 'wait:true' as it disrupts the 'openThisItem on page load' feature. Work out kinks before re-enabling, may never re-enable ! Fixed 'page always dirty' issue with using multiple actions that utilize the mootools library, namely Lightbox at this point. moo v2 stuff >>> Accordion: Done, Stable ! fixed mooArrayCheck to return correct index value ! Corrected collection of index array items for Accordion ! Accordion correctly stays closed, opens marked item, or opens first found item per checkboxes in interface + Grows with page content, height:auto > Accordion seems complete >>> Combo: Done, Stable > combo deprecated ! Built loops to build multiple objects depending on the choices made, height & opacity + Grows with page content, height:auto > Combo seems complete >>> Smooth Scroll: On Hold > Awaiting for smoothScroll release from mootools JS guts not present in Action //////////////////Change from moo v1.x to moo v2.x////////////////// 2.2.7 (not released) Awaiting completion of v2.3 to include this bug fix ------------------ ! Single tag situations would cause incorrect publish, i.e. if only using an image as the header. Workaround involves adding a space (' ') to the link addon area to force retention of the full html structure of the header. 2.2.6 (11/10/06) ------------------ > Same as Demo with expiration date of Jan 1, 2010 > Final release of Action using moo v1.4, unless compelling bug is found 2.2.6 (11/08/06) **DEMO** Expires on 12/01/06 [2.2.5 was internal build number, not released to public] ------------------ ! Missing resource error perpetually showing up when non-layer item is on pasteboard, fixed for Smooth Scrolling as well ! Used some wrong commands to 'clear' unused files + Added an expiration date to Action. Retail version date is way off in future, allows for easy demo publishing for general public ! Demo expire date would cause republish on each time file was opened ! Logic to disable 'open this item' when 'open this Accordion' is turned off ! Clicking on mooGroup'd item would dirty page 2.2.4 (11/02/06) *HOTFIX* ------------------ ! **Pages using previous version always dirtied pages, forcing an unnecessary republish, despite no other changes being made by the user. + Added logic to allow me to keep created support files up to date when version number changes in Action 2.2.3 (11/02/06) > Mainly a bug-fix version, newest features may be 'experimental' in this version ------------------ + Added option for BG color for Stretcher to combat the ClearType(see above) ! Fixed href value for Moo 'Make header into link' ! Fixed href value for non-Moo 'Make header into link' > hrefs now degrade into simple 'jump to page' links (page = current page) with JS turned off, no more awkward file not found messages. + Externalized all 'standard' JS used in this Action, only 'custom' code remains in head ! XML compliant JS used to define CSS style to hide content while page loading Now correctly hides content while page is loading (opacity only option excluded, content may still flash if only this option is chosen) ! Fixed issue with 'Initially Closed' option not being Enabled when appropriate ! Fixed order of JS application to page, libraries inserted before visible