[OMC] Re: default value in text input dialog

[OMC at abracode.com]

Michael,

Let's move it to the mailing list instead of exchanging e-mails  
privately. Knut and other people might be interested in this.
I think that what you try to do it complicated and unique enough to  
justify usage of custom nib dialog. And I have a feeling that the use  
of objects in popup menu or combo box menu is really limited: like  
listing available special OMC objects or choosing from several  
predefined path variations. But you can easily achieve something like  
this by assigning unique numbers or names to popup menu values and  
then check in script which action to perform (using objects or not).
Support for objects in default text in input dialog was requested by  
other people and I think it is reasonable if you want to use some  
combination of selected filename with suffix for a default text in  
dialog.

Comments welcome,
Tom
Abracode

On Jul 12, 2005, at 2:08 PM, Michael Annino wrote:

> That's GREAT Tom,
>
> I'll take a closer look, but I was thinking more along these lines,  
> where the object is contained within the string.
>
> <key>INPUT_DIALOG</key>
>             <dict>
>                 <key>CANCEL_BUTTON_NAME</key>
>                 <string>Nope</string>
>                 <key>DEFAULT</key>
>                 <string>Choose</string>
>                 <key>INPUT_MENU</key>
>                 <array>
>                     <dict>
>                         <key>NAME</key>
>                         <string>New</string>
>                         <key>VALUE</key>
>                         <string>-l __OBJ_PARENT_PATH__</string>
>                     </dict>
>
>
> I was thought this would help to combine my commands into single  
> dialogs and simplify my menus ... an alternative to a full blown  
> nib file.
>
> Some many GREAT options ... who would even consider using Automator  
> when we have OMC :-)
>
> I look forward to the final release and an updated OMCEdit.
>
> M.
>
>
>
>
> On Jul 12, 2005, at 11:51 AM, Tomasz Kukielka wrote:
>
>
>> Michael,
>>
>> It is quite easy to add support for objects in default value edit  
>> field for text input dialog so I decided to add this feature  
>> before OMC 1.7 is release. But this is definitely the last feature  
>> addition. After that there will only be bug fixes. New default  
>> value requires a new keyword: "DEFAULT_VALUE". Previously the  
>> keyword was "DEFAULT". Notice the difference: DEFAULT_VALUE is  
>> array of strings and DEFAULT was just a string. Please see the  
>> example command below. You cannot Use OMCEdit for this yet. You  
>> have to do it by hand.
>> Tom
>>
>>         <dict>
>>             <key>COMMAND</key>
>>             <array>
>>                 <string>echo '</string>
>>                 <string>__DLG_INPUT_TEXT__</string>
>>                 <string>'</string>
>>             </array>
>>             <key>EXECUTION_MODE</key>
>>             <string>exe_popen_with_output_window</string>
>>             <key>INPUT_DIALOG</key>
>>             <dict>
>>                 <key>DEFAULT_VALUE</key>
>>                 <array>
>>                     <string>Default Text</string>
>>                 </array>
>>                 <key>INPUT_TYPE</key>
>>                 <string>input_clear_text</string>
>>                 <key>MESSAGE</key>
>>                 <string>Testing array of strings for default  
>> value</string>
>>             </dict>
>>             <key>NAME</key>
>>             <string>Default text test</string>
>>             <key>REQUIRED_MAC_OS_MIN_VERSION</key>
>>             <string>10.2</string>
>>             <key>REQUIRED_OMC_VERSION</key>
>>             <string>1.7</string>
>>             <key>SUBMENU_NAME</key>
>>             <string>/</string>
>>             <key>VERSION</key>
>>             <integer>1</integer>
>>         </dict>
>>
>>
>>
>>
>> <OMC 1.7 another preview.dmg.gz>
>>
>>
>
>
>
>