Hi! Iâve heard some of you are working on an update of pharo by example. Is there anything ready for now? Some chapter maybe? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
You may have a look here: https://ci.inria.fr/pharo-contribution/view/Books/job/UpdatedPharoByExample/... and contribute here: https://github.com/SquareBracketAssociates/UpdatedPharoByExample On Tue, Mar 10, 2015 at 8:13 PM, Alexandre Bergel <alexandre.bergel@me.com> wrote:
Hi!
Iâve heard some of you are working on an update of pharo by example. Is there anything ready for now? Some chapter maybe?
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/
What's the workflow, to contribute to Updated Pharo By Example? Should people just make PRs against that repo? Looking over some of the other SquareBracketAssociates repos, there seems to be a repository-based workflow? - https://github.com/SquareBracketAssociates/PharoInProgress for work in progress chapters - https://github.com/SquareBracketAssociates/PharoReadyForReviews for chapters ready for reviews? Does that mean that one makes PRs to the main UPBE repo after they get reviews? Or is this a previous / obsolete workflow? On Tue, Mar 10, 2015 at 3:19 PM, Serge Stinckwich < serge.stinckwich@gmail.com> wrote:
You may have a look here:
https://ci.inria.fr/pharo-contribution/view/Books/job/UpdatedPharoByExample/...
and contribute here: https://github.com/SquareBracketAssociates/UpdatedPharoByExample
On Tue, Mar 10, 2015 at 8:13 PM, Alexandre Bergel <alexandre.bergel@me.com> wrote:
Hi!
Iâve heard some of you are working on an update of pharo by example. Is there anything ready for now? Some chapter maybe?
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/
the main repo is here https://github.com/SquareBracketAssociates/UpdatedPharoByExample There is a link for how to contribute in the README. I was added as a contributor, all the above projects are inside an organisation so once you added as a contributor to this orgainsation you can contribute directly to all books . Pull requests make more sense when you create forks and make your own versions that go to a diffirent direction than the original repo. When all you want is to contribute then becoming a contributor makes more sense because its more straightforward for you and the original authors. On Sat, Mar 21, 2015 at 2:59 AM, Dmitri Zagidulin <dmitri@zagidulin.net> wrote:
What's the workflow, to contribute to Updated Pharo By Example?
Should people just make PRs against that repo?
Looking over some of the other SquareBracketAssociates repos, there seems to be a repository-based workflow? - https://github.com/SquareBracketAssociates/PharoInProgress for work in progress chapters - https://github.com/SquareBracketAssociates/PharoReadyForReviews for chapters ready for reviews? Does that mean that one makes PRs to the main UPBE repo after they get reviews? Or is this a previous / obsolete workflow?
On Tue, Mar 10, 2015 at 3:19 PM, Serge Stinckwich < serge.stinckwich@gmail.com> wrote:
You may have a look here:
https://ci.inria.fr/pharo-contribution/view/Books/job/UpdatedPharoByExample/...
and contribute here: https://github.com/SquareBracketAssociates/UpdatedPharoByExample
On Tue, Mar 10, 2015 at 8:13 PM, Alexandre Bergel <alexandre.bergel@me.com> wrote:
Hi!
Iâve heard some of you are working on an update of pharo by example. Is there anything ready for now? Some chapter maybe?
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/
On Sat, Mar 21, 2015 at 4:00 AM, kilon alios <kilon.alios@gmail.com> wrote:
Pull requests make more sense when you create forks and make your own versions that go to a diffirent direction than the original repo. When all you want is to contribute then becoming a contributor makes more sense because its more straightforward for you and the original authors.
You may be slightly misinterpreting the purpose of pull requests. They are not primarily for making your own versions that go in a different direction (although they can help with that). They're a social / workflow mechanism, for reviewing and accepting contributions. PRs are a way to publicly say "I would like to contribute the following change to your repo". And then the actual repo owners/contributors have a chance to comment on the change (with nice tools like you can comment on individual lines of code), and ask for corrections. (And then the author of the PR can make corrections, and they'll show up automatically in the pull request.) Then, finally, if they approve of the contribution, the pull request is merged. If you're a contributor with write access to the original repo, there isn't a straightforward mechanism to do all of those steps. You can make commits, but there isn't the same workflow of discussing and accepting.
Le 21/03/2015 17:56, Dmitri Zagidulin a écrit :
On Sat, Mar 21, 2015 at 4:00 AM, kilon alios <kilon.alios@gmail.com <mailto:kilon.alios@gmail.com>> wrote:
Pull requests make more sense when you create forks and make your own versions that go to a diffirent direction than the original repo. When all you want is to contribute then becoming a contributor makes more sense because its more straightforward for you and the original authors.
You may be slightly misinterpreting the purpose of pull requests.
They are not primarily for making your own versions that go in a different direction (although they can help with that).
They're a social / workflow mechanism, for reviewing and accepting contributions. PRs are a way to publicly say "I would like to contribute the following change to your repo". And then the actual repo owners/contributors have a chance to comment on the change (with nice tools like you can comment on individual lines of code), and ask for corrections. (And then the author of the PR can make corrections, and they'll show up automatically in the pull request.) Then, finally, if they approve of the contribution, the pull request is merged.
If you're a contributor with write access to the original repo, there isn't a straightforward mechanism to do all of those steps. You can make commits, but there isn't the same workflow of discussing and accepting.
As a contributor to a repo, you can create a branch and a pull request towards another branch in that very same repo, so you have access to the same social mechanism if you want to use it. But, as you suggest, as a contributor you can shortcut it and commit directly. Regards, Thierry
"And then the actual repo owners/contributors have a chance to comment on the change (with nice tools like you can comment on individual lines of code), and ask for corrections. (And then the author of the PR can make corrections, and they'll show up automatically in the pull request.) Then, finally, if they approve of the contribution, the pull request is merged." There is a workflow of discussion for contributors , commits can have comments and those comments can form discussions. You can also open issues and have a discussion there pointing to specific commits. Github issues are not just there for bugs and now with its powerful tagging system you can use it for all sort of discussion without polluting other kinds of issues like bugs. Wiki can also be used for roadmap , again linking to specific commits its easy etc. Thats what I love about Github its so flexible. The main difference of pull requests is a way for forks to exchange code. I am not saying you cant have a fork that closely follows the main repo and just send pull requests but as I said in that case it would make more sense to be a contributor directly. The whole process of accepting is not a such a huge deal since you can always revert or even edit specific commits. "As a contributor to a repo, you can create a branch and a pull request towards another branch in that very same repo, so you have access to the same social mechanism if you want to use it." yeah I kinda suspected that could be possible but why not just merge and get it done ? Again the social mechanism of pull request is not any more social that regular contributor commits.
Kilon, I'm not sure I understand - Why such resistance to pull requests? :) On Sat, Mar 21, 2015 at 2:08 PM, kilon alios <kilon.alios@gmail.com> wrote:
"And then the actual repo owners/contributors have a chance to comment on the change (with nice tools like you can comment on individual lines of code), and ask for corrections. (And then the author of the PR can make corrections, and they'll show up automatically in the pull request.) Then, finally, if they approve of the contribution, the pull request is merged."
There is a workflow of discussion for contributors , commits can have comments and those comments can form discussions. You can also open issues and have a discussion there pointing to specific commits. Github issues are not just there for bugs and now with its powerful tagging system you can use it for all sort of discussion without polluting other kinds of issues like bugs. Wiki can also be used for roadmap , again linking to specific commits its easy etc. Thats what I love about Github its so flexible.
The main difference of pull requests is a way for forks to exchange code. I am not saying you cant have a fork that closely follows the main repo and just send pull requests but as I said in that case it would make more sense to be a contributor directly. The whole process of accepting is not a such a huge deal since you can always revert or even edit specific commits.
"As a contributor to a repo, you can create a branch and a pull request towards another branch in that very same repo, so you have access to the same social mechanism if you want to use it."
yeah I kinda suspected that could be possible but why not just merge and get it done ? Again the social mechanism of pull request is not any more social that regular contributor commits.
commits can have comments and those comments can form discussions
With git you are rarely interested in particular commits; usually when someone is proposing a feature/bugfix it composes of many commits. As a reviewer I'm not interested in every "fixed typo" commit etc, but in the whole thing, since one commit can remove a behavior and another add it, I'm interested only in the result. PRs have many other benefits * I am reviewing the code against current master * I see if there are any merge conflicts (since master could have advanced in the meantime) * If the submitter updates the feature I still have everything nicely bundled * I can have overall discussion about the proposed solution - this doesn't belong neither to commits, nor to issues since this is particular to the solution Of course it depends on your style, but for example for code reviews it is invaluable; even if both (submitter and reviewer) are contributors PR is still useful. But I am interested why you don't like pull requests; after all they are just annotated merges. Peter
I had pull request phobias, I saw a doctor and I am fine now with some medication. The important thing is that you guys contribute , how you do it , its up to you. For me not having to deal with pull requests is one less thing to worry about. If I had to use them , I would . I used them once to improve the dark theme in Amber, had no issues with it. The bottom line is that more people are needed to contribute to documentation. That's the important thing, the rest is just details. On Sat, Mar 21, 2015 at 8:50 PM, Peter Uhnák <i.uhnak@gmail.com> wrote:
Also, thread hijacking. :)
thanks dmitri. Indeed I would love to have people helping more. Damien and me are flooded by work right now. If you start here are some suggestions: - start by the end chapters (there are easier because less dependent) - I started to remove interaction details that will make the book obsolete fast. - I use Pharo and not Smalltalk most of the time. - I control reference on squeak because this is a pharo book - I'm redoing the diagram. - I was stuck in the Object Model (because the code changed and I should design an example that will be stable over time and not based on the system). Now the object model is not only presenting it but it is also teaching fundamental aspects of oop (that unfortunately many people got wrong. What would be good - you can start reading what we did already - ideally I would like to extend pillar so that we can execute the code snippets automatically and check that they are correct oscar had this excellent idea for PBE. if you start let us know :) We are working on a Mooc about Pharo so we want to have Pharo by Example fully updated. Stef Le 21/3/15 01:59, Dmitri Zagidulin a écrit :
What's the workflow, to contribute to Updated Pharo By Example?
Should people just make PRs against that repo?
Looking over some of the other SquareBracketAssociates repos, there seems to be a repository-based workflow? - https://github.com/SquareBracketAssociates/PharoInProgress for work in progress chapters - https://github.com/SquareBracketAssociates/PharoReadyForReviews for chapters ready for reviews? Does that mean that one makes PRs to the main UPBE repo after they get reviews? Or is this a previous / obsolete workflow?
On Tue, Mar 10, 2015 at 3:19 PM, Serge Stinckwich <serge.stinckwich@gmail.com <mailto:serge.stinckwich@gmail.com>> wrote:
You may have a look here:
https://ci.inria.fr/pharo-contribution/view/Books/job/UpdatedPharoByExample/...
and contribute here: https://github.com/SquareBracketAssociates/UpdatedPharoByExample
On Tue, Mar 10, 2015 at 8:13 PM, Alexandre Bergel <alexandre.bergel@me.com <mailto:alexandre.bergel@me.com>> wrote: > Hi! > > Iâve heard some of you are working on an update of pharo by example. Is > there anything ready for now? Some chapter maybe? > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > >
-- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/
Thanks, Stef, Kilon. I would like to contribute, actually. (I made a PR to the original PBE repo and the Updated PBE, linking the Readmes to each other etc). My GitHub username is 'dmitrizagidulin', if you'd like to add me to contributors. (I'm happy to merge pull requests etc, if you guys are busy and dont want to deal with it). Dmitri On Saturday, March 21, 2015, stepharo <stepharo@free.fr> wrote:
thanks dmitri. Indeed I would love to have people helping more. Damien and me are flooded by work right now. If you start here are some suggestions: - start by the end chapters (there are easier because less dependent) - I started to remove interaction details that will make the book obsolete fast. - I use Pharo and not Smalltalk most of the time. - I control reference on squeak because this is a pharo book - I'm redoing the diagram. - I was stuck in the Object Model (because the code changed and I should design an example that will be stable over time and not based on the system). Now the object model is not only presenting it but it is also teaching fundamental aspects of oop (that unfortunately many people got wrong.
What would be good - you can start reading what we did already - ideally I would like to extend pillar so that we can execute the code snippets automatically and check that they are correct oscar had this excellent idea for PBE.
if you start let us know :)
We are working on a Mooc about Pharo so we want to have Pharo by Example fully updated.
Stef
Le 21/3/15 01:59, Dmitri Zagidulin a écrit :
What's the workflow, to contribute to Updated Pharo By Example?
Should people just make PRs against that repo?
Looking over some of the other SquareBracketAssociates repos, there seems to be a repository-based workflow? - https://github.com/SquareBracketAssociates/PharoInProgress for work in progress chapters - https://github.com/SquareBracketAssociates/PharoReadyForReviews for chapters ready for reviews? Does that mean that one makes PRs to the main UPBE repo after they get reviews? Or is this a previous / obsolete workflow?
On Tue, Mar 10, 2015 at 3:19 PM, Serge Stinckwich < serge.stinckwich@gmail.com <javascript:_e(%7B%7D,'cvml','serge.stinckwich@gmail.com');>> wrote:
You may have a look here:
https://ci.inria.fr/pharo-contribution/view/Books/job/UpdatedPharoByExample/...
and contribute here: https://github.com/SquareBracketAssociates/UpdatedPharoByExample
On Tue, Mar 10, 2015 at 8:13 PM, Alexandre Bergel <alexandre.bergel@me.com <javascript:_e(%7B%7D,'cvml','alexandre.bergel@me.com');>> wrote:
Hi!
Iâve heard some of you are working on an update of pharo by example. Is there anything ready for now? Some chapter maybe?
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/
Great welcome on board Dmitri , by the way my real name is Dimitri too :) On Sat, Mar 21, 2015 at 10:02 PM, Dmitri Zagidulin <dmitri@zagidulin.net> wrote:
Thanks, Stef, Kilon.
I would like to contribute, actually. (I made a PR to the original PBE repo and the Updated PBE, linking the Readmes to each other etc). My GitHub username is 'dmitrizagidulin', if you'd like to add me to contributors.
(I'm happy to merge pull requests etc, if you guys are busy and dont want to deal with it).
Dmitri
On Saturday, March 21, 2015, stepharo <stepharo@free.fr> wrote:
thanks dmitri. Indeed I would love to have people helping more. Damien and me are flooded by work right now. If you start here are some suggestions: - start by the end chapters (there are easier because less dependent) - I started to remove interaction details that will make the book obsolete fast. - I use Pharo and not Smalltalk most of the time. - I control reference on squeak because this is a pharo book - I'm redoing the diagram. - I was stuck in the Object Model (because the code changed and I should design an example that will be stable over time and not based on the system). Now the object model is not only presenting it but it is also teaching fundamental aspects of oop (that unfortunately many people got wrong.
What would be good - you can start reading what we did already - ideally I would like to extend pillar so that we can execute the code snippets automatically and check that they are correct oscar had this excellent idea for PBE.
if you start let us know :)
We are working on a Mooc about Pharo so we want to have Pharo by Example fully updated.
Stef
Le 21/3/15 01:59, Dmitri Zagidulin a écrit :
What's the workflow, to contribute to Updated Pharo By Example?
Should people just make PRs against that repo?
Looking over some of the other SquareBracketAssociates repos, there seems to be a repository-based workflow? - https://github.com/SquareBracketAssociates/PharoInProgress for work in progress chapters - https://github.com/SquareBracketAssociates/PharoReadyForReviews for chapters ready for reviews? Does that mean that one makes PRs to the main UPBE repo after they get reviews? Or is this a previous / obsolete workflow?
On Tue, Mar 10, 2015 at 3:19 PM, Serge Stinckwich < serge.stinckwich@gmail.com> wrote:
You may have a look here:
https://ci.inria.fr/pharo-contribution/view/Books/job/UpdatedPharoByExample/...
and contribute here: https://github.com/SquareBracketAssociates/UpdatedPharoByExample
On Tue, Mar 10, 2015 at 8:13 PM, Alexandre Bergel <alexandre.bergel@me.com> wrote:
Hi!
Iâve heard some of you are working on an update of pharo by example. Is there anything ready for now? Some chapter maybe?
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/
Ha, that's awesome! :) Thanks On Saturday, March 21, 2015, kilon alios <kilon.alios@gmail.com> wrote:
Great welcome on board Dmitri , by the way my real name is Dimitri too :)
On Sat, Mar 21, 2015 at 10:02 PM, Dmitri Zagidulin <dmitri@zagidulin.net <javascript:_e(%7B%7D,'cvml','dmitri@zagidulin.net');>> wrote:
Thanks, Stef, Kilon.
I would like to contribute, actually. (I made a PR to the original PBE repo and the Updated PBE, linking the Readmes to each other etc). My GitHub username is 'dmitrizagidulin', if you'd like to add me to contributors.
(I'm happy to merge pull requests etc, if you guys are busy and dont want to deal with it).
Dmitri
On Saturday, March 21, 2015, stepharo <stepharo@free.fr <javascript:_e(%7B%7D,'cvml','stepharo@free.fr');>> wrote:
thanks dmitri. Indeed I would love to have people helping more. Damien and me are flooded by work right now. If you start here are some suggestions: - start by the end chapters (there are easier because less dependent) - I started to remove interaction details that will make the book obsolete fast. - I use Pharo and not Smalltalk most of the time. - I control reference on squeak because this is a pharo book - I'm redoing the diagram. - I was stuck in the Object Model (because the code changed and I should design an example that will be stable over time and not based on the system). Now the object model is not only presenting it but it is also teaching fundamental aspects of oop (that unfortunately many people got wrong.
What would be good - you can start reading what we did already - ideally I would like to extend pillar so that we can execute the code snippets automatically and check that they are correct oscar had this excellent idea for PBE.
if you start let us know :)
We are working on a Mooc about Pharo so we want to have Pharo by Example fully updated.
Stef
Le 21/3/15 01:59, Dmitri Zagidulin a écrit :
What's the workflow, to contribute to Updated Pharo By Example?
Should people just make PRs against that repo?
Looking over some of the other SquareBracketAssociates repos, there seems to be a repository-based workflow? - https://github.com/SquareBracketAssociates/PharoInProgress for work in progress chapters - https://github.com/SquareBracketAssociates/PharoReadyForReviews for chapters ready for reviews? Does that mean that one makes PRs to the main UPBE repo after they get reviews? Or is this a previous / obsolete workflow?
On Tue, Mar 10, 2015 at 3:19 PM, Serge Stinckwich < serge.stinckwich@gmail.com> wrote:
You may have a look here:
https://ci.inria.fr/pharo-contribution/view/Books/job/UpdatedPharoByExample/...
and contribute here: https://github.com/SquareBracketAssociates/UpdatedPharoByExample
On Tue, Mar 10, 2015 at 8:13 PM, Alexandre Bergel <alexandre.bergel@me.com> wrote:
Hi!
Iâve heard some of you are working on an update of pharo by example. Is there anything ready for now? Some chapter maybe?
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/
just sent you an invitation , should give you access to whole organization including all books. On Sat, Mar 21, 2015 at 10:02 PM, Dmitri Zagidulin <dmitri@zagidulin.net> wrote:
Thanks, Stef, Kilon.
I would like to contribute, actually. (I made a PR to the original PBE repo and the Updated PBE, linking the Readmes to each other etc). My GitHub username is 'dmitrizagidulin', if you'd like to add me to contributors.
(I'm happy to merge pull requests etc, if you guys are busy and dont want to deal with it).
Dmitri
On Saturday, March 21, 2015, stepharo <stepharo@free.fr> wrote:
thanks dmitri. Indeed I would love to have people helping more. Damien and me are flooded by work right now. If you start here are some suggestions: - start by the end chapters (there are easier because less dependent) - I started to remove interaction details that will make the book obsolete fast. - I use Pharo and not Smalltalk most of the time. - I control reference on squeak because this is a pharo book - I'm redoing the diagram. - I was stuck in the Object Model (because the code changed and I should design an example that will be stable over time and not based on the system). Now the object model is not only presenting it but it is also teaching fundamental aspects of oop (that unfortunately many people got wrong.
What would be good - you can start reading what we did already - ideally I would like to extend pillar so that we can execute the code snippets automatically and check that they are correct oscar had this excellent idea for PBE.
if you start let us know :)
We are working on a Mooc about Pharo so we want to have Pharo by Example fully updated.
Stef
Le 21/3/15 01:59, Dmitri Zagidulin a écrit :
What's the workflow, to contribute to Updated Pharo By Example?
Should people just make PRs against that repo?
Looking over some of the other SquareBracketAssociates repos, there seems to be a repository-based workflow? - https://github.com/SquareBracketAssociates/PharoInProgress for work in progress chapters - https://github.com/SquareBracketAssociates/PharoReadyForReviews for chapters ready for reviews? Does that mean that one makes PRs to the main UPBE repo after they get reviews? Or is this a previous / obsolete workflow?
On Tue, Mar 10, 2015 at 3:19 PM, Serge Stinckwich < serge.stinckwich@gmail.com> wrote:
You may have a look here:
https://ci.inria.fr/pharo-contribution/view/Books/job/UpdatedPharoByExample/...
and contribute here: https://github.com/SquareBracketAssociates/UpdatedPharoByExample
On Tue, Mar 10, 2015 at 8:13 PM, Alexandre Bergel <alexandre.bergel@me.com> wrote:
Hi!
Iâve heard some of you are working on an update of pharo by example. Is there anything ready for now? Some chapter maybe?
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/
I feel alone with damien... :) We are making progress but slowly Stef Le 10/3/15 20:13, Alexandre Bergel a écrit :
Hi!
Iâve heard some of you are working on an update of pharo by example. Is there anything ready for now? Some chapter maybe?
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
I definitely know how that feels ;) On Thu, Mar 12, 2015 at 4:51 PM, stepharo <stepharo@free.fr> wrote:
I feel alone with damien... :) We are making progress but slowly
Stef
Le 10/3/15 20:13, Alexandre Bergel a écrit :
Hi!
Iâve heard some of you are working on an update of pharo by example. Is there anything ready for now? Some chapter maybe?
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
participants (7)
-
Alexandre Bergel -
Dmitri Zagidulin -
kilon alios -
Peter Uhnák -
Serge Stinckwich -
stepharo -
Thierry Goubier