Hismo

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

Hismo

Andre Hora
Hello Doru,

How can I create a "history model" using the Hismo meta-model. Lets say that I have different models (versions) loaded in Moose and I want to create a Hismo model representing these models (versions).
Is there some automatic way to do that?

thanks!

--
Andre Hora


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Hismo

simondenier

On 7 juil. 2011, at 23:29, Andre Hora wrote:

> Hello Doru,
>
> How can I create a "history model" using the Hismo meta-model. Lets say that I have different models (versions) loaded in Moose and I want to create a Hismo model representing these models (versions).
> Is there some automatic way to do that?


As far as I remember, you create one Hismo model, then add each of your versions in order of creation to the Hismo model. It's as simple as that :)

PS: given the great work done by Max and Camillo with FSGit, it should be pretty easy to import a Git repository in Hismo/Kumpel? You can just import the file structure of each commit (a FSGitFileSystem) in a MooseModel. The only problem is a performance problem when browsing a the full history. Right now it's ok to import 100 commits but then it starts to be very slow. Max will have a look at this.

--
Simon Denier




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Hismo

Andre Hora
Hello Simon,

Thanks. I checked the class MooseSampleData :)

On Fri, Jul 8, 2011 at 9:44 AM, Simon Denier <[hidden email]> wrote:

On 7 juil. 2011, at 23:29, Andre Hora wrote:

> Hello Doru,
>
> How can I create a "history model" using the Hismo meta-model. Lets say that I have different models (versions) loaded in Moose and I want to create a Hismo model representing these models (versions).
> Is there some automatic way to do that?


As far as I remember, you create one Hismo model, then add each of your versions in order of creation to the Hismo model. It's as simple as that :)

PS: given the great work done by Max and Camillo with FSGit, it should be pretty easy to import a Git repository in Hismo/Kumpel? You can just import the file structure of each commit (a FSGitFileSystem) in a MooseModel. The only problem is a performance problem when browsing a the full history. Right now it's ok to import 100 commits but then it starts to be very slow. Max will have a look at this.

--
Simon Denier




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--
Andre Hora


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Hismo

Tudor Girba-2
Indeed, that is where the example is.

We do not have a UI for this, but it would be nice to have one based on Merlin.

Cheers,
Doru


On 8 Jul 2011, at 11:22, Andre Hora wrote:

> Hello Simon,
>
> Thanks. I checked the class MooseSampleData :)
>
> On Fri, Jul 8, 2011 at 9:44 AM, Simon Denier <[hidden email]> wrote:
>
> On 7 juil. 2011, at 23:29, Andre Hora wrote:
>
> > Hello Doru,
> >
> > How can I create a "history model" using the Hismo meta-model. Lets say that I have different models (versions) loaded in Moose and I want to create a Hismo model representing these models (versions).
> > Is there some automatic way to do that?
>
>
> As far as I remember, you create one Hismo model, then add each of your versions in order of creation to the Hismo model. It's as simple as that :)
>
> PS: given the great work done by Max and Camillo with FSGit, it should be pretty easy to import a Git repository in Hismo/Kumpel? You can just import the file structure of each commit (a FSGitFileSystem) in a MooseModel. The only problem is a performance problem when browsing a the full history. Right now it's ok to import 100 commits but then it starts to be very slow. Max will have a look at this.
>
> --
> Simon Denier
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
>
> --
> Andre Hora
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"It's not how it is, it is how we see it."


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Hismo

Andre Hora
Hello,

Is there any solution to load not so small versions in Hismo?
I tried with 2 versions of Eclipse.. it does not scale.

regards,


On Fri, Jul 8, 2011 at 6:21 PM, Tudor Girba <[hidden email]> wrote:
Indeed, that is where the example is.

We do not have a UI for this, but it would be nice to have one based on Merlin.

Cheers,
Doru


On 8 Jul 2011, at 11:22, Andre Hora wrote:

