Re: [platform-ui-dev] close editor warning

["Bob Foster" <bob@xxxxxxxxxx>]

Thank you for addressing a point that has been bothering me.

There is a set of actions that should use modified, unsaved files, like
Search, Refactor, etc. and a set of actions that should only use saved,
unmodified files, like Compile, Run, etc. We can call these two sets unsaved
and saved, respectively.

Considering a new action A, are there some guidelines as to whether it is in
the saved or unsaved set? A specific instance is, user has two open files: a
DTD and an XML file using the DTD. User modifies the DTD, switches to the
XML file and validates. Should validation use the saved copy or the copy in
memory? (I currently put this action in the unsaved set, but I am not sure
this is the right answer. Complication: there might be a different answer
depending on whether the user invoked Validate explicitly on an unsaved
document, or implicitly as the byproduct of a Save, both of which are
currently options.)

I am hoping for some general guidance. Even better, if it were documented
somewhere, so Eclipse plugins could have consistent behavior.

Thanks!

Bob

----- Original Message -----
From: <Nick_Edgar@xxxxxxxxxx>
To: <platform-ui-dev@xxxxxxxxxxx>
Sent: Tuesday, January 07, 2003 8:24 AM
Subject: Re: [platform-ui-dev] close editor warning


> I find it surprising that you allow a modified script to be run before it
> is saved.  Usually editors follow and open/edit/save lifecycle, with
> changes having no effect until saved (except for views that show the
> contents of the editor, like the Outline).  For example, when running Java
> programs, changes to a compilation unit are not sent to the VM until you
> save (if the VM supports hot code replace).
>
> Nick
>
>
>
>
>
> jml <jml@xxxxxxxx>
> Sent by: platform-ui-dev-admin@xxxxxxxxxxx
> 01/06/03 09:38 PM
> Please respond to platform-ui-dev
>
>
>         To:     platform-ui-dev@xxxxxxxxxxx
>         cc:
>         Subject:        Re: [platform-ui-dev] close editor warning
>
>
>
> Hi, Nick, thanks for the reply.
>
> We have a very small scripting language, user can debug it. During
> debugging, we want to enable user to directly modify the script code
> inside the editor, and the debugger will always run the newest code. So
> our debugger use the memory of the editor not the saved files. To easy
> implementation, we want to force user to keep the editor open during the
> debug session -- or when user try to close the editor, give us a chance
> to also stop the debugger.
>
> BTW, we want to utilize the eclipse debug framework, but the framework
> allow the debug view to appear in any workbenchwindow, in our case,
> means user can open multiple editor of the same script in multiple
> workbenchwindow, thus multiple memory copy. How can I solve this? Or
> normally is there any other way dealing with this kind of problem?
>
> Thanks
> jml
>
>
>
> Nick_Edgar@xxxxxxxxxx wrote:
> > jml,
> >
> > There is an existing feature request for this:
> > http://dev.eclipse.org/bugs/show_bug.cgi?id=27466
> >
> > However, we currently have no plans to address this for 2.1.
> > If you describe your specific use case for this in the PR, that would
> help
> > us consider whether this would be a useful feature.
> >
> > Thanks,
> > Nick
> >
> >
> >
> >
> >
> >
> > jml <jml@xxxxxxxx>
> > Sent by: platform-ui-dev-admin@xxxxxxxxxxx
> > 12/30/02 01:05 AM
> > Please respond to platform-ui-dev
> >
> >
> >         To:     "platform-ui-dev@xxxxxxxxxxx"
> <platform-ui-dev@xxxxxxxxxxx>
> >         cc:
> >         Subject:        [platform-ui-dev] close editor warning
> >
> >
> >
> > Hi,
> > Is there any plan in the 2.1 release to include the following feature:
> >
> > Give the editor a chance to popup some different warning dialog before
> > it is being closed -- or even let the editor to choose not to be closed.
> >
> > I think this is a very useful feature to many plugins.
> >
> > jml
> >
> > _______________________________________________
> > platform-ui-dev mailing list
> > platform-ui-dev@xxxxxxxxxxx
> > http://dev.eclipse.org/mailman/listinfo/platform-ui-dev
> >
> >
> >
> > _______________________________________________
> > platform-ui-dev mailing list
> > platform-ui-dev@xxxxxxxxxxx
> > http://dev.eclipse.org/mailman/listinfo/platform-ui-dev
> >
>
> _______________________________________________
> platform-ui-dev mailing list
> platform-ui-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/platform-ui-dev
>
>
>
> _______________________________________________
> platform-ui-dev mailing list
> platform-ui-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/platform-ui-dev
>