2010/7/10 Igor Novikov <igor.e.novikov@...400...>:
We have created stand alone version because a lot of win users cannot understand all required installation steps. They prefer downloading 13Mb file than experimenting with separate Python MSI, PIL, ReportLab and UniConvertor .exe installers.
What exactly is the reason UC 1.1.5 doesn't work when dropped into Inkscape's Python directory? I can update Inkscape devlibs to the versions required by UniConvertor 1.1.5, and add any needed stuff.
I think the main problem is that UniConvertor is not perceived by users as a separate application, but as an integral part of Inkscape. The majority of users is probably not even aware of its existence. For me, shipping 1.1.5 but interoperating with a standalone install if present is the way to go; this way a person that hits an import bug can install a newer version but the rest is never bothered.
Additionally, let's not forget about point releases like 0.47.1. I think they can be used for UniConvertor upgrades, and UC upgrades would be an important motivating factor to actually have them.
Also, IMHO installation size does not matter now. Average modern HDD capacity is 1Tb and Win7 requirements for HDD is much more than 1Gb.
Installation size doesn't matter but download size still does.
Regards, Krzysztof