- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Should Job use SystemAnnouncer?

by Camillo Bruni

On 2013-09-02, at 06:25, Stephan Eggermont <stephan(a)stack.nl> wrote: > Stef wrote: >> did you notice a different between SystemAnnouncer and replacing it by another one? > > Yes, it made a significant difference. It did not remove enough overhead though. > Job>value: was called over 100K times, doing that only every 100 increments > helped enough. the main problem with the current progress bar morph design is that updates are forced whenever the underlying model (here job) changes. This is *very* costly for high-frequency updates, which is exactly the moment when you want to use the progress bar ;) It should work the other way around, the progress bar morph polls the underlying model with a given frequency (~10/s) and then refreshes the UI if the model changed.

Sept. 2, 2013

Re: [Pharo-dev] [update 3.0] #30363

by Camillo Bruni

On 2013-09-02, at 06:07, Marcus Denker <marcus.denker(a)inria.fr> wrote: > 30363 > ----- > > 11468 Use singleton for default FileSystem > https://pharo.fogbugz.com/f/cases/11468 I'll take care of it later today

Sept. 2, 2013

Re: [Pharo-dev] OSProcess for Pharo3.0

by Camillo Bruni

On 2013-09-02, at 11:07, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > what we could do is to not deprecate now the methods? > Then we can deprecate them when we release 3.0 I would say the exact opposite, deprecate methods as early as possible If I deprecate a method now, - it is deprecated in the current dev version 3.0 dev - it is deprecated in the next release 3.0 stable - it is removed in the next dev version 4.0 dev so the current behavior is correct. For these issues apply the following strategy: - the latest stable version should load in 2.0 (1.4 is dead) - the latest dev version should most probably work in 3.0 So in this case, OSProcess could be easily updated to use 'Smalltalk os' since that exists already in 2.0, and nobody should even care developing or backporting software for 2.0.

Sept. 2, 2013

Re: [Pharo-dev] "self foo: (var := â¦)" vs "var := â¦. self foo: var"

by Igor Stasenko

On 2 September 2013 14:32, Luc Fabresse <luc.fabresse(a)gmail.com> wrote: > > 2013/9/2 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > >> Alex >> >> from a style point of view I found really ugly to use the side effect >> value. >> I tend to think that they return #undefined as in Scheme. >> > > yes > but it would be nice if := were a message send and in that case it would > make sense to write it like that. > > yes.. in that regard, if you replace assignment with message it will turn it to simple setter method which answers the value being set. the only difference that in most cases setters answer the receiver of message, but not value being set. But if we imagine that variable is an object which holding some value, it works similarly then e.g. you assign the value to variable, and setter answers the variable itself (as a receiver of message) but not its value. > Luc > > >> Stef >> >> On Sep 1, 2013, at 3:02 PM, Alexandre Bergel <alexandre.bergel(a)me.com> >> wrote: >> >> > Hi! >> > >> > I am facing a strange situation: >> > >> > The following expression raises an error: >> > -=-=-=-=-=-=-=-=-= >> > rawView add: (helpLabel := (ROElement on: 'Click here!') + ROLabel). >> > -=-=-=-=-=-=-=-=-= >> > >> > Apparently, what is sent as argument to #add: is an integer. >> > >> > I have to update my code with : >> > -=-=-=-=-=-=-=-=-= >> > (helpLabel := (ROElement on: 'Click here!') + ROLabel). >> > rawView add: helpLabel. >> > -=-=-=-=-=-=-=-=-= >> > >> > To not have an error. >> > >> > This is really strange! By the way, this looks like the issue with >> Metacello? >> > >> > Alexandre >> > >> > -- >> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> > Alexandre Bergel http://www.bergel.eu >> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> > >> > >> > >> > >> >> >> > -- Best regards, Igor Stasenko.

Sept. 2, 2013

Re: [Pharo-dev] OSProcess for Pharo3.0

by Igor Stasenko

