On Wed, Jun 6, 2018 at 4:27 AM Marcus Denker <[email protected]> wrote:
> > > > On 5 Jun 2018, at 20:49, Martin Dias <[email protected]> wrote: > > > > On Tue, Jun 5, 2018 at 3:30 PM Hernán Morales Durand > > <[email protected]> wrote: > >> What are Ombu and Hiedra? > > > > Hello Hernán, this is how I described them: > > > > Ombu: > > "Epicea has a small subproject, named Ombu, which provides simple > > persistence. By default, Ombu uses STON to write the events when they > > are announced in the system." > > ------- from http://smalltalkhub.com/#!/~MartinDias/Epicea > > > > Hiedra: > > "It is a small Pharo project to visually connect items in a > > history-like graph. It uses Athens, and provides support for Morphic > > and Spec." > > ------- from https://github.com/tinchodias/hiedra which is a repo that > > I might close or should say in readme that it's not the official repo > > > > But not sure if I described correctly... in concrete, Hiedra is what's > > used from Epicea Spec UI in a TableModel to draw the links between > > epicea logs in the left panel. > > > > We should add exactly those description as package level comments. > > https://pharo.fogbugz.com/f/cases/22079/package-comments-for-Ombu-and-Hiedra Fine > > > What I do not like is that the package name gives no clue what this is > about… > Not even the “neighbourhood”. E.g. it does not even get clear that Ombu > and Epicea are related… > But we have that problem with many packages. > > I agree. In the beginning, when this was a prototype, it made sense to me to have 2 separate projects but at the end they are so closely related that it could be good to move Ombu classes into Epicea. > Marcus > > > >
