Sebastian Moors wrote: > Hi! > > Gabriel M. Beddingfield wrote >> OK, first idea: utilize a client/server model. Whenever a client (UI) >> starts up... it looks to see if there's already a hydrogen server running. >> If not... it starts one. The user never knows. >> >> If there *is* one running, ask the user: connect to running hydrogen, or >> start a new one? [1] >> >> If a client (UI) connects to the running hydrogen... then both are live >> editors on the real hydrogen server. They can even be in the same view >> editing the same pattern. >> >> If they start a new one... then they have a separate, independent h2 >> session that doesn't interfere with the first session. >> >> Upside: very extensible, very clean, enforces MVC, scales according to >> user's computer resources, client/server could be on different computers. >> >> Downside: No multi-window session management. >> > We could try to use a second window i ( like the mixer in 0.9.4 ) for > the main program. I mean just another window, not another application.. > Otherwise it would be hard to exchange data between those widgets. Or > did you want to avoid this design? The second panel would act only as a > container for widgets and could be enabled via a button. That would save > us the client/server overhead.
I tend to agree with Sebastian. Unless there's a strong feature need for client/server, I'd recommend avoiding it. Implementing the client/server protocol and keeping the call versions synced adds a lot of complexity. The use I can see for it is client and server on separate machines, which personally I don't care about, but might be something other people really want. Dave > - Sebastian > >> ------------------------------------------------------------------------------ >> Come build with us! The BlackBerry(R) Developer Conference in SF, CA >> is the only developer event you need to attend this year. Jumpstart your >> developing skills, take BlackBerry mobile applications to market and stay >> ahead of the curve. Join us from November 9 - 12, 2009. Register now! >> http://p.sf.net/sfu/devconference >> _______________________________________________ >> Hydrogen-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/hydrogen-devel >> > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > Hydrogen-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/hydrogen-devel ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Hydrogen-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hydrogen-devel
