Fujimoto Hisa
hisa****@fobj*****
Wed Apr 25 09:21:40 JST 2007
I'm not good for TextMate, but writing plugin enabler for it may be
almost same as sample/VPRubyPluginEnabler.
* write plugin enabler (like sample/VPRubyPluginEnabler), it should
run in the TextMate process.
* the enabler should be written loading a ruby program as plugin.
* loaded ruby program should run in the same process, so it's enable
to access objects in the process.
hisa
On 2007/04/25, at 8:24, jeanp****@gmail***** wrote:
> 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).