Re: [Pharo-project] Workspace API

2009-02-12 Thread Stéphane Ducasse
No idea >> time >> time time >> have you seen that adrian is working on trait sharing and that we are >> waiting for that >> since a couple of months or more. >> >> Stef >> > Will it load into 3.10? > > Keith > > > ___ > Pharo-project mailing list > Pha

Re: [Pharo-project] Workspace API

2009-02-12 Thread Keith Hodges
> time > time time > have you seen that adrian is working on trait sharing and that we are > waiting for that > since a couple of months or more. > > Stef > Will it load into 3.10? Keith ___ Pharo-project mailing list Pharo-project@lists.gforge.i

Re: [Pharo-project] Workspace API

2009-02-12 Thread Stéphane Ducasse
> > > We stopped fixing the kernel in order to try and facilitate some > harmony > through some tools support. One result was LPF, another MC1.6, and of > course the invisible man, Bob. > > Now you have all the experts, why doesnt someone who knows about > traits > help Matthew to fix

Re: [Pharo-project] Workspace API

2009-02-12 Thread Keith Hodges
Stéphane Ducasse wrote: > On Feb 12, 2009, at 1:47 PM, Keith Hodges wrote: > > >>> Our goal is to make progress. Squeak is dying don't see it? >>> >>> >> The reason it is dying is because once anyone starts a significant >> project they are stuck with the same image that they started with

Re: [Pharo-project] Workspace API

2009-02-12 Thread Stéphane Ducasse
On Feb 12, 2009, at 1:47 PM, Keith Hodges wrote: > >> Our goal is to make progress. Squeak is dying don't see it? >> > The reason it is dying is because once anyone starts a significant > project they are stuck with the same image that they started with. > Thus > everyone gets left along the pa

Re: [Pharo-project] Workspace API

2009-02-12 Thread Keith Hodges
>>> >>> >>> >> I thought that MinimalMorphic was released 2 years ago? >> >> ok I was mistaken, I meant the etoys removal script Keith ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/m

Re: [Pharo-project] Workspace API

2009-02-12 Thread Stéphane Ducasse
Come on this is not the same On Feb 12, 2009, at 1:49 PM, Keith Hodges wrote: > Stéphane Ducasse wrote: >> I know. I just want to tell you that nothing is easy. >> Now saying that we do not pay attention is not exact. >> But really beside integrating fixes and cleaning etoy I have no time. >>

Re: [Pharo-project] Workspace API

2009-02-12 Thread Keith Hodges
Stéphane Ducasse wrote: > I know. I just want to tell you that nothing is easy. > Now saying that we do not pay attention is not exact. > But really beside integrating fixes and cleaning etoy I have no time. > > Stef > > I thought that MinimalMorphic was released 2 years ago? Keith __

Re: [Pharo-project] Workspace API

2009-02-12 Thread Keith Hodges
> Our goal is to make progress. Squeak is dying don't see it? > The reason it is dying is because once anyone starts a significant project they are stuck with the same image that they started with. Thus everyone gets left along the path of progress. They keep up or get left behind to fork their

Re: [Pharo-project] Workspace API

2009-02-12 Thread Stéphane Ducasse
>> You still dont get it do you. *** really look at it *** means pick >> over > the carcass. Adopting it means JOINING IN AND MAKING EVERYTHING BETTER > FOR EVERY ONE. I know. > > > You guys have the expertise to fix things I dont, I'm not sure :) > and test things that I > dont. I dont have

Re: [Pharo-project] Workspace API

2009-02-12 Thread Stéphane Ducasse
I know. I just want to tell you that nothing is easy. Now saying that we do not pay attention is not exact. But really beside integrating fixes and cleaning etoy I have no time. Stef On Feb 12, 2009, at 11:22 AM, Keith Hodges wrote: > Stéphane Ducasse wrote: >> About MC1.5 here is what I receive

Re: [Pharo-project] Workspace API

2009-02-12 Thread Keith Hodges
Stéphane Ducasse wrote: > About MC1.5 here is what I received as a private email. > So I imagine that the person is a bit too negative too but you can > understand that we pay attention and need time > to ***really*** look at it. > > I hope you don't include Monticello 1.5 in Pharo. All cod

