Hello

I am not a Hugin developer either, nor am I a Python developer, but I
feel another user's point of view wouldn't be too much here :-) Just
as Harry did, I will only answer to those items which I have something
to say about.

2011/8/8, Harry van der Wolf <[email protected]>:
> = Going to a (in memory) database format:
> - Even though it seems a good step to make, it will create another
> dependency on all platforms. I don't like that.
I agree in general, but if my informations are correct, sqlite is not
much of a dependency, at
least not in the Windows world. Just copy an executable file and
sqlite is ready to work.

> - Do we implement our own sqlite3 "engine"  into the package or make it a
> system dependency which will certainly hinder a lot of end users.
See above.

> = (wx)Python:
> - Kay suggest to move to (wx)Python for logic and gui. Currently python is
> an issue on both windows and OSX. That doesn't mean that it can't have a
> glorious future but we are certainly not there yet. C(++) is a well defined
> standard. Python should definitely fully backward compatible to at least
> 2.6.
I feel using or not WxPython is a decision where end-users are not
much concerned. Even if the developers decide to indeed switch to
Python for a part of the development, the end-users would still get
pre-compiled complete versions. Switching to Python will indeed
trigger a few problems, but those problems will only bother the people
who will create the end-user setups. I know a few applications which
rely on Python. I mean: I (Windows user) know a few apps (written on
Linux) which rely on Python. In those applications, the decision to
change to something else (or rather not to) has always been a
developer decision ("Python's paradigm does not suit me", or "some
things are much easier with this other tool" or so on), I never saw a
user complain "please leave Python, it sucks".

> - When moving to (wx)Python: what will it do to performance? A compiled
> binary is AFAIK much faster than any interpreted program. If we leave the
> tools in C(++) for performance and only build a wxPython shell around it,
> why not stay entirely on C(++) for the gui and logic.
Python can be compiled. Actually, cross platform dependency handling
is so tricky that a Hugin written in Python would have to be compiled
IMO. So the performance won't be noticeably different.

> - To me the python extension (note my wording) is very good functionality to
> be able to build new functionality (by the experts) to be later on built
> (using C++) into Hugin for the greater, lesser skilled community (also
> related to end user friendliness).
I agree. But if the plugins written in python are good enough, then
there should be no need to rewrite them in C(+/- ++). Which means the
ability to improve those plugins would in the hands of the users.
That's one of the points in the plugin architecture: let the end users
adapt the application to their needs, thus relieving the code
developers of the burden of doing it for them. Or said in a more
positive way: the users stop asking and start doing :-)

Plugins would need to be incorporated into the C core only when they
would do calculation-intensive work.

-- 
Frederic Da Vitoria
(davitof)

Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org

-- 
You received this message because you are subscribed to the Google Groups 
"Hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Reply via email to