Mootools Suite - ChangeLog
Weaver
Have an idea? I would love to hear from you - see: http://www.coastalrugs.com/Actions/ for how to contact me.

Suite contents:
------------------
1.0:
	moo: Lightbox/Slimbox
		- Modifier Action with template system
	moo: Effect on Load
	moo: Accordion (aka FAQ Show Hide)
	moo: Smooth Scrolling to Anchors
1.1 Additions
	moo: Script Locator
	moo: Add Scripts
	moo: Slideshow/Gallery
	moo: Tips
	moo: Accordion Trigger (as of 1.1p3)



ETA's: (all ideas subject to change)
-----
1.1rc3		12/25/07
1.1			12/31/07
1.1p#		1/08 > 10/08 Maintenance and bug-fix releases as needed

Action development will be forked here, so that I can freely expand v1.2 without regard to legacy code environment.

1.2			?? 1/1/09
	- Of course, any necessary bug fixes
	- Deeper compatibility with Prototype (creation of routines to make Proto kosher functions, may limit functionality but will at least output something like what the user expects.
	- New modular file setup to allow for 3rd party development
	- Update structure to allow for bug-fix patches
	- ?Self-updating routine?
	- Update mootools version to latest, and make any necessary tweaks
	- Moodalbox/Thickbox functionality (had been relegated to beta testing till now) With Page modifier Action, similar to Slimbox

2.0			??????
	? Even better modular design that will allow for 'slaves' and remote triggers of events
		- Idea of 'moodules' - discrete actions that can be linked or chained as desired
		- Expansion of moo:EffectOnLoad features and options


Unscheduled Future Additions:
------------------
?	Image Reflections and other effects
?	Transcorners
?	Observer - Allow addition of code, on a per-item basis
?	Sub-Scripts - Allow user addition of subscripts to the page, in the correct relative position to mootools


Abbreviations:
------------------
LB	=	Lightbox/Slimbox, used interchangeably
LBp	=	LB page level Action
SH	=	Show/Hide Accordion Action
SHt	=	Accordion Trigger, follows SH naming convention
GEN	=	General notice
EOL	=	Effect on Load
MB	=	Moodalbox
beta	Notice to beta testers
SS	=	Smooth Scrolling
FS	=	Fading Slideshow
DOC	=	Documentation
AS	=	Add Scripts, headless mootools
CM	=	Central Moo, aka Script Locator
TT	=	ToolTips

Mini-Addons:
-Available as separate downloads
-May be integrated into the Suite as it matures)
------------------
- Slimbox Trigger - Allows remote triggering of moo:Slimbox by any other item.  No plans to make this a 'direct' inclusion into the suite.
- Script Locator (n/a), integrated v1.1



+ New feature
* Changed feature
- Removed feature
> Notice/Event (internal note to me)
! Bugfix


Suite Versions (individual Action versions numbers should now reflect correct suite version)
v1.1p3 bug-fix:1 (10/15/08)
------------------
!	LB	Duplicated Actions would sometimes inherit incorrect popup images

*	FS	'alt' properties now included on generated <img> tags for slides (will now pass XHTML validation)
		Uses concatenated Title / Caption for value, or <img> 'src' if no other information available (no user control)
		CSS validation still throws errors as a result of some necessary IE-specific coding


v1.1p3 (around 7/1/08)
------------------
Sorry, I have been neglecting this log a bit over the last few months.
+	SH	Added option to effectively 'disable' the creation of the accordion header.  It is still there, but just zero height, and not visible.
+	SHt	ACTION ADDITION - {moo: Accordion Trigger} allows for remote accessing of the accordion by this Action.  User can now define header (or multiple headers) any way they want.

!	GEN	Vertically oriented images could output in the wrong size.  Applescript routine fixed.
!	GEN	Foreign character filenames now correctly output, instead of causing resize routine to fail.

v1.1p2 (around 3/1/08) - Another bug-fix release
------------------
!	GEN	Moved location of <scripts>/<style> tags after last <meta> tag as IE seems to be very particular about the scripts and <meta http-equiv='content-type' content='....'> corrupting the previously added scripts.
>	GEN	Suite has not been thoroughly tested with FW5 yet.  An update is in planning stages, no ETA at present.  Any reports of errant behavior in FW5 should be reported to help with this transition.

*	SH	Basically halved length of variable names from the unecessarily long:
		'smkMooDivsmkitem145smk65MooLinkitem145smk67' to something more like: 		'mD_item145_65mL_item145_65'

