- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Pharo-users] Start with a trivial improvement!

by StÃ©phane Ducasse

good idea yes for the blog entry On Oct 10, 2013, at 1:42 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Thank you, Marcus! > > Could you post this on the Pharo blog? > > Doru > > > On Thu, Oct 10, 2013 at 1:36 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > +100 > > On 10 Oct 2013, at 13:21, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > One nice way to get in the mood of doing (and at the same time testing the system) is to start > > with trivial improvements. > > > > This is especially nice as a "starter" when you never contributed any change to Pharo. > > > > And by trivial I mean *really* mean trivial: > > -> a typo in a comment > > -> remove a temp not accessed > > -> clean out some trivial dead code > > -> do a simplistic refactoring of a bad smell, even inside a single method > > -> document something > > -> structure bad stuff better so it is easier to replace later > > > > Taken in itself, single changes like these have no influence, but: > > > > -> they get you in a mood of doing. > > -> they make you feel that Pharo is "owned" by you. > > -> take 1000 of those trivialities and they *do* make a difference. > > -> next time something bothers you, you will have the context of "I can just fix it". > > > > The critic tools is one way of finding these places, another is to just note down every time > > you see a triviality and later go through that list. The bug tracker can be source, too. > > > > > > <wtfm.jpg> > > > > Marcus > > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Oct. 10, 2013

Re: [Pharo-dev] ShortRunArray not in Pharo 3.0 anymore, leading to problems with FFI-Kernel-tbn.25

by Sean P. DeNigris

philippeback wrote > It is too complex for me to get things loaded in 3.0 and be delivering > what > we need to, so I am back to 2.0 now. I think that's the right decision even if you could get it loaded. I wouldn't deploy on a beta version of Pharo (no matter how tempting all the cool new features are!!)... ----- Cheers, Sean -- View this message in context: http://forum.world.st/ShortRunArray-not-in-Pharo-3-0-anymore-leading-to-pro… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 10, 2013

[OT] Git Internals PDF

by Torsten Bergmann

"A PDF by Scott Chacon about how the Git source code control system stores files and revisions." https://github.com/pluralsight/git-internals-pdf/releases Maybe thats interesting for the people working on Pharo & Git

Oct. 10, 2013

Re: [Pharo-dev] Please contributors fill up this form...

by James Foster

PharoContributor new name: 'James Foster'; id: 'JamesFoster'; email: 'smalltalk(a)jgfoster.net'; website: 'https://programminggems.wordpress.com/'; description: 'GemStone/S engineer and evangelist'; image: 'http://www.gravatar.com/avatar/631f05ac3a6ed798c66034d408aceeaf.png'; yourself.

Oct. 10, 2013

Re: [Pharo-dev] Please contributors fill up this form...

by btc＠openinworld.com

StÃ©phane Ducasse wrote: > Hi guys > > I would like to get > contributors.pharo.org a bit more representative of Pharo. > > We should have Previous contributors and enhance the current list. > Can you please reply to this mail > > PharoContributor new > name: 'Ben Coman'; > id: 'bencoman'; > email: 'btc(a)openInWorld.com'; > website: 'http://blog.openInWorld.com'; > description: 'Electrical Power Engineer. Utilised Roassal/Glamour/Magritte with Pharo/Moose for my Masters thesis to develop "LEKtrek - a software development platform for electrical power applications" (release pending)'; > yourself > > > Stef > >

Oct. 10, 2013

Re: [Pharo-dev] [PROVENANCE INTERNET] Re: Please contributors fill up this form...

by Olivier Auverlot

PharoContributor new name: 'Olivier Auverlot'; id: 'olivierauverlot'; email: 'olivier.auverlot(a)gmail.com'; description: 'Artefact,PROXimity'; yourself

Oct. 10, 2013

Re: [Pharo-dev] Start with a trivial improvement!

by kilon

This is something I was contemplating lately for my project Ephestos. The problem I see with your approach is that it takes a long time to see those changes integrated into Pharo cause AFAIK there are not many people to check out those "fixes" approve them and then integrate them. Now multiple that by 1000. Yeah right ! So I decided to follow the external library route. My initial concern about my project was that I want a better Morphic. Now the sensible start would be to do what you suggested, start small , fix morphic problems here and there, tiny clean ups to the code etc. But I realised that if someone pings me back months later about a fix he does not like and I am way forward in the development process that could seriously mess with my code and even make it hard to change the fix. So it was a great news indeed that morphic is entirely (or almost entirely ?) written in smalltalk. I am back at studying opengl since I want to make an opengl implementation of moprhic , but also I would also like to get rid of things I dont like about morphic. Making it into an external lib also makes sure I dont brake people's code but also I am tied into things I dont like and need the approval of the community to fix. So yes I agree that what you say sounds ideal in theory, but its not ideal in practice. -- View this message in context: http://forum.world.st/Start-with-a-trivial-improvement-tp4713648p4713655.ht… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 10, 2013

Re: [Pharo-dev] [Pharo-users] Start with a trivial improvement!

by Marcus Denker

On Oct 10, 2013, at 1:43 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Thank you, Marcus! > > Could you post this on the Pharo blog? > Good idea, yes, I will do that. Marcus

Oct. 10, 2013

Re: [Pharo-dev] [Pharo-users] Start with a trivial improvement!

by Tudor Girba

Thank you, Marcus! Could you post this on the Pharo blog? Doru On Thu, Oct 10, 2013 at 1:36 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > +100 > > On 10 Oct 2013, at 13:21, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > One nice way to get in the mood of doing (and at the same time testing > the system) is to start > > with trivial improvements. > > > > This is especially nice as a "starter" when you never contributed any > change to Pharo. > > > > And by trivial I mean *really* mean trivial: > > -> a typo in a comment > > -> remove a temp not accessed > > -> clean out some trivial dead code > > -> do a simplistic refactoring of a bad smell, even inside a > single method > > -> document something > > -> structure bad stuff better so it is easier to replace later > > > > Taken in itself, single changes like these have no influence, but: > > > > -> they get you in a mood of doing. > > -> they make you feel that Pharo is "owned" by you. > > -> take 1000 of those trivialities and they *do* make a difference. > > -> next time something bothers you, you will have the context of > "I can just fix it". > > > > The critic tools is one way of finding these places, another is to just > note down every time > > you see a triviality and later go through that list. The bug tracker can > be source, too. > > > > > > <wtfm.jpg> > > > > Marcus > > > -- www.tudorgirba.com "Every thing has its own flow"

Oct. 10, 2013

Re: [Pharo-dev] [Pharo-users] Start with a trivial improvement!

by Sven Van Caekenberghe

+100 On 10 Oct 2013, at 13:21, Marcus Denker <marcus.denker(a)inria.fr> wrote: > One nice way to get in the mood of doing (and at the same time testing the system) is to start > with trivial improvements. > > This is especially nice as a "starter" when you never contributed any change to Pharo. > > And by trivial I mean *really* mean trivial: > -> a typo in a comment > -> remove a temp not accessed > -> clean out some trivial dead code > -> do a simplistic refactoring of a bad smell, even inside a single method > -> document something > -> structure bad stuff better so it is easier to replace later > > Taken in itself, single changes like these have no influence, but: > > -> they get you in a mood of doing. > -> they make you feel that Pharo is "owned" by you. > -> take 1000 of those trivialities and they *do* make a difference. > -> next time something bothers you, you will have the context of "I can just fix it". > > The critic tools is one way of finding these places, another is to just note down every time > you see a triviality and later go through that list. The bug tracker can be source, too. > > > <wtfm.jpg> > > Marcus

Oct. 10, 2013