ba-st / kepler Goto Github PK

We need to add a module for each to use them into a installation

SystemInstallation>>install: now requires every module to be created by implementing the toInstallOn: message. This is Ok for self-contained modules, but sometimes we want a module with a bit of configuration and the only way to overcome this limitation now is to create a "module factory".
We can refactor a bit install: so self-contained modules are easy to install, but also allow more exotic module creation strategies.

None of its classes has references

See ba-st/Chalten#6

It is also an opportunity to narrow the dependency just to the Gregorian calendar.

Add as an extension a custom visualisation using Spec2 to list composite system's subsystems and its implemented interfaces.

I've been using this code in Pharo 9

CompositeSystem >> inspectSubsystems [

	<inspectorPresentationOrder: 40 title: 'Subsystems'>
	^ SpTablePresenter new
		items: subsystems;
		addColumn: (SpStringTableColumn 
			title: 'Name' 
			evaluated: [ :subsystem | subsystem name ]);
		addColumn: (SpStringTableColumn 
			title: 'Implemented interfaces'
			evaluated: [ :subsystem | subsystem implementedInterfaces]);
		yourself.
] 

A subsystem X reimplements resolveDependencies to interact with another subsystem Y.
Root system started.

When hot swapping the subsystem Y to swap to a different implementation, it fails when subsystem X access the Y implementation via >> #YInterface .

Probably renamed in Kepler and not updated yet.

Class {
#name : #PersistenceCommandFailed,
#superclass : #SystemCommandExecutionError,
#instVars : [
'originatingErrorMessageText'
],
#category : #'Sagan-Core'
}

Kepler is currently loading Development of Buoy v4. But since it was changed to comply the new community guide standards it must be changed to load default.