Skip to main content



      Home
Home » Eclipse Projects » Eclipse Platform » Editor behaviour for a view
Editor behaviour for a view [message #312795] Tue, 20 February 2007 11:13 Go to next message
Eclipse UserFriend
Hello, is there any possibility to adjust behaviour of the opened project to
to opened project will behave the same way as eclipse editor? It means the
project will follow the Open-Edit-Save lifecycle. It means that project will
have associated with its some state. - saved/neded_to_save.

Do you have any experiences with this?

Thanks for any help.
John Cage
Re: Editor behaviour for a view [message #312810 is a reply to message #312795] Tue, 20 February 2007 17:41 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: jacek.pospychala.pl.ibm.com

Hi,
what you would like to do is a bit tricky. The idea of projects is that
they are containers to store data. Already every project can be opened
or closed, what means it's data will be accessed(/processed/executed) or
not.
I am not sure, how would you define a project that is in "Edit" state.
Does it mean, that until project is not saved it's data is not stored to
disk? And then the same question comes about "Save" state.
Please give us some more details, what is the real need for such behaviour.
I wonder if you considered having a projects with only one master file -
which would mean that open-edit-save state for this file represents also
whole project state. Another way would be introducing a kind of
temporary projects, that are edited until save. On save they would
replace main project.

eclipsemaniac napisał(a):
> Hello, is there any possibility to adjust behaviour of the opened project to
> to opened project will behave the same way as eclipse editor? It means the
> project will follow the Open-Edit-Save lifecycle. It means that project will
> have associated with its some state. - saved/neded_to_save.
>
> Do you have any experiences with this?
>
> Thanks for any help.
> John Cage
>
>
Re: Editor behaviour for a view [message #315859 is a reply to message #312810] Thu, 24 May 2007 04:29 Go to previous message
Eclipse UserFriend
My idea was probasbly bad, because it doesn't fit to eclipse infrastructure.
Thanks for your aim.
Best Regards,
Jan

"Jacek Pospychala" <jacek.pospychala@pl.ibm.com> wrote in message
news:ergpie$v7s$1@utils.eclipse.org...
> Hi,
> what you would like to do is a bit tricky. The idea of projects is that
> they are containers to store data. Already every project can be opened or
> closed, what means it's data will be accessed(/processed/executed) or not.
> I am not sure, how would you define a project that is in "Edit" state.
> Does it mean, that until project is not saved it's data is not stored to
> disk? And then the same question comes about "Save" state.
> Please give us some more details, what is the real need for such
> behaviour.
> I wonder if you considered having a projects with only one master file -
> which would mean that open-edit-save state for this file represents also
> whole project state. Another way would be introducing a kind of temporary
> projects, that are edited until save. On save they would replace main
> project.
>
> eclipsemaniac napisa
Previous Topic:Using developped plugins in a Runtime Workbench
Next Topic:formatting text in swt
Goto Forum:
  


Current Time: Mon Jul 14 19:59:40 EDT 2025

Powered by FUDForum. Page generated in 0.15935 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top