Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[fabtar]

It' ll be very nice to see screenshots of Amule remoteGUI (and of webgui too) in the screenshots Area to understand how these interfaces looks like.
Useful for guys evaluating amule first of installation.
Cheers

[TripleM]

It' ll be very nice to see screenshots of Amule remoteGUI (and of webgui too) in the screenshots Area to understand how these interfaces looks like.

the remote gui looks the same like the monolithic application. the only important difference at the moment is, that it doesnt show that much information, like in the monolithic, cause the ec-protocol doesnt transfer all information in its current state.


so long,

[anybody]

Smo's Windows Binary Builds are now available here for your downloading pleasure:

The amulegui.exe file is rather big (70M), therefor i'm providing ZIP as well as RAR Packages:

amulegui.zip (11MB)
amulegui.rar (7MB)

I wasn't able to connect to my 2.0.3 amuled, but i guess thats because i need CVS ;-) I will try that soon.

[fabtar]

The executable are quite big  8o. Have They  linked the wx enviroment??

[TripleM]

The amulegui.exe file is rather big (70M), ...

I wasn't able to connect to my 2.0.3 amuled, but i guess thats because i need CVS ;-) I will try that soon.

that's really strange. i have build a cvs amulegui myself, and this is only 7,89M in size, which is quite big for a remote gui, but not that big, like your version.

and cvs-versions of amulegui can only connect to the cvs-version of the amuled from the same day, cause they use some kind of date-tag in the ec-protocol.

at least you CANT connect with a cvs-remotegui to a release-amuled.

so at the moment it is not entirely sane to build and share a gui-binary, if you dont provide the proper amuled.



so long,

[GonoszTopi]

and cvs-versions of amulegui can only connect to the cvs-version of the amuled from the same day, cause they use some kind of date-tag in the ec-protocol.

at least you CANT connect with a cvs-remotegui to a release-amuled.

True for all EC applications. You CAN NOT connect a cvs version of remote gui to a release version of amule(d), and vice versa, it doesn't matter which CVS version we're talking about. CVS versions also introduce some sanitiy testing on the EC protocol in order not to crash your application. This test used to use the tarball creation timestamp, but newer versions use another kind of test to see if there is any incomatibility in the protocol. So, with newer CVS versions it is possible to connect two applications from different tarballs, provided that EC didn't change between that two tarball (which is likely to change very often). And, uh, under the word "newer" you should think of tarballs later than 2005-08-07.

so at the moment it is not entirely sane to build and share a gui-binary, if you dont provide the proper amuled.

I totally agree.

[smo]

Hey everybody,

I just want to give some feedback about the aMule remote GUI for Windows. I tried aMule-CVS-20050815.tar.bz2.

- Nice, I really like the idea of having more features and faster refresh than with amuleweb. Compiling works without any problems except the fact that the resulting exe is about 64,3MB using "./configure --enable-amule-daemon". What does the option "--disable-monolithic" do?

- The gui is really "slow". Feels like I'm using it over a slow vnc-connection. For example it isn't easy to reseize the columns in "Transfers"-view, because it takes some time till the gui reacts on my mouse actions. Seems that the screen is only updated when new data from the server is received (every second?)?

- The gui is unstable. It crashes with a "Runtime error" if I'm using my mouse in an aggressive way (fast change "views", click around on some colums for sorting). Should I recompile with some debugging-options to get more information? If yes, how should I do that?

I know, that it is not a release and so it is not supposed to be stable, but I just want to tell you my experiences. So: Thanks again for a working windows version of the remote GUI.

smo

[Mr Faber]

If you use --disable-monolithic aMule isn't compiled within. The huge file size comes from debug compiling. Just use --disable-debug.

cu
Mr Faber

[lfroen]

- The gui is really "slow". Feels like I'm using it over a slow vnc-connection. For example it isn't easy to reseize the columns in "Transfers"-view, because it takes some time till the gui reacts on my mouse actions. Seems that the screen is only updated when new data from the server is received (every second?)?

Seems like windows version of wx have slightly different event model that gtk one. Since I still didn't succeded to compile it on windows i'm not really debugging it. Btw: is wiki page about windows compilation is up2date ?

[smo]

If you use --disable-monolithic aMule isn't compiled within. The huge file size comes from debug compiling. Just use --disable-debug.

Thanks! Using both options my file is about 8,3MB now

smo

[GonoszTopi]

Btw: is wiki page about windows compilation is up2date ?

Yes.

[bigdady]

I compiled the gui, added the dll file and rared it so you can get it here and it is not too huge around 2MB (aMule-CVS-20050823)
http://freeweb.siol.net/msubel1/amulegui.rar

[BeFalou]

Thanks bigdady for the rar & amule devs for amulegui :-)

EDIT: It only ran once and now I can't start it anymore. Should I send a report to MS? ;-P

[m0l0c0]

Hi, i´m a new user , and i have download the upx compress in  http://upx.sourceforge.net/ and the size of the amulegui is now 4.494k and working ok, see  :rolleyes: :

upx --best amulegui.exe

     File size         Ratio      Format      Name
--------------------   ------   -----------   -----------
8778006 ->   4601110   52.42%    win32/pe     amulegui.exe


Bye

Sorry for my bad english , I from Brazil.