in reply to RFC: Tk::SettingsDialog

You may be somewhat interested in Utility to capture parameters and perform a task. Note in particular that the values provided in previous entries can be used to for the default value for later entries. Try it with the following data:

_File_ File name _OutFile_ "_File_" File name as installed _author_ Primary author's name _authoremail_ "_author_@somewhere.com" Email address of primary author _MinVersion_ "7.0" Minimum version required _MajorVersion_ "7" Major version number (single digit) _InstallFolder_ "_OutFile__MajorVersion_" install folder name _NameUI_ "_OutFile_" Name as shown in UI _RootPath_ "dev/_File_" Path to parent folder containing files _SlnPath_ "_RootPath_" Path to folder containing solution _SlnFile_ "_File_" Name of solution file (excluding file extension) _Project_ "_File_" Name of the target project in the sln _BranchTag_ "" Default revision control tag to check out files against
True laziness is hard work

Replies are listed 'Best First'.
Re^2: RFC: Tk::SettingsDialog
by kenearle (Novice) on Sep 07, 2010 at 00:35 UTC

    Thanks grandfather, that's pretty nifty in not much space.

    SettingsDialog goes one extra inch I suppose, for those who want automatic type checking and pickers for dates, files etc. And dropdown lists, which I find handy sometimes (for example I'm working on yet another "Extract Method" for Perl, which uses SettingsDialog to present the options of passing each sub parameter by reference or value, or omitting it altogether, and that seems to want a dropdown menu).