search

tweezy23 / anyedittools

Automatically exported from code.google.com/p/anyedittools
2 stars 0 forks source link

Allow replacing / merging working sets on import #66

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Import a .wst file defining project sets already contained in the workspace.

What is the expected output? What do you see instead?
It would be nice if importing a .wst file would behave similarly to importing 
.psf files: When importing a .psf file (e.g. containing SVN project references) 
the wizard asks what to do with project sets which already exist in the 
workspace. There is the option to "merge" or "replace", both of which can be 
very handy.

What version of the product are you using? On what operating system?
Any Edit 2.4.0.201101292156. Mac OS X.

Please provide any additional information below.
We are currently using Any Edit .wst files as a replacement for .psf files as 
supported by Eclipse Egit. We found the latter to be somewhat too limited.

Original issue reported on code.google.com by knut.wan...@gmail.com on 27 Feb 2012 at 9:37

GoogleCodeExporter commented 9 years ago 
I see your pain.

Original comment by iloveeclipse on 27 Feb 2012 at 9:43

GoogleCodeExporter commented 9 years ago

Original comment by iloveeclipse on 27 Feb 2012 at 10:18

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision a35f7c66051e.

Original comment by iloveeclipse on 27 Feb 2012 at 10:37

GoogleCodeExporter commented 9 years ago 
Attached is the beta update site release which fixes issue 65 and 66.
Please give it a try, and feel free to reopen any of the issues above if you 
don't like the implementation.

P.S. You have to uncheck "show groups" checkbox in the stupid update wizard to 
see the plugin.

Regards,
Andrey

Original comment by iloveeclipse on 27 Feb 2012 at 10:40

Attachments:

GoogleCodeExporter commented 9 years ago 
Hi Andrey,

Thank you very much for the quick fix! I will try it out later today and give 
you feedback.

Regards,
Knut

Original comment by knut.wan...@gmail.com on 28 Feb 2012 at 5:39

GoogleCodeExporter commented 9 years ago 
Your fixes seem to work very well! I have one small change I'd like to propose: 
The option of either merging or replacing a working set (or even all working 
sets) is a very handy feature present in the project set import wizard. See 
screenshot: http://tinypic.com/r/143zzuf/5. It is for instance very useful if a 
coworker moves a project from one working set to another and you'd like to use 
the same working set configuration.

Original comment by knut.wan...@gmail.com on 28 Feb 2012 at 6:59

GoogleCodeExporter commented 9 years ago 
Hi Knut,

Please next time attach pictures here, as is external attachments tend to 
disappear very soon.

I'm not sure if I understood you right. Seems that it is not enough for you to 
have one option "to merge or not", but you want to decide it for each working 
set?
Can you please describe step by step the workflow you would like to see?

CU
Andrey

Original comment by iloveeclipse on 28 Feb 2012 at 7:59

GoogleCodeExporter commented 9 years ago 
Hi Andrey

I actually tried to find a way to attach the screenshot to the issue, but 
somehow I missed the "Attach a file" link that appears once you start typing in 
the comment area. I've now attached the screenshot to the issue.

It is mostly the "replace" operation which I am missing. By selecting "replace" 
instead of "merge" the corresponding project sets would first be cleared. A 
"merge" on the other hand will simply add any projects to the project set which 
are not already in it.

By addressing this with a separate dialog as in the screenshot (as opposed to a 
checkbox in the wizard) it is then also possible to let the user make this 
decision for every individual project set. Although I assume most users will 
typically select the "Apply to all working sets in this import" checkbox.

So the workflow would be the same as for .psf files:

1. Select the .wst file in the import wizard and click finish. The wizard does 
not need to display any options yet.
2a. If none of the project sets in the .wst file already exists in the 
workspace, they are created and populated as usual.
2b. If a project set in the .wst file is encountered which already exists in 
the workspace then display a modal dialog (as in the screenshot) which allows 
the user to "merge", "replace", or "cancel". Optimally also with a "Apply to 
all working sets in this import" checkbox.

Hope that makes it clearer.

Original comment by knut.wan...@gmail.com on 28 Feb 2012 at 8:22

Attachments:

GoogleCodeExporter commented 9 years ago 
Feel free to provide a patch for the dialog as shown, I will be happy to 
integrate it.

Due lack of time I've released the version containing my original patch.

Original comment by iloveeclipse on 3 Apr 2012 at 10:40

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision 7355ce93b855.

Original comment by iloveeclipse on 31 Dec 2012 at 1:03