September 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] PharoLauncher mac download not the latest version

by kilon alios

will do, my pleasure On Wed, Sep 10, 2014 at 7:30 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > On Wed, Sep 10, 2014 at 5:13 PM, kilon alios <kilon.alios(a)gmail.com> > wrote: > > I could do it, if you want me to include specific version from packages > . Or > > if you want some versioning scheme. For example what version you want > this > > stable release to be ? > > > 0.2.0 (totally random). I'm waiting for input from the Pharo board > before releasing 1.0. > > > We keep the bleeding edge for latest stuff like my > > progress bar and as soon as things work without problem we integrate them > > into the next version ? > > > yes > > > You have any guidelines you want me to follow ? > > use the workflow of versionner. > > Thank you Kilon > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > >

Sept. 10, 2014

Re: [Pharo-dev] PharoLauncher mac download not the latest version

by Damien Cassou

On Wed, Sep 10, 2014 at 5:13 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > I could do it, if you want me to include specific version from packages . Or > if you want some versioning scheme. For example what version you want this > stable release to be ? 0.2.0 (totally random). I'm waiting for input from the Pharo board before releasing 1.0. > We keep the bleeding edge for latest stuff like my > progress bar and as soon as things work without problem we integrate them > into the next version ? yes > You have any guidelines you want me to follow ? use the workflow of versionner. Thank you Kilon -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Sept. 10, 2014

Re: [Pharo-dev] Class names and special names for special things.

by phil＠highoctane.be

