Sean P. DeNigris wrote:
EstebanLM wrote
I started thinking on next release of Pharo 1.4 (which will be code named
"summer", not an ugly number).
Re browsers... I would definitely include either OB or Nautilus. The default
is just too limiting. Nautilus does seem to be in a pretty usable s
Igor Stasenko wrote
>
> because 'announcer weak subscribe: ' is explicit
>
Either way, something is implicit. Why not make the common case implicit and
the uncommon one slightly more verbose? "Make common things easy, rare
things possible"
b.t.w. I like that we are all independently discoverin
On 16 June 2012 23:12, Guillermo Polito wrote:
> So, what about making weak a default and notWeak the explicit one? :D
>
you can, but this could lead to confusion.
because 'announcer weak subscribe: ' is explicit
while 'announcer subscribe: ' is implicit..
so i would leave it like it is now.
>
>
My 2cts is for some event (and I think *modified is part of them), you got the
event twice: before and after.
So basically, one of the two events is wrong.
Mariano, you should try to put an halt, and see :)
Ben
On Jun 16, 2012, at 10:26 PM, Guillermo Polito wrote:
> Yeah, but logging superflu
If I search senders of 'foo' I do get those method that has #foo inside.
However, if I search class references to Bar, it doesn't found methods that
have something like Smalltalk at: #Bar.
shouldn't it also find this?
thanks
--
Mariano
http://marianopeck.wordpress.com
2012/6/16 Stéphane Ducasse :
>
> On Jun 16, 2012, at 11:00 AM, Nicolas Cellier wrote:
>
>> 2012/6/16 Stéphane Ducasse :
On Jun 15, 2012, at 12:06 PM, Stéphane Ducasse
wrote:
> why do you need an automatic new method?
> Because by default
> new invoke initial
So, what about making weak a default and notWeak the explicit one? :D
On Sat, Jun 16, 2012 at 11:09 PM, Igor Stasenko wrote:
> On 16 June 2012 22:51, Mariano Martinez Peck
> wrote:
> > Hi, with the help of Guille I noticed that normal instances usually
> register
> > weakly:
> >
> > TestRunner
On 16 June 2012 22:51, Mariano Martinez Peck wrote:
> Hi, with the help of Guille I noticed that normal instances usually register
> weakly:
>
> TestRunner >> initialize
> .
> SystemAnnouncer current
> weak
> on: ClassAdded, CategoryAdded, ClassRemoved, CategoryRemoved,
> Class
In fact, a new instance IS initialized by VM, by putting nil values to each slot
and zeroes in case of byte array.
What happens next, when you sending #initialize? Yes, you rewriting these values
by own, which sound like initial nil-out of all slots was unnecessary.
So, in some cases it could be le
I do not know... Python and Ruby are kind of popular too without needing
such kind of prefixes... I thing we should be original in the name :), and
that's all...
On Sat, Jun 16, 2012 at 10:50 PM, p...@highoctane.be wrote:
> http://en.wikipedia.org/wiki/Java_version_history isn't too bad either
>
Hi, with the help of Guille I noticed that normal instances usually
register weakly:
TestRunner >> initialize
.
SystemAnnouncer current
weak
on: ClassAdded, CategoryAdded, ClassRemoved, CategoryRemoved,
ClassRenamed, CategoryRenamed, ClassRecategorized send: #update to: self.
.
http://en.wikipedia.org/wiki/Java_version_history isn't too bad either
with Update x suffix.
Pharo SE 4 Update 2 ... there is some good marketing touch to that
given the popularity of Java.
They switched after 1.4 - As an innovative platform, maybe we can switch now :-)
2.0 would become Pharo SE
Anyway, we need to learn if we want to create things with something
else than new...
But I like basicNew initialize the way it is now.
2012/6/16 Stéphane Ducasse :
>>
>> Stéphane, would you mind expanding a bit on what mistake CLOS didn't make?
>
> create-instance invokes initialize-instance in C
We are closing the gap with Java versions... Pharo 1.6.3_047 nearing...
2012/6/16 Mariano Martinez Peck :
>
>
> On Sat, Jun 16, 2012 at 3:34 PM, Philippe Marschall wrote:
>>
>> On 13.06.2012 11:08, Esteban Lorenzano wrote:
>>>
>>> Hi,
>>>
>>> I started thinking on next release of Pharo 1.4 (which
Yeah, but logging superfluous changes does not really make a change, does
it?
On Sat, Jun 16, 2012 at 10:04 PM, Stéphane Ducasse <
stephane.duca...@inria.fr> wrote:
> may be because the source changes was listening to the event.
> And the log file needed to log any thing like doits and other.
>
>
On 16 June 2012 21:07, Stéphane Ducasse wrote:
>>
>> Stéphane, would you mind expanding a bit on what mistake CLOS didn't make?
>
> create-instance invokes initialize-instance in CLOS for every class.
>
> In Smalltalk (not squeak or pharo), new does not invoke initialize. Now CLOS
> arrived 10 ye
On Sat, Jun 16, 2012 at 10:06 PM, Stéphane Ducasse <
stephane.duca...@inria.fr> wrote:
>
> On Jun 16, 2012, at 8:14 PM, Schwab,Wilhelm K wrote:
>
> > Stef,
> >
> > I have had experts on it tell me exactly the opposite. Things like
> "always load specific versions" and "never load symbolic version
>
> Stéphane, would you mind expanding a bit on what mistake CLOS didn't make?
create-instance invokes initialize-instance in CLOS for every class.
In Smalltalk (not squeak or pharo), new does not invoke initialize. Now CLOS
arrived 10 years after Smalltalk and we fixed
that problem in our love
On Jun 16, 2012, at 8:14 PM, Schwab,Wilhelm K wrote:
> Stef,
>
> I have had experts on it tell me exactly the opposite. Things like "always
> load specific versions" and "never load symbolic versions." They mean well
> (and have been helpful in the short term), but it is far from a generic
may be because the source changes was listening to the event.
And the log file needed to log any thing like doits and other.
On Jun 16, 2012, at 9:14 PM, Mariano Martinez Peck wrote:
> Hi guys. ChangeSet does at some point:
>
> anEvent itemKind = SystemChangeNotifier classKind ifTrue: [
>
On 16 June 2012 10:46, Stéphane Ducasse wrote:
>
> On Jun 16, 2012, at 11:00 AM, Nicolas Cellier wrote:
>
>> 2012/6/16 Stéphane Ducasse :
On Jun 15, 2012, at 12:06 PM, Stéphane Ducasse
wrote:
> why do you need an automatic new method?
> Because by default
>
On Sat, Jun 16, 2012 at 3:34 PM, Philippe Marschall wrote:
> On 13.06.2012 11:08, Esteban Lorenzano wrote:
>
>> Hi,
>>
>> I started thinking on next release of Pharo 1.4 (which will be code named
>> "summer", not an ugly number).
>>
>
> It's only summer in the northern hemisphere. Eclipse renamed
On Sat, Jun 16, 2012 at 9:19 PM, Guillermo Polito wrote:
> I do not care to write extra stuff into the changes file. My hd is large
> enough to handle some extra kilobytes...
>
>
Usually, people do not add this kind of stuff just because. There is a
reason behind. This method looks from 2004 (by
I do not care to write extra stuff into the changes file. My hd is large
enough to handle some extra kilobytes...
On Sat, Jun 16, 2012 at 9:14 PM, Mariano Martinez Peck <
marianop...@gmail.com> wrote:
> Hi guys. ChangeSet does at some point:
>
> anEvent itemKind = SystemChangeNotifier classKind
Hi guys. ChangeSet does at some point:
anEvent itemKind = SystemChangeNotifier classKind ifTrue: [
...
anEvent isModified
ifTrue: [anEvent anyChanges ifTrue: [self changeClass:
anEvent item
from: anEvent oldItem]].
anEven
So
If it helps at all, I was able (with help) to get sound working on Linux. It's
ugly: one has to copy/rename the plugin from another vm (to use cog). Once I
got it working, I flagged a copy of the plugin in the hopes of making things
easier next time.
Bill
_
Stef,
I have had experts on it tell me exactly the opposite. Things like "always
load specific versions" and "never load symbolic versions." They mean well
(and have been helpful in the short term), but it is far from a generic
solution. The "answer" will invariably be different "every time.
Can someone review these issues?
http://code.google.com/p/pharo/issues/detail?id=6073&colspec=ID%20Type%20Status%20Summary%20Milestone%20Difficulty
http://code.google.com/p/pharo/issues/detail?id=6074&thanks=6074&ts=1339860695
Be careful with the pre and post things to evaluate.
Tx!
> Haha, He will not discuss, but we can :).
:)
>
> The migration is also painful right now because system events are a mess. We
> have SystemChangeNotifier and SystemAnnouncer, and there is a nice hack to
> keep both working. SystemAnnouncer is registered to SystemChangeNotifier and
> old sys
sean this is not that we cannot discuss :)
this is that I'm physically tired too. So I need to rest and somebody has to do
the stuff at the end.
Stef
On Jun 16, 2012, at 2:44 PM, Sean P. DeNigris wrote:
>
> Stéphane Ducasse wrote
>>
>> sorry but I do not have the energy to discuss that public
On 13.06.2012 11:08, Esteban Lorenzano wrote:
Hi,
I started thinking on next release of Pharo 1.4 (which will be code named
"summer", not an ugly number).
It's only summer in the northern hemisphere. Eclipse renamed their
winter releases because it isn't winter in February in half of the wor
On Sat, Jun 16, 2012 at 2:44 PM, Sean P. DeNigris wrote:
>
> Stéphane Ducasse wrote
> >
> > sorry but I do not have the energy to discuss that publicly and via
> email.
> > The problem is that lot of people want a lot… and my energy is limited.
> >
>
> I understand your frustration, but if we can'
Stéphane Ducasse wrote
>
> sorry but I do not have the energy to discuss that publicly and via email.
> The problem is that lot of people want a lot… and my energy is limited.
>
I understand your frustration, but if we can't discuss important new
features on the developers list... wt#$@?!
--
V
EstebanLM wrote
>
> Marcus proposal is good: map RPackage with MCPackage...
>
That sounds right to me...
Mapping packages 1:1 with categories seems like perpetuating the "category =
package" hack I thought we were trying to finally fix...
Sean
--
View this message in context:
http://forum.w
Hi list,
I'm trying to get sound working in Pharo 1.4 (one-click), but the procedure
I used to follow in 1.3 is not working anymore.
I copied squak's pulse plugin to Contents/Linux and ran the image with the
-vm-sound-pulse flag, then DidIt: SoundService soundEnabled: true, but
nothing.
I also t
Marcus proposal is good: map RPackage with MCPackage, tag the subcategories
(RPackage allow adding attributes).
That solve all problems with few difficulties (and well... with time packages
will adapt)
this provides a transparent migration path, which is what we need.
Esteban
On Jun 16, 2012,
sorry but I do not have the energy to discuss that publicly and via email.
The problem is that lot of people want a lot… and my energy is limited.
Stef
On Jun 16, 2012, at 12:06 PM, Mariano Martinez Peck wrote:
>
>
> On Sat, Jun 16, 2012 at 5:41 AM, Sean P. DeNigris
> wrote:
> I was expectin
I am experimenting with that right now. Seems to work.
Envoyé depuis un mobile Samsung
Esteban Lorenzano a écrit :
Hi,
you are asking for two things there:
-a sound package for pharo 1.4 (I don't know if it exists, and in any
case we cannot add it as a core package, you need to install it a
Hi,
you are asking for two things there:
-a sound package for pharo 1.4 (I don't know if it exists, and in any case we
cannot add it as a core package, you need to install it and see how it works by
yourself)
-a working sound plugin for iOS. TBH, while I'm including it in regular
compilations
On Sat, Jun 16, 2012 at 5:41 AM, Sean P. DeNigris wrote:
> I was expecting "PackageOrganizer default packageOfClass: FileSystemError"
> to
> return "FileSystem-Core" but it returned "FileSystem-Core-Kernel", which is
> not a package. It's a category, but it's packaged in "FileSystem-Core". Is
> th
On Jun 16, 2012, at 11:00 AM, Nicolas Cellier wrote:
> 2012/6/16 Stéphane Ducasse :
>>>
>>>
>>> On Jun 15, 2012, at 12:06 PM, Stéphane Ducasse
>>> wrote:
>>>
why do you need an automatic new method?
Because by default
new invoke initialize
and it works well.
2012/6/16 Stéphane Ducasse :
>>
>>
>> On Jun 15, 2012, at 12:06 PM, Stéphane Ducasse
>> wrote:
>>
>>> why do you need an automatic new method?
>>> Because by default
>>> new invoke initialize
>>>
>>> and it works well.
>>>
>>
>> Stéphane, I have been using VW Smalltalk and it creates new classe
On Jun 16, 2012, at 12:57 AM, Schwab,Wilhelm K wrote:
> But if I'm building a new image *today*, I want it to do the right thing now
> (automatically for the current version), with the same incantation as worked
> months ago or months from now.
Bill when do you take the time to have a look at
On Jun 15, 2012, at 11:36 PM, p...@highoctane.be wrote:
> Well, spotlight is really cool indeed. Shift-Space XXX Enter. yay!
>
> But I like to have a view on several classes and typing HOPR¨helps.
>
> Same when exploring the system for doing something (like
> sound-synthesis for example).
>
>
>
>
> On Jun 15, 2012, at 12:06 PM, Stéphane Ducasse
> wrote:
>
>> why do you need an automatic new method?
>> Because by default
>> new invoke initialize
>>
>> and it works well.
>>
>
> Stéphane, I have been using VW Smalltalk and it creates new classes ,by
> default, with a #new method
doru
can you open a bug entry and provide necessary information?
Package and tests?
Stef
On Jun 16, 2012, at 8:07 AM, Tudor Girba wrote:
> Indeed. It would be great to integrate CollectionExtensions into Pharo.
>
> For example, we have:
> #(#(1) #(2 3) #(#(4) 5) ) deepFlatten
> ==> #(1 2 3
46 matches
Mail list logo
