Re: [SrcML] new plugin handling and API structure
Status: Beta
Brought to you by:
crashchaos
From: Dennis W. <den...@in...> - 2005-04-21 17:52:19
|
On Thu, 21 Apr 2005 19:39:58 +0200 Frank Raiser <fra...@in...> wrote: > Now what is the 'order' of API plugins? > Let's say we have a simple dependency on one other plugin. Then this > dependency plugin will be the first to be loaded. Therefore its > dependencies will recursively be loaded before the dependency plugin > itself is loaded. The last one to load is the actual plugin we wanted > to load. Now if we consider the possibility of influencing the order > by the order in which the dependency plugins are listed in plugin.xml > (by adding the corresponding edges to the dependency tree), the plugin > developer basically has free choice over the first depth level of the > tree. I don't know whether you really plan on giving a plugin > developer the ability to define the order in which dependencies of > dependencies are resolved? If not I think this approach should be > pretty good for us already. Uhm... I actually was trying to say that this approach looks good. And the order by using this method is clear. A programer wouldn't care for order of the "super" plugin dependencies. Never thought that this would work out after all. > Ok. So we have been talking about two different things here. I never > intended to enforce a program restart in order to load another > document with another API. My idea was to prepare the match table just > before the SrcML class is instantiated for a document. Then for > another document there'd be a method to reset the match table and > prepare a new one for the new document. So for me this match table is > only important while instantiating the SrcML class and modifications > to it do not affect existing DOM trees (which should remain unchanged > to avoid confusion). So to sum it up from my point of view: > - new document takes a new match table > - only one match table per document That is actually what I meant. And if you check my old mail you see while I called a method after creation of SrcML the basic idea is the same no matter if you do it when instancing or setting it up after it is created. - Dennis |