December 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] We need to do something, seriously!!!! [WAS] Fwd: Issue 1721: Refactoring appears to be broken in web dev image. e.g. OBClassNode(Object)>>doesNotUnderstand: #dynamicProtocols

by Stan Shepherd

Mariano Martinez Peck wrote: > > >> >> Mariano, Adrian's fix does indeed seem to fix up this whole area. After >> running it, I can get right through the menus to run code critics, and >> right/left/middle clicks don't cause problem. It would seem the image on >> the >> download page should be replaced ASAP with one which has had this >> operation. >> >> > Yes, I am agree. Can someone do this please? I have no idea how to do it > neither I have the rights. > > I just to pick up the latest dev and web image from the website evaluate > > Gofer it > wiresong: 'ob'; > package: 'OB-Refactory'; > revert > > > save it and upload it again. > > In addition, we have to take a decision here: > > 1) Remove O2 from the script until O2 has NO dependencies and overrides in > OB and until O2 loads perfectly in a core image without anything about OB. > Those who want to use it anyway, can install by their self. > 2) Add this piece of hack to our script. > > I might have clicked too soon. This seems to reintroduce Issue 1644: BrowserEnvironment(Object)>>doesNotUnderstand: #forPackage: ...Stan -- View this message in context: http://n2.nabble.com/We-need-to-do-something-seriously-WAS-Fwd-Issue-1721-R… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 31, 2009

Re: [Pharo-project] Pharo testers.... WE NEED YOU!!!

by Mariano Martinez Peck

On Thu, Dec 31, 2009 at 11:59 AM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > > On Dec 31, 2009, at 11:50 AM, Mariano Martinez Peck wrote: > > > Ok, you already know the idea. Damien, or the person that build the next > Pharo dev and web images will send those Pharo beta testers a private email > with the link to download the image. No ANN and now update is done yet to > the website. Then the betatesters use that image as much as possible for a > couple of days. Report bugs if necessary and if it is ok, the image is > released. > > send a call in the mailing-list. The image can be on the inria web site > with FORBETATESTERS. > The image can be in the inria site, perfect, but I wouldn't put the link in www.pharo-project.org. > > > > Regarding the list of beta testers would be perfect if we cover the > combination of OS (Linux, Mac, Windows) and the browser (OB, O2). But we > cannot pretend too much. Take into account that not all the people can work > with a new image very easily because they have to migrate data > ...etc..Others can just download the project from MC and start to work :) > > > > So...here is the list, if you offer yourself, it would be cool to know: > OS, VM version, Dev or Web, browser you usually work, 32 o 64 bits, > > I will then collect this and I will put it in the wiki. > > > > - Mariano Martinez Peck. Mac OS, Squeak 4.2.2beta1U.app, Dev, OB, 32 > bits > > - Stan Shepherd > > > > > > WHO ELSE IS IN THE LIST ?? > > - Me. (but usually I'm hacking with core except when coding in Moose.) if > there is nobody else :) > > Ok...but take it easy. Maybe more people join. > > cheers and happy new year!! > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 31, 2009

Re: [Pharo-project] Cannot even browse a class in web image

by Lukas Renggli

> OK, thanks Lukas! But you see that we have a serious problem?Â How many time you heard "I have already fix this in ....."Â or "This bug is present again" The problem is that nobody uses O2 12 hours a day and really cares to fix things on the fly all the time. I do that with OB and RB on a daily bases. It consumes some time here and then, but it is fun, makes me more productive and in the long run pays off. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Dec. 31, 2009

Re: [Pharo-project] We need to do something, seriously!!!! [WAS] Fwd: Issue 1721: Refactoring appears to be broken in web dev image. e.g. OBClassNode(Object)>>doesNotUnderstand: #dynamicProtocols

by Mariano Martinez Peck

On Thu, Dec 31, 2009 at 11:54 AM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > Mariano > > May be you can contact david probably on holidays to see how we can make > progress? > I know that we can publish in david repository so may be a lot of the > problems are simple glicth. > Having a configuration for O2 would be good. > > Sorry, I forgot to mention this...I have already contact David 1 o 2 days ago because I already wrote a ConfigurationOfEnhancedOmniBrowser and I had questions about it dependencies. I discovered some problems with them and ask David. He fixed one of this dependencies, but the one from O2-Refactory is still present and maybe we will fix it next week or similar...he doesn't have too much time. What I am not sure, David, can you confirm this ? is if what we talk in our private email a about the O2-Refactory (the problem we still have) is the same problem we are talking here. Because, in my opinion, one thing is just to depend and another thing is to depend and override. If there are overrides, it matters the order and a lot more stuff. That's why I am asking you :) Is it the same? I hope so :) Cheers. Mariano > Here is what david wrote to me the 20th. > > O2 is stored here: > http://www.squeaksource.com/EnhancedOB > > this repo is globally writable. > > ps: I will get to your other mails soon, I was a bit sick in the > last few days and took some days off. > > David > > Stef > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 31, 2009

Re: [Pharo-project] Pharo testers.... WE NEED YOU!!!

