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

Experiences with git, tODE and GsDevKit_home: Part 1 - basic structure considerations

by Dale Henrichs

This is the first post in what I expect to be a series of posts describing how I work with git and Smalltalk. The content of this post is based on work that I have done over the last 4 years working with FileTree[4], Metacello[3], tODE[1], GsDevKit_home[2], and git. It's important to note that while I will talk exclusively about git in this series of posts, 99% of what I talk about can be directly mapped to other disk-based SCM like svn, mercurial, etc. I will describe the structure used by GsDevKit_home with the intent to provide a reference point for discussion. The structure I am describing is basically my third attempt at disk structure, so it benefits from "mistakes" that I have made in previous attempts. I've been using the current structure on a daily basis for the last 9 months, so what I'm describing is based on real-life structures and code. ---- Currently,the fundamental pharo structure can be described as consisting of: a vm, a sources file, an image file, a changes file, and a package-cache. The vm and sources file are shared resources and can be used with a collection of images. The image and changes files are tied together as the changes files has the source for methods that are in the image. The image and changes files are also tied to specific versions of the sources file and vm... The package-cache can be shared amongst a wide variety of images including images created by different vms ... When you plug git into the mix, you'll have a a local git repository for each project that you have loaded in your image or intend to load into your image. The git repository should be considered as a resource that lies in between the package-cache and a changes file. 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. In the early days of my work with git, I didn't have this feature and it was very difficult to recover work from old images - I also made mistakes by committing an older version of a package over a newer commit ... nasty stuff ... Currently in tODE, i provide two menu items to work with "version skew": `skew diff` and `skew save`. The `skew diff` menu item just show the differences between to two commits (the commit when the code was loaded and the current commit) - if your project isn't dirty and the diff doesn't contain unexpected changeds, then you may simple load the new commit into your image and move forward. The `skew save` menu item, basically does a merge between the code in the image and the current commit - there a number of git operations that go into this process: checkout original SHA; save packages and commit; checkout custom branch from the "current commit", merge new commit into the branch. I plan on adding a `skew clone` menu item that does a git clone into a repository directory that is reserved for use by the stone (image) and then checks out the original SHA... this option would be more useful for folks who "know what they are doing" and allow for different work flows to be followed... Soooo --- managing skew is an important function for the "project browser"... Here's what the tODE "Project Browser" looks like when version skew is detected: project list with version skew Well I think that's enough for now...Here are some topics that I plan to cover in future posts: - what has to be done to get the initial clone and hook it into an image? - sharing git repos between separate "active images" - cloning a github:// repos? - ssh vs https clones - working with remotes Dale [1] https://github.com/dalehenrich/tode [2] https://github.com/GsDevKit/GsDevKit_home [3] https://github.com/dalehenrich/metacello-work [4] https://github.com/dalehenrich/filetree

Jan. 27, 2016

Re: [Pharo-dev] pay attention there is a problem with rubric in latest image...

by stepharo

Wait I could not save no menu nothing. Stef Le 27/1/16 17:41, Esteban Lorenzano a Ã©crit : > if it is that, is a known bugâ¦ just save&quit and reopen (I will find the bug eventually, but is complicated). > > Esteban > >> On 27 Jan 2016, at 17:27, Skip Lentz <skip.lentz(a)inria.fr> wrote: >> >> Hi, >> >> Did it involve Array class>>basicNew: and FreeType? I got it while typing in a Rubric editor. >> I could not reproduce the bug, it was around 2-3 weeks ago and havenât seen it since. >>> On Jan 27, 2016, at 5:23 PM, stepharo <stepharo(a)free.fr> wrote: >>> >>> Hi >>> >>> in Pharo5.0 >>> Latest update: #50550 >>> >>> >>> I got a red square of death due to a wrong initialise in array class... with rubric index in the middle.... >>> could not get more. I had to kill the image. >>> >>> Stef >>> >> > >

Jan. 27, 2016

Re: [Pharo-dev] why do I get error...when I try to find senders?

by stepharo