Re: [Pharo-project] Workspace API

2009-02-12 Thread Keith Hodges
Stéphane Ducasse wrote: > About MC1.5 here is what I received as a private email. > So I imagine that the person is a bit too negative too but you can > understand that we pay attention and need time > to ***really*** look at it. > > I hope you don't include Monticello 1.5 in Pharo. All cod

Re: [Pharo-project] Workspace API

2009-02-12 Thread Stéphane Ducasse
On Feb 11, 2009, at 7:34 PM, Keith Hodges wrote: > Stéphane Ducasse wrote: >> Where? When? >> Keith >> in the long run it would be nice that yu do not bash us >> systematically. >> Yes we have a different way of working but normally this is often by >> pure lack of time or information >> that w

Re: [Pharo-project] Workspace API

2009-02-12 Thread Stéphane Ducasse
About MC1.5 here is what I received as a private email. So I imagine that the person is a bit too negative too but you can understand that we pay attention and need time to ***really*** look at it. I hope you don't include Monticello 1.5 in Pharo. All code that we have seen so fa

Re: [Pharo-project] Workspace API

2009-02-11 Thread Keith Hodges
Stéphane Ducasse wrote: > Where? When? > Keith > in the long run it would be nice that yu do not bash us systematically. > Yes we have a different way of working but normally this is often by > pure lack of time or information > that we do not check what exist. > > Stef > I was concerned to fi

Re: [Pharo-project] Workspace API

2009-02-11 Thread Keith Hodges
Alexandre Bergel wrote: > I was wondering, how many people saved their workspace content in a > file? > > Cheers, > Alexandre > MC1.5 supports files so if you want to manage scripts and readmes having a workspace that knows its file, is a good idea. Also Bob wants a way to (optionally) show y

Re: [Pharo-project] Workspace API

2009-02-11 Thread Gary Chambers
Subject: Re: [Pharo-project] Workspace API I average about once a year (saving contents to a file). However, I regularly open a workspace on strings. -- ___ Pharo

Re: [Pharo-project] Workspace API

2009-02-11 Thread Chris Cunningham
I average about once a year (saving contents to a file). However, I regularly open a workspace on strings. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] Workspace API

2009-02-11 Thread Alexandre Bergel
I was wondering, how many people saved their workspace content in a file? Cheers, Alexandre On 11 Feb 2009, at 08:45, Stéphane Ducasse wrote: > Then I'm not in favor to load files in workspace or saving contents to > file. > Workspace snippets are against classes. If you have a nice and fast

Re: [Pharo-project] Workspace API

2009-02-10 Thread Stéphane Ducasse
Then I'm not in favor to load files in workspace or saving contents to file. Workspace snippets are against classes. If you have a nice and fast snippets then you put it in a class and work a bit and you get an little object. And you can even version it Stef On Feb 10, 2009, at 3:49 PM, Keit

Re: [Pharo-project] Workspace API

2009-02-10 Thread Stéphane Ducasse
Where? When? Keith in the long run it would be nice that yu do not bash us systematically. Yes we have a different way of working but normally this is often by pure lack of time or information that we do not check what exist. Stef On Feb 10, 2009, at 3:49 PM, Keith Hodges wrote: > http://bugs.

Re: [Pharo-project] Workspace API

2009-02-10 Thread Damien Cassou
What do you suggest? On Tue, Feb 10, 2009 at 3:49 PM, Keith Hodges wrote: > http://bugs.squeak.org/view.php?id=5669 > > I requested then implemented a reasonable API for opening Workspaces on > strings and files. I now find that pharo has implemented incompatible > versions of the same. > > Works

[Pharo-project] Workspace API

2009-02-10 Thread Keith Hodges
http://bugs.squeak.org/view.php?id=5669 I requested then implemented a reasonable API for opening Workspaces on strings and files. I now find that pharo has implemented incompatible versions of the same. Workspace openContents: 'blah'. or Workspace new contents: 'blah'; label: 'Title';