January 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Contributing to Pharo

by Thierry Goubier

Le 28/01/2016 20:55, Dale Henrichs a Ã©crit : > > > On 01/28/2016 12:50 AM, Thierry Goubier wrote: >> Hi Dale, >> >> 2016-01-27 15:41 GMT+01:00 Dale Henrichs >> <dale.henrichs(a)gemtalksystems.com >> <mailto:dale.henrichs@gemtalksystems.com>>: >> >> >> >> On 1/27/16 12:03 AM, Thierry Goubier wrote: >> >> Hi Dale, >> >> then a question: how does one query a baselineOf or a configOf >> to retrieve the current project state (i.e. packages) loaded >> in the image? >> >> Thierry >> >> Thierry, >> >> Good question:) >> >> To start with in tODE I have a class >> TDMetacelloProjectRegistrationDefinition which is part of the >> following hierarchy: >> >> Object >> TDDefinition >> TDPackageBasedDefinition >> TDAbstractProjectRegistrationDefinition >> TDGitProjectRegistrationDefinition >> TDMetacelloProjectRegistrationDefinition >> TDMetacelloRegistrationDefinition >> TDMetacelloBaselineRegistrationDefinition >> TDMetacelloConfigurationRegistrationDefinition >> TDMetacelloHybridRegistrationDefinition >> TDMetacelloUnloadedProjectRegistrationDefinition >> >> The method >> TDMetacelloProjectRegistrationDefinition>>workingCopies[1] >> calculates the list of MCWorkingCopy instances for the loaded >> packages associated with a project (including the configurationof >> or baselineof... or both). >> >> The key Metacello methods called include: >> >> MetacelloProjectRegistration>>projectVersion[2] >> MetacelloMCVersion>>packages[3] >> MetacelloPackageSpec>>workingCopy[4] >> MetacelloMCProjectSpec>>projectPackage[5] >> >> This is really the key information for doing all of the other >> operations for a "Project Browser" like "save all dirty packages >> and commit" and "give me diffs for all dirty packages in project"... >> >> >> I was just asking that because I'd like to see that information merged >> as much as possible; separating concepts just strikes me as unneeded >> complexity, at least for baselines. > Not sure what you mean by "separating concepts and unneeded complexity". > I provided a picture of some of the abstractions that I am using in tODE > ... these abstractions are used in a number of commands, but I also > tried to provide you with the basic implementation used in tODE in case > you were interested in the fact that tODE includes the BaselineOf > package in the list of packages for a project... This is me trying to express something and being unable to make it clear :) I'll have something at one point later. Or maybe not. Doesn't really matter; I'll wait until it becomes clearer to me. > The simple answer is MetacelloMCVersion>>packages[3] Thanks. I'll try something. >> Configurations are a bit different, since a configuration can snapshot >> multiple versions. But I'd really like to make it simple and obvious >> how to setup a project. > I'm not sure what you are talking about here. > > In Metacello a BaselineOf has a single version and the > MetacelloMCVersion class manages the version ... Yes, a Configuration > has multiple versions and each of those versions is an instance of > MetacelloMCVersion.... > > Perhaps when you have time, you can provide a bit more information about > what you are trying to do ... I was just looking at it from the angle of having to explain it to one of my students (non-smalltalkers)... The simplest path to creating a project. I guess one must have a tool like Versionner. > I apologize if I provided too much information but when working with > folks in different time zones, I am in the habit of packing as much > information in a message as possible, because it's often a 24 hour > turnaround for responses... (as it is in this case:) Don't worry about that, you already provided a lot, certainly enough for what I was looking for: a way to organize groups of packages in the image out of the Metacello baselines and configurations present, instead of hacking stuff based on catalog keywords and package name prefix. Now, it's time to implement... If I find that time :( Thierry

Jan. 28, 2016

Re: [Pharo-dev] Disable assertions (design by contract)

by Sven Van Caekenberghe

> On 28 Jan 2016, at 20:59, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > > I totally dislike these hacks: it means that the source code does not anymore determine the behavior. > It's OK as long as it's just a hack,.. But it can't be serious. > Copying all the bad features from C is not required to become a mainstream thing ;) > Marcus, I definitely classify these fantastic super powers in evil category ! You are totally right, Nicolas. But, the compiler can be customised per class, if i am right, so then it is no longer global (which would be terrible indeed). > 2016-01-28 17:49 GMT+01:00 Marcus Denker <marcus.denker(a)inria.fr>: > > > On 28 Jan 2016, at 17:32, Torsten Bergmann <astares(a)gmx.de> wrote: > > > > > > > > Havent tried but would that still compile #assert: as used in SUnit? > > > > This very simplistic version would of course delete those, too. > > A real version needs to take this into account. > > Marcus > > >

Jan. 28, 2016

Re: [Pharo-dev] Disable assertions (design by contract)

by Nicolas Cellier

I totally dislike these hacks: it means that the source code does not anymore determine the behavior. It's OK as long as it's just a hack,.. But it can't be serious. Copying all the bad features from C is not required to become a mainstream thing ;) Marcus, I definitely classify these fantastic super powers in evil category ! 2016-01-28 17:49 GMT+01:00 Marcus Denker <marcus.denker(a)inria.fr>: > > > On 28 Jan 2016, at 17:32, Torsten Bergmann <astares(a)gmx.de> wrote: > > > > > > > > Havent tried but would that still compile #assert: as used in SUnit? > > > > This very simplistic version would of course delete those, too. > > A real version needs to take this into account. > > Marcus > > >

Jan. 28, 2016

Re: [Pharo-dev] Contributing to Pharo

by Dale Henrichs

On 01/28/2016 12:50 AM, Thierry Goubier wrote: > Hi Dale, > > 2016-01-27 15:41 GMT+01:00 Dale Henrichs > <dale.henrichs(a)gemtalksystems.com > <mailto:dale.henrichs@gemtalksystems.com>>: > > > > On 1/27/16 12:03 AM, Thierry Goubier wrote: > > Hi Dale, > > then a question: how does one query a baselineOf or a configOf > to retrieve the current project state (i.e. packages) loaded > in the image? > > Thierry > > Thierry, > > Good question:) > > To start with in tODE I have a class > TDMetacelloProjectRegistrationDefinition which is part of the > following hierarchy: > > Object > TDDefinition > TDPackageBasedDefinition > TDAbstractProjectRegistrationDefinition > TDGitProjectRegistrationDefinition > TDMetacelloProjectRegistrationDefinition > TDMetacelloRegistrationDefinition > TDMetacelloBaselineRegistrationDefinition > TDMetacelloConfigurationRegistrationDefinition > TDMetacelloHybridRegistrationDefinition > TDMetacelloUnloadedProjectRegistrationDefinition > > The method > TDMetacelloProjectRegistrationDefinition>>workingCopies[1] > calculates the list of MCWorkingCopy instances for the loaded > packages associated with a project (including the configurationof > or baselineof... or both). > > The key Metacello methods called include: > > MetacelloProjectRegistration>>projectVersion[2] > MetacelloMCVersion>>packages[3] > MetacelloPackageSpec>>workingCopy[4] > MetacelloMCProjectSpec>>projectPackage[5] > > This is really the key information for doing all of the other > operations for a "Project Browser" like "save all dirty packages > and commit" and "give me diffs for all dirty packages in project"... > > > I was just asking that because I'd like to see that information merged > as much as possible; separating concepts just strikes me as unneeded > complexity, at least for baselines. Not sure what you mean by "separating concepts and unneeded complexity". I provided a picture of some of the abstractions that I am using in tODE ... these abstractions are used in a number of commands, but I also tried to provide you with the basic implementation used in tODE in case you were interested in the fact that tODE includes the BaselineOf package in the list of packages for a project... The simple answer is MetacelloMCVersion>>packages[3] > Configurations are a bit different, since a configuration can snapshot > multiple versions. But I'd really like to make it simple and obvious > how to setup a project. I'm not sure what you are talking about here. In Metacello a BaselineOf has a single version and the MetacelloMCVersion class manages the version ... Yes, a Configuration has multiple versions and each of those versions is an instance of MetacelloMCVersion.... Perhaps when you have time, you can provide a bit more information about what you are trying to do ... I apologize if I provided too much information but when working with folks in different time zones, I am in the habit of packing as much information in a message as possible, because it's often a 24 hour turnaround for responses... (as it is in this case:) Dale