Yes that one! Tx alex This should be related to Shout or RB. Le 27/1/16 21:15, Aliaksei Syrel a Ã©crit : > > I have the same. To reproduce: > > 1. open playground. > 2. put both hands on keyboard. > 3. type "at:" > 4. press cmd+n or cmd+m > 5. ... > 6. Syntax Error > Inline image 1 > > > Cheers, > Alex > > On Wed, Jan 27, 2016 at 8:59 PM, Tudor Girba <tudor(a)tudorgirba.com > <mailto:tudor@tudorgirba.com>> wrote: > > Hmm, I never saw this one. Anyone else can reproduce this? > > Doru > > > On Jan 27, 2016, at 6:56 PM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > > > Hi > > > > I open playground or nautilus. > > I type > > compile:classified: > > and select the text > > and I press senders and I get a syntax error expected.... > > > > Just typing this mail now I cannot reproduce it. > > There is something wrong with the system. > > > > Stef > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > www.feenk.com <http://www.feenk.com> > > "Speaking louder won't make the point worthier." > > >

Jan. 27, 2016

Re: [Pharo-dev] Contributing to Pharo

by stepharo

So we are in sync then! Le 27/1/16 21:30, Dale Henrichs a Ã©crit : > Totally agree with having an abstraction layer or common set of > functions ... > > As I've said before, I talk about git mainly because of github and > because there needs to be a "first" and I chose git ... > > Other than details, I think that most if not all of the information I > plan to share is "disk-based SCM neutral" and applies equally to each > SCM .... > > Dale > > On 01/27/2016 11:47 AM, stepharo wrote: >> I think that this is important that we do not think only in terms of >> git. >> People will jump on the next cool and better because nicer versioning >> system. >> I think about fossil for example. I'm waiting for that. Because each >> time I pair program with smart git users >> I see how this is "simple". So I would really be against having git >> menu in Pharo. >> We should have an abstraction over the generic commands that a >> decentralized versioning system should >> offer. >> >> Stef >> >> >> Le 27/1/16 18:23, Dale Henrichs a Ã©crit : >>> >>> >>> On 1/27/16 8:30 AM, stepharo wrote: >>>> We have the catalog. So how different it is. >>> AFAIK the catalog only manages loads of projects ... to make it a >>> "Project Browser" you would add menu items for committing/saving >>> projects (i.e., save all dirty packages and for git repos, do a git >>> commit after updating packages); viewing the diffs for all packages >>> in a project; and of course the load functionality .... >>> >>> As I said somewhere else, I don't think that it is a major job to >>> implement a "Project Browser", but it is something that really needs >>> to be done for supporting git-based projects. There is a natural >>> 1-to-1 mapping between a Metacello project and it's git repository >>> and as you can see in the Git menu below, there are a number of >>> additional git-specific functions that need to be supported ... >>> >>> Dale >>>> >>>> And yes we would to change packages in nautilus. >>>> >>>> >>>> Le 27/1/16 15:13, Dale Henrichs a Ã©crit : >>>>> Haha, I certainly understand the lack of time/manpower ... Just in >>>>> case it wasn't clear, when I said "project browser" I wasn't >>>>> talking about replacing the code browser (Nautilus), but >>>>> replacing/augmenting the Monticello Browser - which should turn >>>>> out to be a much simpler undertaking --- "Project Browser" that >>>>> manages the projects within the image - load, save, changes, etc.: >>>>> >>>>> project list screenshot >>>>> >>>>> >>>>> Dale >>>>> >>>>> On 1/26/16 11:29 PM, Christophe Demarey wrote: >>>>>> Hi Dale, >>>>>> >>>>>> Le 27 janv. 2016 Ã 04:11, Dale Henrichs a Ã©crit : >>>>>> >>>>>>> I've been wondering no-one in the Pharo community has started building a "Project Browser" to replace the "Package Browser" .... I've had a "project browser" in tODE for several years now and you work with a manageble list of Metacello projects like the following: >>>>>> Of course, we have that in mind. We would love to have it but lack of time / manpower ... >>>>>> We are not happy with the current browser (Nautilus). We could have something really more powerful. It will come but we have other projects to achieve before ;) >>>>>> If someone comes with a better browser, we would love to set it as default. >>>>>> >>>>>> Cheers, >>>>>> Christophe >>>>> >>>> >>> >> >

Jan. 27, 2016

Re: [Pharo-dev] Contributing to Pharo

by Esteban A. Maringolo

