Will be handled by 's launcher.ini (pre-configured by build.xml/ant). The installer will run Jitsi by setting the config dir to the appropriate Data subdir as with spec (requires trivial bug fix as in ). * another is a installer which you can configure with or without custom URL handling protocol names. * one is a self-extracting 7zip installer which I usually use to silently install/upgrade Jitsi which in turn registers keys in HKCU So then I patched the build.xml file (attached) in order to create 2 targets: I did this in order to make a custom Jitsi application that makes sure everything is registered as expected instead of relying Them on startup in, eg., HKCU, instead of having the installer do that. This makes more sense if you consider "portable" or "user" apps.Ī second feature is the ability to specify where to register these protocol names. The advantage of customizing the names is that you can avoid using a standard one, maybe already used by another app (eg. So whoever builds Jitsi from source can simply define the SIP and XMPP URL protocol names in default.properties. I'd like to propose patches to improve Jitsi portability and flexibility.įirst of all I'm proposing some patches in order to allow the programmer to easily choose the protocol names for URL handling.
0 kommentar(er)