Jan. 28, 2016

Re: [Pharo-dev] Nitpick: Launcher Colors

by Cyril Ferlicot D.

Le 28/01/2016 20:20, Sean P. DeNigris a Ã©crit : > I don't get the addition of alternating row colors to Launcher. As I > understand this, it's value is in a table-like situation where one wants to > track across the row in the same record. Since both panes have only one cell > per row, I don't get the purpose, and it looks really funky to me in the > dark theme. > > My 2c. > Sean > When the launcher is in full screen and the label of the image/template is short, it allow to click on the right row where there is nothing. In Windows it happen a lot that the window is in full screen. > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Nitpick-Launcher-Colors-tp4874592.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

Jan. 28, 2016

Re: [Pharo-dev] Nitpick: Launcher Colors

by Damien Cassou

"Sean P. DeNigris" <sean(a)clipperadams.com> writes: > I don't get the addition of alternating row colors to Launcher. As I > understand this, it's value is in a table-like situation where one wants to > track across the row in the same record. Since both panes have only one cell > per row, I don't get the purpose, and it looks really funky to me in the > dark theme. I don't care, if others agree, you can change it :-). -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Jan. 28, 2016

Re: [Pharo-dev] Nitpick: Launcher Colors

by Esteban A. Maringolo

2016-01-28 16:20 GMT-03:00 Sean P. DeNigris <sean(a)clipperadams.com>: > I don't get the addition of alternating row colors to Launcher. As I > understand this, it's value is in a table-like situation where one wants to > track across the row in the same record. Since both panes have only one cell > per row, I don't get the purpose, and it looks really funky to me in the > dark theme. I share the same appreciation. The stripes are unnecessary. Esteban A. Maringolo

Jan. 28, 2016

Nitpick: Launcher Colors

by Sean P. DeNigris