>	MB	Suite now properly includes the moo:Spawn New Moodalbox action, though not complete and functioning at 100%, this is added for users to try and see if it does what they need.  ##Not an 'official' part of the Mootools Suite yet.


v1.1p1 (2/1/08) - Major Bug fixes in IE
------------------
!	GEN	Bug fix for entire suite in IE.  This should have been caught in testing


v1.1 (12/31/07) - Bug fixes from RC2 and house-cleaning
------------------
!	GEN	Removed expiration date for public release version

!	SS	Safari 3 does not like current gen (mootools v1.11) script for this, so a custom addition was made to the mootool.js file.

!	FS	I broke this with a small typo in RC2, fixed again

>	TT	FW does not seem to allow hyphens in style names, I will have to see about rewriting the tips function, or see about the ability to 'mimic' a style into another name via mootools.

beta testers: Thank you all very much with the release.


v1.1rc2	(12/21/07) - Bug fixes from previous RC
------------------
++	TT	Added new Action called 'moo: Tips' - a Page/Folder level action that uses CSS selectors to target specific items on a page for application of tooltips.  Uses the 'title' and/or 'href' field of an item for the tooltip information.  Info can be 'forced' by using the syntax 'myTitle::mysubtitle' in the title field of any item (and of course, adding that selector to the list) - I couldn't help myself :)
+	AS	Enabled Slideshow Gallery script to be added via this action
*	GEN	Unified and condensed <head> <script> tag syntax.  All actions now use the same functions for onLoad and onDomReady events.
!	ACC	Fixed CSS issue when using non-mootools accordions
*	ACC	Update close_link backed to better support hiding of 'highest' tag possible.  Instead of just <span>text</span>, it will dig upwards to <p>...text...</p>.
beta:
>>	This is planned as the final release before public consumption.  Please report any/all bugs for fixing.

v1.1rc1	(11/28/07) - Complete the Actions as they stand to make correct and complete for public consumption.  Some Actions won't be included, others will 'frozen' at their current feature-set
------------------
>	GEN	Version changed to v1.1rc1 to reflect the significant additions/changes made since the previous public releases
!	GEN	Changed some of the resizing logic to better handle the possibility of multiple Action instances using the same source image.
!	GEN	Added cleaner function for updates to images and will replace them if not up to the current version.
!	GEN	Removed all instances of writing the source file as a modifiable output file (I have already lost and resized a few files this way!!)
>	GEN	Added extra conditional to the resize AS to prevent overwriting of source files (if source == dest, then error out).  Rather have error than data loss
>	GEN	Added extra test to child writer that will only write children to the 'working folder', if a file is found and not found in the working folder, then a new child is created in the working folder just to be safe.
*	GEN	Minor interface tweaks to better alert user to missing image files inside the Action interface, SB and FS
*	GEN	Moved all markup items into external files in Action bundle.  This should better support future updates and user individualization
*	GEN	Moved many of the 'cleaner' routines to a more appropriate fwFunction location, fwParametersCreated instead of fwApplyError
+	FAQ	Option for hover trigger added.  Hover acts the same as a click.  So hovering once may open the accordion, but if the accordion can close, hovering again will cause close.  Not, entry causes open, exit causes close.  No option for hover time included, set programatically at 300ms.
+	FAQ	Option for 'open link' text to replace text found in the header.  Should correctly displace redundant <br /> tags and remove parent tags as needed.  No substantial change to html structure, just CSS hiding techniques.
*	FAQ	Cookies now respect individual pages, only remember state for the originating page/item, NOT as previous where all items of the same id in the same path would be triggered.
!!	FS	Remove an erroneous line of code that would clear user selected file from the Slideshow Interface on every version update (beta testing artifact)!!
+	FS	Added 'Carousel Text' option to 'Custom Settings...' option list
+	FS	Updated to the latest script from JonsDesign
!	Completed 'guts' of script and allowed for unique captions for each of the folder items.  This system will keep track of up to 50 captions, and draws from that 'history' if the action needs to rebuild when images change.
!	SS	Pages now correctly supersede Folder designations, most child folder takes precedence over parent folder as far as settings go (does not apply to 'synchronize a name/id values')
*	SS	calling function now follows convention of window.addEvent... instead of calling method directly window.ondomReady(...)
+	AS	Integrated mini add-on into full action set
>	AS	Expanded list of possible libraries to include all that is naturally included in Suite
++	CM	**SUSPENDED - Triggered some file publish bugs in Freeway, looking for a solid workaround** Added new action called: 'moo: Script locator' - It is used to specify a url for the mootools library, this allows each action instance to use the same mootools library file.  It is applied to a folder, and affects all child elements below.  In fact, each element (item, page, folder actions, etc...) looks upwards to check to see if itself or its enclosing folder has an action, if not, moves to next higher folder.  So subfolders correctly supersede parents.
>	CM	UPDATE: Seems to be better now, I have used a recently found method: fwDirtyAllActions, that appears to do what I need of the actions rebuilding themselves, instead of seemingly passively sitting by and not reworking themselves.
!	EOL/FAQ	Fixed issue when using this action roughly 30 times on a page in IE.  Now only creates and uses one <style> tag for all calls to the createStyleRule function
*	EOL	Changed the loading script calls to include a setTimeout(function,0) so that the events effectively fire concurrently instead of serially.
beta:
>	This release is a Release Candidate, as reflected by the updated version number - I want to know about anything that seems out of place or not behaving as expected.
>	Minor actions not intended for inclusion to general public have been removed.
>	Documentation is still a mess and won't be updated until the update is complete and finalized.
>	No known issues when updating from either a beta versions or previous commercial releases.

