RE: Main screen ideas 1of2

> >The main window object will loose all of it's phone
> code, it will 
> >only provide the splitter frame, tree view and
> routing for menu and 
> >toolbar events, it will create a phone object to
> add to the root of 
> >the tree.  The tree view will contain a root node
> representing a 
> >phone object.
> 
> That's a significant departure from the current
> BitPim design, which has been thoroughly tested, all
> for a new GUI.  Any advantages of this approach?  If
> you want to pursue this, I'd suggest creating a new
> branch and go at it.

The main advantage will be to allow multiple phones to
be displayed at the same time. The worker thread would
not be moved, I am only thinking about moving the
database and configuration related stuff. 
This does raise the question of how a user would
choose which phone data to send to their phone if
there was more than one phone data available, there
would have to be some way of specifying the active
configuration.

Simon



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642