[tools] Rebuild core tools using classes about livelykernel HOT 5 CLOSED

Further:

• PartsBin Browser
• ObjectEditor
• Inspector

from livelykernel.

Hmm about PartsBin Browser + Object Editor I'm not so sure. Those belong completely in the PartsBin world. But implement interfaces for both (actually our lively.PartsBin interface is quite OK + well tested) in modules might be a good idea and would remove complexity from the Parts.

from livelykernel.

Okay, maybe the Object Editor and the PartsBin Browser don't belong into Core / this repository. However, I'd be in favor of rewriting them with classes or as you suggested at least move more functionality in modules/classes, because both are difficult to maintain as Parts with our current "object-centric development" tools and concepts:

• unclear which object implements what, objects are less "browsable" as classes in modules - that's an issue somewhere between tool-support and conventions
• no code-sharing between parts, yet (and there are already multiple versions of the PartsBin Browser in webwerkstatt's PartsBin)
• parts tend to be untested / there's still no tool-support for parts

from livelykernel.

Is there still work to do on this issue or can it be closed?

from livelykernel.

Most core tools are now implemented using BuildSpecs, see https://github.com/LivelyKernel/LivelyKernel/tree/master/core/lively/ide/tools and https://github.com/LivelyKernel/LivelyKernel/tree/master/core/lively/morphic/tools

from livelykernel.