- Pharo-users - lists.pharo.org

Re: [Pharo-users] FileTree Monticello Repository

by Goubier Thierry

Le 13/09/2013 17:04, btc(a)openinworld.com a Ã©crit : > Goubier Thierry wrote: >> >> >> Le 13/09/2013 04:25, Esteban A. Maringolo a Ã©crit : >>> Is anybody using FileTree repositories? >> >> Which repositories? Dale's github? >> >>> If so, I'd like to know the pros and cons of using it. >> >> More complex to use than Smalltalkhub/Squeaksource because it is not >> yet integrated in the default image. Some features may not work, but >> average MC work under Pharo2.0 works fine with all features of >> Filetree (including gitfiletree). >> >> Easier to use than Smalltalkhub/Squeaksource for authentification. >> >>> I want to use to version everything with git, but I don't know how it >>> keeps git (it is, FileTree files) in sync with MC versions. >> >> A filetree repository appears as a MC repository in the same way as >> another type of MC repository. >> >> Filetree will require that you do all your version management in the >> git repo by hand (i.e. save a version of your package in a filetree >> repo, then switch to a console to commit it. If you forget to commit >> and save a new version of a package on the filetree repo, you >> overwrite the previous version and git will not record it. Filetree by >> itself will only show you the state of the HEAD of your git repository). >> >> If you use gitfiletree (it sits over Filetree), then git commit will >> be done for you when saving your package, and the repository browser >> will show you all the history of the repository, exactly as if it was >> a Smalltalkhub or Squeaksource repository. What will remain to do on >> the command line are the git push and whatever management you do on >> the repository (merging, branching, even if you can also merge via MC >> instead). In short, gitfiletree calls git for you and parse the >> results :) >> >> I'm still wondering about adding more git commands inside the MC GUI >> to do more from inside Pharo (like automagically pushing), but I don't >> want to enforce a specific way of organising the git repository... and >> I'm just trying to get gitfiletree to pass its tests in the pharo3.0 >> branch of Filetree at the moment. >> >> Does this answer your questions? >> >> Thierry > > but I don't want to enforce a specific way of organising the git > repository > > I see this extreme altruism :) around the community, and while it is > very admirable, I think sometimes its misplaced :). The flip side is > that some people (like me) aren't really familiar with git don't know > how we might want git organised, or even what the options are. > Unfortunately this stalls my motivation to try it out (sorry, weak, I > know - but I admit it, and I think its common (or do I just think that > to make myself feel better)). Having a concrete implementation of any > additional functionality that might make git more transparent "out of > the box" would be beneficial for its uptake. As well, without a > concrete example, others who might want to implement something like that > have to start more from scratch, whereas your concrete example might be > 90% of what someone wants and then its only 10% that they need to > customize. The reality of human nature is that its easier to criticize > to pick out what you don't like, than to create something new. However > the hidden benefit of this criticism is that it engages people in > discussion and then you hook them into helping develop what they need. > So anyway, my short response is, if "you" would benefit from that added > functionality then "just do it". :) > cheers -ben > > P.S. I admire what I read about progress with Filtetree and GitFileTree > towards using git. For some segments outside the Pharo community that > we want to draw in, this is going to be an important consideration. Hi Ben, I'm sorry that this doesn't convince you to use git with Pharo :) So far, I very happy with the functionality gitfiletree has; for a common user like me it has been working very nicely for quite some time now :):) It has the features I need: allow the introduction of pharo development in any pre-existing / mixed language repository; allow me to build in 5 sec a new repo for a package; integrate with github; better long history exploration than anything else under Pharo. At the same time, it was a bit of a mock-up, this gitfiletree: just adding some automation to a filetree over git repository, and also add some motivation for someone else to see what can be done and how, so as to eventually reimplement it as a FileSystem / or as a libcgit instead of calling git log and git archive :) It's now a bit of a bench for some future directions of FileTree, such as removing the metadata which is provoking conflicts when merging under git, or as a new replacement of changesets (but EPICEA is going in another interesting direction, so I'm not trying anything there). And don't worry for my altruism not adding functionalities :) I'm the guy who wrote a complete alternative IDE for pharo 2.0, just because I prefer it to Nautilus :O Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Sept. 13, 2013

