On 06/26/2012 02:18 AM, kfj wrote:
Am Dienstag, 26. Juni 2012 02:20:11 UTC+2 schrieb Tduell:I also note that the comments on the gui_overhaul branch have slowed down a bit lately. There really hasn't been a lot of comment, less than I would have expected for such a change. I wouldn't be surprised if there simply aren't that many people who have bothered compiling a branch with an experimental new GUI. Most people have plenty of other stuff to do. When the python interface was being developed, I estimate there were a handful of people involved, and even now that it's in the default branch, it's gone largely unnoticed (mainly because it's only distributed on Linux). Release the GUI overhaul branch now and all of the sudden there will be a great number of 'what is this' 'I can't that' etc. etc. messages.
That's a sign that the new GUI isn't ready for primetime. Especially the "I can't" comments when "I can" is perfectly true of the current GUI.
So I also advise to wait with the GUI overhaul release until the next cycle, and then make that the specific 'topic' of the next release and change little else. Seems cleaner to me that way. And if anyone is adamant to stick with the old GUI, they can stick with 2012.0 as the latest status quo before the new GUI became standard.
Please don't force the new GUI on people without giving people the option to keep the current and highly functional "Classic GUI".
Personally, I'd prefer it if there was a real GUI overhaul built around the preview window as the main UI, rather than what seems to be happening with the current GUI overhaul. Note: to turn the preview window into the main program window will require either making it work flawlessly with video drivers' GL support, or making it fully functional with the non-GL preview ...
Of course, how you'd make the preview window UI work with someone who brings in a bunch of images that aren't aligned yet is a mystery to me. I'd rather not force people to use something that automatically tries to align the images, when they'd prefer to detect CPs and do alignment selectively selectively on images. Maybe just space the images edge-to-edge across the preview window based on the order in which they're added to the project?
Of course, I'm weird. Forget the preview window. Give me a full screen display, no desktop environment GUI borders and widgets and such, with my images arranged on the screen. Let me drag them around, drag select'em, right-click on things and select from popup menus, etc. Just call me an old fan of Targa TIPS.
Question: Someone sometime back talked about storing CPs in some kind of database format (at least in memory) to speed up handling large DP datasets. Would that be something to consider in another release or two?
-- Gnome Nomad [email protected] wandering the landscape of god http://www.clanjones.org/david/ http://dancing-treefrog.deviantart.com/ http://www.cafepress.com/otherend/ -- 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