I don't get the addition of alternating row colors to Launcher. As I understand this, it's value is in a table-like situation where one wants to track across the row in the same record. Since both panes have only one cell per row, I don't get the purpose, and it looks really funky to me in the dark theme. My 2c. Sean ----- Cheers, Sean -- View this message in context: http://forum.world.st/Nitpick-Launcher-Colors-tp4874592.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Jan. 28, 2016

Re: [Pharo-dev] Contributing to Pharo

by Dale Henrichs

On 01/28/2016 12:34 AM, Sven Van Caekenberghe wrote: >> On 28 Jan 2016, at 09:23, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: >> >> I read too fast. >> But my comment is still true. >> We also want a new version browser. Monticello browser is too tied to ... Monticello. We would like a better approach for both git and monticello. > It is totally wrong to put Git and Monticello at the same level, they are related but different things. > > Monticello models our code and your changes to it. It also has a way of putting a package into a persistent representation that can be copied around. An MC server is nothing more than storage. > > Filetree is another way of doing that, using a different representation, but it still needs MC for the high level stuff. Git is versioned storage. And there is a conflict there, yes. > > But throwing away the MC code and changes model would leave you with file outs. You do not want to go there, really. Never, ever. > Sven, If you look at my presentation on "Practical Git for Smalltalk"[1] from 2012, I take pains to differentiate between the Monticello package model (definitions and snapshots) and the Monticello repository model (mcz files). Noone is proposing to throw away the Monticello package model (to my knowledge). So in these discussions about supporting git we are talking about a model where Filetree is still being used for Monticello packages on top of a git storage strata ... I have brought up the point about a "Metacello Project Browser" because both git-based and mcz-based projects can benefit from a higher level of management: - commit all dirty packages, then update and commit the ConfigurationOf for mcz-based projects, OR - save all dirty packages and perform a git commit for git-based projects - perform a diff on all dirty packages in a project ... - etc. Dale [1] http://www.stic.st/wp-content/conferences/2012/Wednesday/1415-Practical_Git…

Jan. 28, 2016

Re: [Pharo-dev] Experiences with git, tODE and GsDevKit_home: Part 1 - basic structure considerations

by Dale Henrichs

On 01/27/2016 06:01 PM, Ben Coman wrote: > > > On Thu, Jan 28, 2016 at 9:41 AM, Ben Coman <btc(a)openinworld.com > <mailto:btc@openinworld.com>> wrote: > > > > On Thu, Jan 28, 2016 at 5:03 AM, Dale Henrichs > <dale.henrichs(a)gemtalksystems.com > <mailto:dale.henrichs@gemtalksystems.com>> wrote: > > The git repository is not tightly coupled to the image like > the changes file (you can delete a git repository without > impacting the functionality of an image), but if you are > making changes in the image, then you _are_ coupled to a > particular git commit identified by its SHA. > > Metacello will record the SHA of the git repository at the > time that packages are loaded from a git repository (to enable > this feature in Pharo, some methods need to be implemented in > the MetacelloPlatform for Pharo) and this information is > stored along with the Metacello registration for the project. > > Since the git repository can be independently manipulated from > the shell or an image can be saved that references a SHA that > is no longer "current" .... it is very important that the SHA > be recorded and made visible to users via the tools. > > > By "current", do you mean the currently checked out directory as > seen from the shell command line? > > Slightly off topic... > I wonder if we could avoid needing a currently checked out > directory as seen from the command line and have the Image work > directly with the git repository (within the .git folder - is this > what libgit integration may give us?) thus making the Image the > equivalent of the current checked out directory? Then lets dump > the .changes file by... rather than a method's source reference > being a (fragile) hardcoded index into the .changes file, make > each method an SHA key into the git (or mercurial) repository. > * Git is fundamentally a content-addressable filesystem with a VCS > user interface written on top of it. Youâll learn more about what > this means in a bit. [2] > * Git is a simple key-value data store. You can insert any kind of > content into it, and it will give you back a key that you can use > to retrieve the content again at any time. [3] > * [In Mercurial...] each revision of a file is identified by a > 'NodeID', which is a SHA hash of its contents (combined with the > position of that node in the history). [4] > > > * The baseline data structures for Fossil and Git are the same (modulo > formatting details). Both systems store check-ins as immutable objects > referencing their immediate ancestors and named by their SHA1 hash. [5] > > So to firm up this idea, while we might not want to tie ourselves too > tightly to git, rather than try working with *all* types of source > code management, would it be reasonable to concentrate on an > abstraction layer focused on *content-addressable* source code? That > is, would this provide flexibility for sufficient backend options, but > a better experience with those than a totally generic source code > management. (btw, Could EPICEA be made to work with SHAs?) > Yes I read the paper on "An Abstraction for Version Control Systems"[1] and if I recall correctly SVN is lacking in a few of the features that had to be "simulated" ... so an abstraction layer that did not have to "fake features out" makes a lot of sense ... with that said, it also makes a lot of sense to not exclude SVN, so an abstraction layer that had provision for unsupported features would be useful ... Dale [1] https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0ahUKEw…

Jan. 28, 2016