Dave Hooper wrote: > Technically, I'm back from my holidays.
Great, hope you had nice holidays. > Are you setting up the registry to call > freenet -insert %1 > or > freenet -insert "%1" I planned setting it to "freenet.exe -import "%1"" It would be terrific, if a file chooser dialog would pop up, to let you choose a dialog if one would omitt the filename and just call "freenet -import" (see also import/export below) > What is the command line syntax to FServe now? (I assume it's been changed > since I last used it, I don't remember the --seed command, and I haven't > played with any of Freenet 0.4 yet...) Not much changed, except that the --seed command needs to be issued once to import a .ref file (initial node reference), that is information about how to contact the first freenet nodes (including their keys). I'll try to do that automatically during install, but people should be able to include references into their routing table lateron. This is what the "freenet.exe -import" thing would do. It would call "fserve --seed <filename>" Thinking of it, do you think it would be possible to do the -import thing on a URL as well? Like having "-import http://freenetproject.org/seed.ref"; importing that via the Net? Mmmh, just a thought. > Are people still using FProxy or has David McNab written a better / > different alternative? If so, does it need integrating into the systray > icon application? A new FProxy is on the way, until that has happened we use Davids McNab's FcpProxy.exe, I am not sure, if/how it should be started automatically with the node. In the long run this won't be necessary. > If not, then I think the main next important things to do are: > o Inform the user when the node is running but fproxy isn't Right, that might be a nice thing to do > o Inform the user when their connection to the internet drops / comes > back (especially useful for dialup freenetters) Sounds good > o A proper configurator Sounds good. I plan on replacing the tools I use for configuration with one consistent config wizard. I wonder if that could be used as configurator as well. (Don't expect anything soon/if all from me. I'll get MS VC++ in a couple of days and will start learning C++/MFC then :-). Do you think that would be a good idea? Or do you know somebody who'd like to give it a try? > o An about box! yep > Have I missed anything? Sounds good to me so far, except maybe the menu entries for import/export of node references. These would require: Import: Pop up a file picker dialog for choosing a .ref file. This file needs to ba passed to the node with "fserve --seed <filename>". The file picker dialog would also pop up if somebody calls "freenet.exe -import" without a filename. Export: Just call "fserve --export MyOwn.ref" to export your own node reference. We could either choose a fixed file name or have a save file dialog to let the user choose a name. Does this make sense to you? See you, Sebastian _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl
