On Sat, Jun 13, 2009 at 1:57 PM, Zero3<ze...@zerosplayground.dk> wrote: > Matthew Toseland skrev: >> On Tuesday 02 June 2009 09:22:13 Zero3 wrote: >>> Matthew Toseland skrev: >>>> On Thursday 21 May 2009 17:32:55 Juiceman wrote: >>>>> On Thu, May 21, 2009 at 6:58 AM, Zero3 <ze...@zerosplayground.dk> wrote: >>>>>> Matthew Toseland skrev: >>>>>>> On Sunday 17 May 2009 11:41:00 Zero3 wrote: >>>>>>>> Matthew Toseland skrev: >>>>>>>>>> Detecting the version of an installed application in the launcher (at >>>>>>>>>> least in Windows) shouldn't be a problem. It will most likely be >>>>>>>>>> registered in the registry next to the .exe path we are checking >>>>>>>>>> already >>>>>>>>>> for the individual browsers. We can also check the version info of >>>>>>>>>> .exes >>>>>>>>>> as an alternative (most Windows applications are compiled with >>>>>>>>>> various >>>>>>>>>> static info like version and author). The Windows launcher is already >>>>>>>>>> running Chrome with a command line argument making it start in >>>>>>>>>> privacy >>>>>>>>>> mode btw. >>>>>>>>> You should prioritise Chrome with privacy mode over Firefox without >>>>>>>>> it. >>>>>>>> Agreed: https://bugs.freenetproject.org/view.php?id=3118. >>>>>>> I thought you had already done this? >>>>>> At time of writing, no. But since then I managed to figure git out and >>>>>> changed it (hence the bug is now "resolved"). >>>>>> >>>>>> ... which leads to another thing to consider: We need to make it >>>>>> possible to update the start.exe/stop.exe/freenetlauncher.exe files for >>>>>> existing users when new updates are made available. >>>>>> >>>>>> The easiest way to do this right now would probably be to add them to >>>>>> the update.cmd script. >>>>>> >>>>>> - Zero3 >>>>>> _______________________________________________ >>>>>> Devl mailing list >>>>>> Devl@freenetproject.org >>>>>> http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl >>>>>> >>>>> I would be happy to do this, however I will need a defined directory >>>>> structure on the download site, with known file names. Like we have >>>>> the .url link for the freenet.jar. I believe I can use the .sha1 file >>>>> to check for updates if you want to have a static name. ie >>>>> wrapper_win32x86.exe etc. Also I would prefer to not have them inside >>>>> a zip unless we have have a built-in unzipping program in Windows I >>>>> can reliably call by command line. Otherwise we will have to bundle >>>>> yet another third party utility. >>>> Well, they should be fetched from >>>> http[s]://checksums.freenetproject.org/latest/<filename>, not from >>>> downloads... are the relevant files currently available from checksums? >>> I don't know if they are? I never had anything to do with the actual >>> uploading of the files to anywhere on freenetproject.org. >> >> I do ... what files exactly do you need? Note that we may need to change >> from https://checksums.freenetproject.org/latest/filename to some other >> domain at some point, but we can hopefully do that by changing the update >> scripts. >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Devl mailing list >> Devl@freenetproject.org >> http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl > > Besides the wrapper .exe and .dll, we need at least the latest built > freenerlauncher.exe to be available, so that we can > add/remove/update/reprioritize browser support. > > - Zero3 > _______________________________________________ > Devl mailing list > Devl@freenetproject.org > http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl >
I'm working on the update.cmd script handling these binaries... it seems the .sha1 of all of these files is blank on the website. The wrappers, start.exe, stop.exe and the freenetlauncher.exe. I'll need that fixed please to continue my work ;-) _______________________________________________ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
