- Pharo-dev - lists.pharo.org

[ANN] Willow 4.0.0 released!
by Gabriel Cotelli Nov. 22, 2017

Nov. 22, 2017

Hi, We're happy to announce the general availability of Willow and it's related projects in the Web Stack ecosystem hosted at https://github.com/ba-st/. Willow is a Web Interaction Library that eases the burden of creating AJAX-based web applications. The project goals are: - Provide a Smalltalk protocol for the interactive behavior of web components - Reify the pieces of a web application to improve reuse - Offer a simple and polymorphic protocol for different front-end frameworks. It's MIT licensed and built on top of the Seaside <https://github.com/SeasideSt/Seaside> Web Framework providing a set of composable components and easier AJAX interaction. It's intented to work alongside the RenoirSt <https://github.com/ba-st/RenoirSt> DSL to define the CSS of your application. This is a multi-release announcement of the following related projects: - Willow <https://github.com/ba-st/Willow> v4.0.0 : Core features, components and commands - Willow-Bootstrap <https://github.com/ba-st/Willow-Bootstrap> v4.0.0 : Bootstrap 3 integration, components and plugins - Willow-JQueryUI <https://github.com/ba-st/Willow-JQueryUI> v4.0.0 : JQuery UI integration and components. - Willow-SpinKit <https://github.com/ba-st/Willow-SpinKit> v1.0.2 : Spinner components - Willow-Playground <https://github.com/ba-st/Willow-Playground/> v1.0.0 : An interactive presentation introducing the project and two example applications: Web Based Test Runner and Live Docs. - RenoirSt <https://github.com/ba-st/RenoirSt> v3.3.0 : CSS DSL. [ Latest Changes: Updated Seaside dependencies (for the Seaside extensions groups) and added Pharo 7 to the build matrix. ] SemanticUI <https://github.com/ba-st/Willow-SemanticUI> integration is still a work in progress. We've started working on a more complete tutorial and a Pharo booklet. Anyone interested in joining our ba-st projects <https://github.com/ba-st/> is welcome Regards, Gabriel Cotelli, Maxi Tabacman and all the contributors.

4 5

Cannot inspect a temporary in debugger
by Nicolas Cellier Nov. 22, 2017

Nov. 22, 2017

Hi again, I'm experiencing strange behaviour again... This is with Pharo7.0-32bit-a8a1e21.image the temp variable index does not want to print value in bottom pane. but when I attempt to inspect it from code pane, no more luck... [image: Images intÃ©grÃ©es 1]

2 1

balloonHelp for menus
by Nicolas Cellier Nov. 22, 2017

Nov. 22, 2017

Hi again, I see no balloon help in menus in Pharo 7.0. Some menu labels are intention revealing and a balloon paraphrasing the label is useless. But that's not the general case, some complex actions like found in Iceberg interface would deserve a bit more explanations for noobs like me. A link from the menu to some Help topic would also be more than welcome (maybe thru an anchor, a tag or some other machinery...)

2 1

method usage example: annotation or comment?
by Nicolas Cellier Nov. 22, 2017

Nov. 22, 2017

Hi, I encountered some annotations in the form: < expr: (foo) result: bar > and some meta comments of the form: " foo >>> bar " I think both are aimed at providing examples of method usage for documentation, non regression testing, etc... I note that the former is requiring a literal result, which is quite limiting (1/3) is not a literal for example, 0@0 neither... IMO it should be extended for handling any valid expression. But that still makes two different ways of expressing the same intent. So what's the canonical one?

2 1

[ANN] Smalltalks 2017 - Videos + Slides + Photos
by Gabriel Cotelli Nov. 22, 2017

Nov. 22, 2017

2 1

[Pharo 7.0-dev] Build #318: 20739-Remove-dead-stream-primitives
by ci-pharo-ci-jenkins2＠inria.fr Nov. 22, 2017

Nov. 22, 2017

There is a new Pharo build available! The status of the build #318 was: SUCCESS. The Pull Request #524 was integrated: "20739-Remove-dead-stream-primitives" Pull request url: https://github.com/pharo-project/pharo/pull/524 Issue Url: https://pharo.fogbugz.com/f/cases/20739 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #317: 20645-Windows-rebuildFieldAccessors-problem
by ci-pharo-ci-jenkins2＠inria.fr Nov. 22, 2017

Nov. 22, 2017

