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]
|
1
|
PureMVC Manifold / Multicore Version / Re: Real World Examples of the Native JS port
|
on: May 08, 2012, 12:30:44
|
This looks great! What kinds of developer tools are people using in the real world for PureMVC projects? I'm looking for tools like auto complete and live error checking. I see in this examples that there are comments that look like they do compile time type checking. What tools are you using for that?
Thanks for the insight, Jon
|
|
|
2
|
Announcements and General Discussion / Architecture / Dynamically created mediators and proxies?
|
on: March 09, 2009, 02:58:39
|
I'm making a type of image editor with layers and the like that can move, scale and rotate. They will need to created or loaded, edited and saved. A problem I'm running into is that I don't know how to manage the layers.
The editor could be viewed in at least two ways:
1. "model data" that describes the "view components" that needs to be displayed. 2. "view components" that need to be recorded as "model data"
Ether way I feel like the two are tightly coupled. And It feels like I'll need to dynamically create mediators and proxies. Any sort of direction would be of great help.
|
|
|
3
|
PureMVC Manifold / Demos and Utils / Re: StateMachine - A PureMVC / AS3 Utility
|
on: February 10, 2009, 02:41:24
|
Cliff, I think I understand. I noticed in the Stop Watch Demo that the state names are references to the something like StopWatch.STATE_FOO.
Are you indicating that If I'm not using flex that I should define the state names in the xml? It seams that I would want to be able to Reference them elsewhere in the app. So should I Define those constants in the facade or in a component or the mediator or the Main???
|
|
|
|
|
|