I mean that the GUI/core separation would be good for: 1. skills separation and thus for development efficiency 2. resources consumption (allow to let only the core running as in MLDonkey)
At first I propose to develop a frontage library with the same development conventions than GTK-G ones. The current GUI would continue to interact directly with the core and ignore this frontage. The favour of this frontage would be the support of the current GUI until the other design is fully implemented. Then I could develop a simple server which uses this frontage and link the current GTK-Gnutella gui to this server. One scenario could be the following. When launching the GTK-G gui the first time, it launches the core and its server and then connect to it. When closing the GUI, the core still run. The next time the gui is started, the gui detects it and connect to it again. ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Gtk-gnutella-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
