Print

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

[juanii]

how about compiling a list of every option which can be included in .eMule? just got amule working without gui and i can't configure it because i have no idea how options are called and by now amuleweb doesn't include all options. i found some info on the wiki page and the forum but i thought of a list explaining all of them (something like mldonkey's wiki ). i can collaborate if any help is needed.

[Jacobo221]

Sure, feel 100% free to do that page
There's an aMule wiki already with almost any info needed, allthough it's true it lacks the explanation of the ~/.eMule file and it's maybe really needed
http://wiki.amule.org
Thanks for your contributions!!!

[juanii]

Originally posted by Jacobo221
Sure, feel 100% free to do that page

well, my first thought was "where can i find that info?" and after reading your message i figured it out: "the sourcecode!"
now, i have made an extensive list extracting all options from Preferences.cpp. some are really easy to describe and other just doesn't give any idea of what they do. i won't trace sourcecode to see what happens when some strange variable is set to true or false so my next question is, where can i ask to put some light on this?

Originally posted by Jacobo221
Thanks for your contributions!!!

it is always a pleasure to contribute!

[lfroen]

where can i ask to put some light on this

Please join #amule and talk to Xaignar.

However, I see no point to adding explanation about config file contents/format to wiki. This file is not supposed to be manually edited.

Webserver and page will be fixed (quite soon )  to include all options available.

[phoenix]

Originally posted by lfroen
However, I see no point to adding explanation about config file contents/format to wiki. This file is not supposed to be manually edited.

Why not manually edit? Whats the point of beeing a text file then?

Cheers!

[Jacobo221]

You can ask Kry about the options you don't know what they are or just leave them there un-explained so someone (maybe me) will fill them

lfroen: documentation is never pointless. never ever

[lfroen]

lfroen: documentation is never pointless. never ever

Wiki is not a place where you should explain coding details. It's a place where user of the program is looking for help.
It perfectly OK to put explanation about config file format into "doc" directory on source tree.

Remark:
Users should NEVER read documentation anyway. If you find yourself in situation when you suggest to user "go to docs" - rething GUI design again.

[Kry]

The more complete is the wiki, the better.

The wiki is a place where people can find info, ANY info, and it's freely editable by users. So, lfroen, let them do a explanation on .eMule if they feel like. And avoid your *BSD/Solaris/ rants.

Ah! And ye, ask me any question about any preferences option