[Vm-dev] Re: Plugin category
Ken G. Brown
kbrown at mac.com
Fri Apr 11 17:55:01 UTC 2008
At 11:55 PM -0600 4/10/08, Ken G. Brown apparently wrote:
>At 10:27 PM -0700 4/10/08, tim Rowledge apparently wrote:
>>On 10-Apr-08, at 8:21 PM, Ken G. Brown wrote:
>>>Don't have what you need. However since you appear to be working on VMMaker, I was wondering about your take on the need for having plugins in the VMMaker Plugins category. At least it seemed to me that you have to put them there in order for VMMaker to pick them up.
>>>Somehow it seems odd to me to have all of a plugin's classes in its own category, except the plugin which has to go somewhat illogically in the VMMaker Plugin category. Most likely its a lot of work to do it any other way. Or am I missing something?
>>Well the main list of plugin classes to work on is derived from
>> "generate the list by asking the InterpreterPlugins"
>> ^ ((InterpreterPlugin allSubclasses
>> select: [:cl | cl shouldBeTranslated])
>> collect: [:cl | cl name]) asSortedCollection
>>so, yes, I think you've got confused.
>Hmmm...ok. The way it works is making more sense to me then. I had added plugin code to the image but for some reason, I did not see it in VMMakerTool 'Plugins Not Built' list until I changed the plugin category to VMMaker-Plugins, I had assumed that was where it needed to live in order to be picked up in the list. I'll try moving the plugin back to its own category and see if I can duplicate what I thought happened.
Ok, it appears what happened was that I must have had VMMakerTool open before I loaded the plugin code and it did not update or find the plugin by the time when I originally looked. I then saw the other plugins in VMMaker-Plugins so changed category of the plugin I loaded to the VMMaker-Plugins and then saw it show in the list. I don't remember for sure what I did originally, but this time, closing and opening VMMakerTool again shows the plugin properly even tho it still lives in its own category now. Great!
What are the conditions that cause VMMakerTool rebuild its lists?
>Ken G. Brown
>>From there any plugin has to be moved to either the internal or external list in order to get actually processed - the UI in VMMakerTool does it by direct manipulation and the various methods in VMMaker>initialize like initializeInternal:external: allow for scripted usage.
>>tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
>>Strange OpCodes: IA: Illogical And
More information about the Vm-dev