The future of Morphic (Re: [squeak-dev] SimpleMorphic Editors)
Casey Ransberger
casey.obrien.r at gmail.com
Sat Apr 2 02:44:01 UTC 2011
This is also a great idea. Andreas decided he didn't like his implementation and we haven't really followed up since. I actually think it wouldn't hurt to use the same underlying system that Pharo is using (Metacello) if it works today, but I may be in the Minority on this one.
Chris Muller has made some pretty compelling arguments about using SqueakMap, which is also worth mentioning as a possible solution.
On Apr 1, 2011, at 4:42 PM, Levente Uzonyi <leves at elte.hu> wrote:
> On Fri, 1 Apr 2011, Bert Freudenberg wrote:
>
>> On 31.03.2011, at 21:15, David T. Lewis wrote:
>>
>>> On Thu, Mar 31, 2011 at 08:00:08PM +0200, Bal?zs K?si wrote:
>>>> On Thu, Mar 31, 2011 at 7:46 PM, Casey Ransberger
>>>> <casey.obrien.r at gmail.com> wrote:
>>>>> I'd like to reverse this statement. In the longer term I'd like to see
>>>>> SimpleMorphic into the core system, and get LegacyMorphic or BigMorphic
>>>>> or whatever we'd call it out of the core and into Squeaksource.
>>>>
>>>> I think we could do even better: Make all the ui frameworks loadable
>>>> and unloadable, and make it easy to implement your own.
>>>>
>>>> Bal?zs
>>>
>>> Yes!
>>>
>>> Dave
>>
>> Not quite a plan yet, but great idea!
>>
>> The old FullMorphic could be maintained as part of Etoys.
>
> Another possible solution is to implement Andreas' idea about Community Supported Packages* (which slight modifications) and maintain it there. Of course, it has to be made unloadable/loadable first.
>
>
> Levente
>
> *http://lists.squeakfoundation.org/pipermail/squeak-dev/2010-May/150658.html
>
>>
>> - Bert -
>>
>>
>>
>
More information about the Squeak-dev
mailing list
|