+1
On Jun 12, 2015, at 9:36 AM, Peter Uhnák i.uh...@gmail.com wrote:
As a sidenote (and since Yuriy mentioned Roassal), we would like to address
the versioning (and release management) of roassal at ESUG (Camp Roassal)
since Roassal was being developed really fast and it was hard to keep
Thanks mathieu.
I do not know.
May be the repl that guillermo is building is the solution.
Stef
Le 13/6/15 19:29, Matthieu Lacaton a écrit :
Isn't it*userInput := UIManager default request: 'Enter whatever you
want'* ?
2015-06-13 19:00 GMT+02:00 stepharo steph...@free.fr
Hi Javier,
First of all, RTGrapherBuilder has been obsoleted. Use RTGrapher instead.
I guess this is a problem with rounding with RTGrapherBuilder. With RTGrapher,
I do not see this behavior.
For example:
-=-=-=-=-=-=-=-=-=-=-=-=
events := { 10.0 @ 1.0. 9.0 @ 2.0. 8.0 @ 3.0.
Le 8/6/15 11:37, mikefilonov a écrit :
I think it is a good idea to get Pharo at Bitnami as it will increase the
visibility of the project to the world and put us to the rightful place
alongside with other platforms like Python, Ruby and other :) Moreover it
opens new clouds like Azure, Google
Ok how do we proceed?
The first one is a product disguised as an open-source software (yeh it
is open-source like C# I guess).
Do we want to spend energy to advertise bitnami?
We could try just to see how many voters we could get?
Stef
Le 7/6/15 13:08, stepharo a écrit :
Hi pharoers
we got
Le 10/6/15 20:39, Sven Van Caekenberghe a écrit :
On 10 Jun 2015, at 15:13, stepharo steph...@free.fr wrote:
This is in the entreprise book. I added a subsection on comments.
May be I committed but forgot to push.
Now I did it.
And now I see it.
I made a small change.
super!
Stef
Le
Le 14/06/2015 18:39, Holger Freyther a écrit :
On 13 Jun 2015, at 14:39, Clément Bera bera.clem...@gmail.com wrote:
Dear Clement,
This is an interesting problem. There is currently no simple way of executing a
message at compile-time instead of at runtime in Pharo, which is useful to
Alexandre
why don't you communicate it well in the code.
This is really easy to deprecate the new method, put the class in a
different package.
We will not use Roassal anymore in our open-devs lectures just because
we literally burnt a poor
student that was systematically bumping into
On 13 Jun 2015, at 14:39, Clément Bera bera.clem...@gmail.com wrote:
Dear Clement,
This is an interesting problem. There is currently no simple way of executing
a message at compile-time instead of at runtime in Pharo, which is useful to
have settings but no runtime overhead.
I did a
Since I've already run into second thing in agile visualization book that
is outdated (RTArrow, which was some time ago renamed to RTArrowedLine (
https://dl.dropboxusercontent.com/u/31543901/AgileVisualization/Roassal/0104-Roassal.html
section 2.2) it made me wonder how many things like these are
On Mon, Jun 15, 2015 at 2:34 AM, Thierry Goubier
thierry.goub...@gmail.com wrote:
Le 14/06/2015 18:39, Holger Freyther a écrit :
On 13 Jun 2015, at 14:39, Clément Bera bera.clem...@gmail.com wrote:
Dear Clement,
This is an interesting problem. There is currently no simple way of
The class has been removed some times ago… There is not much I can do if people
do not update….
Alexandre
On Jun 14, 2015, at 3:42 PM, stepharo steph...@free.fr wrote:
Alexandre
why don't you communicate it well in the code.
This is really easy to deprecate the new method, put the
Hi! We're sending this automatic email twice a month, to give the community an
opportunity to easily know what's happening and to coordinate efforts. Just
answer informally, and feel free to spawn discussions thereafter!
### Here's what I've been up to since the last WhatsUp:
-
Hi Ben,
Le 15/06/2015 01:09, Ben Coman a écrit :
On Mon, Jun 15, 2015 at 2:34 AM, Thierry Goubier
thierry.goub...@gmail.com wrote:
Le 14/06/2015 18:39, Holger Freyther a écrit :
On 13 Jun 2015, at 14:39, Clément Bera bera.clem...@gmail.com wrote:
Dear Clement,
This is an interesting
14 matches
Mail list logo