by StÃ©phane Ducasse

On Dec 31, 2009, at 11:50 AM, Mariano Martinez Peck wrote: > Ok, you already know the idea. Damien, or the person that build the next Pharo dev and web images will send those Pharo beta testers a private email with the link to download the image. No ANN and now update is done yet to the website. Then the betatesters use that image as much as possible for a couple of days. Report bugs if necessary and if it is ok, the image is released. send a call in the mailing-list. The image can be on the inria web site with FORBETATESTERS. > Regarding the list of beta testers would be perfect if we cover the combination of OS (Linux, Mac, Windows) and the browser (OB, O2). But we cannot pretend too much. Take into account that not all the people can work with a new image very easily because they have to migrate data ...etc..Others can just download the project from MC and start to work :) > > So...here is the list, if you offer yourself, it would be cool to know: OS, VM version, Dev or Web, browser you usually work, 32 o 64 bits, > I will then collect this and I will put it in the wiki. > > - Mariano Martinez Peck. Mac OS, Squeak 4.2.2beta1U.app, Dev, OB, 32 bits > - Stan Shepherd > > > WHO ELSE IS IN THE LIST ?? - Me. (but usually I'm hacking with core except when coding in Moose.) if there is nobody else :) > cheers and happy new year!! > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 31, 2009

Re: [Pharo-project] where can I see the slices that were removed from inbox?

by StÃ©phane Ducasse

in TreatedPharoInbox we never delete submissions just move them there. Stef On Dec 31, 2009, at 11:33 AM, Mariano Martinez Peck wrote: > I need to load a slice in 1.0 which was integrated in 1.1 and removed from PharoInbox. Where can I find it? > > thanks > > mariano > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 31, 2009

Re: [Pharo-project] Can't debug in 1.1

by StÃ©phane Ducasse

On Dec 31, 2009, at 11:33 AM, Marcus Denker wrote: > > On Dec 31, 2009, at 9:50 AM, StÃ©phane Ducasse wrote: > >> Probably the changes of Martin von Lowis. > > Yes. The changeset had code to migrate all instances... it might be that the debugger's use > of WeakKeyDictionary was added by Eliot? This would explain why it was not migrated. > > I suggest to just do the reset in a postscript in one of the next updates, and it's fixed. > > >> I imagine that when marcus is bad from holidays he can tell us more. >> > > I'm back... kind of. Decided not to travel to south germany this morning after moving boxes > for 3 days... better to have an IKEA-unboxing-relaxing-reading-emails-hacking-weekend. If you need tools let me know ;) Stef

Dec. 31, 2009

Re: [Pharo-project] We need to do something, seriously!!!! [WAS] Fwd: Issue 1721: Refactoring appears to be broken in web dev image. e.g. OBClassNode(Object)>>doesNotUnderstand: #dynamicProtocols

by StÃ©phane Ducasse

Mariano May be you can contact david probably on holidays to see how we can make progress? I know that we can publish in david repository so may be a lot of the problems are simple glicth. Having a configuration for O2 would be good. Here is what david wrote to me the 20th. O2 is stored here: http://www.squeaksource.com/EnhancedOB this repo is globally writable. ps: I will get to your other mails soon, I was a bit sick in the last few days and took some days off. David Stef

Dec. 31, 2009

[Pharo-project] Pharo testers.... WE NEED YOU!!!

by Mariano Martinez Peck

Ok, you already know the idea. Damien, or the person that build the next Pharo dev and web images will send those Pharo beta testers a private email with the link to download the image. No ANN and now update is done yet to the website. Then the betatesters use that image as much as possible for a couple of days. Report bugs if necessary and if it is ok, the image is released. Regarding the list of beta testers would be perfect if we cover the combination of OS (Linux, Mac, Windows) and the browser (OB, O2). But we cannot pretend too much. Take into account that not all the people can work with a new image very easily because they have to migrate data ...etc..Others can just download the project from MC and start to work :) So...here is the list, if you offer yourself, it would be cool to know: OS, VM version, Dev or Web, browser you usually work, 32 o 64 bits, I will then collect this and I will put it in the wiki. - Mariano Martinez Peck. Mac OS, Squeak 4.2.2beta1U.app, Dev, OB, 32 bits - Stan Shepherd WHO ELSE IS IN THE LIST ?? cheers and happy new year!!

Dec. 31, 2009

Re: [Pharo-project] We need to do something, seriously!!!! [WAS] Fwd: Issue 1721: Refactoring appears to be broken in web dev image. e.g. OBClassNode(Object)>>doesNotUnderstand: #dynamicProtocols

by Mariano Martinez Peck