Re: [Pharo-users] FileTree Monticello Repository

by btc＠openinworld.com

Goubier Thierry wrote: > > > Le 13/09/2013 04:25, Esteban A. Maringolo a Ã©crit : >> Is anybody using FileTree repositories? > > Which repositories? Dale's github? > >> If so, I'd like to know the pros and cons of using it. > > More complex to use than Smalltalkhub/Squeaksource because it is not > yet integrated in the default image. Some features may not work, but > average MC work under Pharo2.0 works fine with all features of > Filetree (including gitfiletree). > > Easier to use than Smalltalkhub/Squeaksource for authentification. > >> I want to use to version everything with git, but I don't know how it >> keeps git (it is, FileTree files) in sync with MC versions. > > A filetree repository appears as a MC repository in the same way as > another type of MC repository. > > Filetree will require that you do all your version management in the > git repo by hand (i.e. save a version of your package in a filetree > repo, then switch to a console to commit it. If you forget to commit > and save a new version of a package on the filetree repo, you > overwrite the previous version and git will not record it. Filetree by > itself will only show you the state of the HEAD of your git repository). > > If you use gitfiletree (it sits over Filetree), then git commit will > be done for you when saving your package, and the repository browser > will show you all the history of the repository, exactly as if it was > a Smalltalkhub or Squeaksource repository. What will remain to do on > the command line are the git push and whatever management you do on > the repository (merging, branching, even if you can also merge via MC > instead). In short, gitfiletree calls git for you and parse the > results :) > > I'm still wondering about adding more git commands inside the MC GUI > to do more from inside Pharo (like automagically pushing), but I don't > want to enforce a specific way of organising the git repository... and > I'm just trying to get gitfiletree to pass its tests in the pharo3.0 > branch of Filetree at the moment. > > Does this answer your questions? > > Thierry > but I don't want to enforce a specific way of organising the git repository I see this extreme altruism :) around the community, and while it is very admirable, I think sometimes its misplaced :). The flip side is that some people (like me) aren't really familiar with git don't know how we might want git organised, or even what the options are. Unfortunately this stalls my motivation to try it out (sorry, weak, I know - but I admit it, and I think its common (or do I just think that to make myself feel better)). Having a concrete implementation of any additional functionality that might make git more transparent "out of the box" would be beneficial for its uptake. As well, without a concrete example, others who might want to implement something like that have to start more from scratch, whereas your concrete example might be 90% of what someone wants and then its only 10% that they need to customize. The reality of human nature is that its easier to criticize to pick out what you don't like, than to create something new. However the hidden benefit of this criticism is that it engages people in discussion and then you hook them into helping develop what they need. So anyway, my short response is, if "you" would benefit from that added functionality then "just do it". :) cheers -ben P.S. I admire what I read about progress with Filtetree and GitFileTree towards using git. For some segments outside the Pharo community that we want to draw in, this is going to be an important consideration.

Sept. 13, 2013

Re: [Pharo-users] FileTree Monticello Repository

by Goubier Thierry