On 2 September 2013 16:41, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > Le 02/09/2013 16:07, StÃ©phane Ducasse a Ã©crit : > > what we could do is to not deprecate now the methods? >> Then we can deprecate them when we release 3.0 >> > > When starting pharo4? That would be perfect :) > > I just noticed that Smalltalk os exist in 1.4 and 2.0. So my code should > work on an old image, isn't it? It would also work on 2.0 and 1.4, no? > > (or something like (Smalltalk respondsTo: #os) ifTrue: [Smalltalk os name]) > > When was Smalltalk>>os introduced ? > > i don't remember.. but it been a while ago. Smalltalk os name => 'Mac OS' Smalltalk os version => '1083' > Thierry > > > Stef >> >> On Sep 2, 2013, at 2:21 PM, Goubier Thierry <thierry.goubier(a)cea.fr> >> wrote: >> >> Stef, >>> >>> a question then: how to check that I am on a pharo3 image which is newer >>> than 2013-07-22 (since this is the date where the OSPlatform methods have >>> been deprecated) ? >>> >>> If I write something like >>> >>> (Smalltalk version beginsWith: 'Pharo3') >>> ifTrue: [ ^ Smalltalk os name ]. >>> >>> Then this code may fail on old Pharo3 images. Or should I test the >>> presence of os and vm as methods of Smalltalk? >>> >>> Thanks, >>> >>> Thierry >>> >>> >>> Le 02/09/2013 12:02, StÃ©phane Ducasse a Ã©crit : >>> >>>> ok I read the big thread and what would be a solution? >>>> >>>> >>>> On Sep 2, 2013, at 11:20 AM, Goubier Thierry <thierry.goubier(a)cea.fr> >>>> wrote: >>>> >>>> Hi, >>>>> >>>>> sometimes during the summer, a method used by OSProcess to determine >>>>> the OS Platform has been deprecated in Pharo 3.0. Is it possible to have a >>>>> look into updating OSProcess? >>>>> >>>>> I'm still unable to use Pharo3.0 because of issue 11102, but I'd like >>>>> to get gitfiletree to work on it, and I think the main issue is OSProcess. >>>>> >>>>> Thanks, >>>>> >>>>> Thierry >>>>> -- >>>>> Thierry Goubier >>>>> CEA list >>>>> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >>>>> 91191 Gif sur Yvette Cedex >>>>> France >>>>> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >>>>> >>>>> >>>> >>>> >>>> >>>> >>> -- >>> Thierry Goubier >>> CEA list >>> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >>> 91191 Gif sur Yvette Cedex >>> France >>> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >>> >>> >> >> >> >> > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 > > -- Best regards, Igor Stasenko.

Sept. 2, 2013

Re: [Pharo-dev] OSProcess for Pharo3.0

by Goubier Thierry

Le 02/09/2013 16:07, StÃ©phane Ducasse a Ã©crit : > what we could do is to not deprecate now the methods? > Then we can deprecate them when we release 3.0 When starting pharo4? That would be perfect :) I just noticed that Smalltalk os exist in 1.4 and 2.0. So my code should work on an old image, isn't it? It would also work on 2.0 and 1.4, no? (or something like (Smalltalk respondsTo: #os) ifTrue: [Smalltalk os name]) When was Smalltalk>>os introduced ? Thierry > Stef > > On Sep 2, 2013, at 2:21 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > >> Stef, >> >> a question then: how to check that I am on a pharo3 image which is newer than 2013-07-22 (since this is the date where the OSPlatform methods have been deprecated) ? >> >> If I write something like >> >> (Smalltalk version beginsWith: 'Pharo3') >> ifTrue: [ ^ Smalltalk os name ]. >> >> Then this code may fail on old Pharo3 images. Or should I test the presence of os and vm as methods of Smalltalk? >> >> Thanks, >> >> Thierry >> >> >> Le 02/09/2013 12:02, StÃ©phane Ducasse a Ã©crit : >>> ok I read the big thread and what would be a solution? >>> >>> >>> On Sep 2, 2013, at 11:20 AM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: >>> >>>> Hi, >>>> >>>> sometimes during the summer, a method used by OSProcess to determine the OS Platform has been deprecated in Pharo 3.0. Is it possible to have a look into updating OSProcess? >>>> >>>> I'm still unable to use Pharo3.0 because of issue 11102, but I'd like to get gitfiletree to work on it, and I think the main issue is OSProcess. >>>> >>>> Thanks, >>>> >>>> Thierry >>>> -- >>>> Thierry Goubier >>>> CEA list >>>> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >>>> 91191 Gif sur Yvette Cedex >>>> France >>>> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >>>> >>> >>> >>> >>> >> >> -- >> Thierry Goubier >> CEA list >> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >> 91191 Gif sur Yvette Cedex >> France >> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >> > > > > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Sept. 2, 2013

