August 2013 - Pharo-dev - lists.pharo.org

Questions about spec

by ClÃ©ment Bera

Hey guys, How do you detect when the user scroll in an element of a window in spec ? I would like to use the event 'whenListScroll:' or something like that but I don't find it. How then can I set the scrolled value of another list to keep them in sync ? Lastly, is there a plan to create some kind of table in spec ? I mean a UI that looks like excel UI ? Thanks for any answers

Aug. 13, 2013

[Amber] News from the last Amber team meeting

by Nicolas Petton

Hi guys, Here's a report of what was discussed on the Amber meeting yesterday. - Communication: It is obvious that we do not communicate enough outside of github or IRC about what's going on in Amber. It was decided that we will focus more on communication (thus this email ;-)). - Next release: Unlike it was initially planned, the next release of Amber won't be 1.0.0. There will probably be more intermediate releases. - Release cycles: It was decided that we will do more releases. We will try to embrace short release cycles. Releases will also be openly discussed on the mailing-list - Release process: The current release process is error-prone and involved a lot of small steps. To improve that we will in a first step write it down on the wiki, and try to automate it in the future - Matthias was introduced to the team - Next meeting in a month What is currently going on in Amber? - There is a huge work being done to make Amber load with an AMD (requirejs) - Helios is getting more attention to make it more stable and usable - The stepping debugger is going to be merged in master any time soon now and is basically working - The bootstrap JS file has been split into smaller and more understandable chunks Attendees: Nicolas Petton Manfred KrÃ¶hnert Herbert VojÄÃk Matthias Springer Excused: GÃ¶ran Krampe Cheers, Nico

Aug. 13, 2013

Re: [Pharo-dev] Should I send news from Amber here?

by Marcus Denker

On Aug 13, 2013, at 1:44 PM, Nicolas Petton <petton.nicolas(a)gmail.com> wrote: > Hi guys, > > I never know if I should or not send news about Amber here. Yes! Marcus

Aug. 13, 2013

Should I send news from Amber here?

by Nicolas Petton

Hi guys, I never know if I should or not send news about Amber here. I always felt like Amber is tightly linked to Pharo as I partly see it as a tool to be used when doing web dev in Pharo. Now I don't want to spam this list :) Nico

Aug. 13, 2013

Re: [Pharo-dev] Uniformizing Pharo

by StÃ©phane Ducasse