Le 13/09/2013 16:30, Esteban A. Maringolo a Ã©crit : > Goubier, > > You do answer my questions. I'm certainly looking for something like > gitfiletree then. > > One last question I have is, does the gitfiletree:// repository type > come bundled with the FileTree package? Or do I need to download and > install it separately? Yes, I think it is in the default configuration for pharo 2.0. > Regarding adding more git commands inside the MC GUI I'd like to have > them separated. > Unless I can load previous versions of my MC package and that causes the > git to checkout the files from a previous commit. No, it does a lot better than that. It loads the definitions of a previous version of a package without doing a checkout on the repo, to do with it in MC as you want : load/merge/compare changes. If you know git, it uses 'git archive' to retrieve a specific package version in the commit history. It also bypass most of the stored metadata in the package: methods timestamps are the git commit timestamps, package history is the git commit history of the repo (pruned to remove all commits not related to the package, in the case of a repo containing multiple packages). > I don't know how the branching is managed or if it's simply ignored. I'm displaying it in the repository inspector, otherwise it's ignored. Thierry > Regards, > > Esteban A. Maringolo > > > 2013/9/13 Goubier Thierry <thierry.goubier(a)cea.fr > <mailto:thierry.goubier@cea.fr>> > > > > Le 13/09/2013 04:25, Esteban A. Maringolo a Ã©crit : > > Is anybody using FileTree repositories? > > > Which repositories? Dale's github? > > > If so, I'd like to know the pros and cons of using it. > > > More complex to use than Smalltalkhub/Squeaksource because it is not > yet integrated in the default image. Some features may not work, but > average MC work under Pharo2.0 works fine with all features of > Filetree (including gitfiletree). > > Easier to use than Smalltalkhub/Squeaksource for authentification. > > > I want to use to version everything with git, but I don't know > how it > keeps git (it is, FileTree files) in sync with MC versions. > > > A filetree repository appears as a MC repository in the same way as > another type of MC repository. > > Filetree will require that you do all your version management in the > git repo by hand (i.e. save a version of your package in a filetree > repo, then switch to a console to commit it. If you forget to commit > and save a new version of a package on the filetree repo, you > overwrite the previous version and git will not record it. Filetree > by itself will only show you the state of the HEAD of your git > repository). > > If you use gitfiletree (it sits over Filetree), then git commit will > be done for you when saving your package, and the repository browser > will show you all the history of the repository, exactly as if it > was a Smalltalkhub or Squeaksource repository. What will remain to > do on the command line are the git push and whatever management you > do on the repository (merging, branching, even if you can also merge > via MC instead). In short, gitfiletree calls git for you and parse > the results :) > > I'm still wondering about adding more git commands inside the MC GUI > to do more from inside Pharo (like automagically pushing), but I > don't want to enforce a specific way of organising the git > repository... and I'm just trying to get gitfiletree to pass its > tests in the pharo3.0 branch of Filetree at the moment. > > Does this answer your questions? > > Thierry > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 > > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Sept. 13, 2013

Re: [Pharo-users] FileTree Monticello Repository

by Esteban A. Maringolo

Goubier, You do answer my questions. I'm certainly looking for something like gitfiletree then. One last question I have is, does the gitfiletree:// repository type come bundled with the FileTree package? Or do I need to download and install it separately? Regarding adding more git commands inside the MC GUI I'd like to have them separated. Unless I can load previous versions of my MC package and that causes the git to checkout the files from a previous commit. I don't know how the branching is managed or if it's simply ignored. Regards, Esteban A. Maringolo 2013/9/13 Goubier Thierry <thierry.goubier(a)cea.fr> > > > Le 13/09/2013 04:25, Esteban A. Maringolo a Ã©crit : > > Is anybody using FileTree repositories? >> > > Which repositories? Dale's github? > > > If so, I'd like to know the pros and cons of using it. >> > > More complex to use than Smalltalkhub/Squeaksource because it is not yet > integrated in the default image. Some features may not work, but average MC > work under Pharo2.0 works fine with all features of Filetree (including > gitfiletree). > > Easier to use than Smalltalkhub/Squeaksource for authentification. > > > I want to use to version everything with git, but I don't know how it >> keeps git (it is, FileTree files) in sync with MC versions. >> > > A filetree repository appears as a MC repository in the same way as > another type of MC repository. > > Filetree will require that you do all your version management in the git > repo by hand (i.e. save a version of your package in a filetree repo, then > switch to a console to commit it. If you forget to commit and save a new > version of a package on the filetree repo, you overwrite the previous > version and git will not record it. Filetree by itself will only show you > the state of the HEAD of your git repository). > > If you use gitfiletree (it sits over Filetree), then git commit will be > done for you when saving your package, and the repository browser will show > you all the history of the repository, exactly as if it was a Smalltalkhub > or Squeaksource repository. What will remain to do on the command line are > the git push and whatever management you do on the repository (merging, > branching, even if you can also merge via MC instead). In short, > gitfiletree calls git for you and parse the results :) > > I'm still wondering about adding more git commands inside the MC GUI to do > more from inside Pharo (like automagically pushing), but I don't want to > enforce a specific way of organising the git repository... and I'm just > trying to get gitfiletree to pass its tests in the pharo3.0 branch of > Filetree at the moment. > > Does this answer your questions? > > Thierry > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 > >

