As regards features, the main enhancement in this release is the option to supply a proxy name to LoadupMonitorProxy, thus enabling independent instances to exist.  See the notes in version.txt.

To migrate to Loadup from StartupManager, see the instructions in the text file migrationToV2.txt.  In developing Loadup, the opportunity was taken to drop code that existed only for backward compatibility purposes.

The two demos have been migrated to Loadup, so we have Loadup as Ordered and Loadup for Assets.  The latter has been enhanced to illustrate the loading of intermittent single assets and a group of assets, as independent tasks.

----Philip

Also, shouldn't viewComponent in the implicit getter reference the Main class , passed in thru the body of the StartUpCommand?

The implicit getter would reference Main in the mediator for Main, often named ApplicationMediator.  But for other mediators, the getter references the viewComponent being mediated, in this case viewComponent LoginPanel.  The LoginPanel instance has been passed to the constructor of LoginPanelMediator.
----Philip

Has StageMediator been registered? - must be registered before it can  be retrieved.
----Philip

The StartupManager utility might be relevant - plus the associated demo Startup As Ordered - to do with loading data records of different types, in a prescribed sequence, so that one type does not commence loading until all the types it depends on have been loaded.
----Philip 

See this post: http://forums.puremvc.org/index.php?topic=259.msg6136#msg6136

Arising from that, with reference to my post above about this demo code in the repository trunk, trunk/libs now has the StartupManager 1.6.1 swc.  The 2.0 one, being invalid, has been removed.

My apologies for any inconvenience caused.
----Philip

See this post: http://forums.puremvc.org/index.php?topic=259.msg6136#msg6136

Arising from that, my post above about this demo code in the repository trunk is premature, since there is not yet a StartupManager Utility version 2.0.  Hence, this demo code is in transition and is not a final version.  Use it at your own risk and be aware that the ultimate version will probably require you to refactor what you've done.

My apologies for any inconvenience caused.
----Philip

I refer to my post above about code in trunk.  It turns out that I was premature in declaring this as a release.  This code is in transition and is not a final version 2.  Use it at your own risk and be aware that the ultimate v2 will probably require you to refactor what you've done.

My apologies for any inconvenience caused.
----Philip

There is a new version of the Startup As Ordered demo in the code repository; in trunk, not tagged.

Here is the relevant extract from version.txt.

1.6 Presentation improved, to conform better to demo presentation
    standards.  Libs now has PureMVC 2.0.4 and StartupManager 2.0.

There is a new version of the StartupForAssets demo in the code repository; in trunk, not tagged.

Here is the relevant extract from version.txt.

2.0 - Requires StartupManager Utility version 2.0.  Now demonstrates
    loading of single assets as well as a group of assets, concurrently
    if desired.

There is a new version of StartupManager in the code repository; in trunk, not tagged.

It has been numbered as version 2.0, since it is a significant enhancement.  Here is the relevant extract from version.txt.

2.0 This release is backward compatible, except for users who have
    implemented their own IResourceList or IRetryParameters (see
    below).
    StartupMonitorProxy (monitor) constructor now takes proxyName
    as an arg (optional), thus enabling concurrent instances.
    Property jobId is disallowed unless the monitor proxyName is
    the default name.
    On sent notifications, the type is the monitor proxyName,
    unless there is a jobId, in which case the type is the jobId
    as it has been since version 1.4.
    On loaded and failed notifications sent by the client app, if
    the monitor proxyName is not the default name, the notification
    type must be the monitor proxyName.
    IResourceList methods addResource and addResources have a
    changed signature, to include an arg that references the
    monitor instance. Existing usage that passes an IResourceList as
    the data arg to the monitor constructor must change to (null,data)
    since data is now the second optional arg, proxyName being the
    first. IResourceList has new method isToBeKeptOpen.
    IRetryParameters has a new parameter, to switch on exponential
    backoff logic when RetryPolicy applies the retry interval.
    Users of the assetLoader facility, note the following:
    - LoadAssetGroupCommand and LoadingInstructions have been
    frozen in their pre-v2 state, and will not be updated; retained
    only to maintain backward compatibility
    - new version of StartupForAssets demo (version 2).

Note also that, though this utility is named Startup Manager, a more appropriate name might be Resource Loading Manager, since it can be used at any time, not just at application startup.

I need to take another look at the class to see how I can push elements that are being added through the "AddSubCommand" method.

Just to be clear, in my post above that refers to getResources and the array of StartupResourceProxy objects, I intend this as a read-only activity; each new resource must still be added using one of the addResource methods of StartupMonitorProxy.
----Philip

Does it help that you can, at any time, use the getResourceList() method of StartupMonitorProxy to get the IResourceList object that contains the StartupResourceProxy objects, and getResources() on that returns an array of the StartupResourceProxy objects?
----Philip

ok, so one possibility is...
- a mediator instance per category, with a mediator name that is same as asset group proxy name
- a popup thumbnails component instance per category; maybe it doesn't have to be a popup, but maybe you want it to be, so whatever you choose.

another possibility, closer to your existing approach, is...
- when you change back to a previous category, the mediator needs to know this; via a notification if needs be, say we call this 'redisplay'
- in mediator, on redisplay, get all the loaded assets from the relevant asset group proxy (via getData() say) and add them to the mediator's view component.

Or maybe you can see other better approaches now.
----Philip

maybe you

I'm sorry. I don't understand the question.

Is there a separate ThumbnailsMediator instance for each category?  When you change back to the previous category, are the thumbnails displayed?  Is each category treated as a separate asset group with it's own AssetGroupProxy instance?

The NEW_ASSET_AVAILABLE notification has the the asset group proxy name as notification type.  This can be used in the mediators to determine whether a notification is relevant.

Hope this helps.
----Philip

bitmap datas should be in SlideShowProxy

Maybe have a reference to the AssetGroupProxy in SlideShowProxy, and give SlideShowProxy accessors to the bitmap data.
----Philip