[update 3.0] #30363

by Marcus Denker

30363 ----- 11524 MessageBrowser new protocol method https://pharo.fogbugz.com/f/cases/11524 11523 SystemNavigation small refactoring https://pharo.fogbugz.com/f/cases/11523 11498 Be able to set an initial filter in ListDialogWindow https://pharo.fogbugz.com/f/cases/11498 11522 NewList separator support https://pharo.fogbugz.com/f/cases/11522 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tools-MarcusDenker.1233.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Tools-MarcusDenker.133.d… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Polymorph-Widgets-MarcusDenke… http://smalltalkhub.com/mc/Pharo/Pharo30/main/NewList-MarcusDenker.56.diff

Sept. 2, 2013

Re: [Pharo-dev] OSProcess for Pharo3.0

by StÃ©phane Ducasse

what we could do is to not deprecate now the methods? Then we can deprecate them when we release 3.0 Stef On Sep 2, 2013, at 2:21 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > Stef, > > a question then: how to check that I am on a pharo3 image which is newer than 2013-07-22 (since this is the date where the OSPlatform methods have been deprecated) ? > > If I write something like > > (Smalltalk version beginsWith: 'Pharo3') > ifTrue: [ ^ Smalltalk os name ]. > > Then this code may fail on old Pharo3 images. Or should I test the presence of os and vm as methods of Smalltalk? > > Thanks, > > Thierry > > > Le 02/09/2013 12:02, StÃ©phane Ducasse a Ã©crit : >> ok I read the big thread and what would be a solution? >> >> >> On Sep 2, 2013, at 11:20 AM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: >> >>> Hi, >>> >>> sometimes during the summer, a method used by OSProcess to determine the OS Platform has been deprecated in Pharo 3.0. Is it possible to have a look into updating OSProcess? >>> >>> I'm still unable to use Pharo3.0 because of issue 11102, but I'd like to get gitfiletree to work on it, and I think the main issue is OSProcess. >>> >>> Thanks, >>> >>> Thierry >>> -- >>> Thierry Goubier >>> CEA list >>> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >>> 91191 Gif sur Yvette Cedex >>> France >>> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >>> >> >> >> >> > > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >

Sept. 2, 2013

Re: [Pharo-dev] Smacc question

by StÃ©phane Ducasse