1.0b6-2	(09/28/07) - Beta release to address specific behavior when updating to latest version
------------------
!	FAQ	Update to latest version caused some irregularities with 'initially open' setting.  Fixed the logic behind the updating script.  This only happens when updating the action versions and not between saves, etc.
beta:
!	interim version of v1.0b6b to fix updating issue released.

1.0b6	(09/28/07) - Just another beta release to keep uninterrupted flow in output.
------------------
>	GEN	Marked this version as RC1.
>	GEN	Migrated Action Suite into bundle/package a la Paul's big Actions.
+	FAQ	Option to 'Remember Accordion State' between page loads via cookie, defaults to on
*	FAQ	Slight changes to interface to support above option (had to enable certain mooGroup features during non-mooGroup operation)
*	FAQ	'Initially hidden' when using moo is replaced by 'Open Accordion on Page Load'  options will be synchronized on action update.
*	FAQ	All show/hide flavors use Accordion, no more jury-rigged solutions objects
!	LB	Minor interface logic for display of additional image caption fields
+	LB	Added number of additional images to the 'Additional Images' disclosure
!	LB	Added loops to alert user if main image is missing from Finder, Action will correctly skip publishing certain page features if images are missing
Beta:
	Packaged as user would receive.  Please comment on any troubles/suggestions with installation/upgrade.
	Suite still contains smaller actions, some working some not...

v1.0b5	(07/31/07) - Planned to make FS 'feature-complete' for public release, with expansion planned in the future
------------------
*	GEN	Tweaked descriptions of Actions to remove superfluous information and detail not fit for consumer viewing
!!!	LB	Resize script incorrectly interpreted results from AS return value.  Expecting Boolean but was being served string.  Result: Images with max sizes larger than the actual image were not being uploaded.
!!!	FS	Resize script incorrectly interpreted results from AS return value.  Expecting Boolean but was being served string.  Result: Images with max sizes larger than the actual image were not being uploaded.
+	FS	'Advanced...' setting implemented, though not to full complement yet.  Correctly sets values as enumerated in fwInterface
>	FS	xfer old settings feature is progressing well.  Drop down in place with button and help files in place.
>	FS	'folder source' - Will have to make some concessions.  Single url/slimbox option probably.  I will have to figure out a method for attaching captions to the images for folder source selections.  Option to convert to 'file source' button (future addition)
*	FS	Upped image limit to 25 images to match previous fading slideshow Action.
+	FS	Added help button to 'Type' setting
!	FAQ	Fixed minor bug in standing JS code for the Link Addon creation and adding extra CSS information
+	FAQ	Added controls for 'Close Links', working, but maybe not to full complement of options yet.  Please send suggestions for improvements
*	FAQ Addon Text class now added to <a> tag instead of internal span, can now better control appearance of link with :hover, :active, etc  pseudo selectors
*	LB/FS	Scripts in place to clear child image hashes when suite version is updated, allows me to 'fix' problems without intervention by the user.
+	FAQ	Added 'Appearance', and 'Advanced' disclosures to help tidy the interface a bit
*	FAQ	Default 'use mootools' state changed to 'yes', now assumes you want to use mootools in newly created actions
*	FAQ	Extracted a lot of the mootools JS into the head where it belongs.  Fewer and fewer commands are actually imbedded in the html.  Moved to dynamically added tags and attributes.  Need to further clean the Tag adding scripts and hopefully move those out as well. *non-moo remains with hard-coded onclick events, as the structure with moo is not added by the user's choice, thus non-moo.
!	GEN	Updated to mootools version 1.11 (June 07)
!	FAQ	Fixed jittery transition height transition for accordions (both group and toggles), as a result of updating to v1.11
Notes:
>	FS	Still not complete, a few things left to do, some settings to add, some settings to disable and save for future use.
>	FAQ	Want to add similar features of close text for addon text and simplify the settings for this feature.
>	FAQ	FOUND ISSUE: Safari does not correctly render the JS generated links until the item is clicked or hovered.  I am blaming this on Safari and not the JS syntax used.
Beta:
	Expiration set to October 1. 2007
	This is considered beta 5, hopefully a release candidate