> Hello Simon,
>
> Thanks. I checked the class MooseSampleData :)
>
> On Fri, Jul 8, 2011 at 9:44 AM, Simon Denier <[hidden email]> wrote:
>
> On 7 juil. 2011, at 23:29, Andre Hora wrote:
>
> > Hello Doru,
> >
> > How can I create a "history model" using the Hismo meta-model. Lets say that I have different models (versions) loaded in Moose and I want to create a Hismo model representing these models (versions).
> > Is there some automatic way to do that?
>
>
> As far as I remember, you create one Hismo model, then add each of your versions in order of creation to the Hismo model. It's as simple as that :)
>
> PS: given the great work done by Max and Camillo with FSGit, it should be pretty easy to import a Git repository in Hismo/Kumpel? You can just import the file structure of each commit (a FSGitFileSystem) in a MooseModel. The only problem is a performance problem when browsing a the full history. Right now it's ok to import 100 commits but then it starts to be very slow. Max will have a look at this.
>
> --
> Simon Denier
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
>
> --
> Andre Hora
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"It's not how it is, it is how we see it."


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--
Andre Hora


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Hismo

Stéphane Ducasse
Andre did you try by limiting the loaded items (just having packages, class, methods).

Stef

On Jul 8, 2011, at 8:57 PM, Andre Hora wrote:

> Hello,
>
> Is there any solution to load not so small versions in Hismo?
> I tried with 2 versions of Eclipse.. it does not scale.
>
> regards,
>
>
> On Fri, Jul 8, 2011 at 6:21 PM, Tudor Girba <[hidden email]> wrote:
> Indeed, that is where the example is.
>
> We do not have a UI for this, but it would be nice to have one based on Merlin.
>
> Cheers,
> Doru
>
>
> On 8 Jul 2011, at 11:22, Andre Hora wrote:
>
> > Hello Simon,
> >
> > Thanks. I checked the class MooseSampleData :)
> >
> > On Fri, Jul 8, 2011 at 9:44 AM, Simon Denier <[hidden email]> wrote:
> >
> > On 7 juil. 2011, at 23:29, Andre Hora wrote:
> >
> > > Hello Doru,
> > >
> > > How can I create a "history model" using the Hismo meta-model. Lets say that I have different models (versions) loaded in Moose and I want to create a Hismo model representing these models (versions).
> > > Is there some automatic way to do that?
> >
> >
> > As far as I remember, you create one Hismo model, then add each of your versions in order of creation to the Hismo model. It's as simple as that :)
> >
> > PS: given the great work done by Max and Camillo with FSGit, it should be pretty easy to import a Git repository in Hismo/Kumpel? You can just import the file structure of each commit (a FSGitFileSystem) in a MooseModel. The only problem is a performance problem when browsing a the full history. Right now it's ok to import 100 commits but then it starts to be very slow. Max will have a look at this.
> >
> > --
> > Simon Denier
> >
> >
> >
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> >
> >
> > --
> > Andre Hora
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.tudorgirba.com
>
> "It's not how it is, it is how we see it."
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
>
> --
> Andre Hora
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Hismo

Tudor Girba-2
Indeed, I forgot to answer this one.

The only way to scale is to only load limited models of the past versions. Typically, I loaded only Namespaces, Packages, Classes, Inheritances and sometimes Methods.

Cheers,
Doru


On 14 Jul 2011, at 13:06, Stéphane Ducasse wrote:

> Andre did you try by limiting the loaded items (just having packages, class, methods).
>
> Stef
>
> On Jul 8, 2011, at 8:57 PM, Andre Hora wrote:
>
>> Hello,
>>
>> Is there any solution to load not so small versions in Hismo?
>> I tried with 2 versions of Eclipse.. it does not scale.
>>
>> regards,
>>
>>
>> On Fri, Jul 8, 2011 at 6:21 PM, Tudor Girba <[hidden email]> wrote:
>> Indeed, that is where the example is.
>>
>> We do not have a UI for this, but it would be nice to have one based on Merlin.
>>
>> Cheers,
>> Doru
>>
>>
>> On 8 Jul 2011, at 11:22, Andre Hora wrote:
>>
>>> Hello Simon,
>>>
>>> Thanks. I checked the class MooseSampleData :)
>>>
>>> On Fri, Jul 8, 2011 at 9:44 AM, Simon Denier <[hidden email]> wrote:
>>>
>>> On 7 juil. 2011, at 23:29, Andre Hora wrote:
>>>
>>>> Hello Doru,
>>>>
>>>> How can I create a "history model" using the Hismo meta-model. Lets say that I have different models (versions) loaded in Moose and I want to create a Hismo model representing these models (versions).
>>>> Is there some automatic way to do that?
>>>
>>>
>>> As far as I remember, you create one Hismo model, then add each of your versions in order of creation to the Hismo model. It's as simple as that :)
>>>
>>> PS: given the great work done by Max and Camillo with FSGit, it should be pretty easy to import a Git repository in Hismo/Kumpel? You can just import the file structure of each commit (a FSGitFileSystem) in a MooseModel. The only problem is a performance problem when browsing a the full history. Right now it's ok to import 100 commits but then it starts to be very slow. Max will have a look at this.
>>>
>>> --
>>> Simon Denier
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> [hidden email]
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>
>>>
>>>
>>> --
>>> Andre Hora
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> [hidden email]
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> --
>> www.tudorgirba.com
>>
>> "It's not how it is, it is how we see it."
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>>
>>
>> --
>> Andre Hora
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"No matter how many recipes we know, we still value a chef."







