2015-06-03 15:46 GMT+02:00 Thierry Goubier thierry.goub...@gmail.com:
2015-06-03 15:09 GMT+02:00 Nicolai Hess nicolaih...@web.de:
self versionFromFileNamed: fileName
is called after it isn't found in the MCCacheRepository
and if it is not found in its own special repository cache , it is
which build?
On Fri, Jun 5, 2015 at 3:48 AM, stepharo steph...@free.fr wrote:
015-06-04 21:47:19.836 Pharo[12527:507] Critical failure: the LastResort
font is unavailable.
On 06/04/2015 12:38 PM, stepharo wrote:
I passed the info to martin mcClure.
May be he will have a look at the issue.
Well, I can reproduce the problem, in Windows. In Linux, my usual
platform, the image does not hang. This suggests that the problem might
be in the Windows VM. Is there a way to
On 06/04/2015 03:35 PM, Martin McClure wrote:
On 06/04/2015 12:38 PM, stepharo wrote:
I passed the info to martin mcClure.
May be he will have a look at the issue.
Well, I can reproduce the problem, in Windows. In Linux, my usual
platform, the image does not hang. This suggests that the
Dear Colleagues and Friends,
We are happy to announce we will organize a CampSmalltalk about the Roassal
visualization engine, on _Sunday 12 July_.
As far as we have seen, the interests are multiple. Here is a list of topics we
will happy to work on:
- Port of Roassal on VisualWorks
Branch: refs/tags/50090
Home: https://github.com/pharo-project/pharo-core
Branch: refs/heads/5.0
Home: https://github.com/pharo-project/pharo-core
Commit: 5598672cd218b1c4355b8ddcdcc60de00804d68b
https://github.com/pharo-project/pharo-core/commit/5598672cd218b1c4355b8ddcdcc60de00804d68b
Author: Jenkins Build Server bo...@pharo-project.org
Date:
Hi Alex,
is it possible to add some discussion about stuff we did in roassal for
dynacase to the list?
Because I feel there is some duplication effort and also we could probably
contribute some stuff we did back. Or perhaps even more general discussion
about using roassal for more dynamic and
015-06-04 21:47:19.836 Pharo[12527:507] Critical failure: the LastResort
font is unavailable.
stepharo wrote
Remember Coral is not about forcing us to edit in vim, but to have a
living scripts that
we be debugged and published as dead files or zombified on demand.
That sounds reeeally interesting! I never understood that before. I heard
that Coral was obsolete because the important
Is Coral using the Opal compiler for its syntax extensions?
it extends petitParser.
Now the challenges of Coral are not in the syntax. But
How can we call system call, how can we manipule OS variable.
How can we edit a script and debug it inside the image and publish it
as a dead file.
Branch: refs/tags/50089
Home: https://github.com/pharo-project/pharo-core
Branch: refs/heads/5.0
Home: https://github.com/pharo-project/pharo-core
Commit: fa14d3f02027756039604eee9c0fd9dc64a02a66
https://github.com/pharo-project/pharo-core/commit/fa14d3f02027756039604eee9c0fd9dc64a02a66
Author: Jenkins Build Server bo...@pharo-project.org
Date:
Le 3 juin 2015 à 22:51, Sean P. DeNigris a écrit :
demarey wrote
I find very strange to have packages of a project in different
repositories. When I saw this kind of things, it was in configurations
using packages from another project without declaring this external
project in the config...
Le 04/06/2015 20:57, stepharo a écrit :
I think that this kind of code should break
when category = packageName+tag and packageName = packageName
ofPackageNamed: aPackageName
| builder |
builder := self new.
self allManifestClasses
detect: [ :each | each category =
I passed the info to martin mcClure.
May be he will have a look at the issue.
Le 2/6/15 00:12, Nicolai Hess a écrit :
2015-06-01 23:44 GMT+02:00 Craig Johnson cr...@hivemind.net
mailto:cr...@hivemind.net:
Sure thing.
To see the bug, file the code below into a clean image and run
But why this is so complex?
Why I cannot have
#ref Object?
or something like that.
And why do we need #ref and not
#r
#m
#s
?
we could have
#p
#c
I'm a super user and I want super user tools :)
Stef
Le 3/6/15 01:20, Tudor Girba a écrit :
Hi,
But, that is already
On 04 Jun 2015, at 10:07, Aliaksei Syrel alex.sy...@gmail.com wrote:
Juhu, thanks Doru! :)
Congratulations, Moose!
+100
Cheers,
Alex
On Jun 4, 2015 9:17 AM, Tudor Girba tu...@tudorgirba.com wrote:
We are happy to announce version 5.1 of the Moose Suite:
Well done! Looking forward to the enjoyment of using it. :)
Peter
On Thu, Jun 4, 2015 at 10:23 AM, Sven Van Caekenberghe s...@stfx.eu wrote:
On 04 Jun 2015, at 10:07, Aliaksei Syrel alex.sy...@gmail.com wrote:
Juhu, thanks Doru! :)
Congratulations, Moose!
+100
Cheers,
Alex
Hi Stef,
What you are proposing is interesting.
The criteria for the current language is to be minimalistic and composable
because it is supposed to work with any object, not just with code, and the
speed should be as good as possible in all cases.
At this point, # means filter the existing
Sven Van Caekenberghe-2 wrote
On 04 Jun 2015, at 10:07, Aliaksei Syrel lt;
alex.syrel@
gt; wrote:
Juhu, thanks Doru! :)
Congratulations, Moose!
+100
Yes!!!
-
Cheers,
Sean
--
View this message in context:
http://forum.world.st/ann-moose-5-1-tp4830357p4830385.html
Sent from
Tudor Girba-2 wrote
Indeed. We already had a similar discussion in the context of XMLParser.
The current idea is to package GT extensions directly in the project, and
not in GT.
That sound's good. I want to have Magritte load this by default in Pharo
4.0, but I guess the only way is to
Impressive!!!
Wonderful team!
Alexande
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Jun 4, 2015, at 4:17 AM, Tudor Girba tu...@tudorgirba.com wrote:
We are happy to announce version 5.1
Branch: refs/tags/50088
Home: https://github.com/pharo-project/pharo-core
Branch: refs/heads/5.0
Home: https://github.com/pharo-project/pharo-core
Commit: 26e83faea0cb84a5be0469a11555fbe0d185011b
https://github.com/pharo-project/pharo-core/commit/26e83faea0cb84a5be0469a11555fbe0d185011b
Author: Jenkins Build Server bo...@pharo-project.org
Date:
25 matches
Mail list logo
