Home » Eclipse Projects » Oomph » how to recover from mistakes?
| how to recover from mistakes? [message #1713759] |
Fri, 06 November 2015 13:18  |
 Stephan Herrmann
Messages: 1853
Registered: July 2009 |
Senior Member |
|
|
As a new Oomph user, I was playing around with creating a new Project Setup, found I might have made a mistake, and wanted to make a fresh start, only to find that Oomph is smart enough to remember each of my mistakes.
Are there any guides where exactly cleanup may be needed for a fresh start on authoring setups?
One thing I found:
- during my first attempt I put a workspace into a wrong location. In that location I had already created a project setup and somehow hooked it up into something.
- after moving that workspace to a different location I got unresolved EProxies from Oomph, and a lot look not right.
- I could see the unresolved proxy in the editors, but I found now way to delete the bogus stuff
- after a lot of poking around I found traces of the broken first attempt in .eclipse/org.eclipse.oomph.setup/setups/org.eclipse.projects.setup
Obviously, beginners make more mistakes than experts. OTOH, beginners have no idea where their experiments left persistent changes.
Aside from guides for cleaning up: would it be possible to create an Oomph-authoring environment in some kind of sandbox that is *not* connected to my local configurations (neither installation nor user ...)? Something that is neither influenced by my private configuration, nor merged into it?
thanks,
Stephan
|
|
|
| Re: how to recover from mistakes? [message #1713819 is a reply to message #1713759] |
Fri, 06 November 2015 17:15  |
Ed Merks
Messages: 33258
Registered: July 2009 |
Senior Member |
|
|
Stephan,
Comments below.
On 06/11/2015 2:18 PM, Stephan Herrmann wrote:
> As a new Oomph user, I was playing around with creating a new Project
> Setup, found I might have made a mistake, and wanted to make a fresh
> start, only to find that Oomph is smart enough to remember each of my
> mistakes.
It has a mind like a steel trap. :-P
>
> Are there any guides where exactly cleanup may be needed for a fresh
> start on authoring setups?
Things like the user extensions of the catalogs can accumulate garbage,
so you can open those from the navigate menu or the toolbar to clean
them up... Otherwise, it's not clear what needs cleaning up to the
extent that it causes problems if you don't.
Note that if you open the overall index and show all resources via the
toolbar button, you can see everything and if there are broken proxies,
they'll be marked with errors. Ideally there are no red markers. Note
that you can only modify the first resource in the resource set, so if
you see another resource with errors, you can open it in its own setup
editor via the context menu on the resource object.
>
> One thing I found:
> - during my first attempt I put a workspace into a wrong location.
I'm not sure what that means. How was it wrong?
> In that location I had already created a project setup and somehow
> hooked it up into something.
It writes out a workspace.setup into the workspace; that would overwrite
an existing on if there was one.
> - after moving that workspace to a different location I got unresolved
> EProxies from Oomph, and a lot look not right.
Workspaces and installations are generally not moveable. Best to delete
them and create fresh clean things.
> - I could see the unresolved proxy in the editors, but I found now way
> to delete the bogus stuff
As I mentioned above, only the first resource is editable. So if there
are errors in other resources, open them in their own editor via the
context menu "Open in Setup Editor".
> - after a lot of poking around I found traces of the broken first
> attempt in
> .eclipse/org.eclipse.oomph.setup/setups/org.eclipse.projects.setup
Yes, your user extension of the catalog.
> Obviously, beginners make more mistakes than experts. OTOH, beginners
> have no idea where their experiments left persistent changes.
The user catalogs are also editable in the wizards. You can select the
project setups you added and use the red "-" button to delete them.
>
> Aside from guides for cleaning up: would it be possible to create an
> Oomph-authoring environment in some kind of sandbox that is *not*
> connected to my local configurations (neither installation nor user
> ...)? Something that is neither influenced by my private
> configuration, nor merged into it?
No, it's all intended to be an integrated whole. It sounds like mostly
you just didn't notice how to delete things you added in the wizard.
>
> thanks,
> Stephan
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: how to recover from mistakes? [message #1713842 is a reply to message #1713819] |
Fri, 06 November 2015 22:44 |
Stephan Herrmann
Messages: 1853
Registered: July 2009 |
Senior Member |
|
|
Hi Ed,
Ed Merks wrote on Fri, 06 November 2015 18:15
It has a mind like a steel trap. 
That usually is great, but can at times be a problem ...
Quote:
Note that if you open the overall index and show all resources via the
toolbar button, you can see everything and if there are broken proxies,
they'll be marked with errors. Ideally there are no red markers. Note
that you can only modify the first resource in the resource set, so if
you see another resource with errors, you can open it in its own setup
editor via the context menu on the resource object.
The last item was where I failed: I saw the unresolvable thing in various tree editors, but in none of them it could be deleted.
I'm back on track by having learned:
- tree editors like the overall index show a mix of resources and eobjects
- (some) resources have an "Open In Setup Editor" context command
- after travelling to the containing resource its content can be edited.
Wouldn't it be useful if a double click on any object in the tree would navigate to the place where it is declared and editable?
Quote:
> One thing I found:
> - during my first attempt I put a workspace into a wrong location.
I'm not sure what that means. How was it wrong?
Basically this was just an example of: user's make mistakes, or may change their mind or such. Specifically, I specified the parent folder of all my workspaces, hoping that a new workspace would be created inside, but I ended up with nested workspaces which doesn't seem like a good idea 
Quote:
> - after moving that workspace to a different location I got unresolved
> EProxies from Oomph, and a lot look not right.
Workspaces and installations are generally not moveable. Best to delete
them and create fresh clean things.
I know to be careful with such moves, but even deleting would have led to the same problem, since the then-deleted thing was still referenced in .eclipse/org.eclipse.oomph.setup/setups/org.eclipse.projects.setup
Quote:
> Aside from guides for cleaning up: would it be possible to create an
> Oomph-authoring environment in some kind of sandbox that is *not*
> connected to my local configurations (neither installation nor user
> ...)? Something that is neither influenced by my private
> configuration, nor merged into it?
No, it's all intended to be an integrated whole. It sounds like mostly
you just didn't notice how to delete things you added in the wizard.
Well, I'll see how it works out now that I can proceed. I assume some isolation would be achieved when strictly using one workspace only for authoring one particular setup. Is that the recommended approach?
thanks again,
Stephan
|
|
|
| Re: how to recover from mistakes? [message #1713846 is a reply to message #1713842] |
Sat, 07 November 2015 03:45 |
Ed Merks
Messages: 33258
Registered: July 2009 |
Senior Member |
|
|
Stephan,
The context menu on any object, including any resource, should have
"Open in Setup Editor" in the context menu and should open that object's
resource in a separate editor. If it's a local resource from the file
system or workspace, it should be editable; if that's not the case,
please open a bugzilla with an example. Also note that the hover text
for the error diagnostics should allow you to navigate to the object
with the error (thought there's a bug in EMF
https://bugs.eclipse.org/bugs/show_bug.cgi?id=480064 that hinders this).
In the end, the only resources that have lasting global impact are the
ones in your user.setup and your catalog extensions, i.e., the things in
..eclipse/org.eclipse.oomph.setup/setups/. so I suppose isolation would
be achieved by specifying user.home to be somewhere else. One good
trick is to make that folder be a local git clone and to have that
folder in your workspace as a project; this way you can commit changes
locally and maintain history, and use reset hard to clean up...
On 06/11/2015 11:44 PM, Stephan Herrmann wrote:
> Hi Ed,
>
> Ed Merks wrote on Fri, 06 November 2015 18:15
>> It has a mind like a steel trap. :p
>
> That usually is great, but can at times be a problem ...
>
> Quote:
>> Note that if you open the overall index and show all resources via
>> the toolbar button, you can see everything and if there are broken
>> proxies, they'll be marked with errors. Ideally there are no red
>> markers. Note that you can only modify the first resource in the
>> resource set, so if you see another resource with errors, you can
>> open it in its own setup editor via the context menu on the resource
>> object.
>
> The last item was where I failed: I saw the unresolvable thing in
> various tree editors, but in none of them it could be deleted.
>
> I'm back on track by having learned:
> - tree editors like the overall index show a mix of resources and
> eobjects
> - (some) resources have an "Open In Setup Editor" context command
> - after travelling to the containing resource its content can be edited.
>
> Wouldn't it be useful if a double click on any object in the tree
> would navigate to the place where it is declared and editable?
>
> Quote:
>> > One thing I found:
>> > - during my first attempt I put a workspace into a wrong location.
>> I'm not sure what that means. How was it wrong?
>
> Basically this was just an example of: user's make mistakes, or may
> change their mind or such. Specifically, I specified the parent folder
> of all my workspaces, hoping that a new workspace would be created
> inside, but I ended up with nested workspaces which doesn't seem like
> a good idea :)
>
> Quote:
>> > - after moving that workspace to a different location I got
>> unresolved > EProxies from Oomph, and a lot look not right.
>> Workspaces and installations are generally not moveable. Best to
>> delete them and create fresh clean things.
>
> I know to be careful with such moves, but even deleting would have led
> to the same problem, since the then-deleted thing was still referenced
> in .eclipse/org.eclipse.oomph.setup/setups/org.eclipse.projects.setup
>
> Quote:
>> > Aside from guides for cleaning up: would it be possible to create
>> an > Oomph-authoring environment in some kind of sandbox that is
>> *not* > connected to my local configurations (neither installation
>> nor user > ...)? Something that is neither influenced by my private >
>> configuration, nor merged into it?
>> No, it's all intended to be an integrated whole. It sounds like
>> mostly you just didn't notice how to delete things you added in the
>> wizard.
>
>
> Well, I'll see how it works out now that I can proceed. I assume some
> isolation would be achieved when strictly using one workspace only for
> authoring one particular setup. Is that the recommended approach?
>
> thanks again,
> Stephan
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
| |
Goto Forum:
Current Time: Sat Dec 07 14:51:24 GMT 2024
Powered by FUDForum. Page generated in 0.03031 seconds |
] 
Search
Help
Register
Login
Home
