squeak6 "root project" is mvc

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

squeak6 "root project" is mvc

Squeak - Dev mailing list
Hi folks,

just an FYI in case the "RootProject" should be morphic.


/opt/usr/src/smalltalk/squeak6.0alpha/shared/Squeak6.0alpha-19537-64bit.image
Squeak6.0alpha




Reply | Threaded
Open this post in threaded view
|

Re: squeak6 "root project" is mvc

David T. Lewis
On Tue, Mar 24, 2020 at 04:54:51PM -0400, gettimothy via Squeak-dev wrote:
> Hi folks,
>
>
>
> just an FYI in case the "RootProject" should be morphic.
>

Don't worry, it's fine. It is part of the emergency evaluator safety
net. If you are doing something in Morphic that causes an unrecoverable
error, such that a debugger cannot be opened in the Morphic framework,
then the system will try to switch over to that root MVC project and
open a debugger using MVC. Finally, that fails again, the system will
drop you into the traditional emergency evaluator.

This allows many kinds of failures that involve the user interface
itself to be handled in another framework. It can be very helpful
if you are working on Morphic itself and make a mistake the breaks
your user interface.

The release image now provides a root MVC project for this reason.

If you are planning to do work in MVC that might breeak the MVC user
interface, then you would want to work in an MVC project that has
a morphic project as a parent. The same emergency evaluation mechanism
will apply there, such that if you break something in MVC the system
will try to open a Morphic debugger.

Dave


Reply | Threaded
Open this post in threaded view
|

Re: squeak6 "root project" is mvc

Squeak - Dev mailing list
That is brilliant!




---- On Tue, 24 Mar 2020 18:04:56 -0400 David T. Lewis <[hidden email]> wrote ----

On Tue, Mar 24, 2020 at 04:54:51PM -0400, gettimothy via Squeak-dev wrote:
> Hi folks,
>
>
>
> just an FYI in case the "RootProject" should be morphic.
>

Don't worry, it's fine. It is part of the emergency evaluator safety
net. If you are doing something in Morphic that causes an unrecoverable
error, such that a debugger cannot be opened in the Morphic framework,
then the system will try to switch over to that root MVC project and
open a debugger using MVC. Finally, that fails again, the system will
drop you into the traditional emergency evaluator.

This allows many kinds of failures that involve the user interface
itself to be handled in another framework. It can be very helpful
if you are working on Morphic itself and make a mistake the breaks
your user interface.

The release image now provides a root MVC project for this reason.

If you are planning to do work in MVC that might breeak the MVC user
interface, then you would want to work in an MVC project that has
a morphic project as a parent. The same emergency evaluation mechanism
will apply there, such that if you break something in MVC the system
will try to open a Morphic debugger.

Dave