#1 split core and gui

[Anonymous]

Hi. Excuse my english, I don't speak good english.

First of all thanks for lmule. I like it. It really
works fine but I would like to run lmule in background.
I think that it would be nice to run the core and
connect to it with the gui.

[Nobody/Anonymous]

Logged In: NO

I absolutely agree with this. I'd love to have the core
running on my headless router while connecting with the
(fabulous!) GUI from different machines in my LAN, similar
to mldonkey. Are there any plans about that or is it a clear
"won't be implemented"?

[Ted R. Smith]

Logged In: YES
user_id=23127

This is technically impossible for one MAJOR reason.

While wxWindows supports console-based applications,
unlike Qt or GTK, you must specially compile a special wx
library for console applications. Threading works totally
different too, at least it did back in the 2.3.x days.

In short, doing this would be infeasible. Might be a console
trick (like redirecting --display to /dev/null or something) that
you could do.

[Honoré David]

Logged In: YES
user_id=616425

Splitting core and gui look a pretty good idea but is not
essential. But web control can be great.

Tips :
--------
juste start lmule on a Xvnc server

#!/bin/bash
vncserver :2
DISPLAY=:2 lmule
vncserver -kill :2

to connect : xvncviewer -passwd ~/.vnc/passwd :2

to improve security you can allow only localhost connection
(default option) and use SSH tunneling features.

[Nobody/Anonymous]

Logged In: NO

I prefer splitting core and gui than using a Xvnc server.

Then I could close my graphical session (gnome for example)
while lmule is running. And take it later when I log in again.

[Mikael Bouillot]

Logged In: YES
user_id=310883

In reply to un-thesis's comment, I don't see why you would
need wxWindows linking for the core. Is this library used
for other services besides GUI? the core would need no GUI,
thus it wouldn't need to be linked to wxWindows... Correct
me if I'm mistaken.

[Nobody/Anonymous]

Logged In: NO

Aye, a command line only -option would be very nice.

[Ted R. Smith]

Logged In: YES
user_id=23127

<quote>

In reply to un-thesis's comment, I don't see why you would

need wxWindows linking for the core. Is this library used

for other services besides GUI? the core would need no GUI,

thus it wouldn't need to be linked to wxWindows... Correct

me if I'm mistaken.

</quote>

Goddammit1!!!

Read up on wx!! Look at the xmule code !or the header fiels!

Every goddamn file except for the 2 pure gtk ones (which
negate the use of wx any way) use wx. Wx is used for
sockets, threading, etc etc etc.

Thus it is very very unfeasible to break the gui from the base
sockets functionality in lmule. You would have to, literally,
start basically from scratch and use a completely different
cross-platform socket/threads library.

I'm actualy in the process of doing this for xmule 2.0

Un

[Ralf Hagen]

Logged In: YES
user_id=736283

I think that would be a VERY good idea!
I tend to leave an Cyrix 6x86-Gateway always on, a machine
where there's no XFree installed. It would in my opinion be
perfect to let a core run on that machine, while an eMule or
lMule GUI, better yet an Web-Based frontend, connects to it
via another computer in the LAN.
(Here in Europe, electricity is not cheap, so we try to
economize on it.)

[Nobody/Anonymous]

Logged In: NO

stupid

this is being implemented in xMule Pro

http://www.xmule.org/ the successor lmule.

[Ralf Hagen]

Logged In: YES
user_id=736283

OT:
To: nobody, 11.07.2003, 22:45 ??T

Thanks for the clue.

But could we PLEASE stay civilized here?
We're not at the heise.de-Forum. TNX.

-=