- Pharo-dev - lists.pharo.org

Re: [Pharo-project] MessageNotUnderstood: UndefinedObject>>includes:

by Hilaire Fernandes

I have to add that fixing those kind of issue look like fixing a ball with many holes as when one is fixed another hole appears somewhere else. Bad feeling of crapyness... 2009/2/25 Hilaire Fernandes <hilaire(a)ofset.org>: > I have this kind of error which appear randomly when I am > instantiating and displaying in real world a Morph. > Next from the morph is deduced Form field to use as the basis of a PNG > image for Seaside canvas. > It is easy to fix (or a least prevent the error) but it is system > land... so I am curious to read if other meet this problem. > > See debuglog > -- > http://blog.ofset.org/hilaire > -- http://blog.ofset.org/hilaire

Feb. 25, 2009

[Pharo-project] MessageNotUnderstood: UndefinedObject>>includes:

by Hilaire Fernandes

I have this kind of error which appear randomly when I am instantiating and displaying in real world a Morph. Next from the morph is deduced Form field to use as the basis of a PNG image for Seaside canvas. It is easy to fix (or a least prevent the error) but it is system land... so I am curious to read if other meet this problem. See debuglog -- http://blog.ofset.org/hilaire

Feb. 25, 2009

Re: [Pharo-project] ScreenController Removed with Issue #610

by Rob Rothwell

On Wed, Feb 25, 2009 at 3:10 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > mike > > is this change dependent on another change of yours? > > Stef I know I just started with the current 10243 dev image if that helps... Rob

Feb. 25, 2009

Re: [Pharo-project] 10243: error related to OB in the transcript

by David RÃ¶thlisberger

Hi Alex, > When I accept methods definition in OB, I have some printout: > ERROR: SAXCModule class>>superSenderSelectors > ERROR: SAXCModule class>>overridesSelectors > ERROR: SAXCModule class>>conflictsSelectors > ERROR: SAXCModule class>>suppliedSelectors > Maybe this is related to the dynamic protocol recently introduced > (which is an excellent thing). yes, you are right, this is caused by dynamic protocols. Those selectors you mention get sent to a class, but they are not defined on Class or Behavior. They are also not extension methods of DynamicProtocols, neither in the recent version nor in older versions. Damien, do you know where this selectors get defined? Is there an external dependency in DynamicProtocols, do we need to load something else to get these methods? David

Feb. 25, 2009

Re: [Pharo-project] MIMEdatabase fix?

by Lukas Renggli

> what seasiders think? > I would be in favor to get a KOM pharo version Having two incompatible versions of Kom makes distribution even more painful as it is today. I would prefer to have compatible versions if this is possible. Otherwise Seaside won't run on Squeak anymore, unless somebody steps up and does all the testing, porting and integration work. We don't have the capacity to maintain different distribution paths and ports. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Feb. 25, 2009

Re: [Pharo-project] Some issues with Pharo-dev build #10243

by Igor Stasenko

Yeah, i found it already 2009/2/25 CÃ©drick BÃ©ler <cdrick65(a)gmail.com>: > 2009/2/25 Damien Cassou <damien.cassou(a)gmail.com>: >> On Tue, Feb 24, 2009 at 10:33 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >>> btw, how i can switch to old one? > > > Toolset askForDefault > > >> >> Have a look at the DevToolSet class (class-side). There is something >> like an #ifOB:else: method. >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > CÃ©drick > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Best regards, Igor Stasenko AKA sig.

Feb. 25, 2009

Re: [Pharo-project] [squeak-dev] Known bug with text editor and scroll ?

by StÃ©phane Ducasse

if you want to get a chance that the bug/enh is integrated in pharo read the pharo web page explaining how to report a bug in pharo I do no thav einternet right now. On Feb 25, 2009, at 3:43 AM, Mariano Martinez Peck wrote: > Thanks for the help Steve. I look in mantis bugs and I found exactly > the same bug I was going to report. I noticed it was fixed and a .cs > attached. I tried it and work like a charm. > > http://bugs.squeak.org/view.php?id=5637 > > So, now, the question is....will this .cs be included in future > squeak images ? I mean, how is the process for the bug fixes ? when > are the fixes put in the images ? > > thanks for the help. > > Mariano > > On Wed, Feb 25, 2009 at 12:11 AM, Steve Wart <steve.wart(a)gmail.com> > wrote: > Please log a bug. If you have some better ideas about how text > editing should work please make a detailed proposal and work with > the developers to understand possible side-effects and how to avoid > them. > > The Mantis wiki page is here - I'm not sure if Pharo has a different > tracking system but I'm sure someone will be working on a > coordination mechanism (maybe we should log that as a bug too) > > http://wiki.squeak.org/squeak/3860 > > Steve > > On Tue, Feb 24, 2009 at 4:51 PM, Mariano Martinez Peck <marianopeck(a)gmail.com > > wrote: > Hi people: I am having a problem and I think is a known bug but I > want to be sure. Sometimes, not very often, I have a method that is > bigger (vertically speaking) than the editor inside the class > browser. I mean, the whole method cannot be see in the edit but a > vertical scroll appear. I want to select text, using shift and down > narrow for example, and go to the end of the method. The scroll > should move and the editor should show the end of the method, but it > doesn't happen. The visible part of the method doesn't change. > However, it does select all the text (the one is down, I can see it). > > Please, don't answer me "this is a feature. You must extract > something to another method" because this is not ALWAYS true just > sometimes. > > Thanks for the help, > > Mariano > > > > > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 25, 2009

Re: [Pharo-project] Some issues with Pharo-dev build #10243

by CÃ©drick BÃ©ler

2009/2/25 Damien Cassou <damien.cassou(a)gmail.com>: > On Tue, Feb 24, 2009 at 10:33 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> btw, how i can switch to old one? Toolset askForDefault > > Have a look at the DevToolSet class (class-side). There is something > like an #ifOB:else: method. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- CÃ©drick

Feb. 25, 2009

Re: [Pharo-project] Some issues with Pharo-dev build #10243

by Damien Cassou

On Tue, Feb 24, 2009 at 10:33 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > btw, how i can switch to old one? Have a look at the DevToolSet class (class-side). There is something like an #ifOB:else: method. -- Damien Cassou http://damiencassou.seasidehosting.st

Feb. 25, 2009

Re: [Pharo-project] MIMEdatabase fix?

by Lukas Renggli

> there is a hopefully fixed version of the Kom package in the Pharo inbox. > I'm not familiar with Universes yet, so I can't easily make a modified > loader for Seaside or Pier. Is it backward compatible? Do your changes to Kom continue to work in Squeak 3.9? If so, we should probably publish it to the official Kom repository: <http://www.squeaksource.com/KomWebServer>. After some testing, I can do a new Seaside and Pier release. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Feb. 25, 2009