Re: [Pharo-project] TORCH: supporting source-code change integration
Locked
Re: [Pharo-project] TORCH: supporting source-code change integration
 
|
Hi Veronica,
A bit of feedback: - After loading Torch, the package contextual menu seems to crash the Monticello Browser - You extend isSuper in RBProgramNode and RBVariableNode, which generates an override conflict with methods in Moose-Core. - The Glamour tags look different, so I guess you also have some Glamour overrides. That should not happen :). Maybe you have some suggestions for improvement, or maybe you just need the border for the [i] icon? Cheers, Doru On 18 May 2010, at 15:16, Veronica Isabel Uquillas Gomez wrote: > Hi Tudor, > > thank you :D > > sure!!! > > cheers, > Veronica > > > On 18 May 2010, at 11:39, Tudor Girba wrote: > >> Hi Veronica, >> >> It is pretty impressive :). >> >> Would it be Ok if I added this on the Moose page? >> >> Cheers, >> Doru >> >> >> On 18 May 2010, at 11:21, Stéphane Ducasse wrote: >> >>> Thanks veronica. >>> lukas said that he was impressed this is a complement :) >>> >>> On May 18, 2010, at 11:00 AM, Veronica Isabel Uquillas Gomez wrote: >>> >>>> Dear all, >>>> >>>> I would like to announce Torch, a tool for supporting source-code >>>> change integration. For now, it offers visualizations of the >>>> changes and enhanced change lists. >>>> Torch can be accessed through Monticello (in the main MC browser, >>>> in the repository browser or in the history browser). Selecting a >>>> version or slice, you can view the changes with Torch using the >>>> contextual menu. >>>> Once you open the Torch dashboard, you can access the enhanced >>>> change list or a detailed visualization via the contextual menu >>>> as well. >>>> >>>> Torch is available on SqueakSource, the repository is named >>>> Torch, and you need to load the ConfigurationOfTorch package. >>>> It runs in a dev or core image. >>>> >>>> For a dev image. >>>> - ConfigurationOfTorch loadVersion10 >>>> >>>> For a core image. >>>> 1) Set fonts - described in the attached file. >>>> 2) ConfigurationOfTorch loadDefault >>>> >>>> I would appreciate comments and feedback! >>>> >>>> Best Regards, >>>> Verónica Uquillas Gómez >>>> Vrije University Brussel - SOFT Lab >>>> University of Lille - RMOD Team >>>> >>>> <torchFontsScript.st> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> [hidden email] >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> [hidden email] >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> -- >> www.tudorgirba.com >> >> "Problem solving efficiency grows with the abstractness level of >> problem understanding." >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> [hidden email] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "Problem solving efficiency grows with the abstractness level of problem understanding." _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Re: [Pharo-project] TORCH: supporting source-code change integration
|
|
On May 19, 2010, at 12:47 AM, Tudor Girba wrote: > Hi Veronica, > > A bit of feedback: > - After loading Torch, the package contextual menu seems to crash the Monticello Browser > - You extend isSuper in RBProgramNode and RBVariableNode, which generates an override conflict with methods in Moose-Core. may be moose should have a look at the new AST-semantics package that lukas created because veronica used that ones originally and after a discussing with lukas he created ast-semantics > - The Glamour tags look different, so I guess you also have some Glamour overrides. That should not happen :). Maybe you have some suggestions for improvement, or maybe you just need the border for the [i] icon? > > Cheers, > Doru > > > On 18 May 2010, at 15:16, Veronica Isabel Uquillas Gomez wrote: > >> Hi Tudor, >> >> thank you :D >> >> sure!!! >> >> cheers, >> Veronica >> >> >> On 18 May 2010, at 11:39, Tudor Girba wrote: >> >>> Hi Veronica, >>> >>> It is pretty impressive :). >>> >>> Would it be Ok if I added this on the Moose page? >>> >>> Cheers, >>> Doru >>> >>> >>> On 18 May 2010, at 11:21, Stéphane Ducasse wrote: >>> >>>> Thanks veronica. >>>> lukas said that he was impressed this is a complement :) >>>> >>>> On May 18, 2010, at 11:00 AM, Veronica Isabel Uquillas Gomez wrote: >>>> >>>>> Dear all, >>>>> >>>>> I would like to announce Torch, a tool for supporting source-code change integration. For now, it offers visualizations of the changes and enhanced change lists. >>>>> Torch can be accessed through Monticello (in the main MC browser, in the repository browser or in the history browser). Selecting a version or slice, you can view the changes with Torch using the contextual menu. >>>>> Once you open the Torch dashboard, you can access the enhanced change list or a detailed visualization via the contextual menu as well. >>>>> >>>>> Torch is available on SqueakSource, the repository is named Torch, and you need to load the ConfigurationOfTorch package. >>>>> It runs in a dev or core image. >>>>> >>>>> For a dev image. >>>>> - ConfigurationOfTorch loadVersion10 >>>>> >>>>> For a core image. >>>>> 1) Set fonts - described in the attached file. >>>>> 2) ConfigurationOfTorch loadDefault >>>>> >>>>> I would appreciate comments and feedback! >>>>> >>>>> Best Regards, >>>>> Verónica Uquillas Gómez >>>>> Vrije University Brussel - SOFT Lab >>>>> University of Lille - RMOD Team >>>>> >>>>> <torchFontsScript.st> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> [hidden email] >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> [hidden email] >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> -- >>> www.tudorgirba.com >>> >>> "Problem solving efficiency grows with the abstractness level of problem understanding." >>> >>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> [hidden email] >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> [hidden email] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > www.tudorgirba.com > > "Problem solving efficiency grows with the abstractness level of problem understanding." > > > > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Re: [Pharo-project] TORCH: supporting source-code change integration
|
|
Hi Tudor,
- could you be more specific, when does the MC browser crash?, i haven't noticed any problem with it. - Yup, Lukas created the AST-semantics package, and I have to include it - No, I am not overriding code, that is a setting already included in Glamour, but true, the border is a cleaner solution... will take a look thank you, Veronica On 19 May 2010, at 08:50, Stéphane Ducasse wrote: > > On May 19, 2010, at 12:47 AM, Tudor Girba wrote: > >> Hi Veronica, >> >> A bit of feedback: >> - After loading Torch, the package contextual menu seems to crash the Monticello Browser >> - You extend isSuper in RBProgramNode and RBVariableNode, which generates an override conflict with methods in Moose-Core. > > may be moose should have a look at the new AST-semantics package that lukas created because veronica used that ones > originally and after a discussing with lukas he created ast-semantics > >> - The Glamour tags look different, so I guess you also have some Glamour overrides. That should not happen :). Maybe you have some suggestions for improvement, or maybe you just need the border for the [i] icon? >> >> Cheers, >> Doru >> >> >> On 18 May 2010, at 15:16, Veronica Isabel Uquillas Gomez wrote: >> >>> Hi Tudor, >>> >>> thank you :D >>> >>> sure!!! >>> >>> cheers, >>> Veronica >>> >>> >>> On 18 May 2010, at 11:39, Tudor Girba wrote: >>> >>>> Hi Veronica, >>>> >>>> It is pretty impressive :). >>>> >>>> Would it be Ok if I added this on the Moose page? >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>> On 18 May 2010, at 11:21, Stéphane Ducasse wrote: >>>> >>>>> Thanks veronica. >>>>> lukas said that he was impressed this is a complement :) >>>>> >>>>> On May 18, 2010, at 11:00 AM, Veronica Isabel Uquillas Gomez wrote: >>>>> >>>>>> Dear all, >>>>>> >>>>>> I would like to announce Torch, a tool for supporting source-code change integration. For now, it offers visualizations of the changes and enhanced change lists. >>>>>> Torch can be accessed through Monticello (in the main MC browser, in the repository browser or in the history browser). Selecting a version or slice, you can view the changes with Torch using the contextual menu. >>>>>> Once you open the Torch dashboard, you can access the enhanced change list or a detailed visualization via the contextual menu as well. >>>>>> >>>>>> Torch is available on SqueakSource, the repository is named Torch, and you need to load the ConfigurationOfTorch package. >>>>>> It runs in a dev or core image. >>>>>> >>>>>> For a dev image. >>>>>> - ConfigurationOfTorch loadVersion10 >>>>>> >>>>>> For a core image. >>>>>> 1) Set fonts - described in the attached file. >>>>>> 2) ConfigurationOfTorch loadDefault >>>>>> >>>>>> I would appreciate comments and feedback! >>>>>> >>>>>> Best Regards, >>>>>> Verónica Uquillas Gómez >>>>>> Vrije University Brussel - SOFT Lab >>>>>> University of Lille - RMOD Team >>>>>> >>>>>> <torchFontsScript.st> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Pharo-project mailing list >>>>>> [hidden email] >>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>> >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> [hidden email] >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "Problem solving efficiency grows with the abstractness level of problem understanding." >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> [hidden email] >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> [hidden email] >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> -- >> www.tudorgirba.com >> >> "Problem solving efficiency grows with the abstractness level of problem understanding." >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> [hidden email] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
«
Return to Moose
|
1 view|%1 views
| Free forum by Nabble | Edit this page |