On Wed, Oct 15, 2014 at 2:22 PM, David T. Lewis <lewis at mail.msen.com> wrote:

> On Wed, Oct 15, 2014 at 01:23:25PM -0700, tim Rowledge wrote:
> >
> > > On Wed, Oct 15, 2014 at 9:45 PM, Eliot Miranda <
> eliot.miranda at gmail.com> wrote:
> > > Hi,
> > >
> > >    occasionally I find it useful to have a window that is always
> present in the current project, so that wen I change projects the window
> either moves to the new project, or is in all worlds.  Is there a way of
> doing this in the standard system?  (I can't see this from reading the
> labyrinthine project enter code, but I could be missing something ;-) ).
> Anyone have a changeset to do the same?
> >
> > Wow, I remember using this all the time back in the Old Days. I think
> you wrote the code for MVC to do it. Or maybe it was me after talking with
> you about it? Dunno.  IIRC it wasn?t at all hard in MVC-land but after
> looking at how this sort of thing is done in Ankh-Morph-pork I?m not sure
> it?s intelligible to mere humans.
> >
>
> Interesting question. Karl's suggestion of using a shared flap is probably
> the quickest expedient. But more generally:
>
> MorphicProject and MVCProject would need to handle this differently as
> would
> (the regrettably yet to be implemented) SeasideProject, AidaProject, and
> CuisMorphic3Project. So the concept would make sense within a given species
> of Project.
>

When I did this years ago I just added a per-window property and had the
Project enter code check for the property and move it if set.  So one could
move windows between projects by setting, entering and unsetting.  That's
simple.  But I hoped someone had already done this.  The Project code is
complex enough as it is...


> For MVC it would presumably be a matter of adding a new View for the given
> Model in all of the projects of type MVCProject. For Morphic, it is
> probably
> a matter of inserting the actual Morph into the morph hierarchy for all
> projects of type MorphicProject. In either case, these would need to be
> top level windows, so the insertion logic is probably not too hard to
> figure
> out.
>
> I guess you would want some window menu option to make the window sticky
> in all projects, or to remove it from all other projects except the
> currently
> active one. Also a visual indicator that the window has been pinned to all
> relevant projects.
>
> It is probably also possible to make the window be migratory (Eliot's
> suggestion of having it be reopened in the currently active project,
> whatever that might happen to be). However, as a practical matter that
> probably would need to be limited to moving from one project to another
> of the same type, unless of course we do a more complete implementation
> of ToolBuilder for all windows of interest.
>
> This would make a great project for somebody to try. Part concept, part
> requirements, part design, part implementation, and none of it too huge
> in scope. Any takers?
>
> Dave
>
>


-- 
best,
Eliot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20141015/fd06cac3/attachment.htm