I did not want to take this discussion further , because I dont like to annoy
people .
But some of the points made here are presented as facts and I don't like that.
Chris, in discussions about compatibility , people always missing to
mention one little thing:
users can always choose to
Guys
could you help us producing a better system instead of winning?
We ported pier to pharo 2.0 and it was fixed in less than one afternoon.
Do you want more examples?
Breaking compatibility is NOT central to pharo. But we do it when we have to.
Pharo is not a Smalltalk in a museum
Stef
Hi,
I assume, this is a bug in Pharo?
I select browse package in the System browser and then file out for the
category *Extensions.
Other categories work. Occurs also in *Extensions of other packages.
Is it fixed in Pharo 2.0?
Greetings
Sabine
15 December 2012 9:31:37 am
VM: Win32 - IX86 -
Hi Sabine.
Verified, that's a bug in 1.3.
In 2.0 the OBSystemBrowserAdaptor isn't loaded by default (I doubt that anyone
got it running (?)) and the default browser is Nautilus. So you don't actually
have that option in 2.0.
Nautillus shows extensions in separate extension categories. These
Some of these games are fun: http://scratch.mit.edu/
On 15 December 2012 05:43, Igor Stasenko siguc...@gmail.com wrote:
On 14 December 2012 21:26, Lawson English lengli...@cox.net wrote:
On 12/13/12 1:58 AM, Igor Stasenko wrote:
On 13 December 2012 09:54, dimitris chloupis
Hi guys,
Is there any technical reason that the old FileDirectory stuff doesn't
stay and work in parallel to a new FileSystem? Maybe in some package
marked obsolete. Both use the same plugin and the same primitives, so
where is the problem?
I also think that for a professionally viable product a
On Dec 14, 2012, at 5:32 PM, Sean P. DeNigris s...@clipperadams.com wrote:
Hey guys, what are your favorite features added in 2.0? Please answer at
http://code.google.com/p/pharo/wiki/ActionsInPharo20
There are so many improvements, I've definitely lost track. I remember there
were some
On 15 December 2012 10:27, Janko Mivšek janko.miv...@eranova.si wrote:
Hi guys,
Is there any technical reason that the old FileDirectory stuff doesn't
stay and work in parallel to a new FileSystem? Maybe in some package
marked obsolete. Both use the same plugin and the same primitives, so
Dne 15. 12. 2012 12:12, piše Igor Stasenko:
On 15 December 2012 10:27, Janko Mivšek janko.miv...@eranova.si wrote:
Is there any technical reason that the old FileDirectory stuff doesn't
stay and work in parallel to a new FileSystem? Maybe in some package
marked obsolete. Both use the same
Janko,
that's already done (since ever), and FD is provided in two different ways: in
the graveyard is the old FD package (loadable into pharo 2.0)
http://smalltalkhub.com/#!/~Pharo/Graveyard20 , and also Camillo made a FD
wrapper to FS...
Esteban
On Dec 15, 2012, at 12:31 PM, Janko Mivšek
On 15 December 2012 12:31, Janko Mivšek janko.miv...@eranova.si wrote:
Dne 15. 12. 2012 12:12, piše Igor Stasenko:
On 15 December 2012 10:27, Janko Mivšek janko.miv...@eranova.si wrote:
Is there any technical reason that the old FileDirectory stuff doesn't
stay and work in parallel to a new
Let me explain this once again: we are not backward compatibility killer
maniacs :)
We prefer to keep backward compatibility whenever is possible, but we don't put
it as a top priority: if we find room to improve, we do it.
but, since we take responsibility for all the packages loaded in what
On 14 December 2012 20:48, Jimmie Houchin jlhouc...@gmail.com wrote:
Hello,
In my app using NB and have a few questions on types.
In one function I have an size_t *arg
for an argument. Is NBUInt64 proper for this argument?
No. 'size_t*' is a pointer.
A size_t type defined as an unsigned
Hi Esteban,
I understand and support the cleanness focus, this is why Pharo actually
seems very promising for the future. Just that cleaning should be
gradual, in a sense that while introducing new you keep an old but
clearly marked as obsolete for a, say, year or two. So that user base
have a
Dne 15. 12. 2012 12:46, piše Igor Stasenko:
Hold on.. Since when Pharo project became professional product?
How much money you and others paying for using it?
Yes, we position it as a product FOR professionals,
but does it automatically makes a professional one?
I don't think so.
So, why
Hi,
what is the reason for integration of KeyChain/UsersManager to the image?
It created the next kernel dependency. Should it replace Author? Should it
be in the Pharo Kernel? And why there was no mention about it in this
mailing list before? ;-)
Cheers,
-- Pavel
On Fri, Dec 14, 2012 at 7:58 PM, Pavel Krivanek pavel.kriva...@gmail.comwrote:
On Fri, Dec 14, 2012 at 7:42 PM, Igor Stasenko siguc...@gmail.com wrote:
On 14 December 2012 19:33, Pavel Krivanek pavel.kriva...@gmail.com
wrote:
On Fri, Dec 14, 2012 at 7:17 PM, Igor Stasenko
it was in the list of things to integrate :)
but we should check to clean the dependence, because is not good.
Esteban
On Dec 15, 2012, at 2:16 PM, Pavel Krivanek pavel.kriva...@gmail.com wrote:
Hi,
what is the reason for integration of KeyChain/UsersManager to the image? It
created the
Well... the FD affaire was discussed in this list like 6 months ago, and that
was the path we choose: to put the ObsoletePackages into a graveyard
repository, so people willing to use it can load and be happy with that. The
path you suggested was analyzed (and discarded) at the time because it
On 12/15/12, Esteban Lorenzano esteba...@gmail.com wrote:
Janko,
that's already done (since ever), and FD is provided in two different ways:
in the graveyard is the old FD package (loadable into pharo 2.0)
http://smalltalkhub.com/#!/~Pharo/Graveyard20 , and also Camillo made a FD
wrapper to
On 15 December 2012 14:16, Pavel Krivanek pavel.kriva...@gmail.com wrote:
Hi,
what is the reason for integration of KeyChain/UsersManager to the image? It
created the next kernel dependency. Should it replace Author? Should it be
in the Pharo Kernel? And why there was no mention about it in
You are not, I need to always recheck the Interval class to see what
messages to use.
-- Pavel
On Sat, Dec 15, 2012 at 5:30 PM, Igor Stasenko siguc...@gmail.com wrote:
hi,
i am alone with this problem (or just mentally ill?), why every time i
use #start and #end protocol for Interval, e.g.:
On 15 December 2012 13:39, Janko Mivšek janko.miv...@eranova.si wrote:
Dne 15. 12. 2012 12:46, piše Igor Stasenko:
Hold on.. Since when Pharo project became professional product?
How much money you and others paying for using it?
Yes, we position it as a product FOR professionals,
but does
and i always hitting the wall with my head again and again.. because
there's no such protocol
and instead (after opening browser and looking at class, i figuring
that i should use #first/#last, but it is completely unintuitive to
me)..
Me too, when I was using what I knew would only ever
H. Hirzel wrote
As Chris points out, the difference is minimal.
Sean, it looks like you need better examples to show how you perceive
the benefits of the FileSystem design
While you ignored the point of my followup post, which is that beauty and
simplicity lead to more than the sum of a few
Hi All,
new Cog VMs available at
http://www.mirandabanda.org/files/Cog/VM/VM.r2636/. The main change here
is to do with corrected headroom and safer signal handling which should
hopefully improve stability on linux.
Cog VM binaries as per VMMaker.oscog-eem.234/r2636/r2638.
Use the -z now
On 15 December 2012 23:45, Chris Muller asquea...@gmail.com wrote:
and i always hitting the wall with my head again and again.. because
there's no such protocol
and instead (after opening browser and looking at class, i figuring
that i should use #first/#last, but it is completely unintuitive
FileDirectory was updated in 2009, but since Pharo had already forked
off Squeak prior to that you didn't know that FileDirectory was
already a lot like FileSystem is today before anyone knew FileSystem
even existed. Today these examples are almost identical.
Example #1:
file := FileDirectory
Chris Muller-3 wrote
I think we agree about what good design is, we just differ about which
path to take there, the more-compatible or the more-beautiful path.
That sums it up I think :)
--
View this message in context:
I agree with what most people have said, from both sides.
Most of the Smalltalkers I know that are making a living out of it are small
teams, if not single developer companies (letting aside the fact my company
have more than a dozen of smalltalkers). The transition path should be done
as
Could I ask that whomever set up the Google Groups mirror of this list get it
back to working order? That mirror was kicked of this list last February for
excessive bounces and at this point is dead. For one, this neglect doesn't
look good for people happening onto Pharo from Google Groups.
31 matches
Mail list logo
