My opinion is that the OS X pop-up selector for the AutoCPs should be removed to allow the now built in selector at the Images interface and the Preferences methods to function as in the windows and presumably linux versions. At the Images interface the text, "Settings:" for the AutoCP selector should be changed to better describe the selector function. Its function is more to select an AutoCP generator than to be "Settings". The text is actually not necessary. The "Feature Matching (Autopano)" title above it already describes the section function. I would remove it to make room for a wider selector button that is wide enough for a user's more lengthy descriptor of his or her custom AutoCP. Following that selector could be a button to open Preferences in context with AutoCP. That would put both controls within a minimal pointer movement effort distance.
Allan On Sep 10, 2009, at 10:54 AM, Harry van der Wolf wrote: > > > 2009/9/10 Allan Seidel <aksei...@gmail.com> > Hello Harry, > > I thought OS X users should know that they could change the plug-in > parameters. > > You are completely right! > Thanks for pointing me in the right direction. I will write > something on my website about it. > > Your idea to save multiple parameter versions for the same plug-in > type is a great idea. If it were me creating the Hugin interface I > would not have the parameter settings accessible only in Peferences. > I'd have the setting available in the context where it is used. In > other words the parameters would be visible and easily changed with > a double click on their representation. One way to do this would be > to have the Peference pane openable to the settings location upon > that double click. That same concept could be applied througout > Hugin where applicable. > > I think that's really a nice idea. > > I don't know how the different os packages are created. It seems to > me that one can code the "parameter less" plugin concept without > needing to change the current the OS X plug-in structure. Hugin > knows all about these plug-in files. > > Yes, This is more or less what I want to look into. > > It can easily read each plug-in's argument line, report it in > Peferences and then alter the argument if needed. > > > My ideas are slightly different. > Option 1: The "file browse" button from Preferences would open in > the plugin directory where you would be able to select the available > plugin(s) and configure them with multiple configurations like it is > now done for linux/windows, thereby bypassing the internal argument > line. > > Option 2: (Even simpler). An installer would copy the AutoCP > generator to the same directory where the plugins reside. The "File > open" selector would than open (by default) in that plugin directory > where you simply select the executable instead of the plugin. > > For lineair images you simply select the panomatic plugin (option 1) > or panomatic executable (option 2) and provide some settings for > this set of images. > For fisheye images you select the same panomatic plugin (option 1) > or panomatic executable (option 2) and provide fish eye settings. > Then this will give you multiple options without needing to copy > anything (just like the linux/windows solution) > > My favourite is option 2 as it is much simpler to realize and this > one gives a cross platform (lin/win/osx) compatibility. > > What's your opinion? > Others are welcome to give their opinion as well off course. > > 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~----------~----~----~----~------~----~------~--~---