On Aug 12, 2013, at 10:21 PM, Sebastian Tleye <stleye(a)gmail.com> wrote: > I can add a rule for that, and check in the releaseTest if all the classes are respecting it (as i did checking repeated code) We will do it together. Now first I want to release the tool to autocategorize the methods when you edit a method. > > > 2013/8/12 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Hi guys > > I started to be fed up about protocol inconsistencies. So I will propose a set of rules (and a tool - I'm working on it) to automatically categorize methods. > The first on the list was printOn: in printing and I clean many methods already with a kind of happy smile on my face. > > Now we discussed today with esteban for initialize* we will use 'initialization' > I hope that this is ok for you because I'm fed up to have the following: > > {269->'initialization'. 248->'initialize-release'. 48->'as yet unclassified'. 15->'accessing'. 14->'private'. 12->'initializing'. 2->'instance creation'. 2->'testing'. 2->'initalize-release'. 2->'protocol'. 2->'display'. 1->'cleaning'. 1->'intializing'. 1->'like fullCopy'. 1->'keymapping'. 1->'ui-building'. 1->'initialize - release'. 1->'initialization-release'. 1->'intialize'. 1->'styling'. 1->'scrolling'. 1->'morphic ui'. 1->'world state'. 1->#'parts bin'} > > Please enjoy this gift from life, I love so much 'like fullCopy' as a category for initialize that I'm a bit sad to > clean this kind of poem (minimal haiku) so we will keep it for us :) > > Yes there is no little steps to get a bright system, every little clean is stop. > > No broken window! No dirt on the floor in Pharo. > > Stef >

Aug. 13, 2013

Re: [Pharo-dev] Updating the Pharo Contributors listing

by StÃ©phane Ducasse

BTW I will check that the contributors did sign well the license agreement. Stef > Dear Fellow Pharoers, > > As some of you may know, we have a page listing Pharo Contributors > > http://www.pharo-project.org/community/contributors > > This page was manually constructed and urgently needs an update. > Based on the code behind the Pharo Consultants page > > http://consultants.pharo.org > > we want a similar data driven, statically generated page for Pharo Contributors > > http://contributors.pharo.org > > the new page is based on some of the old data, but needs updating. Many people are missing as well. So please, please, edit the template and send me your new or up to date information. > > PharoContributor new > name: 'StÃ©phane Ducasse'; > id: 'stephaneducasse'; > email: 'stephane.ducasse(a)inria.fr'; > website: 'http://stephane.ducasse.free.fr/'; > description: 'Research director at INRIA Lille leading the RMoD Team. Pharo board member and president of ESUG.'; > image: 'http://stephane.ducasse.free.fr/StefFingerOnNose128.jpg'; > yourself > > PharoContributor new > name: 'Camillo Bruni'; > email: 'camillobruni(a)gmail.com'; > description: 'Cosmopolitan Swiss Hacker, currently at INRIA'; > yourself > > Some notes: > > - id is only needed when your name contains non-ascii characters > - email will default to pharo-dev(a)lists.pharo.org if missing > - website will default to a Google search for your name if a URL is missing > - image can be omitted if you have a Gravatar, else it becomes a smiley > - images will be rescaled to fit in 128x128, the URL needs to remain accessible > - description is a pure text String, no markup is allowed > - the description does not have to be too formal > - the page is statically generated, only then do changes take effect > > Regards, > > Sven, on behalf of the Pharo Board. > > PS: If you are curious, the code for generating this page can be found at > > http://www.smalltalkhub.com/#!/~Pharo/PharoPeople > >

Aug. 13, 2013

Re: [Pharo-dev] Access to issue tracker?

by HernÃ¡n Morales Durand

Same here El 13/08/2013 0:34, Javier PimÃ¡s escribiÃ³: > Hi, I don't know if it's just me or if I'm doing something wrong but I > was never able to get a user for the issue tracker. I enter here > <http://bugs.pharo.org/issues/register>, put a username, an email and > tick the not a monkey box in order to create an account. It redirects me > here <https://pharo.fogbugz.com/> but I never get a mail or anything I > could use to login, what I am doing wrong? > > Cheers, > Javier > > -- > Lic. Javier PimÃ¡s > Ciudad de Buenos Aires

Aug. 13, 2013

Access to issue tracker?

by Javier PimÃ¡s

Hi, I don't know if it's just me or if I'm doing something wrong but I was never able to get a user for the issue tracker. I enter here<http://bugs.pharo.org/issues/register>, put a username, an email and tick the not a monkey box in order to create an account. It redirects me here <https://pharo.fogbugz.com/> but I never get a mail or anything I could use to login, what I am doing wrong? Cheers, Javier -- Lic. Javier PimÃ¡s Ciudad de Buenos Aires

Aug. 13, 2013

Re: [Pharo-dev] Uniformizing Pharo

by Camillo Bruni

yes please! :) On 2013-08-12, at 17:08, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > I started to be fed up about protocol inconsistencies. So I will propose a set of rules (and a tool - I'm working on it) to automatically categorize methods. > The first on the list was printOn: in printing and I clean many methods already with a kind of happy smile on my face. > > Now we discussed today with esteban for initialize* we will use 'initialization' > I hope that this is ok for you because I'm fed up to have the following: > > {269->'initialization'. 248->'initialize-release'. 48->'as yet unclassified'. 15->'accessing'. 14->'private'. 12->'initializing'. 2->'instance creation'. 2->'testing'. 2->'initalize-release'. 2->'protocol'. 2->'display'. 1->'cleaning'. 1->'intializing'. 1->'like fullCopy'. 1->'keymapping'. 1->'ui-building'. 1->'initialize - release'. 1->'initialization-release'. 1->'intialize'. 1->'styling'. 1->'scrolling'. 1->'morphic ui'. 1->'world state'. 1->#'parts bin'} > > Please enjoy this gift from life, I love so much 'like fullCopy' as a category for initialize that I'm a bit sad to > clean this kind of poem (minimal haiku) so we will keep it for us :) > > Yes there is no little steps to get a bright system, every little clean is stop. > > No broken window! No dirt on the floor in Pharo. > > Stef

Aug. 13, 2013

Checking your Gravatar

by Sven Van Caekenberghe

Hi, Related to the usage of Gravatars (http://en.wikipedia.org/wiki/Gravatar) for http://contributors.pharo.org here is some code you can use to check whether your Gravatar image really works: ZnClient new beOneShot; url: 'http://www.gravatar.com/avatar'; addPathSegment: (ZnDigestAuthenticator md5Hash: 'sven(a)stfx.eu'); queryAt: #s put: '128'; queryAt: #d put: '404'; get; isSuccess. ZnClient new beOneShot; url: 'http://www.gravatar.com/avatar'; addPathSegment: (ZnDigestAuthenticator md5Hash: 'nobody.at.all(a)gmail.com'); queryAt: #s put: '128'; queryAt: #d put: '404'; get; isSuccess. (ZnClient new enforceHttpSuccess: true; beOneShot; url: 'http://www.gravatar.com/avatar'; addPathSegment: (ZnDigestAuthenticator md5Hash: 'tudor(a)tudorgirba.com'); queryAt: #s put: '128'; queryAt: #d put: '404'; contentReader: [ :entity | ImageMorph fromStream: entity readStream ]; get) openInWindow. And now you know how simple Gravatars really are, provided you use a proper programming language to access them. Enjoy! Sven

Aug. 12, 2013