|
I'm building an Air application with multiple pages/sections. For simplicity, let's just focus on two of the sections: Contacts and Events. The contacts "page" will have a list of contacts that, when clicked, pulls into a detail view for that contact. The detail view has a list of events that contact is going to and a todo list for that person. The events page will work in the same way, but with a list of contacts attending and a todo list for the event.
To me, it seems like each page should have it's own core given their complexity and so I can develop them separately or so I can have another developer create the events page while I create the contacts page. I'm having trouble figuring out how to orchestrate this. All of the content has to be pulled from a common database and each of the pages needs info that is specific to the other page.
It doesn't make sense for the contacts page to have an "events proxy" that gets a list of events and for the events page to have essentially a duplicate proxy with the same functions. This is where I'm getting stuck:
1. Should they all be able to access common proxies within the ShellFacade to interact with the database? So the contacts page can pull info from the events proxy (notifications)?
2. I'd rather keep all events logic within the events page and somehow communicate between the two. For example, the contacts page could ask the events page for a list of events. But this feels like they are too tightly coupled.
3. I'll need to be able to add another page down the road that pulls from info from either section as well.
Any direction is much appreciated!
|
Show Posts