On Thu, Dec 31, 2009 at 11:32 AM, Stan Shepherd <stan.shepherd414(a)gmail.com>wrote: > > > Mariano Martinez Peck wrote: > > > > Hi folks. I am really concerned about the instability of the dev and web > > images. WE CANNOT RELEASE a RC where you cannot even double click in a > > class. This cannot happens. We all know that all software can have bugs. > > But > > again, we cannot release images, and even RC images, which are supposed > to > > be quite stable, where you cannot right click a class, you cannot > > refactor, > > you cannot even right click in the code pane. And don't told me "I use > the > > keyboard" because I don't care what you do. A lot of people use the > mouse. > > > > I have already said it several times. Most of the people don't care how > > nice, fast, clean, open source and well programmed is the Pharo Core > image > > if they cannot use the Dev or Web image. > > > > Remember that our users are external users, you even don't care about the > > core. They just use Pharo, they are not developers. > > > > I really think we need to fix this. You are giving a bad impression of > > something which is not true. You are doing AN EXCELLENT work with > > PharoCore. > > Why to wast all of this for this kind of situations? It is a pity :( > > > > I don't know the best solution for this. I will only give an idea I have, > > but I would really like to hear you ideas and do something with this. > > > > 1) We are building a dev image per month more or lest. 5 days before en > of > > months (more or less), the dev image should be built. > > > > 2) During 5 years, some people will use that image as a beta tester. I > > would > > ideally to have different users: different OS, different browsers, etc. > > This people will use that image for their work for those 5 days and > report > > any bug that appears. Of course, not all people can do that. > > How is volunteer to be beta tester ? We can create a wiki page for that > > if > > you are agree with the idea. > > > > 3) After those 5 days, if the image is stable enough, it is released. If > > it > > is not, it is just not released. Nobody will kill you if one month you > > don't > > release a new image. In addition, is better not to release an unstable > > image > > that releasing it and not be able to do a single right click. > > > > In Canonical, all the employees MUST to use for one month or more each > > Ubuntu release. We are not employee, but we can do something similar. > > > > What do you think ? > > > > Cheers > > > > Mariano > > > > > > ---------- Forwarded message ---------- > > From: Stan Shepherd <stan.shepherd414(a)gmail.com> > > Date: Wed, Dec 30, 2009 at 6:26 PM > > Subject: [Pharo-project] Issue 1721: Refactoring appears to be broken in > > web > > dev image. e.g. OBClassNode(Object)>>doesNotUnderstand: #dynamicProtocols > > To: pharo-project(a)lists.gforge.inria.fr > > > > > > > > NB this logs a particular walkback, but the whole area appears to be > > unworkable in the web dev image. Please could the maintainers click, > right > > click, middle click on each part of refactoring browser, take each menu > > item, etc. This will be much quicker than logging one bug at a time. > > If this turns out to be the last one, my apologies in advance. > > Thanks. ...Stan > > > > > > VM: unix - i686 - linux-gnu - Pharo0.1 of 16 May 2008 [latest update: > > #10074] > > Image: PharoCore1.0rc1 [Latest update: #10502] > > pharo1.0-10502-rc1web09.12.2 > > > > Class browser used (if applicable): OR2PackageBrowser. > > > > OBClassNode(Object)>>doesNotUnderstand: #dynamicProtocols > > Receiver: OBClassNode<ShortIntegerArray> > > Arguments and temporary variables: > > aMessage: dynamicProtocols > > exception: MessageNotUnderstood: > > OBClassNode>>dynamicProtocols > > resumeValue: nil > > Receiver's instance variables: > > metaNode: Class > > > > > Mariano Martinez Peck wrote: > > > > ... volunteer to be beta tester ? > > > > I volunteer. And being on Linux and a mouse user, I seem to hit a lot of > the > wrinkles. > > Ok, perfect. I will open another thread for this then. > > Mariano Martinez Peck wrote: > > > > I don't know the best solution for this > > > > Mariano, Adrian's fix does indeed seem to fix up this whole area. After > running it, I can get right through the menus to run code critics, and > right/left/middle clicks don't cause problem. It would seem the image on > the > download page should be replaced ASAP with one which has had this > operation. > > Yes, I am agree. Can someone do this please? I have no idea how to do it neither I have the rights. I just to pick up the latest dev and web image from the website evaluate Gofer it wiresong: 'ob'; package: 'OB-Refactory'; revert save it and upload it again. In addition, we have to take a decision here: 1) Remove O2 from the script until O2 has NO dependencies and overrides in OB and until O2 loads perfectly in a core image without anything about OB. Those who want to use it anyway, can install by their self. 2) Add this piece of hack to our script. Opinions ? > > Adrian Kuhn wrote: > > > > Gofer it > > wiresong: 'ob'; > > package: 'OB-Refactory'; > > revert > > > > this will revert all conflicting package extensions of O2 back to those > of > > OB > > so that you can work with both the green and the yellow browser of OB. > > > > Mariano, thanks for bringing this into sharp focus. As Bart identified, > it's > been a real concern that our "shop window" has been broken like this. > > You are welcome. I don't pretend Pharo to be rock solid. But I pretend not to have those errors were you cannot even browse a class or right click on the code. Cheers Mariano > ...Stan > > -- > View this message in context: > http://n2.nabble.com/We-need-to-do-something-seriously-WAS-Fwd-Issue-1721-R… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 31, 2009