Hi, Can we define what we mean by "Light"? Are we talking about - memory consumption? - Dependencies? - Amount of code? - Complexity? - Size of API?
Guille On Fri, Jun 8, 2018 at 2:31 AM, Hernán Morales <[email protected]> wrote: > Hi Norbert, > > El 7 jun. 2018, a las 03:23, Norbert Hartl <[email protected]> escribió: > > > > Am 06.06.2018 um 22:00 schrieb Hernán Morales Durand < > [email protected]>: > > Hello Martin, > > 2018-06-05 15:49 GMT-03:00 Martin Dias <[email protected]>: > > 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 > > > Ok, so this could be used by any application to log events? Like a > lite version of Beacon logger? > > > Do you assume Beacon is not light? Doesn‘t really matter but a lot of > people seem to assume it is not. > > > I don’t know, never used Beacon. However I know Log4s is not light and I > want to replace it in my projects for some simple logging mechanism. > > I think the are on two different axes. Beacon is more about distribution > of notifications in the system and Ombu seems to be a store only. So the > combination could be cool to have a consumer in beacon that writes to an > Ombu Store > > > Thank you for the tip, I will have a look because I am specially > interested in projects using Beacon. > > Cheers, > > Hernán > > > Norbert > > I am trying to get what would be the typical use case for a "common" app. > > 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. > > > Nice! > I am trying again to make re-use of your work if possible :) > I found a reference in EpLogNodeGraphModel. But could > HiRulerController be used off the Epicea case? > Maybe could you provide a stand-alone example? > > About the documentation use case: > > Class { > #name : #HiedraExampleModel, > #superclass : #ComposableModel, > #instVars : [ > 'treeModel rulerController' > ], > #category : #HiedraExample > } > > { #category : #initialization } > HiedraExampleModel >> initializePresenter [ > > super initializePresenter. > > rulerController := HiRulerController new. > > rulerController treeModel: treeModel. > treeModel whenRootsChanged: [ > rulerController updateFromTree ]. > > ] > > > How do you evaluate that code inside Pharo? > > Thank you, > > Hernán > > > > > > Cheers, Martín > > > Couldn't find any description in the link. > > Cheers, > > Hernán > > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13
