, stephane ducasse
stephane.duca...@free.frwrote:
If you need help to write a configuration of I can help.
The problem is that I do not know all the fine grained dependencies.
But I think that we can do it step by step.
On Mar 7, 2013, at 1:18 AM, Julian Fitzell jfitz...@gmail.com wrote
Have we even done a stable release of 3.1 yet? I don't even think all the
3.0.x fixes have been ported into the 3.1 repository...
On Mon, Mar 4, 2013 at 8:20 PM, Torsten Bergmann asta...@gmx.de wrote:
Hi @seaside-dev (CC-ing Pharo list and seaside users list):
Pharo 2.0 is upon completion and
2011/6/30 Janko Mivšek janko.miv...@eranova.si
Whole point is that this is a non-blocking code, in contrast to
continuation based approach like in Seaside, where similar code would
block and wait until dialog component returns answer.
Janko, what are you talking about? If it's not blocking,
2011/7/1 Janko Mivšek janko.miv...@eranova.si
S, Julian Fitzell piše:
2011/6/30 Janko Mivšek janko.miv...@eranova.si
Whole point is that this is a non-blocking code, in contrast to
continuation based approach like in Seaside, where similar code would
block and wait until
that's the sensible thing to do.
Cheers,
- Andreas
On 1/8/2011 6:02 PM, Julian Fitzell wrote:
On Wed, Jan 5, 2011 at 8:15 AM, Paolo Bonzinibonz...@gnu.org wrote:
On 01/05/2011 04:58 PM, mkobe...@cincom.com wrote:
Here's maybe a bit more concise example. If you run the thing below
On Wed, Jan 5, 2011 at 8:15 AM, Paolo Bonzini bonz...@gnu.org wrote:
On 01/05/2011 04:58 PM, mkobe...@cincom.com wrote:
Here's maybe a bit more concise example. If you run the thing below
in a workspace,
it returns 'Squeak' in Squeak and 'VW' in VW
[ [ [ self
This still seems confusing. Could we just have a new SqueakSource
project called Xtreams (small T + an S)? It's not like projects are
expensive to create...
Julian
On Sat, Oct 9, 2010 at 11:33 PM, Nicolas Cellier
nicolas.cellier.aka.n...@gmail.com wrote:
So, I started a quick port of VW Xtreams
2010/8/31 Levente Uzonyi le...@elte.hu:
On Mon, 30 Aug 2010, Miguel Enrique Cobá Martínez wrote:
You must be kidding. The freedom to fork is a essential right of open
source software:
http://news.cnet.com/8301-13505_3-10379280-16.html
of specialization a little easier, but even now
an individual project can add fine-grained attributes that could allow code
to be conditional on a build by build basis ... if needed.
Dale
Julian Fitzell wrote:
Hmm... Why did I only receive this email today...?
Anyway, I agree that those
On Fri, Jun 18, 2010 at 4:43 AM, Stéphane Ducasse
stephane.duca...@inria.fr wrote:
On Jun 17, 2010, at 3:14 PM, Julian Fitzell wrote:
2010/6/17 Marcus Denker marcus.den...@inria.fr:
On Jun 17, 2010, at 12:27 PM, Lukas Renggli wrote:
- If included with Pharo I suggest to rename all
On Mon, Jun 21, 2010 at 9:38 AM, Michael Roberts m...@mjr104.co.uk wrote:
On 21 Jun 2010, at 14:30, Stéphane Ducasse stephane.duca...@inria.fr
wrote:
but do we want all grease?
Well. Not sure. Grease core is not that big. It has other useful stuff in. I
was in part commenting on the
.
In the end this doesn't sound that awful...
Dale
Julian Fitzell wrote:
2010/6/17 Marcus Denker marcus.den...@inria.fr:
On Jun 17, 2010, at 12:27 PM, Lukas Renggli wrote:
- If included with Pharo I suggest to rename all the methods,
otherwise we will run into big troubles with Seaside
2010/6/17 Marcus Denker marcus.den...@inria.fr:
On Jun 17, 2010, at 12:27 PM, Lukas Renggli wrote:
- If included with Pharo I suggest to rename all the methods,
otherwise we will run into big troubles with Seaside and other
projects that depend on Grease.
From a philosophical standpoint,
the ancestor/working copy mismatch that Julian has
described.
Also exploring the MCRepositoryGroup I've noted the useCache instVar
is never disabled. This is another way to go.
Opinions?
Hernán
2010/6/15 Julian Fitzell jfitz...@gmail.com:
The Copy button allows you to copy the version from
is less helpful than the previous behaviour when
this (common) error happens.
Julian
On Tue, Jun 15, 2010 at 2:12 AM, Hernán Morales Durand
hernan.mora...@gmail.com wrote:
Hi Julian,
2010/6/15 Julian Fitzell jfitz...@gmail.com:
It seems that in Pharo 1.1 MC no longer displays the Version
It seems that in Pharo 1.1 MC no longer displays the Version window
after a failed commit attempt (due to missing authentication for
example). As a result, cannot easily resubmit the version after fixing
the credentials.
In fact, as I look further, it's worse than that. Let's say I had
version 1
On Tue, Jun 15, 2010 at 12:12 AM, Julian Fitzell jfitz...@gmail.com wrote:
It seems that in Pharo 1.1 MC no longer displays the Version window
after a failed commit attempt (due to missing authentication for
example). As a result, cannot easily resubmit the version after fixing
the credentials
Hi everyone,
I'm speaking about Seaside and web development this week at the Irish
Software Show (epicenter) in Dublin. The organizers have offered each
of the speakers 10 discount tickets (€50/day) to pass along to people
who are interested in attending. It looks like there will be some
Much to our delight, there seems to be a lot of interest in the Camp
Smalltalk event in London. We originally estimated our capacity at 30,
and those slots have already filled up in less than 4 days!
We are just now discussing what our actual maximum capacity is. We'll
be able to handle a few
Take a look at the ANSI standard - it has the collection behaviour
already broken up into traits that are multiply-inherited to define
the protocols of each class.
Julian
On Thu, May 27, 2010 at 10:32 AM, Tristan Bourgois
tr.bourg...@laposte.net wrote:
Thanks, that's very interesting but not
The UK Smalltalk User Group would like to invite everyone to attend
Camp Smalltalk London this July 16-18.
The Pharo team will be holding one of their regular coding sprints
and, in true Camp Smalltalk spirit, other Smalltalkers will be
gathering together to do some productive work on their
The fact that MC2 is still a moving target. Or at least it would be if it
was moving. :) More to the point, the early releases had some problems that
prompted further redesign and I'd recommend against creating large amounts
of date in those versions that will need to be brought forward. In other
On Wed, Apr 28, 2010 at 10:01 PM, Geert Claes geert.wl.cl...@gmail.comwrote:
Seeing a -4 reminded me of the dreadful GSOC voting debacle so I am glad it
has nothing to do with that.
:)
Nice work Geert... that's a very attractive site with just a nice minimal
set of information cleanly
On Sat, Apr 24, 2010 at 10:54 AM, stephane ducasse stephane.duca...@free.fr
wrote:
What are the expectation for DateAndTimereadFrom?
Personally, my expectation is that it doesn't exist. :)
To believe that there is a single way of parsing strings into dates (or
numbers, or anything else) that
2010/4/18 Nicolas Petton petton.nico...@gmail.com
Le dimanche 18 avril 2010 à 19:25 +0100, Julian Fitzell a écrit :
2010/4/18 Nicolas Petton petton.nico...@gmail.com
Now I'm not really happy with the codec stuff, as from a GNU
Smalltalker
point of view it seems
On Sun, Apr 18, 2010 at 1:10 AM, Henrik Sperre Johansen
henrik.s.johan...@veloxit.no wrote:
On 18.04.2010 01:05, Julian Fitzell wrote:
Cool stuff, Nicolas. I'm happy to see Grease getting use in the wild...
I'm curious to what degree it met your needs?
I just recorded a podcast with James
2010/4/18 Nicolas Petton petton.nico...@gmail.com
Now I'm not really happy with the codec stuff, as from a GNU Smalltalker
point of view it seems too Squeak/Pharo oriented, but I can leave with
that for now.
To be honest, I'm not totally happy with that part either. :) It's good
enough for
Cool stuff, Nicolas. I'm happy to see Grease getting use in the wild... I'm
curious to what degree it met your needs?
I just recorded a podcast with James Robertson this week talking about
cross-platform development. He asked what other projects were using Grease
and I'm afraid I didn't know to
On Sat, Mar 13, 2010 at 12:23 AM, Levente Uzonyi le...@elte.hu wrote:
- SortedCollection: just deprecate it (or replace it's crappy quicksort
implementation if you really want to improve it. But I think it's useless)
You shouldn't deprecate it... it's ANSI. :)
But it's implementation could
Yes. Administrative tools for Seaside would be an excellent project.
Julian
On Tue, Mar 9, 2010 at 8:50 AM, Maarten MOSTERT
maarten.most...@wanadoo.fr wrote:
Mariano,
This is a very good initiative !
I don't think what other peoples opinion is about this, but personnally I
would
On Sat, Mar 6, 2010 at 12:54 PM, Paolo Bonzini bonz...@gnu.org wrote:
We think that one of the most important reasons why we failed in 2009 is
that Google was looking for bigger communities that Squeak. This is why
this year we all go under the ESUG umbrella. We present ESUG as the
mentor
I'm not sure, but in ANSI, indexOfSubcollection:startingAt: is defined
as returning 0 (no match) for an empty collection.
This doesn't necessarily mean that #beginsWith: needs to return false
as well, of course, but it would be another data point. And I just
checked VW and it returns true for
On Wed, Feb 17, 2010 at 5:13 AM, Lukas Renggli reng...@gmail.com wrote:
#sort you mean? Not yet... we either need to add it in Pharo, fix it
in the one click, or add it to the Grease package.
OrderedCollection#sort and OrderedCollection#sort: is already part
of Pharo 1.1. The Seaside tests
On Wed, Feb 17, 2010 at 12:32 PM, Lukas Renggli reng...@gmail.com wrote:
covers, for example, Arrays that are marked as immutable. There are
many many subclasses of SequenceableCollection that do implement
#at:put: and can be sorted properly...
Yes, OrderedCollection and ArrayedCollection
On Thu, Jan 7, 2010 at 11:56 PM, Lukas Renggli reng...@gmail.com wrote:
I could do everything in one build (and use Mason for the dependency
resolution), but then I'd loose the nice per-build reporting of
Hudson.
I don't see why... you'd just have to do a build for stage A and then one
for B
On Tue, Dec 29, 2009 at 2:13 AM, Adrian Kuhn ak...@iam.unibe.ch wrote:
On Dec 29, 2009, at 7:21 AM, Julian Fitzell wrote:
Then, having said that, #assume: sounds a bit like the test should
assume the statement is true and then carry on running with that
assumption. Maybe #expect: would
On Mon, Dec 28, 2009 at 2:19 PM, Adrian Kuhn ak...@iam.unibe.ch wrote:
For example, when your test case depends on the availability of a certain
database you can write
testBlob
self assumeThat: Database default = DatabaseWithBlobs.
...
Can I suggest simply #assume: ? The
Fyi, PackageInfo (and thus base Pharo currently) defines
Collectiongather: which has basically this behaviour (minus the nil
check). I had this marked as a method for discussion when going
through the VASt/Pharo collection protocols.
I think #collectAll: is problematic as a selector because All:
Personally, I would rather see #ifEmpty: modified to return self in
the false case like #ifNil: does. The only in-image sender I can find
that even uses the return value seems to actually expect this
behaviour anyway. :)
Then you could simply write:
(aCollection select: [:ea | ...]) ifEmpty: [
I'm pretty sure John was going to add #sort: at the level of
SequenceableCollection. As I mentioned, it is implemented in terms of
#at:put: and therefore errors reasonably on Interval.
We might require a special implementation for SortedCollection,
alright. I don't see why that would be a problem
On Wed, Dec 23, 2009 at 9:22 AM, Levente Uzonyi le...@elte.hu wrote:
On Wed, 23 Dec 2009, Julian Fitzell wrote:
#sort and #sort: -- Squeak/Pharo have it on ArrayedCollection, VW has
it on SequenceableCollection, and VASt will now add it. This sorts the
instance in place.
The problem here
On Thu, Dec 24, 2009 at 12:19 AM, Stéphane Ducasse
stephane.duca...@inria.fr wrote:
#sortBlock: is defined by ANSI on SortedCollection as an accessor and
an instance creation method. That's what it sounds like and shouldn't
be implemented on non-sorted collections.
Why? what would be the
On Thu, Dec 24, 2009 at 12:19 AM, Stéphane Ducasse
stephane.duca...@inria.fr wrote:
#sorted, #sorted: -- VW already has this. VA is adding it.
What is sorted? a boolean predicate method?
What a bad name. Did they forgot Kent?
An example of my previous message -- this name is confusing and
On Thu, Dec 24, 2009 at 1:26 AM, Stéphane Ducasse
stephane.duca...@inria.fr wrote:
On Dec 24, 2009, at 10:00 AM, Julian Fitzell wrote:
On Thu, Dec 24, 2009 at 12:19 AM, Stéphane Ducasse
stephane.duca...@inria.fr wrote:
#sortBlock: is defined by ANSI on SortedCollection as an accessor
On Wed, Dec 23, 2009 at 1:45 AM, Nicolas Cellier
nicolas.cellier.aka.n...@gmail.com wrote:
2009/12/23 Stéphane Ducasse stephane.duca...@inria.fr:
Apparently sort: is not understood by SortedCollection :(
And sortBlock: is not understood by ArrayedCollection subclasses :(
So this is cool
On Tue, Dec 22, 2009 at 2:17 PM, Martin McClure mar...@hand2mouse.com wrote:
But if
there can be one true SUnit for all Smalltalk, that seems like a
better answer.
Agreed.
Julian
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
On Mon, Dec 21, 2009 at 9:36 AM, Stéphane Ducasse
stephane.duca...@inria.fr wrote:
Thanks julian. I think that this is nice way to look at it.
Defining another one would be good - the only important point is that we
could load it and
it can transparently replace SUnit.
Yes, it would be nice
On Mon, Dec 21, 2009 at 4:15 PM, Adrian Kuhn ak...@iam.unibe.ch wrote:
Julian Fitzell jfitz...@... writes:
Well, the second may require working *with* SUnit maintainers on other
platforms. :)
Where can I find their names?
Dunno... guess this is a start: http://sunit.sourceforge.net
48 matches
Mail list logo
