Hello
The roadmap has been announced a while ago but I will repeat it.
To prepare the migration to Bloc and Brick in the future we are rewriting
all the tools using a new version of Spec (called Spec20).
In addition we are providing a GTK backend so that companies can do business by
exposing a
nicer UI and as a validation that all our tools will be able to work without
Morphic.
The idea is to reuse the logic of the tools and avoid to have to rewrite them
systematically.
And to let companies do the same.
The current iteration will not touch Calypso (but we will have sadly to rewrite
Calypso because
some of the logic in mixed with Morphs) so that we can migrate to Bloc.
Esteban is rewriting all the tools
Inspector
Playground
Debugger
are now the main focus (in addition to other tools).
We will deprecate Glamour because it is not maintained anymore and we have
serious
problems with its design. We will deprecate all the GT tools except Spotter.
But we will propose replacement because we like these tools.
You will have
a nice Inspector framework
a nice new debugger with object-centric and scriptable API
a new playground
Spotter will be also rewritten (may be not during this iteration) why?
Because
- it does not scale.
- it has its own set of experimental and unmaintained widgets (and
memory leaks that we fixed :)
We will also revisit all the pragma uses and also symbols walking for completion
that systematically scan the complete memory and make Pharo slow.
We will create a super large image to have a case to show that we can improve
on the speed front.
The new inspector will let people define their own extensions but not using the
same glamourous block-based API.
Esteban started to migrate extensions of Pharo and we will help as soon as the
new inspector is available.
The community will also be able to help.
Is it clearer?
Do not hesitate to ask questions if you need. We do not have hidden agenda.
Note that we do not that by pleasure. And frankly we would prefer to do
something else - it would have been nice that as a community
we understand that there is a value in having models well separated outside of
UI but this is not the case.
But we do not really decide. We cannot stay with Morphic forever and improving
Morphic is a dead-end.
We do it because it is important for Pharo and for consortium members.
Stef
>
>> NewTools
>> Inspector
>> it now implements Miller columns
>> Using TaskIt as backend for stepping.
>> extensions migrated (we are at 10% of the total of migrations needed, we
>> will enhance this in iterative way).
>> Debugger
>> Almost complete revamp of UI.
>> Fix context updating (to allow commands to actually work)
>> Integrate new inspector.
>> Work on new layouts for debugger
>> Make an experimental tool: "playbook", to concentrate playgrounds and test
>> some UI ideas.
>>
>> ...
>
> I try to follow Pharo development with regards to UI, but I'm still lost.
>
> Are you ditching GToolkit and replacing it with new tools?
> If so, what about inspector ans spotter extensions?
>
> Also what are the plans for next generation of GToolkit?
>
>
>
>
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
>