_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Hismo

Andre Hora
Thanks, I will try.

On Thu, Jul 14, 2011 at 1:10 PM, Tudor Girba <[hidden email]> wrote:
Indeed, I forgot to answer this one.

The only way to scale is to only load limited models of the past versions. Typically, I loaded only Namespaces, Packages, Classes, Inheritances and sometimes Methods.

Cheers,
Doru


On 14 Jul 2011, at 13:06, Stéphane Ducasse wrote:

> Andre did you try by limiting the loaded items (just having packages, class, methods).
>
> Stef
>
> On Jul 8, 2011, at 8:57 PM, Andre Hora wrote:
>
>> Hello,
>>
>> Is there any solution to load not so small versions in Hismo?
>> I tried with 2 versions of Eclipse.. it does not scale.
>>
>> regards,
>>
>>
>> On Fri, Jul 8, 2011 at 6:21 PM, Tudor Girba <[hidden email]> wrote:
>> Indeed, that is where the example is.
>>
>> We do not have a UI for this, but it would be nice to have one based on Merlin.
>>
>> Cheers,
>> Doru
>>
>>
>> On 8 Jul 2011, at 11:22, Andre Hora wrote:
>>
>>> Hello Simon,
>>>
>>> Thanks. I checked the class MooseSampleData :)
>>>
>>> On Fri, Jul 8, 2011 at 9:44 AM, Simon Denier <[hidden email]> wrote:
>>>
>>> On 7 juil. 2011, at 23:29, Andre Hora wrote:
>>>
>>>> Hello Doru,
>>>>
>>>> How can I create a "history model" using the Hismo meta-model. Lets say that I have different models (versions) loaded in Moose and I want to create a Hismo model representing these models (versions).
>>>> Is there some automatic way to do that?
>>>
>>>
>>> As far as I remember, you create one Hismo model, then add each of your versions in order of creation to the Hismo model. It's as simple as that :)
>>>
>>> PS: given the great work done by Max and Camillo with FSGit, it should be pretty easy to import a Git repository in Hismo/Kumpel? You can just import the file structure of each commit (a FSGitFileSystem) in a MooseModel. The only problem is a performance problem when browsing a the full history. Right now it's ok to import 100 commits but then it starts to be very slow. Max will have a look at this.
>>>
>>> --
>>> Simon Denier
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> [hidden email]
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>
>>>
>>>
>>> --
>>> Andre Hora
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> [hidden email]
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> --
>> www.tudorgirba.com
>>
>> "It's not how it is, it is how we see it."
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>>
>>
>> --
>> Andre Hora
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"No matter how many recipes we know, we still value a chef."







_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--
Andre Hora


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Hismo

Nicolas Anquetil
In reply to this post by Tudor Girba-2

Question for Jannik (and may be Doru)

Do you think what you did for Orion (delta between models) could be used here?
There would be much more changes than what you typically have in Orion, so I am not sure it would be useful...

nicolas

----- Mail original -----

