On Sat, 24 Oct 2009, Sebastian Moors wrote:
> That would allow that someone who works on a Netbook could work just
> with one widget at the time, but people with a 24" tft can work with
> more widgets ( like sequencer + instrument rack) at the same time..
> Maybe we can even extent the idea and allow it to spawn a second
> "widget-container window" on a second screen.
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.
-gabriel
[1] Naturally, this dialog will annoy "power" users... so we
can have a user pref. to avoid the dialog.
------------------------------------------------------------------------------
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
