My favorites | Sign in
Logo
                
Search
for
Updated Nov 02, 2009 by jeffdep@yahoo.com
nextRelease  
Features and changes implemented in the next release of Fosfr.

.9 release, current development build: 128, 11/02/09

  1. Entire framework rebuilt as a combination of 2 SWC source files and an associated single SWF library. Implementations now consist of the following base weights: FosfrMainSWF files - base weight approx 13kb. Library source file (contains the remainder of the Fosfr framework; preloaded along with Shell) - approx. 27 kb. FosfrShellSWF and FosfrSubSWF files - approx 4 kb per file. See the SWCImplementationGuide for more details.
  2. Fosfr supports loading of custom external libraries, further reducing overall file size of applications built with the framework.
  3. FosfrLite deprecated.
  4. Major overhaul of package layout. All internal use classes have been moved into the core subpackage.
  5. custom namespace fosfrns defined in fosfr core.fosfrns; currently being implemented throught the package to restrict access to internal methods and properties more effectively.
  6. methods that should not be overriden now marked as final throughout the framework.
  7. all internal events are now in fosfr.core.events, public events now reside in com.jeffdePascale.fosfr.events.
  8. prequel has been moved directly into the package under com.jeffdePascale.fosfr.prequel.
  9. subHolder and shellHolder clips are now optional and will be generated automatically at parent origin points if not specified.
  10. externalClasses sub package removed; classes renamed FosfrClass and FosfrLibItem and placed in the fosfr top level package. Lite versions removed following with FosfrLite deprecation.
  11. Fosfr 'projects' are now referred to as 'applications'. Application 'version' property is now a number value, added 'build' property, uint. Both appear in the Fosfr class.
  12. Debug class renamed to Notifier, notification functionality properly implemented and utilized throughout build. This class now allows for control over what Fosfr internal notifications are sent to the debugger via the notificationLevel property, which should be set to value from the NotificationLevel class - ALL, CRITICAL, ERRORS_ONLY, or NONE.
  13. Notifier debug panel features a basic code injector,allowing for properties and methods to be modified and called at runtime.
  14. Notifier debug panel now allows for custom property inspectors, capable of displaying the values of public properties as they change.
  15. Scrollbar functionality added to the Notifier debug panel, as well as a new boolean value toggleLargePanelSize which increases the size of the panel.
  16. Notifier debug panel now has buttons for toggling error trapping (see below), the notification severity level, and the size of the panel itself (toggleLargePanelSize).
  17. Notifier debug panel has a maxHistory property, controlling how much data is to be stored in the panel before purging the oldest. default is 200.
  18. Notifier debug panel now stores values in an array with their respective severity levels. Changing the notification level affects what is displayed, not what is stored, allowing for toggling of debug info dynamically.
  19. Notifier debug panel now features a detailed information tab, displaying framerate, memory usage, availability of external interface, player version and whether it is a debug player, and the ability to force garbage collection when using a debug player version.
  20. Notifier debugPanel has new optional property 'jsInjectName'. Setting this value to a string value will create a JS method in the HTML container page defined with the name specified, which, if called and passed the instance id of the SWF embed, will trigger the debug panel. useful for security if you wish to disable keystroke launching of the debug panel but still want access; the JS method can be called to prompt the panel through injection (firebug, etc).
  21. FosfrError class defined and implemented across framework through the Notifier class. Fosfr notices that before would strictly appear in the debug panel now appear in flash player debug notification windows if using a debug player. Errors also appear in the debug panel unless the notification level is set to NONE.
  22. Errors can be trapped and controlled using the new doc class level throwError method. This allows for suppression of potential error points if the trapErrorNotifications property of the Notifier class is set to true. If set to false, error information will display as expected in the output panel or in the debug player's window. All FosfrEvents are subject to suppression by this parameter by default. Instead of calling throw new Error() in a try catch, call throwError(Error()) to route the error through the Notifier.
  23. Notifier debugPanel now contains the property 'enableErrorBeacon', which if set to true, will display a blinking red dot in the upper left corner of the stage if an error is trapped and the debug panel is closed. This respects the enabled property for the panel and will not display if the panel is disabled.
  24. Notifier properties can now be set from the config file.
  25. The debug panel itself can now be accessed via fosfr.notifier.debugPanel.
  26. doc class level debug method now add optional 'severity' parameter, if a value is specified (uint value from NotificationLevel class), debug message will respect fosfr notificationLevel setting.
  27. GraphicalNavHandler renamed NavManager and moved to fosfr level. Like other packages at this level, it can now be standalone instantiated outside the framework.
  28. SoundController - accessible via the 'sound' property of the fosfr framework, sounds can be added via the config xml under the 'sound' node. Files are denoted as subNodes named 'file'. optional name attribute allows sounds to be referenced by a short name identifier. Each sound loaded is assigned a unique discreet audio channel in the order loaded. Sounds may also be added via the addSounds method. global mute and volume controls, as well as independent volume control per channel, addressable by channel number or short name. Methods for controlling playback: cueSound, stopSound, loopSound.
  29. New halt position added to the SubLoader class, allowing for sitewide notification of the unload of the existing swf prior to the load of the subsuquent swf. (Currently only the existing swf is notified of the unload event).
  30. LoaderState class and NavLoaderEvent classes overhauled. NavLoaderEvent now defines, UNLOAD, UNLOAD_COMPLETE, INIT, LOADER_STATE_CHANGE, and COMPLETE. LOADER_STATE_CHANGE is dispatched for each step of the process, defined by LoaderState: IDLE, INITIALIZING, PAUSED_BEFORE_UNLOAD, UNLOADING, PAUSED_BEFORE_PRELOAD, PRELOADING, PAUSED_BEFORE_FINALIZE, and FINALIZING. All states of the load process are now consistent and accounted for.
  31. SubLoader property 'pauseAfterPreload' has been renamed to 'pauseBeforeFinalize', consistent with aformentioned loader states.
  32. Tracking class - new property 'trackPreamble' allows definition of a string value to be prepended to every tag fired through the tracking engine. Useful for setting folder structures in google analytics.
  33. Tracking class - new method 'getMethodInstance' returns the instance of the requested tracking method instance. Tracking methods are stored sequentially based on the order in which they are instantiated. Defaults to 0, specifying the first method.
  34. Tracking can now optionally be instantiated standalone outside of Fosfr.
  35. Fosfr external classes (in the fosfr.utils.externalClasses package) no longer require a direct call to 'attachFosfr' upon init. Instead, instantiate an external class that extends one of these classes via: foo = declareFosfrClass(foo()); Class will be attached to framework on init call.
  36. fixed a substantial bug where the fosfr object was modifiable outside of Fosfr internal classes.
  37. doc classes now all properly extend Sprite instead of MovieClip.
  38. Fosfr is now a singleton and cannot be instantiated directly; FosfrMainSWF must be used as a document class to instantiate.
  39. config XML parser better handles properties with integer values.
  40. FlashDevelop template files have been generated for all of the document classes and the configuration XML file.


Sign in to add a comment
Hosted by Google Code