> De: "Tudor Girba" <[hidden email]>
> À: "Moose-related development" <[hidden email]>
> Envoyé: Jeudi 14 Juillet 2011 13:10:28
> Objet: [Moose-dev] Re: Hismo
> Indeed, I forgot to answer this one.
>
> The only way to scale is to only load limited models of the past
> versions. Typically, I loaded only Namespaces, Packages, Classes,
> Inheritances and sometimes Methods.
>
> Cheers,
> Doru
>
>
> On 14 Jul 2011, at 13:06, Stéphane Ducasse wrote:
>
> > Andre did you try by limiting the loaded items (just having
> > packages, class, methods).
> >
> > Stef
> >
> > On Jul 8, 2011, at 8:57 PM, Andre Hora wrote:
> >
> >> Hello,
> >>
> >> Is there any solution to load not so small versions in Hismo?
> >> I tried with 2 versions of Eclipse.. it does not scale.
> >>
> >> regards,
> >>
> >>
> >> On Fri, Jul 8, 2011 at 6:21 PM, Tudor Girba <[hidden email]>
> >> wrote:
> >> Indeed, that is where the example is.
> >>
> >> We do not have a UI for this, but it would be nice to have one
> >> based on Merlin.
> >>
> >> Cheers,
> >> Doru
> >>
> >>
> >> On 8 Jul 2011, at 11:22, Andre Hora wrote:
> >>
> >>> Hello Simon,
> >>>
> >>> Thanks. I checked the class MooseSampleData :)
> >>>
> >>> On Fri, Jul 8, 2011 at 9:44 AM, Simon Denier
> >>> <[hidden email]> wrote:
> >>>
> >>> On 7 juil. 2011, at 23:29, Andre Hora wrote:
> >>>
> >>>> Hello Doru,
> >>>>
> >>>> How can I create a "history model" using the Hismo meta-model.
> >>>> Lets say that I have different models (versions) loaded in Moose
> >>>> and I want to create a Hismo model representing these models
> >>>> (versions).
> >>>> Is there some automatic way to do that?
> >>>
> >>>
> >>> As far as I remember, you create one Hismo model, then add each of
> >>> your versions in order of creation to the Hismo model. It's as
> >>> simple as that :)
> >>>
> >>> PS: given the great work done by Max and Camillo with FSGit, it
> >>> should be pretty easy to import a Git repository in Hismo/Kumpel?
> >>> You can just import the file structure of each commit (a
> >>> FSGitFileSystem) in a MooseModel. The only problem is a
> >>> performance problem when browsing a the full history. Right now
> >>> it's ok to import 100 commits but then it starts to be very slow.
> >>> Max will have a look at this.
> >>>
> >>> --
> >>> Simon Denier
> >>>
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> Moose-dev mailing list
> >>> [hidden email]
> >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >>>
> >>>
> >>>
> >>> --
> >>> Andre Hora
> >>>
> >>> _______________________________________________
> >>> Moose-dev mailing list
> >>> [hidden email]
> >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >>
> >> --
> >> www.tudorgirba.com
> >>
> >> "It's not how it is, it is how we see it."
> >>
> >>
> >> _______________________________________________
> >> Moose-dev mailing list
> >> [hidden email]
> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >>
> >>
> >>
> >> --
> >> Andre Hora
> >>
> >> _______________________________________________
> >> Moose-dev mailing list
> >> [hidden email]
> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.tudorgirba.com
>
> "No matter how many recipes we know, we still value a chef."
>
>
>
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Hismo

Stéphane Ducasse
Orion is good for representing deltas
so we would have a check that.
Hismo is more snapshotting.

Stef

On Jul 15, 2011, at 10:23 AM, Nicolas Anquetil wrote:

