[Pharo-project] Bug in OBBrowser: "Metaclass class>>does not understand: #isScarySelector:"
Hi all, In OB Package Browser and OB System Browser, it is impossible to make a class side method. An exception appears "Metaclass class>>does not understand: #isScarySelector:" Any idea to resolve it ? Cheers --- Jannik Laval ---
On Mon, Sep 21, 2009 at 9:46 AM, Laval Jannik <jannik.laval@gmail.com> wrote:
In OB Package Browser and OB System Browser, it is impossible to make a class side method. An exception appears "Metaclass class>>does not understand: #isScarySelector:"
Any idea to resolve it ?
I can't reproduce that in a pharo1.0-10451-BETAdev09.09.3. Could you please try again? -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry
Any idea to resolve it ?
I can't reproduce that in a pharo1.0-10451-BETAdev09.09.3. Could you please try again?
I think the Moose loader loads an ancient version of OB from Package Universes. Could that be the problem? Lukas -- Lukas Renggli http://www.lukas-renggli.ch
I have just done a "ScriptLoader loadOB", and the same bug appears. Cheers Jannik On Sep 21, 2009, at 11:30 , Lukas Renggli wrote:
Any idea to resolve it ?
I can't reproduce that in a pharo1.0-10451-BETAdev09.09.3. Could you please try again?
I think the Moose loader loads an ancient version of OB from Package Universes. Could that be the problem?
Lukas
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
--- Jannik Laval PhD Student - Rmod Team - INRIA Certified Project Management Associate (IPMA) http://www.jannik-laval.eu http://rmod.lille.inria.fr ---
I have just done a "ScriptLoader loadOB", and the same bug appears.
Yes, but that uses Universes. If you use the part that loads OB from this script (everything up to the section on Seaside), it should work: http://code.google.com/p/pharo/wiki/ImageBuildScripts Lukas
Cheers Jannik
On Sep 21, 2009, at 11:30 , Lukas Renggli wrote:
Any idea to resolve it ?
I can't reproduce that in a pharo1.0-10451-BETAdev09.09.3. Could you please try again?
I think the Moose loader loads an ancient version of OB from Package Universes. Could that be the problem?
Lukas
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
--- Jannik Laval PhD Student - Rmod Team - INRIA Certified Project Management Associate (IPMA) http://www.jannik-laval.eu http://rmod.lille.inria.fr ---
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Lukas Renggli http://www.lukas-renggli.ch
On Mon, Sep 21, 2009 at 11:44 AM, Laval Jannik <jannik.laval@gmail.com> wrote:
I have just done a "ScriptLoader loadOB", and the same bug appears.
Why do you use this old and not working script when I'm generating new images three times a month? http://pharo-project.org/pharo-download -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry
On Sep 21, 2009, at 13:14 , Damien Cassou wrote:
On Mon, Sep 21, 2009 at 11:44 AM, Laval Jannik <jannik.laval@gmail.com> wrote:
I have just done a "ScriptLoader loadOB", and the same bug appears.
Why do you use this old and not working script when I'm generating new images three times a month?
because it is present in the image :) If it is an old version, maybe we must clean ScriptLoader.
http://pharo-project.org/pharo-download
-- Damien Cassou http://damiencassou.seasidehosting.st
"Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
--- Jannik Laval PhD Student - Rmod Team - INRIA Certified Project Management Associate (IPMA) http://www.jannik-laval.eu http://rmod.lille.inria.fr ---
yes we should not use scriptLoader for that because scriptLoader should not be part of the default image. stef On Sep 21, 2009, at 1:40 PM, Laval Jannik wrote:
On Sep 21, 2009, at 13:14 , Damien Cassou wrote:
On Mon, Sep 21, 2009 at 11:44 AM, Laval Jannik <jannik.laval@gmail.com> wrote:
I have just done a "ScriptLoader loadOB", and the same bug appears.
Why do you use this old and not working script when I'm generating new images three times a month?
because it is present in the image :)
If it is an old version, maybe we must clean ScriptLoader.
http://pharo-project.org/pharo-download
-- Damien Cassou http://damiencassou.seasidehosting.st
"Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
--- Jannik Laval PhD Student - Rmod Team - INRIA Certified Project Management Associate (IPMA) http://www.jannik-laval.eu http://rmod.lille.inria.fr ---
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
El lun, 21-09-2009 a las 16:35 +0200, Stéphane Ducasse escribió:
yes
we should not use scriptLoader for that because scriptLoader should not be part of the default image.
This is confusing for me. Maybe the Pharo board should take a decision now in order to the community to push it. There are: ChangeSets ScriptLoader Monticello alone Monticello configurations Metacello Installer Gofer maybe others too. They share a lot of overlapped functionality. Some scripts use one of them, some other. This confuse the developers and the community. Maybe now is the moment to discuss the tools in order to polish them and use them, at leas until a new tool arrives that is better than the used by Pharo. You said that ScriptLoader will not be part of the core image but as I can see, only ScriptLoader and Installer can be installed directly from the web in an image that it doesn't have it. Can the community discuss this? Or the Pharo board write its opinion?
stef
On Sep 21, 2009, at 1:40 PM, Laval Jannik wrote:
On Sep 21, 2009, at 13:14 , Damien Cassou wrote:
On Mon, Sep 21, 2009 at 11:44 AM, Laval Jannik <jannik.laval@gmail.com> wrote:
I have just done a "ScriptLoader loadOB", and the same bug appears.
Why do you use this old and not working script when I'm generating new images three times a month?
because it is present in the image :)
If it is an old version, maybe we must clean ScriptLoader.
http://pharo-project.org/pharo-download
-- Damien Cassou http://damiencassou.seasidehosting.st
"Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
--- Jannik Laval PhD Student - Rmod Team - INRIA Certified Project Management Associate (IPMA) http://www.jannik-laval.eu http://rmod.lille.inria.fr ---
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Miguel Cobá http://miguel.leugim.com.mx
2009/9/21 Miguel Enrique Cobá Martinez <miguel.coba@gmail.com>:
This is confusing for me. Maybe the Pharo board should take a decision now in order to the community to push it. There are:
If we are talking about a package management system (a way for the end-user to install more packages):
ChangeSets
not a package management system. It's a format to exchange code.
ScriptLoader
private/internal way to manage the update stream. Should not be visible to the end user.
Monticello alone
does not allow loading of projects with dependencies on other repositories
Monticello configurations
I don't know
Metacello
+1 but we need a place to put Metacello descriptions
Installer
+1 but we need a place to put Installer scripts (Sake/Packages)
Gofer
I see it more as a backend for Installer and Metacello -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry
This is confusing for me.
this is simple ScriptLoader should be named ThePrivateClassIntegratorUseToIntegrateAndManageRelease
Maybe the Pharo board should take a decision now in order to the community to push it. There are:
ChangeSets ok to keep to manage simple changes
ScriptLoader private don't use don't look at it is crap (I wrote)
Monticello alone ok Monticello configurations ok
Metacello will manage group of packages and projects based on Monticello
Installer to script different code input
Gofer to script Monticello
They share a lot of overlapped functionality. Some scripts use one of them, some other. This confuse the developers and the community. Maybe now is the moment to discuss the tools in order to polish them and use them, at leas until a new tool arrives that is better than the used by Pharo.
You said that ScriptLoader will not be part of the core image but as I can see, only ScriptLoader and Installer can be installed directly from the web in an image that it doesn't have it.
Can the community discuss this? Or the Pharo board write its opinion?
done :)
participants (5)
-
Damien Cassou -
Laval Jannik -
Lukas Renggli -
Miguel Enrique Cobá Martinez -
Stéphane Ducasse