Magritte-Model changes .455, .456
by stephan
I'm not sure the replacement of
visitNumberDescription: aDescription
| contents |
contents := self contents.
contents isEmpty
ifTrue: [ MAReadError signal ].
(contents occurrencesOf: $-) > 1
ifTrue: [ MAReadError signal ].
(contents indexOf: $-) > 1
ifTrue: [ MAReadError signal ].
(contents occurrencesOf: $.) > 1
ifTrue: [ MAReadError signal ].
(contents allSatisfy: [ :each | '+-0123456789.eE' includes: each ])
ifFalse: [ MAReadError signal ].
super visitNumberDescription: aDescription
by
visitNumberDescription: aDescription
| isContentsValid |
isContentsValid := NumberParser isNumber: self contents.
isContentsValid ifFalse: [ MAReadError signal ].
super visitNumberDescription: aDescription
works cross-platform.
There are two 455s, and 456 misses changes from both.
Merged in 457
Stephan
8 years, 7 months
Re: [Pharo-users] [Esug-list] [ANN] Pharo 4.0 is released!
by Mariano Martinez Peck
Super good news! thank you all!
On Thu, Apr 16, 2015 at 1:08 PM, Richard Wettel <wettel(a)gmail.com> wrote:
> Great! And thank you all!
> Ricky
>
> —
> Sent from Mailbox <https://www.dropbox.com/mailbox>
>
>
> On Thu, Apr 16, 2015 at 5:24 PM, Serge Stinckwich <
> serge.stinckwich(a)gmail.com> wrote:
>
>> Thank you all !
>>
>> On Thu, Apr 16, 2015 at 11:29 AM, Esteban Lorenzano <estebanlm(a)gmail.com>
>> wrote:
>>
>>> Please spread widely.
>>> Sorry for multiple posts.
>>>
>>> (this post can be see here: http://pharo.org/news/pharo-4.0-released)
>>>
>>> Dear World,
>>>
>>> Pharo 4.0 (http://www.pharo.org) is here.
>>>
>>> Pharo is a pure object-oriented programming language and a powerful
>>> environment, focused on simplicity and immediate feedback.
>>>
>>> Many things have changed in Pharo. Here are some highlights:
>>> - Inspector/Playground/Spotter are new moldable development tools for
>>> inspecting, coding and searching objects.
>>> - Slots model instance variables as first class entities and enable
>>> meta-programming on this level.
>>> - ShoreLine reporter introduces a way to report system errors and
>>> collect statistics, that we will use for future improvements
>>> - Dark theme.
>>>
>>> These are just the more prominent highlights, but the details are just
>>> as important. We have closed 1697 issues in Pharo 4. Take a moment to go
>>> through a more detailed recount of the progress:
>>>
>>>
>>> https://github.com/pharo-project/ChangeLogs/blob/master/Pharo40ChangeLogs.md
>>>
>>> Pharo is improving on many fronts, but one of the most prominent changes
>>> is the addition of moldable tools for inspection and search. These tools
>>> provide extension mechanisms that allow every object to define ways in
>>> which it can be understood effectively. To provide an idea of the impact of
>>> the already existing extensions, the map below shows the Pharo classes
>>> grouped in packages, highlighting in red those parts of the system that
>>> have at least one such custom view coming with the main distribution. The
>>> spread of these extensions shows that moldability is powerful mechanism
>>> that can be used in many contexts.
>>>
>>>
>>> Remember that Pharo is your platform. We thank all the contributors of
>>> this release:
>>>
>>> Clara Allende, Jean-Baptiste Arnaud, Jean-Christophe Bach, Philippe
>>> Back, Clement Bera, Alexandre Bergel, Torsten Bergmann, Vincent Blondeau,
>>> Noury Bouraqadi, Santiago Bragagnolo, Johan Brichau, Sven Van Caekenberghe,
>>> Damien Cassou, Nicolas Cellier, Guido Chari, Dimitris Chloupis, Andrei
>>> Chis, Ben Coman, Bernardo Contreras, Tommaso Dal Sasso, Jan Van De Sandt,
>>> Christophe Demarey, Sean DeNigris, Marcus Denker, Martin Dias, Stephane
>>> Ducasse, Stephan Eggermont, Luc Fabresse, Johan Fabry, Hilaire Fernandes,
>>> Jerome Garcia, Tudor Girba, Thierry Goubier, Jigyasa Grover, Kris Gybels,
>>> Norbert Hartl, Dale Henrichs, Pablo Herrero, Nicolai Hess, Pavel Krivanek,
>>> Juraj Kubelka, Jan Kurs, Laurent Laffont, Jannik Laval, Kevin Lanvin, Max
>>> Leske, David Lewis, Diego Lont, Esteban Lorenzano, Tim Mackinnon, Attila
>>> Magyar, Esteban Maringolo, Stefan Marr, Max Mattone, Martin Mc Clure, Eliot
>>> Miranda, Alain Plantec, Guillermo Polito, Damien Pollet, Stefan Reichhart,
>>> Mark Rizun, Udo Schneider, Ignacio Sniechowski, Henrik Sperre Johansen,
>>> Igor Stasenko, Aliaksei Syrel, Ciprian Teodorov, Camille Teruel, Sebastian
>>> Tleye, Yuriy Tymchuk, Peter Uhnak, Andres Valloud, Sven Van Caekenberghe,
>>> Thomas Vincent, Jan Vrany, Martin Walk, Richard Wettel, Dmitri Zagidulin
>>>
>>> And all those who contributed indirectly, by reporting bugs,
>>> participating in discussion threads, providing feedback...
>>>
>>> Pharo 4.0 is another big step. And, the best is yet to come.
>>>
>>> Enjoy!
>>> The Pharo Team
>>>
>>>
>>> _______________________________________________
>>> Esug-list mailing list
>>> Esug-list(a)lists.esug.org
>>> http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org
>>>
>>>
>>
>>
>> --
>> Serge Stinckwich
>> UCBN & UMI UMMISCO 209 (IRD/UPMC)
>> Every DSL ends up being Smalltalk
>> http://www.doesnotunderstand.org/
>>
>
>
--
Mariano
http://marianopeck.wordpress.com
8 years, 7 months
[ANN] Pharo 4.0 is released!
by Esteban Lorenzano
Please spread widely.
Sorry for multiple posts.
(this post can be see here: http://pharo.org/news/pharo-4.0-released <http://pharo.org/news/pharo-4.0-released>)
Dear World,
Pharo 4.0 (http://www.pharo.org) is here.
Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback.
Many things have changed in Pharo. Here are some highlights:
- Inspector/Playground/Spotter are new moldable development tools for inspecting, coding and searching objects.
- Slots model instance variables as first class entities and enable meta-programming on this level.
- ShoreLine reporter introduces a way to report system errors and collect statistics, that we will use for future improvements
- Dark theme.
These are just the more prominent highlights, but the details are just as important. We have closed 1697 issues in Pharo 4. Take a moment to go through a more detailed recount of the progress:
https://github.com/pharo-project/ChangeLogs/blob/master/Pharo40ChangeLogs.md
Pharo is improving on many fronts, but one of the most prominent changes is the addition of moldable tools for inspection and search. These tools provide extension mechanisms that allow every object to define ways in which it can be understood effectively. To provide an idea of the impact of the already existing extensions, the map below shows the Pharo classes grouped in packages, highlighting in red those parts of the system that have at least one such custom view coming with the main distribution. The spread of these extensions shows that moldability is powerful mechanism that can be used in many contexts.
Remember that Pharo is your platform. We thank all the contributors of this release:
Clara Allende, Jean-Baptiste Arnaud, Jean-Christophe Bach, Philippe Back, Clement Bera, Alexandre Bergel, Torsten Bergmann, Vincent Blondeau, Noury Bouraqadi, Santiago Bragagnolo, Johan Brichau, Sven Van Caekenberghe, Damien Cassou, Nicolas Cellier, Guido Chari, Dimitris Chloupis, Andrei Chis, Ben Coman, Bernardo Contreras, Tommaso Dal Sasso, Jan Van De Sandt, Christophe Demarey, Sean DeNigris, Marcus Denker, Martin Dias, Stephane Ducasse, Stephan Eggermont, Luc Fabresse, Johan Fabry, Hilaire Fernandes, Jerome Garcia, Tudor Girba, Thierry Goubier, Jigyasa Grover, Kris Gybels, Norbert Hartl, Dale Henrichs, Pablo Herrero, Nicolai Hess, Pavel Krivanek, Juraj Kubelka, Jan Kurs, Laurent Laffont, Jannik Laval, Kevin Lanvin, Max Leske, David Lewis, Diego Lont, Esteban Lorenzano, Tim Mackinnon, Attila Magyar, Esteban Maringolo, Stefan Marr, Max Mattone, Martin Mc Clure, Eliot Miranda, Alain Plantec, Guillermo Polito, Damien Pollet, Stefan Reichhart, Mark Rizun, Udo Schneider, Ignacio Sniechowski, Henrik Sperre Johansen, Igor Stasenko, Aliaksei Syrel, Ciprian Teodorov, Camille Teruel, Sebastian Tleye, Yuriy Tymchuk, Peter Uhnak, Andres Valloud, Sven Van Caekenberghe, Thomas Vincent, Jan Vrany, Martin Walk, Richard Wettel, Dmitri Zagidulin
And all those who contributed indirectly, by reporting bugs, participating in discussion threads, providing feedback...
Pharo 4.0 is another big step. And, the best is yet to come.
Enjoy!
The Pharo Team
8 years, 7 months
Pillar package dependency
by Johan Brichau
Hi all,
Can someone give me access to the Pillar repository or fix the issue below?
I was trying to play around with Pier3 (which uses Pillar) but immediately hit an issue. When loading:
Metacello new
configuration: 'Pier3';
version: #'release3.1';
load.
And then opening localhost:8080 pier gives you a DNU on MacOSXPlatform>>pillarLineEnding
The issue is that the code of Pillar-Model (which is loaded by Pier) is dependent on Pillar-ExporterCore (which contains the method above).
I think two things need to be done:
- move the #pillarLineEnding method to the Pillar-Model
- move the #pillarLineEnding method from Platform class to GRPlatform class to ease porting to other Smalltalks
thanks
Johan
8 years, 7 months
Issue Tracker
by Sean P. DeNigris
Now that Google Code is shutting down, what shall be done about Magritte's
issue tracker? The standard move seems to be to export to GitHub, a painless
process I just undertook for a personal project.
-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Issue-Tracker-tp4814743.html
Sent from the Magritte, Pier and Related Tools mailing list archive at Nabble.com.
8 years, 7 months
Version 3.3
by Sean P. DeNigris
Committed to stHub/Magritte3 & MetaRepoForPharo40:
- New version 3.3 (semantic minor version bump for added functionality). For
pharo4.x, add Magritte-GT package and add it to the default group.
- Declare 3.3 as stable
- Declare 3.3 baseline as development
-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Version-3-3-tp4817750.html
Sent from the Magritte, Pier and Related Tools mailing list archive at Nabble.com.
8 years, 8 months
