Over 10 years of community discussion and knowledge are maintained here as a read-only archive. New discussions should be taken up in issues on the appropriate projects at https://github.com/PureMVC
|
|
|
Show Posts
|
Pages: 1 [2] 3 4 ... 10
|
16
|
PureMVC Manifold / Demos and Utils / Re: Loadup - A PureMVC AS3 Utility
|
on: February 12, 2010, 05:33:53
|
@Ross Thanks for this work. It should be a great addition to the utility. I will incorporate it into a new release as soon as I can. I expect the release to also include support for flv type files, based on work contributed by another forum member, and it should also address the flash-only requirement as dealt with previously on this forum. ----Philip
|
|
|
17
|
PureMVC Manifold / Demos and Utils / Re: Loadup - A PureMVC AS3 Utility
|
on: February 11, 2010, 04:35:20
|
I presume the key factor here is the loader class. You don't mention the AssetFactory /IAssetFactory class and interface.
By default, a file with extension .mp3 will get treated the same as a text file, since there is no specific recognition of the mp3 file type. Hence, by default, the file will get loaded by a loader of type URLLoader (see AssetFactory and AssetTypeMap).
I note that the Sound class itself has the facility to load mp3 files, so maybe the Sound class must be used as the loader. This would require a new loader class in Loadup, using Sound, and implementing the IAssetLoader interface.
No doubt there are others out there that can comment more knowledgeably on this requirement. ----Philip
|
|
|
18
|
PureMVC Manifold / Demos and Utils / Re: Loadup for Assets - A PureMVC AS3 / Flex / Loadup Utility Demo
|
on: January 11, 2010, 04:45:31
|
@myIP You could let the completion of the first group of assets be as in the demo, with removal of the progress bar and the load button and the other cleanup stuff. And let the next group be a totally new, independent load, for example - the new loading instructions would/might specify a new instance name for the loadup monitor, but see below - the new loading instructions would specify a new instance name for the new asset group proxy - add a new load button, with a label that describes this particular group of assets - and so on - however the test of note type at the top of handleNotification would now have to be aware of which monitor was current.
----Philip
|
|
|
20
|
Announcements and General Discussion / Getting Started / Re: Managing a lot of Proxys and Mediators
|
on: December 14, 2009, 04:19:38
|
It have not to listen to the LOADING_COMPLETE but the LoadupUtility dispatchs the Notification twice. First, when the data is loaded and second, when the images are loaded. If there is a question about this Loadup behaviour, I have a comment that relates to notification type. But best to keep that stuff to the Loadup thread as Cliff says. ----Philip
|
|
|
23
|
PureMVC Manifold / Demos and Utils / Re: Loadup - A PureMVC AS3 Utility
|
on: November 18, 2009, 04:46:14
|
Since my previous post, it has occurred to me that... - the intermittent, ad hoc product loads could also be done with a single instance of LoadMonitorProxy, where keepResourceListOpen() is invoked - then, as required, a product resource can be added to the monitor; it will be loaded as usual - there will not be a loading complete notification until closeResourceList() is invoked and all outstanding resources have been loaded.
Just thought I'd mention it. ----Philip
|
|
|
24
|
PureMVC Manifold / Demos and Utils / Re: Loadup - A PureMVC AS3 Utility
|
on: November 17, 2009, 05:14:52
|
This is not a response to the state machine query, just a comment regarding LoadupMonitorProxy.
If I understand correctly, it seems that there are separate Loadup sessions - one for the ProductCatalog load and one for each Product load - but using the one LoadupMonitorProxy instance. Instead, if you use separate instances of LoadMonitorProxy for these, then - you can have concurrent retrieval of more than one product - the loading complete notification will have the instance name in the type, hence differentiating the different contexts.
However, I well recognise the role the state machine can have in overall management of this. ----Philip
|
|
|
25
|
PureMVC Manifold / Demos and Utils / Re: Loadup for Assets - A PureMVC AS3 / Flex / Loadup Utility Demo
|
on: November 13, 2009, 04:37:07
|
Kouri, If the LFA demo code is a good match to a real application requirement, then great. I don't have doubts about reliability of the code.
As regards the group classes in the demo, are they not a closed set, so that they can all be dropped without compromising the handling of single assets? Is there a cross-over that I'm missing?
Nice to see the translation - well done. Bon Chance! ----Philip
|
|
|
27
|
PureMVC Manifold / Demos and Utils / Re: Loadup for Assets - A PureMVC AS3 / Flex / Loadup Utility Demo
|
on: November 12, 2009, 05:02:19
|
In addition to dropping GroupOfAssets.mxml, I think you would drop several other classes, including GroupOfAssetsMediator and LoadAssetGroupCommand and LoadAssetGroupInstructions. I hope I'm not missing something. Let me say some general things, by way of trying to be helpful, even if you know it all already - The basic or core Loadup utility offers functionality that provides nothing special for assets; the loadup as ordered demo (lao) is intended to demonstrate this basic functionality
- Loadup also includes an asset loader suite of classes, to make it easier to use Loadup when loading assets; these asset loader classes act as a client of the basic utility; they interact with the basic functionality
- the loadup for assets demo (lfa) is intended to demonstrate how to use the asset loader classes; lfa uses a subset of the basic Loadup functionality (not the typical use), and it has the complication of also using the asset loader classes
- hence, lfa is not the best way to learn the basic Loadup functionality, but it is good if you just want to load assets
- the lao demo wants to demonstrate the basic functionality, with asynchronous retrieval of resources being a key requirement; it avoids the baggage of actual retrieval, such as database access, by simulating the asynchronous retrieval
- these demos are intended to exercise and illustrate the utility; they are not primarily intended to be templates for real application solutions; the lao demo probably does not have much code that could be directly reused; the lfa demo is probably much better as regards sections of code that could be directly reused.
----Philip
|
|
|
30
|
PureMVC Manifold / Demos and Utils / Re: Loadup - A PureMVC AS3 Utility
|
on: October 05, 2009, 10:12:14
|
In the case you mention, from LoadUpAsOrdered demo, the line of code is
var rCus :LoadupResourceProxy = makeAndRegisterLoadupResource( CustomerProxy.SRNAME, cusPx );
Note the first argument is CustomerProxy.SRNAME as opposed to CustomerProxy.NAME. That's what I mean. ----Philip
|
|
|
|
|
|