There is a new Pharo build available! The status of the build #317 was: SUCCESS. The Pull Request #521 was integrated: "20645-Windows-rebuildFieldAccessors-problem" Pull request url: https://github.com/pharo-project/pharo/pull/521 Issue Url: https://pharo.fogbugz.com/f/cases/20645 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

DateAndTime local time zone not initialised in Pharo 7
by Sven Van Caekenberghe Nov. 22, 2017

Nov. 22, 2017

In my Pharo 7 images, DateAndTime's local time zone is not initialised. Normally, Locale class>>#startUp: calls DateAndTime localTimeZone: LocalTimeZone new but that was somehow not the case, hence the image operated as in TZ 0, UTC, offset 0. Does anyone else see this ? It seems Locale is not in the #startupList but it should be. Sven

2 1

Re: [Pharo-dev] Pharo and special unary selectors
by Peter UhnÃ¡k Nov. 22, 2017

Nov. 22, 2017

I just randomly ran into this project https://github.com/ba-st/aconcagua which seems to be designed around such unary selectors. On Sat, Nov 18, 2017 at 12:55 AM, Benoit St-Jean via Pharo-dev < pharo-dev(a)lists.pharo.org> wrote: > > > ---------- Forwarded message ---------- > From: Benoit St-Jean <bstjean(a)yahoo.com> > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Cc: > Bcc: > Date: Fri, 17 Nov 2017 23:55:56 +0000 (UTC) > Subject: Re: [Pharo-dev] Pharo and special unary selectors > Personnally, I against adding those special symbols. They add close to > nothing (except complexity in the parser) to what we can actually do! > > Besides, what does 30$ + 17$ add up to? Oh! Did I tell you it was > actually $30USD + $17CAN ? :) > > > ----------------- > BenoÃ®t St-Jean > Yahoo! Messenger: bstjean > Twitter: @BenLeChialeux > Pinterest: benoitstjean > Instagram: Chef_Benito > IRC: lamneth > Blogue: endormitoire.wordpress.com > "A standpoint is an intellectual horizon of radius zero". (A. Einstein) > > > On Friday, November 17, 2017, 6:41:11 PM EST, Ben Coman < > btc(a)openinworld.com> wrote: > > > If a valid Smalltalk method identifier contains only... > [a-zA-Z][a-zA-Z0-9]* > http://www.osdata.com/programming/firstprograms/valididentifiers.html > > then one option could be that unary symbols must touch the previous > identifier, i.e. no intervening whitespace, > > 100% > 20$ > 40â¬ > 12â° > portion% > someMoney$ > > > or pick a new "unary separator/binder" > > 100'% or 100 '% > 20'$ or 20 '$ > 40'â¬ or 40 'â¬ > 12'â° or 12 'â° > portion'% > someMoney'$ > > > or re-use the existing colon which indicates an argument to the right, > to indicate an argument to the left.... > > 100 :% > 20 :$ > 40 :â¬ > 12 :â° (for promille) > portion :% > someMoney :$ > > which is unambiguous regarding block variable definitions since no > messages are valid in the block variable definition area, > but this may complicate precedence semantics due to its similarity to a > keyword selector, > and would complicate things if the space was missing. > > > > On 18 November 2017 at 04:02, Nicolas Cellier <nicolas.cellier.aka.nice@ > gmail.com> wrote: > > > > 2017-11-17 18:32 GMT+01:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > > Le 17/11/2017 Ã 10:14, Nicolas Cellier a Ã©crit : > > > > 2017-11-17 17:40 GMT+01:00 Gabriel Cotelli <g.cotelli(a)gmail.com <mailto: > g.cotelli(a)gmail.com>>: > > I would really like to see % removed as a binary selector and > available to use in unary or keyword ones. The only implementor in a > Pharo 6 image is: > > % aNumber > > ^ self \\ aNumber > > > +1, such alias has nothing to do in Kernel > > So it's juts aliasing \\ , and % most widespread usage in the real > world is por percentages (the use in modular arithmetic is more a > programming thing that math notation I think). > > And for allowing more Unicode code points for selector names I'm > totally in for Symbols, Arrows, Math Symbols, etc... We just need to > analyse the ones that makes sense as binary selectors, and the ones > allowed for unary and keyword ones. This will allow us to write > pretty cool DSLs. > > Just my opinion. > > This could also be the case for punctuation like ! and ? > > The idea of Torsten is more generic, any combination of binary char could > be used. > From what I understand from https://en.wikipedia.org/wiki/ LR_parser > <https://en.wikipedia.org/wiki/LR_parser> we would just have to scan one > more token ahead for deciding if unary or binary, and could preserve our > simple shift reduce steps... > > > The Smalltalk parsers being handwritten, there wouldn't be shift/reduces > to contend with, and, anyway, the lexer doesn't shift/reduce; it would > simply creates a token up to the next separator (that is goble up the next > space/cr/end of line dot/closing parenthesis/etc...) > > > I don't have academical cursus, so I may be approximate, but the manually > written parsers just have to read a single token ahead so far, and linearly > build the parseNode, to me it was equivalent. > > > So it seems doable for resolving the send. > > > Sort of. The parser difficulty would be this one: > > anObject % print > > > Yes, that's a severe limitation. Context free => it's a binary... Or we > have to use ( ). > But then it's unfriendly to have different rules for unary symbols versus > unary words... > It devaluates the idea... > > > > Is this a binary selector with a print argument or two unary selectors? > > > Less ambiguous... > anObject'% print > anObject '% print > > > > > Using the symbol table when you parse would solve it, but that is > certainly not context free... > > More problematic would be the declaration of method, if we have both a > unary + and a binary +, we will need new syntax for marking the difference. > > > > In most cases, distinguishing between unary + declaration and binary + > declaration would be doable: > > + whatever > > is the start of a binary selector > > + ^ self > > is the start (or the declaration of) an unary selector. > > But writing > > + self > > Can be interpreted as either unary plus doing self, or binary + method > definition... > > > a "unary binder" could distinguish them... > > binary method definition... > + self > > unary method definition... > '+ self > > > > issues... > > + b | c | > > a binary plus with unused temp and implicit ^self, or unary + with binary > | sent to b with unary (c |) parameter etc... > > > + b | c | > binary plus, unused temporary c > > '+ b | c | > unary plus, first | is binary, second | is unary > or maybe it would need to be... '+ b | c'| > > > > So we need a new syntax meaning that there is no parameter, like + ][ or > anything yet unused... > > > without ' > > + || b | c | > empty local variable definition, next | is binary, second | is unary > > also with local variable... > + | lv1 | b | c | > + | lv1 | b | c'| > > > > > > > Whether it's worth or not is another matter... > > > Well, one should probably try to implement the various parsers for that > (extend RB, extend the SmaCC Smalltalk parser, extend the Petit Parser) to > see how much complexity it would bring. > > Coming up with strange interpretations one could do with that syntax can > be helpfull as well. > > Regards, > > Thierry > > On Fri, Nov 17, 2017 at 6:32 AM, Torsten Bergmann <astares(a)gmx.de > <mailto:astares@gmx.de>> wrote: > > Hi, > > just something to think about: one thing I always liked about > Smalltalk is that it allows for nice DSL's. We have nice things > like a unit framework in Pharo, ... > > In the most simple case one can easily implement own units just > by providing a unary messages: > > 1 m > 1 second > 1 px > 1 EUR > > One can easily implement an own Money class with a currency and > then do polymorphic tricks like > > 10 EUR + 20 EUR > > > btw, did the recently announced QA Release Tests add enforcement all > selectors to start with a lowercase? > I felt that one a bit overly-restrictive, which would break such a > currency DSL. > > cheers -ben > > > > But we can currently can not implement special unary selectors > (including special unary selectors with unicode) like: > > 100 % > 20 $ > 40 â¬ > 12 â° (for promille) > > Especially things like 20 % would be nice for layout issues or > other (Bloc comes to mind). > > Maybe we should put that on the roadmap of Pharo because IMHO it > would be cool to support such things in the > future. Dont know how much effort it currently means on the > technical level but maybe others can comment. > > Thx > T. > > > >

1 0

[Pharo 7.0-dev] Build #316: 20735-ComposablePresenter-classowneron-is-missing-the-initialization-call
by ci-pharo-ci-jenkins2＠inria.fr Nov. 22, 2017

Nov. 22, 2017

There is a new Pharo build available! The status of the build #316 was: SUCCESS. The Pull Request #517 was integrated: "20735-ComposablePresenter-classowneron-is-missing-the-initialization-call" Pull request url: https://github.com/pharo-project/pharo/pull/517 Issue Url: https://pharo.fogbugz.com/f/cases/20735 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0