On 20 déc. 05, at 14:40, Cees De Groot wrote:

> On 12/20/05, stéphane ducasse <ducasse at iam.unibe.ch> wrote:
>> For the explorer I was willing to spend some time to move behavior
>> around but does it make sense to have morphic specific
>> code in the explorerPlus?
>>
> No - the PlusTools should be completely UI agnostic.

Ok this was what I was looking for. For example in the explorer you  
have morphic specific features.

> No UI-specific
> code is allowed in there. So if Morphic-specific code is transported
> from current tools to PlusTools, it should be split up in code driving
> ToolBuilder and maybe ToolBuilder enhancements.
>
> Note that ToolBuilder is a maintained package
> http://kilana.unibe.ch:8888/ToolBuilder/ so patches should go through
> the upstream.

Ok my goal is not to change or touch ToolBuilder but to see how we  
can move the Plus Tool adoption
since keeping two separate set of tools is dangerous in the long term.

>
> I'm not sure about PlusTools' status - Andreas, is it an idea to
> maintain it in the same repository as ToolBuilder?
>
>