I am in favor of moving ahead with this plan if it's mostly
just
moving stuff around. I.e., doesn't take us too far out of
our .3
(er, .5) plan due to major architectural changes.
On Aug 21, 2006, at 1:43 PM, Matthew Eernisse wrote:
> Here are the notes from our whiteboard session on
Tuesday:
>
> Client app
> * UI
> - Events
> - Dialog
> - i18n
> * View
> - Calendar
> + Canvas
> + Conflicts
> * Session management
> * Data services
> - Remoting
> - Local
>
> I don't know if it helped everyone else, but I found
it
> tremendously helpful in getting concrete direction on
the immediate
> refactoring work for cal_main.js, as well as getting
closer to a
> shared understanding of the architecture for the
client-side code
> that we should be moving toward.
>
> Unless there are specific technical objections, I'm
going to take
> the first step to getting us where we want to go,
working in
> cal_main.js according to the above outline -- starting
with the
> calendar canvas and conflicts.
>
>
> Matthew
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev
_______________________________________________
cosmo-dev mailing list
cosmo-dev lists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev
|