Alternative would be that each open, print etc is an object of class Command with some methods. Le 10 sept. 2014 17:32, "phil(a)highoctane.be" <phil(a)highoctane.be> a Ã©crit : > A > Le 10 sept. 2014 17:21, "kilon alios" <kilon.alios(a)gmail.com> a Ã©crit : > > > > how about introducing a secondary parser on top of the code editor that > you can enable disable at will and can create "code shortcuts" using such > symbols ? it will then store them as regular pharo syntax without affecting > the pharo system. Its an idea I am thinking playing with but not so much > for special class names but rather omitting the class names altogether and > create shorter version of calling a method that is more English like, like : > > > > open "mydoc.pdf" in documents. > > display pdf. > > go to page 4. > > print page > > I would do that with a dedicated petit parser grammar. > > As for highlighthing the styler stuff is unknown territory for me. > > In the GT doc / pillar stuff, I saw Interesting stuff going on on Doru's > blog. > > Phil > > > > > > On Wed, Sep 10, 2014 at 6:13 PM, phil(a)highoctane.be <phil(a)highoctane.be> > wrote: > >> > >> Of course. But there are some other things that are available. > >> > >> Â§, `, ? comes to mind. > >> > >> Phil > >> > >> > >> > >> > >> On Wed, Sep 10, 2014 at 4:59 PM, Marcus Denker <marcus.denker(a)inria.fr> > wrote: > >>> > >>> > >>> On 10 Sep 2014, at 16:38, phil(a)highoctane.be wrote: > >>> > >>> > I was playing around with the idea of using stuff like in jQuery, > where we do have the '$' function that would do a lot of things. > >>> > > >>> > But one cannot create such elements as > >>> > > >>> > SlotClassBuilder>>validateClassName > >>> > "Validate the new class name. Raise warning if invalid." > >>> > > >>> > name > >>> > detect: [ :c | (c isAlphaNumeric or: [ c = $_ ]) not ] > >>> > ifFound: [ :c | InvalidGlobalName signal: 'Invalid > character: ''' , c printString , '''' for: name ]. > >>> > name first canBeGlobalVarInitial > >>> > ifFalse: [ InvalidGlobalName signal: 'Class name does > not start with a valid Global Var Initial' for: name ] > >>> > > >>> > doesn't let us. > >>> > > >>> > Is there a reason for that (ok, we have $ for chars, and #, ... and > other things but still). > >>> > > >>> > >>> The problem is that $ is part of the smalltalk grammar for symbols, $ > can not be a variable name. > >>> > >>> $asdasd > >>> > >>> is parsed as a message send to the character a, for example. > >>> > >>> Marcus > >> > >> > > >

Sept. 10, 2014

Re: [Pharo-dev] Tests around Pharo

by Ben Coman

Mathieu Schepens wrote: > > As students of Master 2 IAGL from Lille 1 university (France), four of > us are asked to develop some tests around an open-source project. > Among proposed projects, we decided to contribute to Pharo. > > We'll have to develop 15-20tests > (isolated/automated/reproducible/quick/good code coverage), and we are > wanting them to be as much useful as possible for developers. > > Where (in the project) could it be useful to develop some tests ? Do > you have advices/instructions for us in order to develop them ? > > > We are new with Pharo and Smalltalk, and are having about 8-10hours > available per developer. > > > Best regards, > > Mathieu Schepens > Thanks for your consideration of Pharo. Now we should properly understand your time constraints. So... * What is your experience with Pharo? * How comfortable are you with the syntax, Browser and Debugger? * Have you used the TestRunner previously? * Have you submitted a code Slice for integration before? In a lot of areas, a lot of background knowledge is required to writing useful tests, which you obviously can't gain in your allocated time. However every additional test increasing coverage is useful. However even more use than these individual tests is that you have a good experience with Pharo, to hopefully see you back here later are this course requirement is done. (Careful, Pharo is addictive). So to be pragmatic, I suggest a good starting point is a widely understood domain like strings. I'll give you an example of how to discover some coverage gaps yourself. FINDING GAPS 1. Open World menu > Tools > Finder 2. From its pulldown menu which says "Selectors" choose "Examples" 3. Now imagine some kind of string function you are familiar with... What are the parameters and what is the result? For example, imagine a function to might give you the first N characters of a String. For two parameters 'abcd' and 2, the result would be 'ab'. Now in the text box on the left side, type those three items separated by a dot. For example... 'abcd' . 2 . 'ab' 4. Press the <Search> button, and you will see three results. Using "contractTo:" as an example, navigate to view its code. In that code select the text "contractTo:", right-click and choose "Extended search... > senders of it". The list that comes up shows a class on the left and on the right the method that calls "contractTo". Now you will notice that none of the classes include the name "Test". Ah-Haaa!! A gap to fill :) DEFINING TESTS 1. Open Spotlight in the top right by pressing CMD-SPACE (on a Mac, other platforms have a different key modifier) 2. Enter... StringTest which should open a Browser on the StringTest class 3. Just for practice, click on the little circle next to the method names to run that test method. Right-click on the test and choose "Debug" to step through the test. 4. Review the other existing tests and replicate for you own tests for methods found that have a gap in coverage. SUBMISSION AND INTEGRATION Once you have your new tests working you should get a login to the Pharo issue tracker at http://pharo.fogbugz.com create a ticket, and submit a "Slice" with your changes for review and integration. (btw, right now I am heading off to bed so others will follow up further questions). good luck, cheers -ben

Sept. 10, 2014

Re: [Pharo-dev] Class names and special names for special things.

by phil＠highoctane.be

A Le 10 sept. 2014 17:21, "kilon alios" <kilon.alios(a)gmail.com> a Ã©crit : > > how about introducing a secondary parser on top of the code editor that you can enable disable at will and can create "code shortcuts" using such symbols ? it will then store them as regular pharo syntax without affecting the pharo system. Its an idea I am thinking playing with but not so much for special class names but rather omitting the class names altogether and create shorter version of calling a method that is more English like, like : > > open "mydoc.pdf" in documents. > display pdf. > go to page 4. > print page I would do that with a dedicated petit parser grammar. As for highlighthing the styler stuff is unknown territory for me. In the GT doc / pillar stuff, I saw Interesting stuff going on on Doru's blog. Phil > > > On Wed, Sep 10, 2014 at 6:13 PM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: >> >> Of course. But there are some other things that are available. >> >> Â§, `, ? comes to mind. >> >> Phil >> >> >> >> >> On Wed, Sep 10, 2014 at 4:59 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>> >>> On 10 Sep 2014, at 16:38, phil(a)highoctane.be wrote: >>> >>> > I was playing around with the idea of using stuff like in jQuery, where we do have the '$' function that would do a lot of things. >>> > >>> > But one cannot create such elements as >>> > >>> > SlotClassBuilder>>validateClassName >>> > "Validate the new class name. Raise warning if invalid." >>> > >>> > name >>> > detect: [ :c | (c isAlphaNumeric or: [ c = $_ ]) not ] >>> > ifFound: [ :c | InvalidGlobalName signal: 'Invalid character: ''' , c printString , '''' for: name ]. >>> > name first canBeGlobalVarInitial >>> > ifFalse: [ InvalidGlobalName signal: 'Class name does not start with a valid Global Var Initial' for: name ] >>> > >>> > doesn't let us. >>> > >>> > Is there a reason for that (ok, we have $ for chars, and #, ... and other things but still). >>> > >>> >>> The problem is that $ is part of the smalltalk grammar for symbols, $ can not be a variable name. >>> >>> $asdasd >>> >>> is parsed as a message send to the character a, for example. >>> >>> Marcus >> >> >

Sept. 10, 2014

Re: [Pharo-dev] Class names and special names for special things.

by kilon alios

how about introducing a secondary parser on top of the code editor that you can enable disable at will and can create "code shortcuts" using such symbols ? it will then store them as regular pharo syntax without affecting the pharo system. Its an idea I am thinking playing with but not so much for special class names but rather omitting the class names altogether and create shorter version of calling a method that is more English like, like : open "mydoc.pdf" in documents. display pdf. go to page 4. print page On Wed, Sep 10, 2014 at 6:13 PM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > Of course. But there are some other things that are available. > > Â§, `, ? comes to mind. > > Phil > > > > > On Wed, Sep 10, 2014 at 4:59 PM, Marcus Denker <marcus.denker(a)inria.fr> > wrote: > >> >> On 10 Sep 2014, at 16:38, phil(a)highoctane.be wrote: >> >> > I was playing around with the idea of using stuff like in jQuery, where >> we do have the '$' function that would do a lot of things. >> > >> > But one cannot create such elements as >> > >> > SlotClassBuilder>>validateClassName >> > "Validate the new class name. Raise warning if invalid." >> > >> > name >> > detect: [ :c | (c isAlphaNumeric or: [ c = $_ ]) not ] >> > ifFound: [ :c | InvalidGlobalName signal: 'Invalid >> character: ''' , c printString , '''' for: name ]. >> > name first canBeGlobalVarInitial >> > ifFalse: [ InvalidGlobalName signal: 'Class name does not >> start with a valid Global Var Initial' for: name ] >> > >> > doesn't let us. >> > >> > Is there a reason for that (ok, we have $ for chars, and #, ... and >> other things but still). >> > >> >> The problem is that $ is part of the smalltalk grammar for symbols, $ can >> not be a variable name. >> >> $asdasd >> >> is parsed as a message send to the character a, for example. >> >> Marcus >> > >

Sept. 10, 2014

Re: [Pharo-dev] TWM - Shortcuts - Fixed.

by phil＠highoctane.be

Can't be without it. Just make sure you close it and do a GC at some points in time as it seems to hold a bit too strongly on some objects. We should do a little "recycle" button :-) Phil On Wed, Sep 10, 2014 at 4:58 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > let me hijack this thread saying I really love the TWM , brilliant way of > managing the biggest problem of Pharo, windows mania. Great job and thanks > :) > > On Wed, Sep 10, 2014 at 5:48 PM, phil(a)highoctane.be <phil(a)highoctane.be> > wrote: > >> I was frustrated by being unable to have the Tiling Window Manager >> shortcuts not working properly in 3.0 >> >> This is now fixed by registering the category as a global one. >> >> Sean, Laurent, is this working for you? >> >> Phil >> > >

Sept. 10, 2014

Re: [Pharo-dev] Class names and special names for special things.

by phil＠highoctane.be

Of course. But there are some other things that are available. Â§, `, ? comes to mind. Phil On Wed, Sep 10, 2014 at 4:59 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 10 Sep 2014, at 16:38, phil(a)highoctane.be wrote: > > > I was playing around with the idea of using stuff like in jQuery, where > we do have the '$' function that would do a lot of things. > > > > But one cannot create such elements as > > > > SlotClassBuilder>>validateClassName > > "Validate the new class name. Raise warning if invalid." > > > > name > > detect: [ :c | (c isAlphaNumeric or: [ c = $_ ]) not ] > > ifFound: [ :c | InvalidGlobalName signal: 'Invalid > character: ''' , c printString , '''' for: name ]. > > name first canBeGlobalVarInitial > > ifFalse: [ InvalidGlobalName signal: 'Class name does not > start with a valid Global Var Initial' for: name ] > > > > doesn't let us. > > > > Is there a reason for that (ok, we have $ for chars, and #, ... and > other things but still). > > > > The problem is that $ is part of the smalltalk grammar for symbols, $ can > not be a variable name. > > $asdasd > > is parsed as a message send to the character a, for example. > > Marcus >

Sept. 10, 2014

Re: [Pharo-dev] PharoLauncher mac download not the latest version

by kilon alios

I could do it, if you want me to include specific version from packages . Or if you want some versioning scheme. For example what version you want this stable release to be ? We keep the bleeding edge for latest stuff like my progress bar and as soon as things work without problem we integrate them into the next version ? You have any guidelines you want me to follow ? On Wed, Sep 10, 2014 at 5:56 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > On Wed, Sep 10, 2014 at 11:36 AM, kilon alios <kilon.alios(a)gmail.com> > wrote: > > ah ok yes I realised that it was a complex process one build triggering > the > > other build but I did not notice it was triggered manually. Yes I agree > > thats a good idea but I expected this control to be at Configuration > level > > by having a "stable" release. > > > Ben explanation is the way I'm doing it currently. Your way is the way > I would like it to be :-). But I had no time to give to any Smalltalk > development recently. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > >

Sept. 10, 2014

Re: [Pharo-dev] Class names and special names for special things.

by Marcus Denker

On 10 Sep 2014, at 16:38, phil(a)highoctane.be wrote: > I was playing around with the idea of using stuff like in jQuery, where we do have the '$' function that would do a lot of things. > > But one cannot create such elements as > > SlotClassBuilder>>validateClassName > "Validate the new class name. Raise warning if invalid." > > name > detect: [ :c | (c isAlphaNumeric or: [ c = $_ ]) not ] > ifFound: [ :c | InvalidGlobalName signal: 'Invalid character: ''' , c printString , '''' for: name ]. > name first canBeGlobalVarInitial > ifFalse: [ InvalidGlobalName signal: 'Class name does not start with a valid Global Var Initial' for: name ] > > doesn't let us. > > Is there a reason for that (ok, we have $ for chars, and #, ... and other things but still). > The problem is that $ is part of the smalltalk grammar for symbols, $ can not be a variable name. $asdasd is parsed as a message send to the character a, for example. Marcus

Sept. 10, 2014