On Thu, 11 May 2006, bulia byak wrote:
Is there ever a reason that you'd want to use the version in the PATH? It seems atleast for testing you might want to use a different version.
If you want to test how some changes affect it, just make those changes to Inkscape's python and test. Or make inkscape/share/python a symlink/batch file calling the "real python". Anyway, I don't think we need to add an option for that.
Okay, sounds good. Can someone tell me how we know the location of "our" python on windows?
- Enable extensions/effects by default and remove the prefs setting.
I don't know of anything that prevents us from doing that.
I agree. I think we should make the "configurable menu" the whiteboard menu and make it compile in by default. Thoughts?
Last I heard, it even gets compiled in the Windows version. If it also works :) let's just enable it always.
In Linux binaries we provide, I think it should also be enabled, and the library it uses linked statically. Is this possible?
I static linking is a really bad idea, especially for a library that is network facing. I understand that we have to do it on Windows, but Linux has good dependency management, and we should use it. I think loudmouth is reasonably well distributed.
--Ted