male hugin skinnable
paisajesenvenezuela
the user chance the appearance of the programs windows??
john doe
hey how about adding an option to make hugin skinnable??that is let
the user chance the appearance of the programs windows??
--
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 hugi...@googlegroups.com
To unsubscribe from this group, send email to hugin-ptx+...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
Lukáš Jirkovský
OH NO! Never ever ever ever ever do this. I don't understand why some
people want every application look completely different from the rest
of desktop.
just my 2 cents.
Bart van Andel
Windowblinds [0]? Or, if you're on Linux (guess not) there are enough
ways to customize look&feel already. For Hugin this has absolutely no
priority.
Would you ask Adobe to do the same thing for Photoshop? I guess you
won't.
[0] http://www.windowblinds.net
--
Bart
On 10 nov, 07:42, Lukáš Jirkovský <l.jirkov...@gmail.com> wrote:
Henk Tijdink
Pasajesenvenezuela and John Doe have the same e-mail adress.
Does he likes a discussion with himself? Or a certain hidden agenda?
Henk Tijdink
Carl von Einem
> Why is someone using 2 names on the forum?
> Pasajesenvenezuela and John Doe have the same e-mail adress.
> Does he likes a discussion with himself? Or a certain hidden agenda?
Messages sent from a mail app such as Thunderbird will show the
information from the account settings while messages sent via Google's
web interface will show the nick name for that Google account.
Carl
zarl
john doe
Hello firstly I do use linux I use ubuntu use
Carl von Einem
zarl schrieb am 10.11.10 14:11:
dbur
features. Not what the windows look like. I'd rather anyone wants to
do this just put the effort into an 'official' windows build site
instead. Or even just uncheck the 'optimize camara parameters'
default would be of more interest to me.
David B
On Nov 9, 6:25 pm, paisajesenvenezuela <guerrerodelu...@gmail.com>
wrote:
Jeffrey Martin
be in line with ptgui/autopanopro? the tech behind hugin has been
solid for a while now, but the UX still needs a lot of work.
if there is some way for me (as a non-programmer) to help with this,
please let me know.
Yuval Levy
> Instead of making hugin skinnable, how about improving the UI / UX to
> be in line with ptgui/autopanopro?
What do you mean by "in line"?
> if there is some way for me (as a non-programmer) to help with this,
> please let me know.
Play with Hugin and when you find something that does not feel right,
articulate your findings and share them.
Do so in relationship to how Hugin is now and not in relationship to other
stitchers you are using.
Start with small things, with "papercuts". These are usually quick to fix
(e.g. not being able to select all entries in a list with a keystroke) and
developers may not be aware of how cutting they are.
Don't expect quick fixes. Resources are what they are. But reporting helps a
lot, even if you don't get an immediate fix in return.
Slowly but surely you can move toward bigger things. Avoid the pitfall of
trying to bend Hugin into being a clone of one of the other programs you're
used to.
Last but not least, please hold off with the feedback for a few days until the
new tracker is announced here. Next week we should have a tracker with better
functionality, where non-programming users like you will have a possibility to
give more feedback and get more involved.
* Filing tickets: users will face a simplified ticketing system. No matter
if what you file is a bug report, an enhancement request, or even a patch.
It's the same queue.
* Tagging of tickets: gone is the rigid structure. Users and triagers (power
users that process new tickets without necessarily being a programmer) get an
opportunity to categorize and classify tickets along multiple dimensions. If
the UI is your area of interest, you can triage (read) all new reports and if
a report is about the UI and has not yet been tagged, you can tag it. And of
course you can add to its discussion.
* For most of that activity there is no need to log-in to the web based
application and suffer long web-latencies. Everything can be done right in
your inbox [0], although it needs to be setup first. I'm working on
documenting how to set it up, bear with me please.
* "Voting" on tickets: With the simple click on a button, users can notify
the system that an issue "affects them too". This gives an heat indicator and
chances are that bug fixer will follow that indication.
* Blueprints: A complete section that helps word out, analyze, articulate and
even plan in detail bigger change. Projects like GSoC projects can start as
blueprints, which has the advantage to make them live longer than a GSoC
season if necessary (i.e. if there were not enough resources to implement them
during a GSoC). If you think you have the next mind blowing UI design, this
is where you would put in detailed specs, mock ups, etc. up for discussion.
* Personalized view of what is important to you. E.g. [1] is mine. As you
register an account with the system, say as 360cities, and start using it, you
will get a similar overview at [2] (non working now, since there is no
registered user called 360cities yet), personalized on your interest (simply
based on your subscriptions and your feedbacks).
HTH
Yuv
[0] <https://help.launchpad.net/Bugs/EmailInterface>
[1] <https://launchpad.net/~yuv>
[2] <https://launchpad.net/~360cities>