jeanp****@gmail*****
jeanp****@gmail*****
Wed Apr 25 08:24:20 JST 2007
hi list - i am trying to create a rubycocoa plugin for textmate again, with hopes of both initializing rubycocoa in textmate and to make the rubycocoa framework available to textmate commands. currently, on textmate launch, the plungin is initialized and all is well - i can display windows and all sorts of other rubycocoa trickery, however it is later on that i have problems. the plugin embeds the rubycocoa framework (and bridge support files) and i was thinking from textmate commands i could just require some ruby file embedded in the rubycocoa textmate plugin, it would handle all the requires (of the embedded rubycocoa framework), but what i have found is that this second require, requires the uninitialized-in-textmate version of the file. so i can call non-windowing operations like beep/sounds but interacting with the windowserver is not allowed, likely because the rubycocoa calls are not originating from a GUI process and instead from a standalone ruby script. might anyone have an idea how this could be accomplished? i'd rather not write full applications for my rubycocoa-accessing textmate commands however i'm unsure how i could get a script setup with the proper rubycocoa requires and have the process run from within textmate (or likely from within my textmate plugin). cheers, jean-pierre -------------- next part -------------- An HTML attachment was scrubbed... Download