Hi all,
I am having a problem getting started with tm_dialog. I followed the instructions (intro_to_tm_dialog.mov -- http://macromates.com/blog/archives/2006/10/28/new-dialog-system-for-command... ) but the first error I found was this: > tm_dialog /Applications/TextMate.app/Contents/SharedSupport/Support/bin/tm_dialog: line 5: /bin/tm_dialog_v5: No such file or directory
( In this 20 seconds I learned the ctrl-R - whoa KICK BUTT!! -- but sadly `which tm_dialog` didn't work (strange tm_dialog worked)..)
The script was easy so I just will use tm_dialog_v5, but then the following error occurred. Upon simply creating an empty nib and attempting to use tm_dialog with it I get the following error: > tm_dialog_v5 ~/Desktop/test.nib tm_dialog: you have updated the Dialog plug-in to v8 but the tm_dialog tool is still at v5
Since the movie ended abruptly I figured someone has a working example buried in the TM application. I dug into the SharedBundles and started looking around hoping to find a completion to the movie - or a bunch of people who have created some nibs. I only found 10. (Uh-oh) Doing some digging I can't seem to find any code which calls a nib other than the subversion example but I don't understand how that works - it doesn't appear to actually call it (i.e It doesn't ever seem to do a tm_dialog??) So I am left with a bunch of questions I hope you experts can help me with.
1. How can I get tm_dialog v8 or how do I get this to work as is? 2. Can someone give me a crude example of how to call a nib from a bundle command and use it's output? 3. When creating a nib I want to get a password from a user - how do I obfuscate the input? 4. How can I store that password so I can use it in other functions within the bundle? 5. There was mention of a python property list parser - does anyone know how this works with tm_dialog (example would be great), where it is and how to use it?
Thanks a lot from A paying customer - who just bought the book too!!
---
Steven M. Klass
Strategic Manager, Design Automation - Analog Mixed Signal
SMSC 3930 East Ray Road, Suite 200 Phoenix, Arizona 85044 (480) 704-7046 (Desk) (480) 225-1112 (Mobile) steven.klass@smsc.com
Steven.Klass@smsc.com wrote:
Hi all,
I am having a problem getting started with tm_dialog. I followed the instructions (intro_to_tm_dialog.mov --
http://macromates.com/blog/archives/2006/10/28/new-dialog-system-for-command...
) but the first error I found was this:
tm_dialog
...
Yeah, many details of using tm_dialog have changed since the screencast. Threw me off at first, too. Perhaps you could comment the screencast with those differences if you get it working? Ideally, Allan would update the blog post itself with those differences as well.
As far as I can recall (in something of a hurry; not re-watching the screencast), the main difference is that you should use the value of the DIALOG environment variable for tm_dialog, e.g.
"$DIALOG" -p '{}' "/my/nib.nib"
In my case, that variable points to "/Applications/TextMate.app/Contents/PlugIns/Dialog.tmplugin/Contents/Resources/tm_dialog".
Also, the command will stall (actually wait for STDIN) if you do not pass it any input properties, so do the above rather than
"$DIALOG" "/my/nib.nib"
Good luck. Might have missed something; let us know if you're successful.
On 15. Mar 2007, at 05:29, Henrik Nyh wrote:
[...] Yeah, many details of using tm_dialog have changed since the screencast. Threw me off at first, too. Perhaps you could comment the screencast with those differences if you get it working? Ideally, Allan would update the blog post itself with those differences as well.
Done: http://macromates.com/blog/archives/2006/10/28/new-dialog- system-for-commands/ :)
It really only should be the s/tm_dialog/$DIALOG/ though.
I’ll have to check if some of the default stuff still use tm_dialog, if not, I can replace the Support/bin/tm_dialog with a script that explains the change (as its error message).