Upppssss, I just see this email. Since Abdelghani visits RMoD, I've discussed with him in person about this topic.
Ring-Ficus is an alternative implementation to Ring (as it is in the Pharo image). Like Ring, Ficus-Ring provides models that represent system's code entities, and they are also polymorphic with them. For example, RFiClass shares the API of Class (partially) . The main differences are: - closed-universe approach: a Ring-Ficus code entity will always answers a Ring-Ficus code entity (in Ring it is not always like that) - efficient for importing and querying whole Pharo environments: for example, you can import all Pharo 40xxx code entities and query them, e.g. find all the implementors or senders of a selector at each version. Martin On Sat, Jun 6, 2015 at 3:34 PM, stepharo <steph...@free.fr> wrote: > Hi abdelghani > > Welcome to this list :) > > Hi Guys, > > I believe the Ring metamodel has been proposed 4 or 5 years earlier. > Is it acctually in use in the current pharo tools? which ones? > > > Ring should be improved (probably with stubs) to support that we can > create a method and that it does not create > automatically the class of the method. > > Ring proposed strategy to query the code of a method (the one currently > being in the image), or the method represented in the past or another one. > and we should have a look at it. > > I have been told that Martin has develloped a different model : Ficus > > > Martin explained to me that ficus is built on two parts: one that describe > the model and they other the "body " of an entity (data) > and such data can be shared between multiple versions. > > What are the limitations that Martin tried to fixed? > What can be further unhanced? > > Thanks. > > Abdou. > > >
