mldonkey, a multi-networks file-sharing client - Tasks: task #5382, un-hardcode webgui
You are not allowed to post comments on this tracker with your current authentication level.
task #5382: un-hardcode webgui
Submitter: | Joakim Verona <jave> | ||
Submitted: | Thu 06 Apr 2006 10:03:42 AM UTC | ||
Votes: | 100 | ||
Category: | None | Priority: | 1 - Later |
Status: | None | Assigned to: | None |
Open/Closed: | Open | Should Start On: | Thu 06 Apr 2006 12:00:00 AM UTC |
Should be Finished on: | Thu 06 Apr 2006 12:00:00 AM UTC |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 100 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2008-01-21 | azmeuk | Carbon-Copy | - | ![]() |
Added azmeuk |
The webgui is pretty much hardcoded within the mlnet binary.
It would be useful decouple this a bit, for obvious reasons.
This is a large task, but here are some ideas, in order of difficulty:
- the various links to external services, for instance fake check buttons, etc, can be placed in a ini file, just like "web infos".
there would then be a syntax within the external url:s so they can contain variables to be interpolated before calls.
for instance: http://fakecheckservice/$ed2khash$.
this and other urls would then appear on the filew view, user configurable.
- templating system
for instance, ocamltemplate can be used to get the html out of the binary into template files.
a benefit is that people with html templating skillsets are much more common than people with ocaml skillsets, so wew could get more contributors.