2016-01-27 17:30 GMT-03:00 Dale Henrichs <dale.henrichs(a)gemtalksystems.com>: > > Totally agree with having an abstraction layer or common set of functions ... > > As I've said before, I talk about git mainly because of github and because there needs to be a "first" and I chose git ... > > Other than details, I think that most if not all of the information I plan to share is "disk-based SCM neutral" and applies equally to each SCM .... AFAIU FileTree has that purpose, although I don't know if it is used with something other than Git as a SCM. Esteban A. Maringolo

Jan. 27, 2016

Re: [Pharo-dev] Contributing to Pharo

by Dale Henrichs

Totally agree with having an abstraction layer or common set of functions ... As I've said before, I talk about git mainly because of github and because there needs to be a "first" and I chose git ... Other than details, I think that most if not all of the information I plan to share is "disk-based SCM neutral" and applies equally to each SCM .... Dale On 01/27/2016 11:47 AM, stepharo wrote: > I think that this is important that we do not think only in terms of git. > People will jump on the next cool and better because nicer versioning > system. > I think about fossil for example. I'm waiting for that. Because each > time I pair program with smart git users > I see how this is "simple". So I would really be against having git > menu in Pharo. > We should have an abstraction over the generic commands that a > decentralized versioning system should > offer. > > Stef > > > Le 27/1/16 18:23, Dale Henrichs a Ã©crit : >> >> >> On 1/27/16 8:30 AM, stepharo wrote: >>> We have the catalog. So how different it is. >> AFAIK the catalog only manages loads of projects ... to make it a >> "Project Browser" you would add menu items for committing/saving >> projects (i.e., save all dirty packages and for git repos, do a git >> commit after updating packages); viewing the diffs for all packages >> in a project; and of course the load functionality .... >> >> As I said somewhere else, I don't think that it is a major job to >> implement a "Project Browser", but it is something that really needs >> to be done for supporting git-based projects. There is a natural >> 1-to-1 mapping between a Metacello project and it's git repository >> and as you can see in the Git menu below, there are a number of >> additional git-specific functions that need to be supported ... >> >> Dale >>> >>> And yes we would to change packages in nautilus. >>> >>> >>> Le 27/1/16 15:13, Dale Henrichs a Ã©crit : >>>> Haha, I certainly understand the lack of time/manpower ... Just in >>>> case it wasn't clear, when I said "project browser" I wasn't >>>> talking about replacing the code browser (Nautilus), but >>>> replacing/augmenting the Monticello Browser - which should turn out >>>> to be a much simpler undertaking --- "Project Browser" that >>>> manages the projects within the image - load, save, changes, etc.: >>>> >>>> project list screenshot >>>> >>>> >>>> Dale >>>> >>>> On 1/26/16 11:29 PM, Christophe Demarey wrote: >>>>> Hi Dale, >>>>> >>>>> Le 27 janv. 2016 Ã 04:11, Dale Henrichs a Ã©crit : >>>>> >>>>>> I've been wondering no-one in the Pharo community has started building a "Project Browser" to replace the "Package Browser" .... I've had a "project browser" in tODE for several years now and you work with a manageble list of Metacello projects like the following: >>>>> Of course, we have that in mind. We would love to have it but lack of time / manpower ... >>>>> We are not happy with the current browser (Nautilus). We could have something really more powerful. It will come but we have other projects to achieve before ;) >>>>> If someone comes with a better browser, we would love to set it as default. >>>>> >>>>> Cheers, >>>>> Christophe >>>> >>> >> >

Jan. 27, 2016

Re: [Pharo-dev] [ANN] First release of FFICHeaderExtractor

by Mariano Martinez Peck

On Wed, Jan 27, 2016 at 4:48 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi! > > Can this be useful to make OpenGL bindings? > It will be useful for autogenerating methods (for different platforms) to initialize constants in SharedPools. But this is NOT for autogenerating FFI bindings. > I remember that Igor used some function headers to generate the bindings. > > Probably you are talking about TalkFFI??? That's a different story. That is for automatically making the FFI callout stub methods of a certain C library. > Alexandre > > > > > On Jan 27, 2016, at 6:44 AM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > > > > Dear all, > > > > I am happy to announce the first release of FFICHeaderExtractor project. > You can find the project and the documentation here: > > > > https://github.com/marianopeck/FFICHeaderExtractor > > > > Any feedback is more than welcome. > > > > Best, > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > -- Mariano http://marianopeck.wordpress.com

