[squeakland] Artifacts in ObjectCatalog
sthomas1 at gosargon.com
Thu Jun 3 09:53:25 EDT 2010
I agree that we need to provide higher level artifacts. I am just not sure
that the object catalog is the best place to put them all, because I can see
a large number of higher level artifacts that would be useful.
There have been a number of times where I created something from one project
I wanted to include in another and until I discovered the "copy" and "paste"
method to move things between projects I didn't have any good method. I
still run into some problems with copying and pasting between projects where
the scripts seem to break.
We need a way to make these artifacts available and discoverable and the
object catalog is one way.* At this point* I just don't know what the best
way to do that is.
On Thu, Jun 3, 2010 at 9:10 AM, Hilaire Fernandes <
hilaire.fernandes at edu.ge.ch> wrote:
> Steve Thomas a écrit :
> As far as whether they should be included in the Etoys Object Catalog. At
>> this point I think not.
>> Etoys (as near as I can figure) is built upon doing everything from first
>> principles, which is part of its power and beauty.
>> That said I think we need to solve the problem that it can take quite a
>> while and not everyone is capable of building things from first principles.
> You can even wrote most people are not capable of building things from
> first principles. If we want Etoys to scale to a larger audiance, it is a
> way to go.
> Of course, it is not because we provide higher level artefact (in a way we
> found appropriate) we are closing the door.
> Some higher levels of domain specific abstractions are useful and I
>> believe necessary. Also, Hilaire makes a good point that to make things
>> scalable these would need to be done in smalltalk.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the squeakland