On Fri, Feb 27, 2009 at 10:38:43AM +0100, St?phane Ducasse wrote:
> Ideally we should check that the guy sign the squeak MIT agreement but
> this is not clear where this information here to me
> Matthew? do you know?
The most up-to-date list of ok contributors is at
http://www.squeaksource.com/
+1 to package
2009/2/28 Rob Rothwell :
> I kind of like that Package idea...although I have years of QBColor(13) to
> overcome...!
>
> On Fri, Feb 27, 2009 at 9:18 AM, Stéphane Ducasse
> wrote:
>>
>> > http://code.google.com/p/pharo/issues/detail?id=112
>> >
>> > Who thinks that we should add the
I kind of like that Package idea...although I have years of QBColor(13) to
overcome...!
On Fri, Feb 27, 2009 at 9:18 AM, Stéphane Ducasse wrote:
> > http://code.google.com/p/pharo/issues/detail?id=112
> >
> > Who thinks that we should add these colors? These are more than 100
> > additional name
Hello Stef,
i designed own little thingy to intercept any message sent to an
object, including #DNU.
See, if it can be useful for you.
As an example there is a subclass (CVMsgHandlingProxy) which i'm using
to write an inline code to handle messages right in place where i
creating a proxy:
superR
>> Just curious: Did you load this versions by hand? Because those versions of
>> OB are
>> still alpha, so we have to expect dev-dev behavior in those. ;)
>
> pharo-dev is now based on #loadOBAlpha.
ah.
Hm, not sure whether this is convenient. I mean every commit to the OB
repository has
to
> so what about Morph's abuse of includesSelector: would it be
> confused by asking ProtoObject instance if it
> understands #lalaland:
I have to think :)
Right now it freezes hard :)
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.
Hi guys
I would like to add redefinedMethods in class and friend. Because this
is useful.
Do you know if something like that already exist?
Point selectors intersection: (Point allSuperclasses inject: Set new
into: [:sum :each | sum addAll: each selectors; yourself])
Stef
__
Philippe,
One idea: Kom needs MIME support, Swazoo does not. So in case of Swazoo
you deal with a MIME in web server adapter, right?
What if you do the same, use your own MIME support in adapter for Kom as
well?
Best regards
Janko
Philippe Marschall pravi:
> Stéphane Ducasse wrote:
>> I have pr
so what about Morph's abuse of includesSelector: would it be confused
by asking ProtoObject instance if it
understands #lalaland:
On 27-Feb-09, at 10:02 AM, Stéphane Ducasse wrote:
> John
>
> normally when a method is not found I copy it from the class to the
> empty copy so slowly it gets
On Feb 27, 2009, at 6:51 PM, Igor Stasenko wrote:
> 2009/2/27 Stéphane Ducasse :
>> May be this can be useful to have that defined in ContextPart
>>
> this is definitely useful to hackers, who playing with contexts.
> But code which deals with contexts is uncommon thing.
but when you need it you
John
normally when a method is not found I copy it from the class to the
empty copy so slowly it gets automagically filled
up. This is fun you see the result of your actions live.
So normally I should not have the problem you describe. In fact the
first thing I tried was to inspect the object
2009/2/27 Stéphane Ducasse :
> May be this can be useful to have that defined in ContextPart
>
this is definitely useful to hackers, who playing with contexts.
But code which deals with contexts is uncommon thing.
From this point i see it worth adding only to have a complete coverage
of ways to acc
Well for the objective C bridge
MCHttpRepository
location: 'http://www.squeaksource.com/ObjectiveCBridge2'
user: ''
password: ''
I used ProtoObject as the super class of the ObjectiveCObject and
supplied doesNotUnderstand: to forward messages to the
Objective-C plugin fo
Hi
I wanted to see what is used in Morph so I did the following
Define a subclass of ProtoObject and redefnied DNU as follow
doesNotUnderstand: aMessage
| sel category |
sel := aMessage selector.
Transcript show: 'Does not understand ', aMessage selector
printString
>>>
> With my changes to Pharo (which of course first need to be
> integrated),
I will integrate them this evening.
>
> the changed (not forked!) version of Kom and the few changes for
> Seaside
> (which need to be integrated) there is no need for a fork!!!
>
> Those versions should work on b
So you even got a solution :)
Excellent!
But this is also a good point because it means that for the future
we will have again this kind of discussion.exciting.
Stef
On Feb 27, 2009, at 6:06 PM, Michael Rueger wrote:
> Philippe Marschall wrote:
>> Stéphane Ducasse wrote:
>>> I have problems
you know I guess that I know what is maintenance.
>> I have problems to understand why this would be not reasonable that
>> people load a give kom version for seaside on squeak
>> and one for seaside on pharo.
>
> Loading is one thing. What bothers we more is the maintenance
> situation.
> Let's
Philippe Marschall wrote:
> Stéphane Ducasse wrote:
>> I have problems to understand why this would be not reasonable that
>> people load a give kom version for seaside on squeak
>> and one for seaside on pharo.
>
> Loading is one thing. What bothers we more is the maintenance situation.
> Let's f
Stéphane Ducasse wrote:
> On Feb 25, 2009, at 5:59 PM, Michael Rueger wrote:
>
>> Lukas Renggli wrote:
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
Stéphane Ducasse wrote:
> I have problems to understand why this would be not reasonable that
> people load a give kom version for seaside on squeak
> and one for seaside on pharo.
Loading is one thing. What bothers we more is the maintenance situation.
Let's face it, there are far too resources b
May be this can be useful to have that defined in ContextPart
arguments
"returns the arguments of a message invocation"
| arguments numargs |
numargs := self method numArgs.
arguments := Array new: numargs.
1 to: numargs do: [:i | arguments at: i p
On Feb 27, 2009, at 12:02 PM, Lukas Renggli wrote:
> On Fri, Feb 27, 2009 at 10:30 AM, Stéphane Ducasse
> wrote:
>> I have problems to understand why this would be not reasonable that
>> people load a give kom version for seaside on squeak
>> and one for seaside on pharo.
>
> The problem is that
> http://code.google.com/p/pharo/issues/detail?id=112
>
> Who thinks that we should add these colors? These are more than 100
> additional named colors like #paleGoldenrod, #mediumOrchid, #thistle,
> etc.
>
> I'd vote against adding them since I don't see their merit.
>
> Other opinions?
we could
http://code.google.com/p/pharo/issues/detail?id=112
Who thinks that we should add these colors? These are more than 100
additional named colors like #paleGoldenrod, #mediumOrchid, #thistle,
etc.
I'd vote against adding them since I don't see their merit.
Other opinions?
Cheers,
Adrian
On Fri, Feb 27, 2009 at 12:02 PM, Lukas Renggli wrote:
> The problem is that people load released versions from SqueakMap or
> Package Universe. As long as Pharo shares the Squeak Package Universe
> there is no way of cleanly deciding which version of Kom to load.
Pharo will probably have its own
> Second the fix is not that ugly. It just sends #asString to something it
> expects to be a String. This is not a that uncommon idiom. And we
> already have to do something way uglier for ensuring author initials.
>
How about taking the Author initials stuff from pharo, and publishing it
as a
On Fri, Feb 27, 2009 at 10:30 AM, Stéphane Ducasse
wrote:
> I have problems to understand why this would be not reasonable that
> people load a give kom version for seaside on squeak
> and one for seaside on pharo.
The problem is that people load released versions from SqueakMap or
Package Univer
That's a known problem, see "[Pharo-project] MIMEdatabase fix?".
As a workaround use an old Pharo image from around December.
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http:/
Hi, I downloaded latest pharo-dev from the downloads page, and executed this:
Installer universe install: 'Seaside'.
But it fails, I'm getting a DNU on MIMEDocument>>resetMIMEdatabase... :(
Cheers,
Esteban
___
Pharo-project mailing list
Pharo-proje
2009/2/26 Norbert Hartl :
> On Thu, 2009-02-26 at 07:45 -0800, Michael Rueger wrote:
>> Keith Hodges wrote:
>>
>> >> We will include it.
>> >>
>> >>
>> >> Thanks, we will try with Pharo then.
>> >> Lautaro Fernández
>> > I am confused. Surely you would expect a loadable package to remain
>> > l
Hi henrik
(I should check that your fax arrived :)
Ideally we should check that the guy sign the squeak MIT agreement but
this is not clear where this information here to me
Matthew? do you know?
I could add that next to the list of ok committers.
If the code is not MIT we do not
I agree.
Am 26.02.2009 um 17:19 schrieb Janko Mivšek:
>
> Announcements will soon become as core as Morphic, actually even more,
> because they can replace the existing event mechanism in Morphic. VW
> guys actually did that in their GUI, so this is proven in practice.
>
> Therefore it is good for
Yes... time time time...
Stef
On Feb 26, 2009, at 11:30 PM, John M McIntosh wrote:
>>> Hi,
>>> I just saw the list of pending packages for pharo-dev and I noted
>>> that
>>> there is a package made by me (OB-Algernon), it is a little package
>>> with few changes to algernon...
>
>
> I if I might
On
> Luigi was one of the best students I ever worked with. He worked very
> hard on Safarà and I am impressed by the result, especially given that
> he was relatively new to Smalltalk and Squeak when the project
> started. He has a strong background in Lisp and Emacs and therefore
> has good know
thanks!
put a nice stamp :)
Stef
On Feb 27, 2009, at 2:54 AM, Rob Rothwell wrote:
> Ok...it may take a while to get there from the United States!
>
> Rob
>
> On Thu, Feb 26, 2009 at 6:19 AM, Stéphane Ducasse > wrote:
> we do not have problem in the future...
>
> http://pharo.gforge.inria.fr/lice
I have problems to understand why this would be not reasonable that
people load a give kom version for seaside on squeak
and one for seaside on pharo.
If you put too much constraints then do not cry after that squeak code
is shitty
because it is.
On Feb 27, 2009, at 7:39 AM, Philippe Marschall
Hi philppe
If seaside people does not help then you should not complain that
Squeak sucks
and that nothing is fixed.
So what is important it to find what is reasonable to do. So either
help and we will
arrive to a fix point or don't complain for the next 5 years.
Stef
> Michael Rueger wrot
Hi esteban
two questions:
- what is the license of algernon?
MIT I hope
- then to sign the agreement this is easy you print the page and sign
it.
http://pharo.gforge.inria.fr/licenseDocuments/
Stef
On Feb 26, 2009, at 7:42 PM, Esteban Lorenzano wrote:
> Hi,
> I
do you think that this is a matter of running a profiler or that there
is something
consuming too much messages (double dispatch or something like that?)
Do you know if its author would like to continue in a SummerTalk or
related?
Stef
On Feb 26, 2009, at 8:33 PM, Lukas Renggli wrote:
>> Is
39 matches
Mail list logo
