Build an excel like application

[koirsm]

Hi, this is my first post here.
I'm playng with puremvc a bit and I want build an application Excel like in AS3.
User create a selection on an "fluid" grid (24x24) with scrollbars: every time the user draw a selection, the system prompt (or not) a configuration window for cutomize with colors the selected cells.
I don't want draggable rows and columns (for set rows and columns width) but I have to build a shits navigation system.

Some questions:

1) standard puremvc or multicore?
2) some advice on how to implement it? 

[koirsm]

Ok, I'm traying some approach by myself

Starting from this great example http://hubflanger.com/building-a-flash-site-using-puremvc/ I reuse the facade, controller and first view creation.
Now I want manage the fluid behavior of GUI, so the grid and other Component can be adaptable to the user monitor.
I create 1 mediator for every component that also implement a simple interface with a method that get a component istance and return the avaible space for that component according to Stage dimension.
The mediators send to views the coord and the view do the redraw.
I use a proxy class to store dimension and position of Components and register Component's Mediators to listen for Proxy internal VO changes.

Everytime the stage is resized:
- Proxy notify to facade that data is changed
- Components Mediators is listening for that changes
- Mediators tell to views how they have to behave

Am I totally wrong?


 

[puremvc]

What responsibilities does IPositionManager add to the mediators?

-=Cliff>

[koirsm]

I want use BoundManager (sorry for the wrong Interface's name) to get final width and height of a Component (view) for redraw process.
The Mediator initialize a BoundManager passing the Component, and the BoundManager return width and height to Mediator as Object.
Mediator send Obj to view.

Txs.

[puremvc]

Can the mediator not inspect the width and height of its own view component?

-=Cliff>

[koirsm]

Mmmm...yes of course.
I can:

- register a proxy (guiProxy) at startup and create an object to store component's id, width, height, isResizable, ecc..
- keep the component mediator clean and register only a notification about guiProxy changes
- move the redraw logic in the view by implementing interafce

Now, if I'm not wrong:

- user --> stage resize
- facade listen stage resize
- facade dispatch event for proxy
- proxy listen the event and change guiProxy data
- mediator listen for proxy changes and notify to view
- view call an Interface method to get final position/dimension
- view redraw

is it correct?

[puremvc]

Why does a Proxy need to become involved in keeping View-related information such as component id, width, height, etc? The component keeps its own info. Unless the Domain Model being persisted is coordinates and component details, the Proxies should never have to traffic in View details.

-=Cliff>

[koirsm]

Ok, so I've to keep the logic of resize inside views and only register mediator for listen to resize notifications.
Right?
I've found a post in general forum about this...
I'm sorry for wasting your time..
Txs.

[puremvc]

Yes, best to encapsulate as much of the view component's behavior as possible.

Not a problem with the questions. It takes a while for everything to find it's place in your mental picture of an app based on PureMVC (or any framework for that matter). When it all clicks, you can move like lightning, though, because you're not stopping every 5 minutes wondering 'now where does this thing go?'.

-=Cliff>