How come I never got the original of this? Was it sent to a different
freenet mailing list than this one (it's the only one I'm subbed to
unfortunately).
> you should announce these things to the web mailing list so that the
> translators can do their thing.
>
> Ian.
> I am still not 100% happy with the changes made
Which changes are you not happy with? Spit it out and we'll fix them
together!
> A couple of things got broke while I didn't really pay attention to the
> installer:
> 1) Taking away the -cp freenet.jar from FLaunch.ini broke the system
> tray utility as Dave Hoopers implementation reads that file, but didn't
> set the classpath variable. It does set the classpath now, fixed! (that
> was the could main class not found thingy)
Well your implementation would've done the same thing! :-p
Don't forget my implementation started out as a straight port of your code
into C;
> 2) Dave's implementation reads the entry "fserve" in FLaunch.ini which
> starts the graphical Node invisibly and thus wastes RAM. The solution
> will be to have an entry fserveCLI (or similar which is read instead).
> This is feasible
Ok, Makes sense. I'll have to have a play to see if I can still quit the
non-GUI freenet node by sending it a WM_CLOSE message. I might check in an
update tonight, or, I might just go to bed.
> 3) Daves freenet.exe will signal an error on startup when using the CLI
> node (Freenet.node.Node) while the graphical node (node.gui.GUINode)
> works fine. *He* will have to fix this, as he added some complicated
> stuff (multiple threads etc...) to my simple implementation, making it
> impossible to me to understand it fully ;-). Dave are you listening?
> Otherwise, I'll have to downgrade your tool to a level I can handle :-)
Meow! I'll talk you through the code sometime if you like, but essentially
there's one thread running the main message pump, which handles the popup
menu appearing and suchlike, and there's a background thread to actually
service the requests. So when you rightclick the icon, the message loop in
the first thread takes control causing the menu to popup - and when you
click on Start Freenet or Stop Freenet this first thread sends a message to
the second thread to tell it to actually do something. It's just a more
responsive version of what you already had - except this background thread
also handles flashing the icon in the "Freenet Is Having Problems" state.
I'll look into using the CLI node. Again, my port to C is still essentially
currently doing the same old stuff your assembler did
Dave
_______________________________________________
Devl mailing list
[EMAIL PROTECTED]
http://lists.freenetproject.org/mailman/listinfo/devl
