Panel Framework updates

Categories:Blog

Lots of updates today!

Logging and Output

  • Refactored the external.JSFLLog class to now be utils.Output
  • Moved Output.debug() to utils.Debug.process() which allows for better debugging (no anonymous functions so a proper stack trace!). However, Output.debug() still shortcuts Debug.process()
  • Rebuilt Debug.process() to handle XML and Date properly, as well as native types, and strings now output with quotes. Internally, it's much, much tidier, even though it was fairly functional to begin with.
Debug: Test
--------------------------------------------------------------
Object =>
     a: 1
     b: "hello"
     c: Thu Sep 16 15:16:06 GMT+0100 2010
    [d] => Array
         0: 1
         1: 2
        [2] => Array
             0: null
             1: undefined
             2: true
             3: false
             4: <xml a="1"/>
             5: [object Sprite]
             6: [object URLLoader]
         3: 4

Panel Framework

The MVC Panel Framework is as good as finished today as well.

It's just really nice, and everything just has its logical place now, with nothing feeling like it's been shoved in, just to put it somewhere.

The MVC triad is still really lightweight, and can be used or not used. It just does nice things like assigns a primary view per controller, automatically instantiates the TransportFacade in each model, and hands an optional model to views.

Views don't even need to be View Classes, they can simply be DisplayObjects.

The next step is to start plugging in the layout framework and the small amount of components I've already built, and seeing how it works. I'm hoping that the Tabs, State and Container components make light work of pushing UI elements around!

Glad I didn't resort to Flex now, although it should still just plug in as needed :)

Comments are closed.