>> > Nodeconfig is majorly broken. It needs to be fixed in such a way to be >> > updatable easily (allowing for easy conversions between moving config >> > options and such). I never figured out a good way to do it. >> >> Why not use GTK or somesuch, and simply add each option, allowing GTK to >> organize the options? You could have freenet export a list of options at >> startup in an easily-parsable form (XML?). > > It does - kinda. Try running it with the "--manual" command line option.
That would be a good starting point but there's a lot of aesthetic information required if an ok-for-Windows-users-to-use UI is to be generated from a parsable output. If you've seen Nodeconfig you'll know what I mean - it's not just a multi-paged dialog with lists of options. We would need a basic specification language to organise the options ourselves rather than have the interface elements organised automatically. If there's any simple tools to do this on Windows information would be greatly appreciated! d _______________________________________________ devl mailing list devl at freenetproject.org http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl ** Classified by CRM114 SS as good ** Probabalistic match quality: 0.000000 P(succ): 1.135939e-313, P(fail):1.000000e+00