>
> Question for Jannik (and may be Doru)
>
> Do you think what you did for Orion (delta between models) could be used here?
> There would be much more changes than what you typically have in Orion, so I am not sure it would be useful...
>
> nicolas
>
> ----- Mail original -----
>> De: "Tudor Girba" <[hidden email]>
>> À: "Moose-related development" <[hidden email]>
>> Envoyé: Jeudi 14 Juillet 2011 13:10:28
>> Objet: [Moose-dev] Re: Hismo
>> Indeed, I forgot to answer this one.
>>
>> The only way to scale is to only load limited models of the past
>> versions. Typically, I loaded only Namespaces, Packages, Classes,
>> Inheritances and sometimes Methods.
>>
>> Cheers,
>> Doru
>>
>>
>> On 14 Jul 2011, at 13:06, Stéphane Ducasse wrote:
>>
>>> Andre did you try by limiting the loaded items (just having
>>> packages, class, methods).
>>>
>>> Stef
>>>
>>> On Jul 8, 2011, at 8:57 PM, Andre Hora wrote:
>>>
>>>> Hello,
>>>>
>>>> Is there any solution to load not so small versions in Hismo?
>>>> I tried with 2 versions of Eclipse.. it does not scale.
>>>>
>>>> regards,
>>>>
>>>>
>>>> On Fri, Jul 8, 2011 at 6:21 PM, Tudor Girba <[hidden email]>
>>>> wrote:
>>>> Indeed, that is where the example is.
>>>>
>>>> We do not have a UI for this, but it would be nice to have one
>>>> based on Merlin.
>>>>
>>>> Cheers,
>>>> Doru
>>>>
>>>>
>>>> On 8 Jul 2011, at 11:22, Andre Hora wrote:
>>>>
>>>>> Hello Simon,
>>>>>
>>>>> Thanks. I checked the class MooseSampleData :)
>>>>>
>>>>> On Fri, Jul 8, 2011 at 9:44 AM, Simon Denier
>>>>> <[hidden email]> wrote:
>>>>>
>>>>> On 7 juil. 2011, at 23:29, Andre Hora wrote:
>>>>>
>>>>>> Hello Doru,
>>>>>>
>>>>>> How can I create a "history model" using the Hismo meta-model.
>>>>>> Lets say that I have different models (versions) loaded in Moose
>>>>>> and I want to create a Hismo model representing these models
>>>>>> (versions).
>>>>>> Is there some automatic way to do that?
>>>>>
>>>>>
>>>>> As far as I remember, you create one Hismo model, then add each of
>>>>> your versions in order of creation to the Hismo model. It's as
>>>>> simple as that :)
>>>>>
>>>>> PS: given the great work done by Max and Camillo with FSGit, it
>>>>> should be pretty easy to import a Git repository in Hismo/Kumpel?
>>>>> You can just import the file structure of each commit (a
>>>>> FSGitFileSystem) in a MooseModel. The only problem is a
>>>>> performance problem when browsing a the full history. Right now
>>>>> it's ok to import 100 commits but then it starts to be very slow.
>>>>> Max will have a look at this.
>>>>>
>>>>> --
>>>>> Simon Denier
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Moose-dev mailing list
>>>>> [hidden email]
>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Andre Hora
>>>>>
>>>>> _______________________________________________
>>>>> Moose-dev mailing list
>>>>> [hidden email]
>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>
>>>> --
>>>> www.tudorgirba.com
>>>>
>>>> "It's not how it is, it is how we see it."
>>>>
>>>>
>>>> _______________________________________________
>>>> Moose-dev mailing list
>>>> [hidden email]
>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>
>>>>
>>>>
>>>> --
>>>> Andre Hora
>>>>
>>>> _______________________________________________
>>>> Moose-dev mailing list
>>>> [hidden email]
>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> [hidden email]
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> --
>> www.tudorgirba.com
>>
>> "No matter how many recipes we know, we still value a chef."
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Hismo

Tudor Girba-2
Hismo is not just for snapshotting. It's just that the use cases were based on snapshots :). If there would be a diff information, it can easily be accommodated as a subclass of Version.

Cheers,
Doru


On 15 Jul 2011, at 13:39, Stéphane Ducasse wrote:

