On 11 Jun 2015, at 09:30, Jan Kurš k...@iam.unibe.ch wrote:
That sounds really cool and useful extension.
Thank you Jan!
Regarding the furthest failure, the core of the problem is the distinction
between an error and a failure. Error reports on a problem in the input,
while failure is
Esteban wrote:
If you want to contribute just tell Esteban so he can add you to the
project.
well no… I just made it public access, so anyone can commit changes there… :)
(And I will move it to PharoExtras team soon, that’s the correct place once
integrated in image… but well… time is
Branch: refs/heads/5.0
Home: https://github.com/pharo-project/pharo-core
Commit: eadef90589fff2e2b12c6773b0a0acc98cf97b08
https://github.com/pharo-project/pharo-core/commit/eadef90589fff2e2b12c6773b0a0acc98cf97b08
Author: Jenkins Build Server bo...@pharo-project.org
Date:
Branch: refs/tags/50105
Home: https://github.com/pharo-project/pharo-core
Hi,
On 11 Jun 2015, at 08:55, Torsten Bergmann asta...@gmx.de wrote:
Hi,
maybe you already noticed. The latest update for Pharo 5 which is 50103 (see
[1]).
includes a new tool called Catalog Browser.
Where to go
===
You will find it under Tools - Catalog Browser and it
On Thu, Jun 11, 2015 at 2:55 PM, Torsten Bergmann asta...@gmx.de wrote:
Hi,
maybe you already noticed. The latest update for Pharo 5 which is 50103 (see
[1]).
includes a new tool called Catalog Browser.
Where to go
===
You will find it under Tools - Catalog Browser and it will
On 11/06/15 07:52, Yuriy Tymchuk wrote:
Once Stef mentioned that there is some project for dependency checking. What
was it? Maybe we can use that?
What I've done is get all latest versions out of smalltalkhub and
collect the signatures that are used. That can provide upper and lower
limits
The 'fix' for Pharo40 is in the Pharo40Inbox as Slice-14387.
It formats code on accept and/or display using the RBConfigurableFormatter.
Marcus Denker-4 wrote
On 11 Jun 2015, at 08:16, Peter Uhnák lt;
i.uhnak@
gt; wrote:
If my understanding of Pharo's release management is correct,
On Thu, Jun 11, 2015 at 2:29 AM, Max Leske maxle...@gmail.com wrote:
On 10 Jun 2015, at 17:13, Martin Dias tinchod...@gmail.com wrote:
Hi everybody,
I'm writing you to discuss about a new feature for Pharo. I would like to
know your opinions and ideas. Thanks in advance.
My point is that
Branch: refs/tags/50106
Home: https://github.com/pharo-project/pharo-core
Thanks, I will have a look.
On 11 Jun 2015, at 16:39, Paul DeBruicker pdebr...@gmail.com wrote:
The 'fix' for Pharo40 is in the Pharo40Inbox as Slice-14387.
It formats code on accept and/or display using the RBConfigurableFormatter.
Marcus Denker-4 wrote
On 11 Jun 2015, at 08:16,
On Thu, Jun 11, 2015 at 11:11 PM, Esteban Lorenzano esteba...@gmail.com wrote:
On 11 Jun 2015, at 16:42, Ben Coman b...@openinworld.com wrote:
On Thu, Jun 11, 2015 at 2:55 PM, Torsten Bergmann asta...@gmx.de wrote:
Hi,
maybe you already noticed. The latest update for Pharo 5 which is 50103
Branch: refs/heads/5.0
Home: https://github.com/pharo-project/pharo-core
Commit: cdf1593f415e3d68410dc04b992fb195615bceeb
https://github.com/pharo-project/pharo-core/commit/cdf1593f415e3d68410dc04b992fb195615bceeb
Author: Jenkins Build Server bo...@pharo-project.org
Date:
Hello Javier,
I copied the packages to Vivid, can you try again? Please also install
pharo-sources
Best regards,
Markus
Am 11.06.2015 um 15:54 schrieb Javier Pimás:
Hi there, after adding the ppa to the system I cannot install the vm.
Only pharo-launcher is available but it can't be
Thanks! I now installs just fine, and everything works correctly after also
installing pharo-source-files
On Thu, Jun 11, 2015 at 4:08 PM, Markus Fritsche mfrits...@reauktion.de
wrote:
Hello Javier,
I copied the packages to Vivid, can you try again? Please also install
pharo-sources
Best
@Max: I watched the presentation but I'm not sure how to apply it in this
case. (Last exam!? good!)
@Ben: I agree that there are not only 2 levels, high-level and low-level
announcements but a hierarchy. For example, a MCVersionLoad could have a
MetacelloProjectLoad as a parent.
@Chris (and
Hi there, after adding the ppa to the system I cannot install the vm. Only
pharo-launcher is available but it can't be installed because the
pharo-vm-core-i386 is not installable.
What I tried was this:
sudo apt-add-repository ppa:pharo/stable
sudo dpkg --add-architecture i386
sudo apt-get
Hi Martin,
I believe your job example express better what you need, so what I would
propose would be a notion of parent in the normal code announcements,
containing, in a hierarchical way, the higher level context information.
But implementing that parent in the announcements will be difficult,
That sounds really cool and useful extension.
Regarding the furthest failure, the core of the problem is the distinction
between an error and a failure. Error reports on a problem in the input,
while failure is information for choice parser combinator. In general, the
furthest failure is a better
On 10 Jun 2015, at 20:31, Richard Sargent
richard.sarg...@gemtalksystems.com wrote:
camille teruel wrote
On 10 Jun 2015, at 19:11, Chris Cunningham lt;
cunningham.cb@
gt; wrote:
Inteteresting
On Wed, Jun 10, 2015 at 9:36 AM, Camille lt;
camille.teruel@
lt;mailto:
Date: Thu, 11 Jun 2015 08:35:10 +0200
From: steph...@free.fr
To: pharo-dev@lists.pharo.org
Subject: Re: [Pharo-dev] Pharo 4, format on accept/display
Le 10/6/15 20:47, Paul DeBruicker a écrit :
Hi
I've hacked together an implementation of format on accept display.
I know
Really cool!
About the spotter integration, it is really nice to be able to search and
find new projects like this. Well done.
But, there are two things that I would change:
- Right now, the processor order is 10. If you search for GTSpotter, you
will get the catalog project before the class:
On 11 Jun 2015, at 08:16, Peter Uhnák i.uh...@gmail.com wrote:
If my understanding of Pharo's release management is correct, then no new
features are added after a release, only bugfixes.
Yes, but we do make exceptions…
e.g. I added format on display and accept to Pharo3 after the
If my understanding of Pharo's release management is correct, then no new
features are added after a release, only bugfixes.
So from this perspective I would suggest to publish it to Pharo50Inbox
instead, including creating a new issue in Pharo bugtracker where you
describe what is it changing.
Le 10/6/15 20:47, Paul DeBruicker a écrit :
Hi
I've hacked together an implementation of format on accept display.
I know someone is redoing that functionality to better suit future needs.
Should I publish what I've got as a slice to the Pharo40Inbox for people to use
that may miss it
Hi,
maybe you already noticed. The latest update for Pharo 5 which is 50103 (see
[1]).
includes a new tool called Catalog Browser.
Where to go
===
You will find it under Tools - Catalog Browser and it will display the
configs together with the catalog metadata like project
On Jun 11, 2015, at 2:47 AM, Camille camille.ter...@gmail.com wrote:
But furthest failure gives wrong messages in other cases to.
Consider this sequence parser:
keyword := #letter asParser plus , $: asParser.
keyword parse: ‘foo'
This returns 'letter expected at 3’, but no matter how
Absence of Metacello won't help you dealing with dependencies
and loading stuff by using hand-made scripts by dozens of people
written at different points in time and not maintained by anyone.
It may be too complicated to use, especially at earlier stages of
development,
and in situations, when
Format on display does horrible things to the Playground for the version I
uploaded yesterday. A new version is in the inbox that does not do them.
Marcus Denker-4 wrote
Thanks, I will have a look.
On 11 Jun 2015, at 16:39, Paul DeBruicker lt;
pdebruic@
gt; wrote:
The 'fix'
Hi!
I cannot figure out what this package is about. Looks like a kind of change set?
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Le 11 juin 2015 à 07:52, Yuriy Tymchuk a écrit :
Once Stef mentioned that there is some project for dependency checking. What
was it? Maybe we can use that?
http://smalltalkhub.com/#!/~PharoExtras/Tool-DependencyAnalyser
But take care, it only spots static dependencies (inheritance,
Branch: refs/heads/5.0
Home: https://github.com/pharo-project/pharo-core
Commit: 8d0d4b83a51fc2534b07dc6a7b56038f792cc62f
https://github.com/pharo-project/pharo-core/commit/8d0d4b83a51fc2534b07dc6a7b56038f792cc62f
Author: Jenkins Build Server bo...@pharo-project.org
Date:
Branch: refs/tags/50104
Home: https://github.com/pharo-project/pharo-core
On 11 Jun 2015, at 16:42, Ben Coman b...@openinworld.com wrote:
On Thu, Jun 11, 2015 at 2:55 PM, Torsten Bergmann asta...@gmx.de
mailto:asta...@gmx.de wrote:
Hi,
maybe you already noticed. The latest update for Pharo 5 which is 50103 (see
[1]).
includes a new tool called Catalog
2015-06-11 16:49 GMT+02:00 Ben Coman b...@openinworld.com:
Just a *very* divergent thought that I'm not sure is a good idea...
maybe the parent announcement could hold the announcer of its
children.
The problem is then that all tools which are not interested in the parent
announcement
35 matches
Mail list logo
