- Why did I write DropUNIX?
- Basically I was tired of writing support for some sort of user interface for UNIX ports. What it really comes down to is I dislike both Symantec’s and MetroWerk’s cconsole call. I thought, “Mac users don’t DO paths… It is even discouraged by Apple…”. So I wrote this little library allowing people to convert their ugly console app with no real interface to at LEAST be drag & drop’able.
- Why should I use it?
- Simplicity for the first part. You don’t have to do much of anything to get it up. Second, to maintain Apple’s Human Interface Guidelines. I hate, You hate, we all hate icky GUI’s! Last, but not least Productivity. By using DropUNIX you have increased your productivity by giving the port a new interface for free, and you have increased your users productivity by giving them an interface they can use intuitively…
- Why shouldn’t I use it?
- Because a lot of unix applications change options through flags, if you require these flags to be settable, you are out of luck for now… Well, this isn’t entirely true… If one REALLY needs a flag, say ‘-f’ they can make a folder with the name ‘-f’ and include that in the drop, then the flag would get there… It just seems wierd to have to do that…. Also, if ordering is important, then one would have to physically rename their files to be: 1.aFile, 2.anotherFile… etc, because the finder sends the files in alphabetical order… Version 2.0 will address these issues.
- How do I use this with a debugger?
- Debugging is interesting. Basically I’ve done it in the past by bringing up the application in the debugger, selecting run, and then using the finder to drag files/folders to the application’s icon. This will trigger the same apple event that it would had you done this at the start w/o the debugger.