> Orion is good for representing deltas
> so we would have a check that.
> Hismo is more snapshotting.
>
> Stef
>
> On Jul 15, 2011, at 10:23 AM, Nicolas Anquetil wrote:
>
>>
>> Question for Jannik (and may be Doru)
>>
>> Do you think what you did for Orion (delta between models) could be used here?
>> There would be much more changes than what you typically have in Orion, so I am not sure it would be useful...
>>
>> nicolas
>>
>> ----- Mail original -----
>>> De: "Tudor Girba" <[hidden email]>
>>> À: "Moose-related development" <[hidden email]>
>>> Envoyé: Jeudi 14 Juillet 2011 13:10:28
>>> Objet: [Moose-dev] Re: Hismo
>>> Indeed, I forgot to answer this one.
>>>
>>> The only way to scale is to only load limited models of the past
>>> versions. Typically, I loaded only Namespaces, Packages, Classes,
>>> Inheritances and sometimes Methods.
>>>
>>> Cheers,
>>> Doru
>>>
>>>
>>> On 14 Jul 2011, at 13:06, Stéphane Ducasse wrote:
>>>
>>>> Andre did you try by limiting the loaded items (just having
>>>> packages, class, methods).
>>>>
>>>> Stef
>>>>
>>>> On Jul 8, 2011, at 8:57 PM, Andre Hora wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> Is there any solution to load not so small versions in Hismo?
>>>>> I tried with 2 versions of Eclipse.. it does not scale.
>>>>>
>>>>> regards,
>>>>>
>>>>>
>>>>> On Fri, Jul 8, 2011 at 6:21 PM, Tudor Girba <[hidden email]>
>>>>> wrote:
>>>>> Indeed, that is where the example is.
>>>>>
>>>>> We do not have a UI for this, but it would be nice to have one
>>>>> based on Merlin.
>>>>>
>>>>> Cheers,
>>>>> Doru
>>>>>
>>>>>
>>>>> On 8 Jul 2011, at 11:22, Andre Hora wrote:
>>>>>
>>>>>> Hello Simon,
>>>>>>
>>>>>> Thanks. I checked the class MooseSampleData :)
>>>>>>
>>>>>> On Fri, Jul 8, 2011 at 9:44 AM, Simon Denier
>>>>>> <[hidden email]> wrote:
>>>>>>
>>>>>> On 7 juil. 2011, at 23:29, Andre Hora wrote:
>>>>>>
>>>>>>> Hello Doru,
>>>>>>>
>>>>>>> How can I create a "history model" using the Hismo meta-model.
>>>>>>> Lets say that I have different models (versions) loaded in Moose
>>>>>>> and I want to create a Hismo model representing these models
>>>>>>> (versions).
>>>>>>> Is there some automatic way to do that?
>>>>>>
>>>>>>
>>>>>> As far as I remember, you create one Hismo model, then add each of
>>>>>> your versions in order of creation to the Hismo model. It's as
>>>>>> simple as that :)
>>>>>>
>>>>>> PS: given the great work done by Max and Camillo with FSGit, it
>>>>>> should be pretty easy to import a Git repository in Hismo/Kumpel?
>>>>>> You can just import the file structure of each commit (a
>>>>>> FSGitFileSystem) in a MooseModel. The only problem is a
>>>>>> performance problem when browsing a the full history. Right now
>>>>>> it's ok to import 100 commits but then it starts to be very slow.
>>>>>> Max will have a look at this.
>>>>>>
>>>>>> --
>>>>>> Simon Denier
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Moose-dev mailing list
>>>>>> [hidden email]
>>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Andre Hora
>>>>>>
>>>>>> _______________________________________________
>>>>>> Moose-dev mailing list
>>>>>> [hidden email]
>>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>>
>>>>> --
>>>>> www.tudorgirba.com
>>>>>
>>>>> "It's not how it is, it is how we see it."
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Moose-dev mailing list
>>>>> [hidden email]
>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Andre Hora
>>>>>
>>>>> _______________________________________________
>>>>> Moose-dev mailing list
>>>>> [hidden email]
>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>
>>>>
>>>> _______________________________________________
>>>> Moose-dev mailing list
>>>> [hidden email]
>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>
>>> --
>>> www.tudorgirba.com
>>>
>>> "No matter how many recipes we know, we still value a chef."
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> [hidden email]
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"The coherence of a trip is given by the clearness of the goal."





_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Hismo

jannik laval
Hi,

And Orion is adapted to make changes on models.

Jannik

On Jul 15, 2011, at 13:44 , Tudor Girba wrote:

