On Thu, Jul 8, 2010 at 6:14 PM, bulia byak
<buliabyak@...400...> wrote:
2010/7/8 Nicolas Dufour <nicoduf@...48...>:
> 1. Removing the Uniconvertor scripts from the devlibs. UniConvertor import or export scripts warn users to install UniConvertor manually (and give the site address) when the libs are missing. (Note to self: fix the gettext import bug in uniconv_output.py...).
I think that will be perceived as a regression. Lots of formats that
used to work will suddenly stop working. We had a lot of pain with
displaying messages like this - most people simply perceive any such
message as an error and complain or give up without reading. Those who
read it and act on it will be a minority.
From other side a lot of win32 users ask us "Why you announce XXX feature but i have not this in Inkscape?".
We cannot synchronize our project development cycles, it's normally. But we could provide for user a way updating UniConvertor.
External UniConvertor installation is a best solution because current bundle updating is a task rather for programmer than for
conventional user/designer.
What's such a big problem with including a new UC into devlibs?
Actually there are not impossible tasks. It's just a subject of additional development time and resulted bundle size. Latest version
has several new native extensions and more complex structure. And in next versions we will add new native resources because users
ask for more and more complex features.
As a simple solution we can provide for users an Inkscape-0.48-with-UniConvertor.zip archive with Inkscape installer, UniConvertor MSI
and small REAME file inside. To simplify UniConvertor download the best way is not a message "You need downloading from bla-bla-bla site..."
but just a button "Download" which opened browser on required page. Last option is for those users who download Inkscape exe installer only.
Another valuable reason is planned preferences for translation. We are going provide a lot of translation options (we already have the code
but we still not expose it as a command line options) and naturally such preferences could be managed better from GUI than command line.
So we will add preferences dialogs for each format into UniConvertor. It's not an easy task so for Inkscape team will be better utilizing ready
dialogs from UniConvertor than creating the same but on Inkscape side. And as I have wrote UniConvertor translation progress dialog
would be also a good additional feature for Inkscape.