v1.0b4	05/25/07 - Some tweaks to existing Actions, additions to FS - Pushed out so users would have uninterrupted beta usage.
------------------
+	FS	Hide caption area if there is no caption or title to show. JS script
+	FS	Added option for random order, should help with migration from previous Fading Slideshow Action instances.  JS script
+	FS	Added hiding CSS for unused/unnecessary elements in the non-js page layout
*	FS	Made layout for non-JS viewing more attractive and compact.  Still relies on CSS for positioning and visibility.
+	FS	Added placeholders for Custom Settings disclosure and populated with some currently non-working widgets
+	FS	Added placeholder controls for transfer of old Fading Slideshow settings to the new Action
*	EOL	Migrated JS calls into singular onLoad control function
*	EOL	Split out JS to set up for effect into standalone calls so the item is set as the page loads, then effect is called when page is finished loading
Beta:
	Expiration set to August 1, 2007
	This is considered beta 4

v1.0b3	04/13/07 - Fix of any bugs found in previous beta cycle.  Hopeful addition of 'major' suite feature in this build.
------------------
!	EOL	**removed - not cause of problem, just general issues with png's and IE** Added check for presence of ClearType and exit for function if found.  ClearType really mangles any fade transition.  But really noticeable in IE6/7.  Added ct_test.vb to head with VB to check and set variable.
>	EOL	Changed code to try...catch instead of if...else statement.  Better catches errors and fallback to showing materials if transition fails.  Less code besides : )
>	EOL	Tweaked and reduced size of 'flicker' transition, still considered a beta transition and should be used with caution.
!	GEN	Added "event.returnValue = false;" to all generated onclick events as just 'return false;' appears to not be enough anymore to prevent IE6/7 from following hrefs
!	GEN	Added check and addition of 'fixing code' for FW_Object.js JS library that will prevent page corruption when generating FLash objects and such, EOLAS related
>	GEN	Converted visible 'moo.js' text to 'mootools'
!	LB	Changed random 'group' name to fwItem.fwTitle, as it was noted that a new action-generated html page was created on each publish cycle otherwise.
>	GEN	Changed version number of all included Actions to reflect suite version number instead of separate versions for each Action.  Now takes on form of 'Suite v1.0', etc...
!	LBp	Tweaked application cycle to allow the Fading Slideshow to insert its libraries before these.  FS now respects these settings.
Additions:
+	DOC	version 1.0 of documentation added to website.  Only current major components at present.
>	FS	Settled on method and general scope of Fading Slideshow.  Will migrate to html item, as FW better supports the use of child elements, and is the method used by the slideshow.  Will eventually allow at least three methods of content definition: 1)manually, 2)via folder, 3)existing div layer on page.
>	FS	Need to apply Slideshow to an html item or table cell to support the required structure for the Slideshow itself.  Better reflects connection between layout in FW and final appearance in browser.  Concession is that images are not visible.
+	AS	Add Script Action, used to headlessly add scripts to the page.  Currently only adds Slimbox.js library and mootools.js, others to follow.
+	FS	Added Slimbox popup options to the Action.  Now independently adds script libraries as needed.
++	FS	Officially added moo:Slideshow Gallery to the Suite as a component.  Soon to be publicly released.
Beta:
	Expiration bumped to June 1, 2007
	This is considered beta 3 (v1.0b3)

