On Mar 2, 2009, at 1:34 AM, Rob Rothwell wrote:
> I notice that the current median is:
>
> median
> "Return the middle element, or as close as we can get."
>
> ^ self at: self size + 1 // 2
>
> Any reason not to make that accurate and return the average of the
> middle two values for co
excellent!
I'm happy.
>>> With my changes to Pharo (which of course first need to be
>>> integrated),
>>
>> I will integrate them this evening.
>
> A quick test with loading the following packages into both the latest
> Pharo and a Squeak 3.9.1 image seemed to work :-)
>
> from http://www.squeakso
>> I continued to code a little tool based on code of Alain to detect
>> deadcode, so far I'm too sick to have clear
>> idea why it freezes on Morph.
>
> This kinda reminds me of that moment in the horror film when you
> want to
> yell "Don't go in there!" at the characters on the screen.
lol
E
Stéphane Ducasse wrote:
> Hi
>
> I continued to code a little tool based on code of Alain to detect
> deadcode, so far I'm too sick to have clear
> idea why it freezes on Morph.
This kinda reminds me of that moment in the horror film when you want to
yell "Don't go in there!" at the charact
Matthew,
By the right thing too soon, I think there are influential people who are not
yet ready to allow Squeak to change. I do not necessarily agree that Stef et
al. have rekindled interest in Smalltalk so much as they have given many new
hope for Squeak to realize its potential to be a clea
On Sun, Mar 01, 2009 at 11:12:23PM -0500, Matthew Fulmer wrote:
> I know this is deep stuff, but I believe an automated image
> builder will have several advantages, both for you, as Pharo
> developers, and for me, as an enthusiast for cross-squeak
> compatibility:
> - making releases is faster
> -
On Sun, Mar 01, 2009 at 08:47:53PM -0500, Schwab,Wilhelm K wrote:
> My sense is that Matthew is doing the right thing, with the best of
> intentions, but might be trying it too soon.
I would appreciate it if you would expand on that.
> Pharo is establishing a spirit of finding the common prob
Hi Alain, this sounds very interesting. I have never been a big fan of the
current "Preference Browser". I am now trying to grasp (still learning
here) how this new "Pharo Preference Mechanism" works. It would be great if
the mechanism could be explained in detail in something like the new Phar
Stef,
If you need a break from the noise, I would probably encourage you to "take a
vacation" from Squeak rather than to "quit." I still wonder whether I have
found everything that was said, which I mention only to excuse myself if I'm
missing something important.
My sense is that Matthew is
Well, I work in a Six Sigma department so...!
Anyway, I agree that your proposal could be interesting...what do you think
of the current implementations in Pharo?
#median, for example, doesn't seem to be used anywhere except as an
"approved" method name in MethodFinder>>initialize...
Take care,
On Mon, Mar 2, 2009 at 1:34 PM, Rob Rothwell wrote:
> I notice that the current median is:
>
> median
> "Return the middle element, or as close as we can get."
>
> ^ self at: self size + 1 // 2
>
> Any reason not to make that accurate and return the average of the middle
> two values for
I notice that the current median is:
median
"Return the middle element, or as close as we can get."
^ self at: self size + 1 // 2
Any reason not to make that accurate and return the average of the middle
two values for collections containing an even number of items?
Or...better yet...sh
2009/3/1 Stéphane Ducasse :
> Hi guys
>
> I probably should not have forwarded to you the email I replied to
> matthew
> but I was thinking that other people can know that I was personally
> touched
> by the situation in Squeak.
> I'm sorry about.
>
> We got a lot of bird names and others. Recently
Stéphane Ducasse wrote:
>> With my changes to Pharo (which of course first need to be
>> integrated),
>
> I will integrate them this evening.
A quick test with loading the following packages into both the latest
Pharo and a Squeak 3.9.1 image seemed to work :-)
from http://www.squeaksource.co
On Mar 1, 2009, at 11:32 PM, Mariano Martinez Peck wrote:
> I have the blame of it. I am who send emails to both list. So...this
> is my fault.
No don't be sorry. The situation is stupid.
> Sorry about it. The main problem I have is that when I have
> questions, suggestions, ideas or whatev
tx
Stef
On Mar 1, 2009, at 10:46 PM, Sebastian Sastre wrote:
> Hi Stephane, I would not take it that seriously. Just focus that
> good energy you
> have and use it in getting things done in pharo and adding real
> value to it.
> Much it will receiver in return I'm sure of that.
> best,
> seb
I have the blame of it. I am who send emails to both list. So...this is my
fault.
Sorry about it. The main problem I have is that when I have questions,
suggestions, ideas or whatever, I really don't know where to post it: if in
squeak-dev or pharo. I really don't know If what I want to say depend
Hi
I continued to code a little tool based on code of Alain to detect
deadcode, so far I'm too sick to have clear
idea why it freezes on Morph. However it works on ClockMorph and
IconicButton.
If you want to have fun save your image before
MCHttpRepository location: 'http://www.squeak
Talking about colors, Mondrian for Squeak includes few color
normalizers...
Cheers,
Alexandre
On 27 Feb 2009, at 15:18, 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 named
What is split/join?
Alexandre
On 1 Mar 2009, at 19:22, Stéphane Ducasse wrote:
> I think that there was a split/join package somewhere.
> Does anybody know where it is?
> At one point it was planned to get added to squeak and nothing
> happened.
>
> Stef
>
>
Stéphane Ducasse-2 wrote:
>
> ... and I will not justify anymore why I quit. Now I want pharo to be
> cool.
> Stef
>
Good on ya mate! :)
--
View this message in context:
http://n2.nabble.com/A-point-a.k.a-excuse-to-you-tp2406159p2406200.html
Sent from the Pharo Smalltalk mailing list archive
On 01.03.2009, at 22:29, Stéphane Ducasse wrote:
> Hi guys
>
> I probably should not have forwarded to you the email I replied to
> matthew
> but I was thinking that other people can know that I was personally
> touched
> by the situation in Squeak.
> I'm sorry about.
>
> We got a lot of bird nam
Hi Stephane, I would not take it that seriously. Just focus that good energy you
have and use it in getting things done in pharo and adding real value to it.
Much it will receiver in return I'm sure of that.
best,
sebastian
> -Mensaje original-
> De: pharo-project-boun...@lists.gforge.inr
Hi guys
I probably should not have forwarded to you the email I replied to
matthew
but I was thinking that other people can know that I was personally
touched
by the situation in Squeak.
I'm sorry about.
We got a lot of bird names and others. Recently somebody was implying
that
marcus was b
Oscar Nierstrasz wrote:
> Here it is:
>
> http://www.squeaksource.com/RubyShards.html
>
>
Here it is
http://bugs.squeak.org/view.php?id=4874
Keith
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-b
That's the best possible place :D
cheers
sebastian
> -Mensaje original-
> De: pharo-project-boun...@lists.gforge.inria.fr
> [mailto:pharo-project-boun...@lists.gforge.inria.fr] En
> nombre de Adrian Lienhard
> Enviado el: Sunday, March 01, 2009 16:41
> Para: Pharo-project@lists.gforge.i
Good idea.
We can set up a blog on the Pharo web site. Will add this to my todo
list...
Adrian
On Mar 1, 2009, at 20:32 , Sebastian Sastre wrote:
> Actually I was thinking simple :)
> I had in mind a well writen blog post with that script, talking how
> cool and fun
> the environment is with
Here it is:
http://www.squeaksource.com/RubyShards.html
- on
On Mar 1, 2009, at 19:22, Stéphane Ducasse wrote:
> I think that there was a split/join package somewhere.
> Does anybody know where it is?
> At one point it was planned to get added to squeak and nothing
> happened.
>
> Stef
>
> __
Actually I was thinking simple :)
I had in mind a well writen blog post with that script, talking how cool and fun
the environment is with those and maybe mentioning why good UI helps do better
software. Just that could be teasing about pharo to an outsider.
Of course the a blog should be for bran
Oh...I get it!
What would be nice about Fonts (unlike window appearances), is that you
could EASILY define your own custom themes as well, just by saving your
current settings. Then you could save them somehow for re-use when the next
version of the image came out!
Again, this would be hard for
Thanks for the feedback, Pavel.
I tagged these issues with Milestone-1.0 and reopened issue 71 since
it seems still open according to the comment below.
Cheers,
Adrian
On Mar 1, 2009, at 18:18 , Stéphane Ducasse wrote:
>
>>
>> Hi Stef,
>>
>> there are some opened issues so we may start with t
Rob Rothwell wrote:
> I kind of like the idea, but I'm not sure what the UI would look like?
> Is it the option of choosing the same font for multiple purposes that is
> attractive?
Not necessarily just the same font name but as with the UI themes a
group of settings that work well together.
Y
I kind of like the idea, but I'm not sure what the UI would look like? Is
it the option of choosing the same font for multiple purposes that is
attractive?
I also do something like:
Preferences addBooleanPreference: #ScanAtStartup categories: #(FreeType)
default: false balloonHelp: 'select t
Rob Rothwell wrote:
> And if you get tired of setting your fonts individually, you can set
> them all at once:
we should add something like that as font themes to the preferences?
Michael
>
> font := LogicalFont familyName: 'Andika Basic' pointSize: 10.
> codeFont := LogicalFont family
The refactoring browser has this:
genericPatternForSelector: aSymbol
^ String streamContents: [ :stream |
aSymbol keywords keysAndValuesDo: [ :index :value |
stream space; nextPutAll: value.
aSymbol last = $:
may be we should add it somewhere in symbol because this is handy when
you want to generate methods on the fly.
signatureFromSelector: aSelector
"self new signatureFromSelector: #foo:bar: "
"self new signatureFromSelector: #foo"
"self new signatureFromSelector: #foo:"
I think that there was a split/join package somewhere.
Does anybody know where it is?
At one point it was planned to get added to squeak and nothing
happened.
Stef
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge
Hi
does one of you get to know a method for doing that?
#foo:bar:
-> foo: arg1 bar: arg2
Stef
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Hi sebastian
So far we only have the web site and the code.google site.
I'm not really a blogger (I'm writing too much other stuff --- soon
you will see :).
But if somebody would like to have a blog I would happily read and
comment.
> I'm happy to see that pharo has a lot to be a winner
I can
Lukas: good news! thanks for it. I tried to test it but doesn't work for me.
I updated the packages you said but after then, I am trying to open a system
browser and I get the following error.
I guess I must update another package, but I don't know. Anyway, don't
worry. I can test it then when all
>
> Hi Stef,
>
> there are some opened issues so we may start with them:
> 310 and 311 - the goal is to be able to unload all tests. As Adrian
> sugested, we may place it the package Tests - at least for now.
> 346 - easy and safe to integrate
> 348 - very important issue. Maybe you should place i
great script thanks!
hey Pharo project already has an official blog? I mean, I image how good this
simple things would help to propagate the pharo ideavirus when posted in cool
posts by a team of developers. Ideally a team of authors with a an editor (to
filter possible misconceptions about pharo p
Damien
it should be fixed. At least I integrated in 10245 the latest fixes of
mike.
So may be now you just need to load the Kom package which is in the
inbox.
If you give a try let us know.
Stef
On Mar 1, 2009, at 6:09 PM, Damien Cassou wrote:
> On Sat, Feb 28, 2009 at 2:41 PM, Sebastian Sast
Thanks!
I will check that. Now I'm getting sick :(
Stef
On Mar 1, 2009, at 6:11 PM, Pavel Krivanek wrote:
> Hi,
>
> I added some code to the issue 467 so all obsolete classes can be
> removed (part of Milestone-1.0)
>
> Cheers,
> -- Pavel
>
> ___
> Ph
Hi,
I added some code to the issue 467 so all obsolete classes can be
removed (part of Milestone-1.0)
Cheers,
-- Pavel
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-projec
On Sat, Feb 28, 2009 at 2:41 PM, Sebastian Sastre wrote:
> first of all thanks for making Pharo. I can see there is a lot to do but I'm
> so
> glad to see an open smalltalk evoluting in such a direction.
>
> I wanted to give a try with a web app I'm porting to seaside 2.9a2 but it
> won't
> load
On Fri, Feb 27, 2009 at 9:34 PM, David Röthlisberger wrote:
> Hm, not sure whether this is convenient. I mean every commit to the OB
> repository has
> to be tested very carefully then, and I cannot commit experimental features
> anymore,
> because they automatically get loaded with #loadOBAlpha
Should I post an issue?
Thank your,
Rob
On Sun, Mar 1, 2009 at 7:54 AM, Adrian Lienhard wrote:
> Seems a problem in OB: OBDBSuperSend sends #superSenderSelectors,
> which is not implemented.
>
> Adrian
>
> On Feb 28, 2009, at 19:06 , Rob Rothwell wrote:
>
> > Maybe I just wasn't able to follow
And if you get tired of setting your fonts individually, you can set them
all at once:
font := LogicalFont familyName: 'Andika Basic' pointSize: 10.
codeFont := LogicalFont familyName: 'DejaVu Sans Mono' pointSize: 9.
Preferences setListFontTo: font.
Preferences setMenuFontTo: font
It suddendly started to work, I think it was SqueakFFIPrims.dll that was missing
cheers,
sebastian
> -Mensaje original-
> De: pharo-project-boun...@lists.gforge.inria.fr
> [mailto:pharo-project-boun...@lists.gforge.inria.fr] En
> nombre de Sebastian Sastre
> Enviado el: Sunday, March 0
hi there,
sorry for the noob question but I see pharo has freetype in the image but it's
only accuny font among options. Shouldn't freetype read the fonts on the system
and offer those too?
thanks,
sebastian
___
Pharo-project mailing list
Pharo-project
Bill,
On Sun, 2009-03-01 at 09:23 -0500, Schwab,Wilhelm K wrote:
> Norbert,
>
> I agree re aliases, but only to a point. When trying to be compatible with
> other dialects, the aliases spare many other users from independently having
> to add them. When it is reasonable, I have no problem wit
Dear Smalltalkers,
After one year I'm glad to announce a new release 2.2 of Swazoo
Smalltalk Web Server, currently just for Squeak and VisualWorks.
What is new?
* upload streaming 30 times better for large file uploads
* additional improvements of streamed upload performance, as a result
Stéphane
your previous question makes me think of a better solution
with requires only one mandatory class and which makes use of
standard event notification (without PreferenceCollector).
I've joined 4 packages :
- PrefCore contains PreferenceValue which is now the only mandatory class.
2 pac
Norbert,
I agree re aliases, but only to a point. When trying to be compatible with
other dialects, the aliases spare many other users from independently having to
add them. When it is reasonable, I have no problem with it. This is another
example of how nice it would be to have Dolphin's ab
On Mar 1, 2009, at 10:47 AM, Tudor Girba wrote:
> I copied it to the repository of Lukas as well.
I did not see it when I did the release.
>
>
> Does anyone actually see a reason for not having the when:do: method
> in as an alias to on:do:? I do not see it.
>
> Cheers,
> Doru
>
>
> On 1 Mar 2
On Sun, 2009-03-01 at 10:47 +0100, Tudor Girba wrote:
> I copied it to the repository of Lukas as well.
>
> Does anyone actually see a reason for not having the when:do: method
> in as an alias to on:do:? I do not see it.
>
Because then there is
on:do:
subscribe:do:
when:do:
with all for: and
Seems a problem in OB: OBDBSuperSend sends #superSenderSelectors,
which is not implemented.
Adrian
On Feb 28, 2009, at 19:06 , Rob Rothwell wrote:
> Maybe I just wasn't able to follow the conversation properly, but if
> you
> open a Transcript in 10243 (dev) and, say, search for the class
>> Not at the moment, I noticed myself several times that this would be
>> useful. If I find time, I will have a look at it tomorrow.
>
> No problem. I was just asking :)
Update in this order:
1. AST-lr.164
2. Refactoring-Core-lr.40
3. OB-Refactory-lr.141
4. OB-Regex-lr.15
To get case insensiti
Lukas Renggli writes:
>
> > Is it possible to configurate the search engine to case no sensitive ?
>
> Not at the moment, I noticed myself several times that this would be
> useful. If I find time, I will have a look at it tomorrow.
>
> > Suppose you have more than 1 match of what you are look
Stéphane Ducasse a écrit :
> sounds cool.
> For me the most important aspect is that preferenceCollector (our
> current preference class should be a removable layer on top
> of the system that are declaring preference.
>
> Is is correct that
>
> PreferenceCollector whenChanged: #gradientButtonLoo
I copied it to the repository of Lukas as well.
Does anyone actually see a reason for not having the when:do: method
in as an alias to on:do:? I do not see it.
Cheers,
Doru
On 1 Mar 2009, at 10:19, Stéphane Ducasse wrote:
> Where?
> It was not on lukas source and in the pharo inbox
> Then th
Begin forwarded message:
> From: Stéphane Ducasse
> Date: February 28, 2009 2:07:42 PM CEST
> To: Matthew Fulmer
> Cc: Marcus Denker
> Subject: Re: Some personal thoughts and questions about Pharo
>
> Hi matthew
>
>
>> Hi. I stumbled across a rather interesting email while I was
>> researchin
sounds cool.
For me the most important aspect is that preferenceCollector (our
current preference class should be a removable layer on top
of the system that are declaring preference.
Is is correct that
PreferenceCollector whenChanged: #gradientButtonLook inClass:
PrefProvider notify: self
Where?
It was not on lukas source and in the pharo inbox
Then there is the question to be sure if we want it.
On Mar 1, 2009, at 9:56 AM, Tudor Girba wrote:
> Hi Stef,
>
>> Some more happy people :)
>>
>> - Announcements-lr.10 from souce.lukas-renggli.ch
>> Is when:do: not missing for
For the ones that were not there at that time.
Study history as always been a way to understand the present :)
Begin forwarded message:
> From: Matthew Fulmer
> Date: February 28, 2009 6:26:00 AM CEST
> To: Marcus Denker , St?phane Ducasse
> >
> Cc: Matthew Fulmer
> Subject: Some personal th
Hi guys
I think that we should pay attention that people do not say stupid
stuff on us on squeak-dev (even if this is not that
important ;) ).
Stef
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-b
Hi all,
joined Zoo package is a attempt to translate in code what we discussed
here before about preference refactoring.
The framework is made of 3 classes: PreferenceCollector,
PreferenceDefinition and PreferenceValue.
In Zoo there are also 2 classes for testing: PrefProvider and
PrefChang
Hi Stef,
> Some more happy people :)
>
> - Announcements-lr.10 from souce.lukas-renggli.ch
> Is when:do: not missing for compatibility with VW?
I published a new version containing when:do: Announcements-tg.11.
Cheers,
Doru
>
> - Polymorph
> Fix for button for cu
Begin forwarded message:
From: Eliot Miranda
Date: March 1, 2009 8:08:46 AM CEST
To: The general-purpose Squeak developers list >
Subject: Re: [squeak-dev] recategorize a bunch
Reply-To: The general-purpose Squeak developers list >
On Sat, Feb 28, 2009 at 7:42 PM, Sebastian Sastre > wrot
Some more happy people :)
- Announcements-lr.10 from souce.lukas-renggli.ch
Is when:do: not missing for compatibility with VW?
- Polymorph
Fix for button for currently selected window in tasklist not being
differentiated when using Watery 2 theme.
71 matches
Mail list logo