I will check because may be the author of the code committed code that does not compile on VW either. Thanks for your hints. stef On Sep 2, 2013, at 12:57 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > Hi Stef, > > I don't see unsupported syntax, just missing quotes around some tokens, such as > ** should be "**", + should be "+" in binary_adding_operator, etc... > BOOLEAN is probably <BOOLEAN> > > Are you sure that the text you're joining isn't unquoted? It's hard to requote everything as it should be, and not having the lexer definition makes testing with SmaCC a bit painfull. > > Thierry > > Le 02/09/2013 12:18, StÃ©phane Ducasse a Ã©crit : >> Hi thierry >> >> I imported the generated parsers (a student did a while ago on VW using Smacc). >> The generated parser parse apparently the tests. >> Now when I regenerate the parser with Pharo I cannot get the Smacc compuling the parser. >> I get a SmaCCParserError: Token not expected >> >> do you have any idea what would not be supported in the Pharo/Squeak version >> >> >> # >> # Expression Parser >> #============================================= >> >> goal: expression* ; >> >> expression: relation >> ( ( >> and >> | >> and then >> | >> or >> | >> or else >> | >> xor >> ) relation )*; >> >> relation: simple_expression >> sndPart?; >> >> sndPart: relational_operator simple_expression | >> ( >> not >> )? ( >> in range >> | >> in >> type_mark); >> >> simple_expression: (unary_adding_operator)? >> term (binary_adding_operator term)*; >> >> term: factor (multiplying_operator factor)*; >> >> factor: primary ( >> ** >> primary)? | >> abs >> primary | >> not >> primary; >> >> #<identifier> instead of name >> primary: <numeric_lit> | >> null >> | <string_lit> | <number> | >> <identifier> | <identifier> >> '' >> <identifier> | >> function_call | >> ( >> expression >> ) >> ; >> #simplified >> >> binary_adding_operator: >> + >> | >> - >> | >> & >> ; >> unary_adding_operator: >> + >> | >> - >> ; >> multiplying_operator: >> * >> | >> / >> | >> mod >> | >> rem >> ; >> relational_operator: >> = >> | >> /= >> | >> < >> | >> <= >> | >> > >> | >> >= >> ; >> >> #============================================================================= >> >> function_call: <identifier> ''identifier'' function_arguments ''args'' >> { ADFunctionCall withElements: args withName: identifier } ; >> >> function_arguments: >> ( >> expression ( >> , >> expression)* >> ) >> ; >> >> #==== Declarations =========================================================== >> >> discrete_range: range | subtype_indication; #discrete_? >> >> subtype_indication: type_mark (constraint)? ; >> >> type_mark: type; >> >> constraint: range_constraint; >> >> range_constraint: >> range >> range; >> >> range: range_attribute | (simple_expression >> .. >> simple_expression); >> >> range_attribute: <identifier> >> '' >> >> range >> ; #cf. 4.1.4 >> >> #==== Names ================================================================== >> >> name: simple_name | <char_lit> | >> indexed_component | >> slice | selected_component | >> attribute; #operator_symbol >> >> prefix: name | function_call; >> >> simple_name: <identifier>; >> >> indexed_component: prefix >> ( >> expression ( >> , >> expression )* >> ) >> ; >> >> slice: prefix >> ( >> discrete_range >> ) >> ; >> >> selected_component: prefix >> . >> selector; >> >> selector: simple_name | <char_lit> | >> >> all >> ; #operator_symbol >> >> attribute: prefix >> '' >> attribute_designator; >> >> attribute_designator: simple_name ( >> ( >> <universal_static_expression> >> ) >> )? ; >> >> #==== Types: appendix c: package STANDARD plus more ========================================================= >> type: >> BOOLEAN >> | >> REAL >> | >> INTEGER >> | >> FLOAT >> | >> CHARACTER >> | >> DURATION >> | >> >> STRING >> | >> RAINBOW >> ; >> >> ' >> >> > > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >

Sept. 2, 2013

Re: [Pharo-dev] Aida 6.6 OneClicks for Pharo now ready, about geolocation

by Sven Van Caekenberghe

Ahh, OK, it is a way to read the location info from the browser. Cool. Thanks for the explanation. On 02 Sep 2013, at 14:42, Janko MivÅ¡ek <janko.mivsek(a)eranova.si> wrote: >> I was looking for the Geolocation support, but can't seem to find it. Where should I look ? > > There is no docs or dev notes yet, but usage is simple. Say you'd like > to show your location on realtime example: > http://demo.aidaweb.si/demos?view=realtime. Look at the > WebDemo/WebDemoApp classes: > > WebDemoApp viewRealtime > self page addGeolocationScript. "to report current geolocation" > ... > loc := self session geolocation "instance of WebGeolocation" > e > addText: 'My current location is: '; > addText: loc locationPoint printString. > ... > > When you switch-on the geolocation, the browser starts sending the > geolocation changes by Ajax or (in this realtime case) WebSocket to the > current session. It is stored in an instance of WebGeolocation class. > > It can be simple to extend it by showing the location of last who > changed the counter (by help of additional instvar lastLocation in > WebDemo domain object): > > WebDemoApp viewRealtime > ... > (e cell addButtonText: ' Decrement ') > noSubmit; > onClickDo: > [self observee decCounter. > self observee lastLocation: self session geolocation].

Sept. 2, 2013