v1.0b2	(03/11/07) - BETA Release - Mainly Bug release. Some minor additions to the existing Suite Action set.
------------------
!	LB	Action would timeout with large png files (1280 x 1024 and larger).  Exit condition set for hash function (length of string) as well as generous fwTimeout.  No noticeable impact on customer end, but should still add enough uniqueness for the hash.
!	EOL	Added some checking code so that if the browser chokes on the transition, the item will appear, whether immediately if 'fatal' choke, or after transition time for 'minor' choke.  End justifies means with this fix.  Complete experience is what is expected for end user.
+	MB	Partial moodalbox inter-workings in place.  Both Inline Action and Item Action for graphics.  Appear to be working correctly, no styling options in place yet, plan to be similar to Slimbox options and such.  Hopefully will be able to reuse a lot of that css and code.  MAY CHANGE GUTS TO ANOTHER SCRIPT LIBRARY.
+	GEN	Added 'Credits' button to all Actions to assign proper credit where credit is due.
+	EOL	Added 'flicker' Transition.  May remove so use tentatively at present.
+	SH	Page Load delay time option for Accordion.  Only for 'use Moo' and items belonging to a group.
+	SS	Added Transition and Duration to Smooth Scrolling Actions, both folder and page level
beta	This release expiration bumped to May 1, 2007
beta	This is considered beta 2 (v1.0b2)

v1.01	(02/28/07) - Bug fix release, may grow to feature addition release
------------------
!	GEN	Added loop to automatically rebuild support files when suite version number changes, prevents certain types of output corruption
!	LB	Reverted to 'standard' output of slimbox/lightbox flow for compliance with IE, May limit some of the options for the page modifiers and such.  Will revisit to bring back options.
!	LB	Rebuilt output for this action so that it appears consistently across browsers, needed to add a few IE specific IE definitions (only in theme file, so is 'user-customizable)

v1.0	(02/12/07) - Rewrite for mootools and add some more functionality
------------------
>	LB	Change from prototype.js to mootools full library.  Mainly made for compatibility with my other Actions
>	LB	Change from 'Lightbox' to 'Slimbox' libraries
!	LB	Made CSS file flexible to the actual upload position/filenames of the images
!	LB	Fixed addition of mootools from multiple Actions always dirtying pages.  Set precedence for replacement of previous versions.
>	LB	Made provisions for potential resizing loop
>	LB	provisions made for <noscript> gallery to be generated so the user has at least something to look at that is somewhat along the lines of what the designer wants to show
>	LB	Template system planned for <noscript> gallery page. Limitations will need to be followed, but pretty open to any non-JS features
+	LBp	Added Language options to Page Modifiers, can define custom [Image] # [of] # text
!	LBp	Fixed issue with modifiers and global variables.  Publish of LBp moved to fwAfterEndHead.
+	LBp	Added Themes structure and automatic addition of CSS and images to the page
+	LB	Enabled maxSize features, should now correctly generate images as needed
>	SH	Converted free-standing action to use the mootools Suite construct, no changes other than function names and markup.  should output the same code.  Incorporates the latest (read unreleased yet) Show/Hide code.  Main Action trunk is terminated for this version.
!	SH	fixed issue with migrating to suite in regards to converting variable names and such (tempfuncB)
!	Anchors in myHeader caused nested <a> tags which negated the operation of he header controlling the show/hide
+	SH	Added '#mooFAQ' hash to the end of generated links so on page links don't automatically show as 'visited', could also serve as trigger for page loading and opening of specific accordion items
!	GEN	Several bugs noticed with FW and reported directly.  Hopefully SP will resolve them or I will have to look for a way around the trouble (4.3.2 release), awaiting response from SP in regards to these.
+	LB	Added html file creation to action so that people with JS turned off see something like what the designer intended.  Will probably allow themes to modify these as well.
!	GEN	Need to work out hash function to be able to read graphic files and parse them as strings.  I just need a consistent 'view' of the contents, they don;t have to be 'accurate' or manipulatable, just unique.
+	GEN	###	Updated to mootools v1.00	###
!	SH	Fixed toggler with mootools v1.0, Fx.Height and Fx.Opacity have been deprecated as far as I can tell.  Converted to single element Accordion
!	SH	Fixed single tag situations not receiving correct id's and carrying through to mootools functions.  Moved ID building to after singleTag tests
!	LB	Minor tweaks for update to v1 on a couple of lines of slimbox js code
>	EOL	Seems to be OK
!	GEN	mootools file is now rebuilt every time the page is dirtied.  In contrast to the previous method for checking for presence of file.
!	SH	Some commands have been deprecated from mtv1.00 so onComplete had t be rewritten to accommodate all elements and such for accordions
+	SH	Added 'alwaysHide' syntax to transition, under the name 'Allow Accordion to Close'
!	SH	Action set now 'functions' as expected.  Code is cleaned up pretty good.  May need to readdress this, but it works and I am not touching it again if it stays that way.