Futurescale, Inc. PureMVC Home

The PureMVC Framework Code at the Speed of Thought


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

* | |

  Show Posts
Pages: 1 2 3 [4] 5 6 ... 17
46  Announcements and General Discussion / Getting Started / Re: notifications, commands and mediators on: July 13, 2009, 09:17:48
I tended to put my note names in a *Constants.as file to keep them out of my Facade. I also put all the notification constant names that a Proxy sends in the Proxy itself so they stay self contained and reusable, without having to drag along the *Constants.as file when reusing them.

It also creates a clear distinction when showing interest in a notification from a Proxy (ie: DataProxy.DATA_READY instead of ApplicationFacade.DATA_READY). The proxy is the only one likely to send such a notification so it makes sense to have it in the Proxy itself. A DATA_READY note send from a different proxy or a command would likely hold a different meaning/data then the DataProxy.DATA_READY note.
47  Announcements and General Discussion / Architecture / Re: Tool and Canvas Architecture on: July 10, 2009, 09:25:48
If I'm not mistaken, I believe his "tools" are simply components, not cores. Hence my suggestion of putting them in subfolders of view ONLY if he has a lot of views and wants to organize them.

Otherwise, despite the naming of commands as controller, I use the same setup as you Cliff for MultiCore projects.
48  Announcements and General Discussion / Architecture / Re: Tool and Canvas Architecture on: July 10, 2009, 07:57:40
My typical structure is:

APP
+--commands
+--constants
+--model
    +--vo
+--view
    +--components

You could add a tools folder under the components directory. I usually sub divide up my View folder into multiple folders if I have a lot of views.

Example:

view
    |--Main view mediators here
    +--components - main view components
    +-- tools
        |--Tool Mediators Here
        +--components - Tool Components Here
   
49  Announcements and General Discussion / Getting Started / Re: StartupCommand can't see view component on: July 09, 2009, 08:22:50
Where are you calling init() from? You should be calling it on the ApplicationComplete event so that you can ensure Flex has finished it's creation sequence. My guess is you are sometimes beating out Flex and starting the PMVC apperatus too early.
50  Announcements and General Discussion / General Discussion / Re: Reusing components as subcomponents / dynamic mediators on: July 07, 2009, 01:14:53
Demo and view source are dead links.
51  Announcements and General Discussion / Getting Started / Re: Stage resizing on: July 06, 2009, 08:22:27
There is only ever one stage in a flash application, regardless of how many modules/SWF's are loaded. THey all point to the same "root" stage.

Just have your components/modules listen for the ADD_TO_STAGE event and then have them register with the stage for the resize event. This ensures you have access to the stage before trying to add an event listener to it (otherwise it'll throw an error if you do it before the stage is available). It's also a good idea to listen for when components are removed from the stage and have them remove their own stage event listeners for good clean-up.
52  Announcements and General Discussion / Getting Started / Re: Stage resizing on: July 06, 2009, 06:07:47
Resizing is definetly a function of the view component. There shouldn't be any "logic" in your mediators. I'd also recommend having a view component listen for stage events itself, rather than dispatching an event through PMVC. All components on the display list have access to the stage to add event listeners to.
53  Announcements and General Discussion / General Discussion / Re: Memory management and garbage collection on: June 30, 2009, 01:27:50
Yeah, I'm more referring to wierd obscure things like, for instance, 150 instances of Class, 780 instance of Function, and 1052 instances of Object that all refer to ApplicationDomain. All the path info says is:

:
[newclass]()
    global$init:global$init()
    flash.system:ApplicationDomain:flash.system:ApplicationDomain()

I have no clue how to use this little bit of useless info to determine why I have so many ApplicationDomain instances... should I even worry?

There's very little info out there about how we should treat these items (Object, Class, String, Function). Should I worry about increasing instances of these base types? It doesn't seem to push my memory up much but the instances DO keep increasing as I click around in my app.

PS: This is more to do with a Replace Current scenario then a Create and Destroy one. See http://blogs.adobe.com/aharui/profiler/ProfilerScenarios.swf
54  Announcements and General Discussion / General Discussion / Re: Memory management and garbage collection on: June 30, 2009, 06:16:24
The thing I still struggle with, and can't seem to find really solid info on, is the proper use of the Profiler in Flash/Flex Builder. Sure, I know the basics, but I constantly feel like I'm missing something important about how to properly read all that info. I wish I could find that one article (or series) that gives me an "aha!" moment with regards to the Profiler.
55  Announcements and General Discussion / Public Demos, Tools and Applications / Re: flex poker on: June 28, 2009, 07:58:46
Very nice! I actually found it quite addictive. I'd love to see how you put it together.
56  Announcements and General Discussion / General Discussion / Re: Using MacroCommand with StartupResourceProxy utility on: June 24, 2009, 11:14:44
I might have misslead you, when I said SM I meant the StartupManager, not StateMachine.

Or are you starting a different discussion concerning the State Machine now and not the start-up Manager (damn acronyms are confusing lol).
57  Announcements and General Discussion / General Discussion / Re: Using MacroCommand with StartupResourceProxy utility on: June 23, 2009, 06:01:22
I've used the SM with macro commands before, it works almost exactly the same (except you need to grab an instance of the SM in each command.

Where are you having trouble? I usually have my first macro command set-up the initial SM and then each command add what it needs to it. Then the last macro starts the loading process.
58  Announcements and General Discussion / Public Demos, Tools and Applications / Re: Flex modules with PureMVC pipes simple demo on: June 19, 2009, 01:00:45
It's the lastest version of FF. I do have Firebug but it is not turned on for your website. It happens on your homepage as well. Everytime it locks up Firefox about half way through loading the page.

UPDATE: Tried disabling Firebug and it still happens.
59  Announcements and General Discussion / Public Demos, Tools and Applications / Re: Flex modules with PureMVC pipes simple demo on: June 19, 2009, 06:15:10
Everytime I try to load your website it kills my firefox. Seems to work fine in Chrome. Just an FYI.
60  Announcements and General Discussion / Public Demos, Tools and Applications / Re: Edoboard advance whiteboard for Math: PureMVC AFCS Degrafa on: June 18, 2009, 08:38:40
Now I wish I had paid more attention in French class.  Looks great!
Pages: 1 2 3 [4] 5 6 ... 17