Hi Marcus,
I completely agree.
Now, just one thing. We have to start with putting in place a full fledged
dev image as soon as a new Core version is started. Like this we can use that
one from the beginning. For example, in Moose we switch to the new version as
soon as the dev is
Hi Marcus,
I completely agree.
Now, just one thing. We have to start with putting in place a full fledged dev
image as soon as a new Core version is started. Like this we can use that one
from the beginning. For example, in Moose we switch to the new version as soon
as the dev is available.
Very good! We then can release the 1.2 Full soon, too.
I wonder if we should adopt your OB codebase for that? Or do
we wait for 1.2.1?
I would wait a bit. I noticed that the debugger is quite broken. I
only get the pre-debug window, but clicking on any button opens
another pre-debug window. I
Ahh, looks like SimpleMorphic has some (probably unintentional)
overrides of core methods. Unloading the package pretty much breaks
everything :-(
Lukas
On 18 March 2011 07:02, Lukas Renggli reng...@gmail.com wrote:
Very good! We then can release the 1.2 Full soon, too.
I wonder if we should
On Mar 18, 2011, at 7:09 AM, Lukas Renggli wrote:
Ahh, looks like SimpleMorphic has some (probably unintentional)
overrides of core methods. Unloading the package pretty much breaks
everything :-(
Lukas
On 18 March 2011 07:02, Lukas Renggli reng...@gmail.com wrote:
Very good! We then
On 18.03.2011 07:41, Marcus Denker wrote:
On Mar 18, 2011, at 7:09 AM, Lukas Renggli wrote:
Ahh, looks like SimpleMorphic has some (probably unintentional)
overrides of core methods. Unloading the package pretty much breaks
everything :-(
Lukas
On 18 March 2011 07:02, Lukas
On Mar 18, 2011, at 8:04 AM, Henrik Sperre Johansen wrote:
And nobody ever unloaded anything from Core.
Marcus
I thought the general idea was to remove SimpleMorphic before releases?
Think I read so in an issue, or on the list.
Yes, but it was not done for 1.2 and 1.2 is
+1
Doru
On 18 Mar 2011, at 08:07, Marcus Denker wrote:
On Mar 18, 2011, at 8:04 AM, Henrik Sperre Johansen wrote:
And nobody ever unloaded anything from Core.
Marcus
I thought the general idea was to remove SimpleMorphic before releases?
Think I read so in an issue, or on
Yes, but it was not done for 1.2 and 1.2 is *finished*.
If we want to do that, we need to do that *not after the release is released*
but before.
This whole thing just shows that I only look at 1.2 when it is released *DOES
NOT WORK*.
1.2 Core was Release Canditate for *two months*.
I would not unload packaged.
Everything not tested is broken, and so if you do things like that I am
sure you will have problems.
And nobody ever unloaded anything from Core.
You must be joking right? In the mission you say stable and small
core, but the numbers say something entirely
On Mar 18, 2011, at 8:16 AM, Lukas Renggli wrote:
I would not unload packaged.
Everything not tested is broken, and so if you do things like that I am
sure you will have problems.
And nobody ever unloaded anything from Core.
You must be joking right? In the mission you say stable and
On Mar 18, 2011, at 8:24 AM, Marcus Denker wrote:
On Mar 18, 2011, at 8:16 AM, Lukas Renggli wrote:
I would not unload packaged.
Everything not tested is broken, and so if you do things like that I am
sure you will have problems.
And nobody ever unloaded anything from Core.
You
+1
I would not unload packaged.
Everything not tested is broken, and so if you do things like that I am
sure you will have problems.
And nobody ever unloaded anything from Core.
You must be joking right? In the mission you say stable and small
core, but the numbers say something
Lukas
Marcus is RIGHT.
How can we make progress without adding temporarily new libraries and migrating?
How can we make progress if people do not use the release candidate phase as it
should be?
Tell me because we are all ears opened.
Stef
I would not unload packaged.
Everything not tested
lukas
Can you tell us where?
What method is doing a problem?
The point of simpleMorphic is that there is a value in it and if we do not give
a chance to people to have a look
at it then the money spent by esug is lost (of course esug was not paying for
simpleMorphic but this is like that).
Can you tell us where?
What method is doing a problem?
Model#topView seems to be the only override of a core method.
Lukas
--
Lukas Renggli
www.lukas-renggli.ch
On Mar 18, 2011, at 11:18 AM, Lukas Renggli wrote:
Can you tell us where?
What method is doing a problem?
Model#topView seems to be the only override of a core method.
Ok:
http://code.google.com/p/pharo/issues/detail?id=3828
I will add that tonight.
--
Marcus Denker --
+1
El vie, 18-03-2011 a las 08:24 +0100, Marcus Denker escribió:
On Mar 18, 2011, at 8:16 AM, Lukas Renggli wrote:
I would not unload packaged.
Everything not tested is broken, and so if you do things like that I am
sure you will have problems.
And nobody ever unloaded anything
Another issue is the class GLMOrangeUITheme being in the 'Morphic'
package and an indirect subclass of UITheme that is in the 'Polymorph'
package which itself depends on the 'Morphic' package == circular
dependency == loading/unloading impossible.
Lukas
On 18 March 2011 17:14, Miguel Cobá
On 18 March 2011 20:47, Lukas Renggli reng...@gmail.com wrote:
Another issue is the class GLMOrangeUITheme being in the 'Morphic'
package and an indirect subclass of UITheme that is in the 'Polymorph'
package which itself depends on the 'Morphic' package == circular
dependency ==
I've got my complete Jenkins server building on Pharo 1.2 now:
http://jenkins.lukas-renggli.ch/
Some stuff is still a bit broken, but it looks good so far.
Lukas
On 16 March 2011 18:09, Lukas Renggli reng...@gmail.com wrote:
Excellent! Can somebody update
On 17 March 2011 19:11, Lukas Renggli reng...@gmail.com wrote:
I've got my complete Jenkins server building on Pharo 1.2 now:
http://jenkins.lukas-renggli.ch/
Some stuff is still a bit broken, but it looks good so far.
cool.
We need to put a pressure on INRIA guys to upgrade to jenkins..
I've got my complete Jenkins server building on Pharo 1.2 now:
http://jenkins.lukas-renggli.ch/
Some stuff is still a bit broken, but it looks good so far.
cool.
We need to put a pressure on INRIA guys to upgrade to jenkins..
because right now
some things are not working well
On Mar 17, 2011, at 7:13 PM, Lukas Renggli wrote:
I've got my complete Jenkins server building on Pharo 1.2 now:
http://jenkins.lukas-renggli.ch/
Some stuff is still a bit broken, but it looks good so far.
Very good! We then can release the 1.2 Full soon, too.
I wonder if we should
Excellent! Can somebody update
http://www.pharo-project.org/pharo-download/stable-core
because it still points to Pharo 1.1.1, thus the build server picks up
the old image.
Lukas
On 14 March 2011 22:13, Noury Bouraqadi bouraq...@gmail.com wrote:
Saturday, 1.2 worked with a Cog-Stack VM.
Please check...
https://gforge.inria.fr/frs/download.php/28340/PharoCore-1.2.zip
--
Marcus Denker -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.
On Mon, Mar 14, 2011 at 2:40 PM, Marcus Denker marcus.den...@inria.frwrote:
Please check...
https://gforge.inria.fr/frs/download.php/28340/PharoCore-1.2.zip
What is the official VM for Pharo 1.2 ? Running all tests with Cog (OSX) =
crash.
Laurent.
--
Marcus Denker --
On Mar 14, 2011, at 3:08 PM, laurent laffont wrote:
On Mon, Mar 14, 2011 at 2:40 PM, Marcus Denker marcus.den...@inria.fr wrote:
Please check...
https://gforge.inria.fr/frs/download.php/28340/PharoCore-1.2.zip
What is the official VM for Pharo 1.2 ? Running all tests with
Saturday, 1.2 worked with a Cog-Stack VM.
Noury
On 14 mars 2011, at 15:17, Marcus Denker wrote:
On Mar 14, 2011, at 3:08 PM, laurent laffont wrote:
On Mon, Mar 14, 2011 at 2:40 PM, Marcus Denker marcus.den...@inria.fr
wrote:
Please check...
29 matches
Mail list logo
