dependency management for projects is *never* an easy task.
who think that the complex on loading project X or Y is because of metacello
simply does not understand the inherent complexity the task it tries to solve
has.
things can be improved, yes… but no matter what tools we create, this will
Hi Camile
On 11 Jun 2015, at 10:47, Camille camille.ter...@gmail.com wrote:
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
Hi,
Did you tried to inspect the PPFailure in the Moose? There is a tab with a
tree structure giving you a pretty good overview, what is going wrong... Or
as an alternative, one can call:
myParser enableDebug parse:myInput
Otherwise, PetitParser really needs some nice error reporting system. I
On 12-06-15 10:24, Esteban Lorenzano wrote:
it was just an example of why using #stable in project dependences is a bad
idea :)
you made #releaseN.N to fix precisely my point.
there should exist something like I say “3.*”
#'release3' always refers to the latest stable 3.*.*.*
I’m sorry for
On 12 Jun 2015, at 09:36, Jan Kurš k...@iam.unibe.ch wrote:
Hi,
Did you tried to inspect the PPFailure in the Moose? There is a tab with a
tree structure giving you a pretty good overview, what is going wrong... Or
as an alternative, one can call:
myParser enableDebug parse:myInput
On 12-06-15 09:34, Esteban Lorenzano wrote:
Project A uses for instance Seaside stable which is, when Project A
starts Seaside 3.0
time after owner tries to load Project A… but since then stable from
Seaside has move from Seaside 3.0, to 3.1.2
Seaside is the one example where we are using
it was just an example of why using #stable in project dependences is a bad
idea :)
you made #releaseN.N to fix precisely my point.
but since this is a convention of Seaside and not a regular practice… who knows
it? (not saying that is wrong, is in fact very good, but there should exist
Branch: refs/heads/5.0
Home: https://github.com/pharo-project/pharo-core
Commit: ddfc63bc91c676059adbcc0f7ff4c7525a152e36
https://github.com/pharo-project/pharo-core/commit/ddfc63bc91c676059adbcc0f7ff4c7525a152e36
Author: Jenkins Build Server bo...@pharo-project.org
Date:
Branch: refs/tags/50107
Home: https://github.com/pharo-project/pharo-core
Hi,
This is a reader for .st and .cs files. Guille did it.
It can
- evaluate for traditional fileIn
- load as Monticello model when falling back to .st file load
(it is actually used by Monticello since last week)
- load as Ring Model
On 12 Jun 2015, at
Branch: refs/heads/5.0
Home: https://github.com/pharo-project/pharo-core
Commit: 15ee0fd1df8e66f0a22de43ebc152ab8b24fe298
https://github.com/pharo-project/pharo-core/commit/15ee0fd1df8e66f0a22de43ebc152ab8b24fe298
Author: Jenkins Build Server bo...@pharo-project.org
Date:
Branch: refs/tags/50108
Home: https://github.com/pharo-project/pharo-core
On 12 Jun 2015, at 10:40, Stephan Eggermont step...@stack.nl wrote:
On 12-06-15 10:24, Esteban Lorenzano wrote:
it was just an example of why using #stable in project dependences is a bad
idea :)
you made #releaseN.N to fix precisely my point.
there should exist something like I say
Branch: refs/tags/50109
Home: https://github.com/pharo-project/pharo-core
Branch: refs/heads/5.0
Home: https://github.com/pharo-project/pharo-core
Commit: fbddd5da6a723df2c0e9c653be19d5c9d12739f5
https://github.com/pharo-project/pharo-core/commit/fbddd5da6a723df2c0e9c653be19d5c9d12739f5
Author: Jenkins Build Server bo...@pharo-project.org
Date:
Just a quick side note:
my initial email was kind of a troll. Because when you ask for
something about roassal and 3D, you get a reply about Roassal-Woden i.e.
Roassal3D is not supported anymore, you have to use Woden instead. Now when you
have to load Woden, you can’t so you have to
On Fri, Jun 12, 2015 at 1:48 PM, Yuriy Tymchuk yuriy.tymc...@me.com wrote:
Just a quick side note:
my initial email was kind of a troll. Because when you ask for
something about roassal and 3D, you get a reply about Roassal-Woden i.e.
Roassal3D is not supported anymore, you have to
Branch: refs/heads/5.0
Home: https://github.com/pharo-project/pharo-core
Commit: 7632a1d68461a54aa62b0166af94b1409a12a50b
https://github.com/pharo-project/pharo-core/commit/7632a1d68461a54aa62b0166af94b1409a12a50b
Author: Jenkins Build Server bo...@pharo-project.org
Date:
Branch: refs/tags/50110
Home: https://github.com/pharo-project/pharo-core
Branch: refs/heads/5.0
Home: https://github.com/pharo-project/pharo-core
Commit: 823b806724cad9c9800bdf2b44db968be52b44cc
https://github.com/pharo-project/pharo-core/commit/823b806724cad9c9800bdf2b44db968be52b44cc
Author: Jenkins Build Server bo...@pharo-project.org
Date:
Branch: refs/tags/50111
Home: https://github.com/pharo-project/pharo-core
Hi,
for tracing and logging one could easily write:
foo
...
Log enabled ifTrue: [ do some tracing here ].
...
but this always requires some message sends/checks if the debug mode is active.
This is OK while debugging/tracing to find errors - but for runtime one whishes
to have the
best
12986 Increase speed of accessing sourceCode
https://pharo.fogbugz.com/f/cases/12986
Wow! Searching through sources using Finder in latest Pharo 5 is now
super fast ... a good candidate for a backport to Pharo 4 (if possible).
Thanks Camillo!
Bye
T.
EstebanLM wrote
In any case this is Pharo 5 super-alpha… so there is no need to keep
things going until we replace them :)
IMHO it's not too much to ask to keep the old tool *at least* until the
release when we've have time to adapt and have these discussions. If we
removed it because we want
Hi Thierry,
On Jun 11, 2015, at 8:16 AM, Thierry Goubier thierry.goub...@gmail.com wrote:
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
On Fri, Jun 12, 2015 at 9:40 PM, Franck Warlouzet
franck.warlou...@hotmail.fr wrote:
Hello,
I really would like to have a shortcut to Halt enableHaltOnce. What could
be a good combinaison ? I thought about cmd e, h (for Enable Halt) but I do
not know if it is already taken.
What do you
EstebanLM wrote
Which other functionality you think we should add?
Browse configuration class from context menu when present
-
Cheers,
Sean
I just added this in Tool-Catalog-TorstenBergmann.14
(allow to browse the config class when loaded similar to what Config browser
had).
Will
On Sat, Jun 13, 2015 at 5:49 AM, Torsten Bergmann asta...@gmx.de wrote:
Hi,
for tracing and logging one could easily write:
foo
...
Log enabled ifTrue: [ do some tracing here ].
...
but this always requires some message sends/checks if the debug mode is
active.
This is OK while
Hi Torsten,
On Jun 12, 2015, at 2:49 PM, Torsten Bergmann asta...@gmx.de wrote:
Hi,
for tracing and logging one could easily write:
foo
...
Log enabled ifTrue: [ do some tracing here ].
...
but this always requires some message sends/checks if the debug mode is
active.
This
Torsten Bergmann wrote
I just added this in Tool-Catalog-TorstenBergmann.14
Thanks :)
-
Cheers,
Sean
--
View this message in context:
http://forum.world.st/New-Tool-Catalog-Browser-in-Pharo-5-0-tp4831575p4832176.html
Sent from the Pharo Smalltalk Developers mailing list archive at
EstebanLM wrote
Which other functionality you think we should add?
Browse configuration class from context menu when present
-
Cheers,
Sean
--
View this message in context:
http://forum.world.st/New-Tool-Catalog-Browser-in-Pharo-5-0-tp4831575p4832172.html
Sent from the Pharo Smalltalk
Loading via catalog browser gives: 'This package depends on the following
classes: GRDelegatingStream You must resolve these dependencies before...
Any idea what we should do?
-
Cheers,
Sean
--
View this message in context:
http://forum.world.st/Magritte3-in-Pharo-5-0-tp4832177.html
Esteban wrote:
But is a superset.
We do not want to keep two tools with same functionality (we already did this a lot in the past, but we are like alcoholics in recovery now :P
Hi Esteban,
you removed the Config Browser in Pharo5.0Latest update: #50111 much too early.
As I stated in the
Branch: refs/heads/5.0
Home: https://github.com/pharo-project/pharo-core
Commit: 7b783bc7f66015b84528dd395e780e7b8b19e4da
https://github.com/pharo-project/pharo-core/commit/7b783bc7f66015b84528dd395e780e7b8b19e4da
Author: Jenkins Build Server bo...@pharo-project.org
Date:
Branch: refs/tags/50112
Home: https://github.com/pharo-project/pharo-core
Hello,
I really would like to have a shortcut to Halt enableHaltOnce. What could be
a good combinaison ? I thought about cmd e, h (for Enable Halt) but I do not
know if it is already taken.
What do you think about it ?
Cheers,
Franck
I think that use case it too specific to add that for everybody.
But it would be nice if this was a one liner that you could add to your
personal settings (I mean, binding a global shortcut to a block doing what you
want).
My 2c
On 12 Jun 2015, at 15:40, Franck Warlouzet
On Fri, Jun 12, 2015 at 4:43 PM, Sven Van Caekenberghe s...@stfx.eu wrote:
I mean, binding a global shortcut to a block doing what you want).
It would have to be context-aware, but that sounds like a very interesting
idea.
Hi Henrik
I was under the impression the plan was to standardize on Ring as the meta
model to use; to replace ChangeRecord / MCDefinition.
We do not know if ring is for replacing changeRecord. I'm not sure that
we can.
Ring is to have a representation of a program not the file
representation
Thanks!!!
Le 11/6/15 08:55, Torsten Bergmann a écrit :
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
In two words, It's an extraction of FileStreamnextChunk, to avoid
bloating the code in file stream with unrelated concerns.
El vie., 12 de jun. de 2015 a la(s) 10:14 a. m., Marcus Denker
marcus.den...@inria.fr escribió:
Hi,
This is a reader for .st and .cs files. Guille did it.
It can
Hi,
I’m sorry I didn’t see that functionality.
In any case this is Pharo 5 super-alpha… so there is no need to keep things
going until we replace them :)
Is also a good moment to reflect about how to implement things missing.
In case of add own repositories, I’m not sure anyone used it… but
On 06/12/2015 01:24 AM, Esteban Lorenzano wrote:
it was just an example of why using #stable in project dependences is a bad
idea :)
you made #releaseN.N to fix precisely my point.
but since this is a convention of Seaside and not a regular practice… who knows
it? (not saying that is wrong,
I was under the impression the plan was to standardize on Ring as the meta
model to use; to replace ChangeRecord / MCDefinition.
However, after Ring as added to the image in 2011, no further work as been done
to actually replace the ChangeRecord / MCDefinition use though, and I recently
ran
44 matches
Mail list logo
