Hi Kilon,
You error is strange. I use Versionner on Pharo 4.0 without any problem.
If I take a closer look at the stack trace, the error comes from the
MetacelloToolBox when Versionner asks for configuration classes.
What is really strange is that after this message sent, the stack shows the
Well to kepp you updated , because I did not bother replying to my own
thread since none seemed to care or have the same issue as me. I tried on
windows again same error as macos on a fresh image by the way. So I know it
must not be me.
But now with a latest Pharo 4 image i get no errors in both
Le 19 sept. 2014 à 11:21, kilon alios a écrit :
Well to kepp you updated , because I did not bother replying to my own thread
since none seemed to care or have the same issue as me.
I was out of office last days ...
I tried on windows again same error as macos on a fresh image by the way.
just for the record I have not created any kind of configuration in
Ephestos. The code that you can download from Smalltalkhub or github is the
only thing that lives inside the image. I use Smalltalkhub as a backup for
github repo until I make sure filetree is a reliable way to work with
github
So I tried today to open versioner to make a configuration for Ephestos and
i got this error
RBMethodNode(Object)doesNotUnderstand: #asSequenceNode
EphPyParser class(Object)mustBeBooleanInMagic:
EphPyParser class(Object)mustBeBoolean
MetacelloProjectRegistration classExecuteUnOptimizedIn:
Am 30.06.2014 um 20:50 schrieb Stephan Eggermont step...@stack.nl:
Kilon wrote:
I disagreed with this Stephan
That being said, I am getting a bit nervous about how versioner is
released. It should aim to improve the way people can work, and not to
create a single workflow for all
That is exactly my point. But Stef currently tries to enforce this
workflow of working to Moose. And since this workflow will not work
well for Moose (because of the demands on the process), I object to this.
I don't think Stef wants to impose the workflow. Stef wants to improve
code
Your response shows that I have not made my point well. I wanted to
point out that we need different workflows because of the different
demands. A workflow is more than only a tool, but starts with people
building something and ends with people using something. And you point
out that
Hi Stephan,
Le 30 juin 2014 à 20:50, Stephan Eggermont a écrit :
Kilon wrote:
I disagreed with this Stephan
That being said, I am getting a bit nervous about how versioner is
released. It should aim to improve the way people can work, and not to
create a single workflow for all people
I just don't see it the way you do. For me Versioner is a tool to make life
a bit easier with Configurations, its not the one ring to rule them all ,
far from it. What stops anyone from implementing his own configuration tool
?
On Mon, Jun 30, 2014 at 10:23 AM, Diego Lont diego.l...@delware.nl
Kilon wrote:
I just don't see it the way you do.
That's fine, you work in a different context than we do. What do you disagree
on?
You might have missed a discussion on the Moose list. There Stef proposed to
use Versioner to
manage the Moose configuration, and use it in a specific way. We
On Mon, Jun 30, 2014 at 8:49 AM, Stephan Eggermont step...@stack.nl wrote:
Kilon wrote:
I just don't see it the way you do.
Versioner makes life easier for a specific kind of projects. It is
important to be aware
of its limitations.
What stops anyone from implementing his own configuration
Stephan---
That's fine, you work in a different context than we do. What do you
disagree on?
I disagreed with this Stephan
That being said, I am getting a bit nervous about how versioner is
released. It should aim to improve the way people can work, and *not* to
On Mon, Jun 30, 2014 at 10:01 AM, kilon alios kilon.al...@gmail.com wrote:
--Dale-
Smalltalk with it's heavy reliance on GUI-based tools is not quite as
easy to customize (for several reasons) ... before knickers get knotted,
please keep in mind that I think that
2014-06-30 13:15 GMT-03:00 Dale Henrichs dale.henri...@gemtalksystems.com:
Smalltalk with it's heavy reliance on GUI-based tools is not quite as easy
to customize (for several reasons) ... before knickers get knotted, please
keep in mind that I think that customizable GUI-based tools are
Kilon wrote:
I disagreed with this Stephan
That being said, I am getting a bit nervous about how versioner is released.
It should aim to improve the way people can work, and not to create a single
workflow for all people working on pharo projects. I hope my fears are
unfounded.
this what I
Esteban,
Just to be clear, I believe that there should be Smalltalk scripting/cli
from within the image (augment workspace usage) as well as from without ...
more food (for lunch) thought:)
Dale
On Mon, Jun 30, 2014 at 11:36 AM, Esteban A. Maringolo emaring...@gmail.com
wrote:
2014-06-30
17 matches
Mail list logo