Sept. 13, 2013

Re: [Pharo-users] Labeling

by Damien Cassou

On Wed, Sep 11, 2013 at 9:04 PM, Natalia Tymchuk <natalia.moskovchuk(a)unikernel.net> wrote: > I want to draw a bar diagram for my benchmarks in Graph-ET. Does anybody > know how to add the labels to x-axis? you may want to ask on the moose mailing list or on stackoverflow (tag #pharo) -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Sept. 13, 2013

Re: [Pharo-users] FileTree Monticello Repository

by Goubier Thierry

Le 13/09/2013 04:25, Esteban A. Maringolo a Ã©crit : > Is anybody using FileTree repositories? Which repositories? Dale's github? > If so, I'd like to know the pros and cons of using it. More complex to use than Smalltalkhub/Squeaksource because it is not yet integrated in the default image. Some features may not work, but average MC work under Pharo2.0 works fine with all features of Filetree (including gitfiletree). Easier to use than Smalltalkhub/Squeaksource for authentification. > I want to use to version everything with git, but I don't know how it > keeps git (it is, FileTree files) in sync with MC versions. A filetree repository appears as a MC repository in the same way as another type of MC repository. Filetree will require that you do all your version management in the git repo by hand (i.e. save a version of your package in a filetree repo, then switch to a console to commit it. If you forget to commit and save a new version of a package on the filetree repo, you overwrite the previous version and git will not record it. Filetree by itself will only show you the state of the HEAD of your git repository). If you use gitfiletree (it sits over Filetree), then git commit will be done for you when saving your package, and the repository browser will show you all the history of the repository, exactly as if it was a Smalltalkhub or Squeaksource repository. What will remain to do on the command line are the git push and whatever management you do on the repository (merging, branching, even if you can also merge via MC instead). In short, gitfiletree calls git for you and parse the results :) I'm still wondering about adding more git commands inside the MC GUI to do more from inside Pharo (like automagically pushing), but I don't want to enforce a specific way of organising the git repository... and I'm just trying to get gitfiletree to pass its tests in the pharo3.0 branch of Filetree at the moment. Does this answer your questions? Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Sept. 13, 2013

Re: [Pharo-users] FileTree Monticello Repository

by phil＠highoctane.be

I wish. I think that what is done with the VM (still need to catch up on that "new way") is a great way to go. Are there resources about that? Regards, Phil On Fri, Sep 13, 2013 at 4:25 AM, Esteban A. Maringolo <emaringolo(a)gmail.com>wrote: > Is anybody using FileTree repositories? > > If so, I'd like to know the pros and cons of using it. > > I want to use to version everything with git, but I don't know how it > keeps git (it is, FileTree files) in sync with MC versions. > > Regards! > > Esteban A. Maringolo >

Sept. 13, 2013

Re: [Pharo-users] [Moose-dev] [ann] moose 4.8

by Ben Coman

Sept. 13, 2013

Re: [Pharo-users] [ann] moose 4.8

by Sven Van Caekenberghe

Impressive. On 13 Sep 2013, at 07:04, Tudor Girba <tudor(a)tudorgirba.com> wrote: > We are happy to announce version 4.8 of the Moose Suite: > http://moosetechnology.org/download/4.8 > > Description > -- > > This was supposed to be a minor release, but in the end it turned out to be a major release with significant improvements. > > The key highlights are: > - Based on Pharo 2.0. > - All built-in visualizations use Roassal. > - Roassal received a significant performance boost and new smart graph layouts like TreeMapLayout or ForceBasedLayout. > - Roassal uses Athens for nice looking vectorial graphics. > - New charting engine based on Roassal: Graph-ET. > - Glamour changed to enable dynamic scripts, while still remaining backward compatible. > - Glamour received a RubricTextPresentation for using the new Rubric text morph. > - Glamour, Roassal, EyeSee, Graph-ET editors are more robust when dealing with errors in scripts.- New GTDebugger with dedicated workflows for Announcements, PetitParser and Glamour itself. > - Extended GTInspector for several object types. > - Usable version of GTMetaceller for handling Metacello configurations. > - FAMIX was strengthen to handle functions better in various programming languages. > - New free type fonts and simpler whitespace-loving theme. > - Lower memory footprint for large models. > - Faster MSE import. > > A list of issues addressed in this release can be found at: > http://code.google.com/p/moose-technology/issues/list?can=1&q=status=Fixed%… > > > Installation > -- > > The Moose Suite 4.8 comes for each platform as a separate bundle: > - Mac: https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_8-mac.zip > - Windows: https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_8-win.zip > - Linux: https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_8-linux.zip > > The Moose Suite 4.8 can also be loaded in a Pharo 2.0 image either from the Configuration Browser, or by executing the following script: > > Gofer new > smalltalkhubUser: 'Moose' project: 'Moose'; > package: 'ConfigurationOfMoose'; > load. > ((Smalltalk at: #ConfigurationOfMoose) > project version: '4.8-snapshot') load > > > Enjoy, > The Moose Team > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Sept. 13, 2013

[ann] moose 4.8

by Tudor Girba

We are happy to announce version 4.8 of the Moose Suite: http://moosetechnology.org/download/4.8 Description -- This was supposed to be a minor release, but in the end it turned out to be a major release with significant improvements. The key highlights are: - Based on Pharo 2.0. - All built-in visualizations use Roassal. - Roassal received a significant performance boost and new smart graph layouts like TreeMapLayout or ForceBasedLayout. - Roassal uses Athens for nice looking vectorial graphics. - New charting engine based on Roassal: Graph-ET. - Glamour changed to enable dynamic scripts, while still remaining backward compatible. - Glamour received a RubricTextPresentation for using the new Rubric text morph. - Glamour, Roassal, EyeSee, Graph-ET editors are more robust when dealing with errors in scripts.- New GTDebugger with dedicated workflows for Announcements, PetitParser and Glamour itself. - Extended GTInspector for several object types. - Usable version of GTMetaceller for handling Metacello configurations. - FAMIX was strengthen to handle functions better in various programming languages. - New free type fonts and simpler whitespace-loving theme. - Lower memory footprint for large models. - Faster MSE import. A list of issues addressed in this release can be found at: http://code.google.com/p/moose-technology/issues/list?can=1&q=status=Fixed%… Installation -- The Moose Suite 4.8 comes for each platform as a separate bundle: - Mac: https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_8-mac.zip - Windows: https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_8-win.zip - Linux: https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_8-linux.zip The Moose Suite 4.8 can also be loaded in a Pharo 2.0 image either from the Configuration Browser, or by executing the following script: Gofer new smalltalkhubUser: 'Moose' project: 'Moose'; package: 'ConfigurationOfMoose'; load. ((Smalltalk at: #ConfigurationOfMoose) project version: '4.8-snapshot') load Enjoy, The Moose Team -- www.tudorgirba.com "Every thing has its own flow"

Sept. 13, 2013