Instead of copying large portions of other mails I would like to go directly
into some of the points mentioned with my end user point of view mixed in:

= User friendliness (not mentioned before, but my point of view):
- All solutions offered so far come from the "techies" and relate to the
code base, and off course they are the driving force behind the hugin
community, but the techies are only 5% (maximum!) of the end-user base where
both the windows end users (by far the biggest amount) and OSX end-users are
(almost by definition) not the most technical users.
All solutions should aim for more user friendliness. By now the python
integration is certainly a help for new functionality but it's not user
friendly. Also remember our discussions about how Hugin should look like.
I'm not a coder of course but I don't think the code base is that bad, like
mentioned by Tom Sharpless and the article mention by Habi. When looking at
first at the code, even if you are experienced in other languages (php for
me or maybe python for others), it is always tricky to find your way.
- Again: the techies know their way in the program as they are experienced,
some with many, many years of experience. It still strikes me that so many
users experience issues on "simple user-friendly" functionality (note:
simple and user-friendly to the experienced users).

= 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.
- 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.
- What about the translations? It seems very logical to me to put them as
well (or even as first) in a database. But then: what about the translators:
Do they need to setup a development environment with e.g. sqlite to be able
to do their translation work? I'm afraid that won't work. So in that case:
Do we still use the .po files and "someone" writes a C(++) or (wx)Python
tool to import them into the database?

= (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.
- 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.
- 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).
- We have some C(++) programmers on board. How many (wx)Python programmers
do we have? This is a neccessity for continuity.

= how? or why?
- In previous mails we were already discussing "how to
plan/structure/execute". To me this is how many projects (also within my own
company) go off  the rails. The first questions are: Why do we want to do
it? And actually who want's it: 95% end users struggling for the year to
come or leaving, or 5% techies? What's the "business case"? Is it worth it?
This is not some GSOC minor project (I don't mean this derogatory, not at
all) which can be integrated at some point. It will make hugin shake (or
break) at it's foundation.

I don't give much answers or solutions. Merely things to consider when doing
such a major step which could break hugin easily for at least a year (or
worse).

my 2 cents.

Harry

-- 
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