Jan. 27, 2016

Re: [Pharo-dev] Morphic magician requested. What is referencePosition?

by Aliaksei Syrel

Aha, understood! Thanks a lot :) Cheers, Alex On Wed, Jan 27, 2016 at 5:04 PM, Henrik Nergaard <henrik.nergaard(a)uia.no> wrote: > > > > > *From:* Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] *On Behalf > Of *Henrik Nergaard > *Sent:* Wednesday, January 27, 2016 4:47 PM > *To:* Pharo Development List <pharo-dev(a)lists.pharo.org> > *Subject:* Re: [Pharo-dev] Morphic magician requested. What is > referencePosition? > > > > #referencePostion returns the specified center for the morph in global > coordinates. > > By default this will be the same as âself bounds origin + (self bounds > extent/2.0)â but can have other depending on what #rotationCenter returns. > > > > #referencePositon: on the other hand do not set a new centre, but moves > the morph to a new position by using the referencePosition as origin > instead of its top left corner. > > > > Example: > > > > > > | m | > > > > m := Morph new > > color: Color orange; > > extent: 200@72; > > openCenteredInWorld; > > yourself. > > > > m on: #click send: #value to: [ m referencePosition: (m referencePosition > + (10@10)) ] . > > > > *Looking at Morph>>#handleDropMorph: referencePosition is used to place > the dropped morph in centre of the new owner. * > > > > *â* > > *observation: * > > *â(self transformedFrom: anEvent hand world) globalPointToLocal: aMorph > referencePositionâ looks incomplete as it will always be equal to just > doing âaMorph referencePositionâ because #transformedFrom: always returns > an IdentityTransform where # globalPointToLocal: just returns the point > given to it.* > > *â* > > > > Correction*:* > > > > #transformedFrom: translates the dropped morph âcenterâ to the receiving > morph local coordinates (local from the owning transformationMorph) if it > has an owner which is a transformation type Morph (see implementors > #tranformFrom:) . > > > > > > > > Best regards, > > Henrik > > > > *From:* Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org > <pharo-dev-bounces(a)lists.pharo.org>] *On Behalf Of *Aliaksei Syrel > *Sent:* Wednesday, January 27, 2016 4:12 PM > *To:* Pharo Development List <pharo-dev(a)lists.pharo.org> > *Subject:* [Pharo-dev] Morphic magician requested. What is > referencePosition? > > > > Hi > > > > Do anyone know what is Morph>>#referencePosition and why is it used to > handle drag and drop? > > > > Here is what method doc says: > > "Return the current reference position of the receiver" > > > > Thanks, > > Alex >

Jan. 27, 2016

Re: [Pharo-dev] why do I get error...when I try to find senders?

by Aliaksei Syrel

I have the same. To reproduce: 1. open playground. 2. put both hands on keyboard. 3. type "at:" 4. press cmd+n or cmd+m 5. ... 6. Syntax Error [image: Inline image 1] Cheers, Alex On Wed, Jan 27, 2016 at 8:59 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hmm, I never saw this one. Anyone else can reproduce this? > > Doru > > > On Jan 27, 2016, at 6:56 PM, stepharo <stepharo(a)free.fr> wrote: > > > > Hi > > > > I open playground or nautilus. > > I type > > compile:classified: > > and select the text > > and I press senders and I get a syntax error expected.... > > > > Just typing this mail now I cannot reproduce it. > > There is something wrong with the system. > > > > Stef > > > > -- > www.tudorgirba.com > www.feenk.com > > "Speaking louder won't make the point worthier." > > >

Jan. 27, 2016

Re: [Pharo-dev] why do I get error...when I try to find senders?

by Tudor Girba

Hmm, I never saw this one. Anyone else can reproduce this? Doru > On Jan 27, 2016, at 6:56 PM, stepharo <stepharo(a)free.fr> wrote: > > Hi > > I open playground or nautilus. > I type > compile:classified: > and select the text > and I press senders and I get a syntax error expected.... > > Just typing this mail now I cannot reproduce it. > There is something wrong with the system. > > Stef > -- www.tudorgirba.com www.feenk.com "Speaking louder won't make the point worthier."

Jan. 27, 2016