On Wed, May 30, 2012 at 10:52 AM, Michael Banck <[email protected]> wrote: > On Wed, May 30, 2012 at 10:40:31AM -0400, Geoffrey Hutchison wrote: >> I think both things are important -- disable the menu item when no >> files are available. My concern about the source tree is knowing where >> that is. I'm not sure I want to compile-in the source directory. >> Should I know that it was compiled by /home/mbanck/avogadro/... ? > > I guess it wouldn't hurt, so long as it is just a fall-back that is > used if the data directory is not available and the source tree is > present, but it should not be exposed to GUI in any way otherwise. > We do this for the plugins etc already. I would like to find a way to remove some of the burden from the developer of the plugin. We might just want to add one function that gives a prefix for data directories that can have a second entry for the build tree. We would have one place to disable that second entry then for distros etc if they were concerned about searching additional paths.
Marcus ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Avogadro-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/avogadro-devel
