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

Mariano Martinez Peck wrote: > > On Thu, Dec 31, 2009 at 2:07 PM, David Röthlisberger > wrote: > >> I need to know which Pharo version, which browser version and which >> packages are >> loaded to reproduce and locate the problem. >> It might or might not be related to the problem we discussed,

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

On Thu, Dec 31, 2009 at 2:07 PM, David Röthlisberger wrote: > > > > 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 conf

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

> 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. > What I am not sure, David, can you con

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

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

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

On Thu, Dec 31, 2009 at 11:54 AM, Stéphane Ducasse < stephane.duca...@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

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

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 st

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

On Thu, Dec 31, 2009 at 11:32 AM, Stan Shepherd 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

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

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, a

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

On Thu, Dec 31, 2009 at 1:54 AM, Adrian Kuhn wrote: > Mariano Martinez Peck writes: > > > What's OP? > > Original Poster > > > With 10502 I cannot even click on a class neither in the code panel. > > I use 10502 and I observe no such bugs (using OB, not O2 though). > mmm are you sure about 1182

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

On Thu, Dec 31, 2009 at 1:19 AM, Adrian Kuhn wrote: > Lukas Renggli writes: > > > Then somebody that uses OB and Traits daily should commit on that. I > > am not a trait user, so I can't help here. The same for the package > > browser: I am pretty happy with OB, the package browser of > > OB-Ref

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

The main problem is that we are not integrating enough. Please, take 5 minutes and see this example: Open http://source.wiresong.ca/ob In pharo1.0-10502-rc1dev09.12.2 the version loaded is OB-Standard-DamienCassou.438 which actually loads the OB-Standard-lr.434. I really don't understand why this

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

Bart in Morphic may be this is not broken in 3.9 there was a recordMorph that recorded the mouse location and that could be replied after. I read the code long time ago and forgot but may. I remember that on VisualAge there was a tool to capture and replay UI tests. So I would be really intereste

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

tinez Peck Sent: Wednesday, December 30, 2009 1:30 PM To: Pharo-project@lists.gforge.inria.fr Subject: 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: #dynamicPr

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

I highly agree also !! Its related to Pharo for Professional Developmentthread I started 2 weeks ago. It basically says the same. My gut feeling is still that stability should be the number one focus. Its great to inno

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

>> Thanks Lukas to be agree. I like your scripts, but the problem is that you >> use your own forked repository to get an stable version. I would love to >> have THAT, but in the original repositories. Examples: omnibrowser, >> unsorted, etc. Do you know how we can fix this ? > > Well, if you wa

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

Yes we should find somebody. I will ask around. Stef On Dec 30, 2009, at 8:05 PM, Lukas Renggli wrote: >> Yes lukas now damien was nice to build the images because I could not do >> them. >> But damien is doing Java daily. > > Yes, I know. This is definitely not the fault of Damien, he is doin

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

Yes, I know Dale ;) But anyway, that's just a part. We still have several problems and needs: 1) We have different repositories for the same project. As the examples I did, we have omnibroswer in Lukas and wiresong. The same with other packages. So, we need someone who integrates and merges betwe

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

> Thanks Lukas to be agree. I like your scripts, but the problem is that you > use your own forked repository to get an stable version. I would love to > have THAT, but in the original repositories. Examples: omnibrowser, > unsorted, etc.  Do you know how we can fix this ? Well, if you want to do

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

> Yes lukas now damien was nice to build the images because I could not do them. > But damien is doing Java daily. Yes, I know. This is definitely not the fault of Damien, he is doing an excellent job in integrating, merging and fixing the obvious bugs. The problem is that nobody that uses the ima

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

Metacello will be used to identify stable versions of the packages that are known to work and there is an ongoing effort to create Metacello configurations for all of the projects that go into the dev and web images. So that part of the puzzle is being addressed. Dale - "Mariano Martinez

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

Thanks Lukas to be agree. I like your scripts, but the problem is that you use your own forked repository to get an stable version. I would love to have THAT, but in the original repositories. Examples: omnibrowser, unsorted, etc. Do you know how we can fix this ? On Wed, Dec 30, 2009 at 7:25 PM

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

Yes lukas now damien was nice to build the images because I could not do them. But damien is doing Java daily. And you do not like the package browser and we need it :). So I do not know what to do. - first we should add simple trait creation to the OB - now frankly I do not know h

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

> 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. This is what I am telling for years already. I don't know how other people think about this, but to me i

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

I agree.! Now what I suggest is that we do not release a pharo-dev image without having tested it. > 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. I agree. > We a

[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

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