> Hismo is not just for snapshotting. It's just that the use cases were based on snapshots :). If there would be a diff information, it can easily be accommodated as a subclass of Version.
>
> Cheers,
> Doru
>
>
> On 15 Jul 2011, at 13:39, Stéphane Ducasse wrote:
>
>> Orion is good for representing deltas
>> so we would have a check that.
>> Hismo is more snapshotting.
>>
>> Stef
>>
>> On Jul 15, 2011, at 10:23 AM, Nicolas Anquetil wrote:
>>
>>>
>>> Question for Jannik (and may be Doru)
>>>
>>> Do you think what you did for Orion (delta between models) could be used here?
>>> There would be much more changes than what you typically have in Orion, so I am not sure it would be useful...
>>>
>>> nicolas
>>>
>>> ----- Mail original -----
>>>> De: "Tudor Girba" <[hidden email]>
>>>> À: "Moose-related development" <[hidden email]>
>>>> Envoyé: Jeudi 14 Juillet 2011 13:10:28
>>>> Objet: [Moose-dev] Re: Hismo
>>>> Indeed, I forgot to answer this one.
>>>>
>>>> The only way to scale is to only load limited models of the past
>>>> versions. Typically, I loaded only Namespaces, Packages, Classes,
>>>> Inheritances and sometimes Methods.
>>>>
>>>> Cheers,
>>>> Doru
>>>>
>>>>
>>>> On 14 Jul 2011, at 13:06, Stéphane Ducasse wrote:
>>>>
>>>>> Andre did you try by limiting the loaded items (just having
>>>>> packages, class, methods).
>>>>>
>>>>> Stef
>>>>>
>>>>> On Jul 8, 2011, at 8:57 PM, Andre Hora wrote:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> Is there any solution to load not so small versions in Hismo?
>>>>>> I tried with 2 versions of Eclipse.. it does not scale.
>>>>>>
>>>>>> regards,
>>>>>>
>>>>>>
>>>>>> On Fri, Jul 8, 2011 at 6:21 PM, Tudor Girba <[hidden email]>
>>>>>> wrote:
>>>>>> Indeed, that is where the example is.
>>>>>>
>>>>>> We do not have a UI for this, but it would be nice to have one
>>>>>> based on Merlin.
>>>>>>
>>>>>> Cheers,
>>>>>> Doru
>>>>>>
>>>>>>
>>>>>> On 8 Jul 2011, at 11:22, Andre Hora wrote:
>>>>>>
>>>>>>> Hello Simon,
>>>>>>>
>>>>>>> Thanks. I checked the class MooseSampleData :)
>>>>>>>
>>>>>>> On Fri, Jul 8, 2011 at 9:44 AM, Simon Denier
>>>>>>> <[hidden email]> wrote:
>>>>>>>
>>>>>>> On 7 juil. 2011, at 23:29, Andre Hora wrote:
>>>>>>>
>>>>>>>> Hello Doru,
>>>>>>>>
>>>>>>>> How can I create a "history model" using the Hismo meta-model.
>>>>>>>> Lets say that I have different models (versions) loaded in Moose
>>>>>>>> and I want to create a Hismo model representing these models
>>>>>>>> (versions).
>>>>>>>> Is there some automatic way to do that?
>>>>>>>
>>>>>>>
>>>>>>> As far as I remember, you create one Hismo model, then add each of
>>>>>>> your versions in order of creation to the Hismo model. It's as
>>>>>>> simple as that :)
>>>>>>>
>>>>>>> PS: given the great work done by Max and Camillo with FSGit, it
>>>>>>> should be pretty easy to import a Git repository in Hismo/Kumpel?
>>>>>>> You can just import the file structure of each commit (a
>>>>>>> FSGitFileSystem) in a MooseModel. The only problem is a
>>>>>>> performance problem when browsing a the full history. Right now
>>>>>>> it's ok to import 100 commits but then it starts to be very slow.
>>>>>>> Max will have a look at this.
>>>>>>>
>>>>>>> --
>>>>>>> Simon Denier
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Moose-dev mailing list
>>>>>>> [hidden email]
>>>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Andre Hora
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Moose-dev mailing list
>>>>>>> [hidden email]
>>>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>>>
>>>>>> --
>>>>>> www.tudorgirba.com
>>>>>>
>>>>>> "It's not how it is, it is how we see it."
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Moose-dev mailing list
>>>>>> [hidden email]
>>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Andre Hora
>>>>>>
>>>>>> _______________________________________________
>>>>>> Moose-dev mailing list
>>>>>> [hidden email]
>>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Moose-dev mailing list
>>>>> [hidden email]
>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>
>>>> --
>>>> www.tudorgirba.com
>>>>
>>>> "No matter how many recipes we know, we still value a chef."
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Moose-dev mailing list
>>>> [hidden email]
>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> [hidden email]
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.tudorgirba.com
>
> "The coherence of a trip is given by the clearness of the goal."
>
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

---
Jannik Laval


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev