Community
Participate
Working Groups
It would be convenient if user could export (end import) task content for specific task from standard Eclipse File->Export (Import) dialogs. Current method of using drag-and-drop from task list to file system and back is not immediately obvious for most of the users.
I'd like to suggest to extend Attach/Retrieve context actions to allow to save/read context to and from file system.
This sounds good to me. Drag-and-drop can be a pain and as you indicate is not obvious. What I've also been thinking about is something like a "Send to" button that could have the following in it's sub-menu: * Task Repository: e.g. to convert a local task to a repository task, prompts for repository, can attach context if available * File: creates a zip file with the context, and a proxy for the task and repository Then we could the Retrieve Context wizard page to allow such a zip to be selected. But this would probably also need to work via Import/Export, since some users would expect it to be there. Thoughts?
*** Bug 178908 has been marked as a duplicate of this bug. ***
By the way, Mik. I've been talking with Dmitri about this and he suggested to allow to save those contexts into the workspace. My initial though was that we have cross-project contexts, so it won't be really god idea. However on a second thought it would work really nice for small single-project setups and for multiple projects user can actually dedicate special project for saving contexts. Then, if needed, those contexts can be committed to the version control outside of Mylar (at least for now). So, users would have an alternative way to share those contexts. It might work even nicer if we can point Mylar's folder where those contexts are stored to the same project folder... So, when you'll be sketching this UI, I suggest design it similar to first wizard page of the attachment wizard, except that "clipboard" choice would be "repository".
I agree with Eugene on this. Quite often my tasks are confined within one project and having ability to (optionally) store context into the project workspace would be great. This way it could be commited into version control as any other file.
(In reply to comment #0) > Current method of using drag-and-drop from task list to file system and back is > not immediately obvious for most of the users. Cool! I did not believe that drag'n'drop works for KDE, but it really works. So for the moment, I have a suitable workaround. But an explicit "Save / Load..." dialog would be helpful, though. Please go ahead :-)
Patch welcome on this in case anyone wants it soon, but I'd like to see it in 2.0 so adding to our overloaded schedule :)
(In reply to comment #7) > Patch welcome on this in case anyone wants it soon, but I'd like to see it in > 2.0 so adding to our overloaded schedule :) Mik, I already had your Mylar-E_3_2 working set in my workspace and started tracking your source changes. But I have no experience in plugin development, so some starting points would be helpful. Would you mind to attach a task context for the E_3_2 branch? Thanks, Jörg
This a good source of materials for getting started with plug-in development: http://www.eclipse.org/articles/ To get started, I suggest taking a look at the TaskDataImportWizard, but you'll probably want to make a separate wizard for this. For the first pass it should be able to do an import of a task context that was dragged out, and use the same underlying facility for moving the context out (that's current in TaskListDragSourceListener, but should be abstracted out so that both the wizard and the dragging can call it).
Created attachment 62044 [details] mylar/context/zip
(In reply to comment #9) > This a good source of materials for getting started with plug-in development: > http://www.eclipse.org/articles/ > To get started, I suggest taking a look at the TaskDataImportWizard, [...] OK. Thanks, Mik. I will look at this as soon as I have time. Currently I am very busy and lost half a day due to 179494: Complete Eclipse lookup due to XML file in task context
Jvgeni: this is a good first task for your summer of code work.
Created attachment 72288 [details] Export wizard Attached an intermediate patch - context export functionality (File export menu & context popup menu)
Created attachment 72289 [details] mylar/context/zip
Created attachment 72290 [details] Working patch Now this patch should work. Difference with the first one - now context popup menu should contain Export Context action.
Created attachment 72291 [details] mylar/context/zip
Jvgeni: I will try to review next week, but at this point in the cycle could get delayed if anything comes up with Europa since we won't be able to incorporate this until after Europa. In the meantime, could you please synch up and create a new patch? Source cleanup has made this one go stale.
(In reply to comment #17) > Jvgeni: I will try to review next week, but at this point in the cycle could > get delayed if anything comes up with Europa since we won't be able to > incorporate this until after Europa. In the meantime, could you please synch > up and create a new patch? Source cleanup has made this one go stale. Yes, after I'm finished with "importing", I'll synch and then submit a new patch.
Created attachment 72490 [details] Context export/import from file or context menu wizards This patch does not contain .refactorings files, tell me, if you prefer a patch with them, I'll create another one.
Created attachment 72491 [details] mylar/context/zip
Just checked the latest patch, it merged with latest changes without conflicts.
Jevgeni: fyi, I've done a very quick review and this looks promising. The only problem is that, as mentioned previously, we need to review patches in smaller chunks. There are practical reasons for this (they are easier to review) but there is also a legal reason (I cannot apply patches over a certain size ~250 lines of code) without kicking off an IP review process. Could you please break this up into 2-3 patches that separate the functionality (e.g. wizard, tests, etc.)?
Created attachment 73243 [details] Added hasChildren method
Created attachment 73244 [details] Export Context Wizards
Created attachment 73245 [details] Import Context Wizard
Created attachment 73246 [details] Task Context Export test
Created attachment 73247 [details] Task Context Export/Import from Context Menu
Mik: Export and Import wizard patches come out to be larger than 250 lines of code, since I was not able to split them without breaking the code.
Did not apply "Added hasChidren method" patch since not much Utility in hasChildren() method. Instead I changed the client call to be !container.getChildren().isEmpty(). Could not apply "Export Context Wizards" patch since it has a conflict. Did not apply the "Import Context Wizard" patch because the UI design is problematic. The amount of times that people will import a context from a global wizard is likely to be very low, so not worth adding a new wizard page to complicate the current workflow. Do the following instead: * Add an "Import..." action to the "Context" section of the task's popup menu. Have this pop up a wizard similar to the one that you have now. * The wizard page should allow the user to select a file as the source of the context as you currently do. No need to list tasks since that's the "Copy context to..." functionality, which we can consider merging later.
Created attachment 74477 [details] Task Context exporting/importing from task list menu For both cases a file dialog asks for the context file. Context exporting is done by copying the original context file from the mylyn working folder to the destination. (If the context for a task is not yet created, then trying to export it leads to "noFileFoundException". I'll suppose it is a separate issue, isn't it?). Context importing is done by deactivating the task first and then using the existing mylyn API activating it with a new context.
Created attachment 74478 [details] mylyn/context/zip
Any updates on this bug?
(In reply to comment #32) > Any updates on this bug? > No yet, I have been working on exporting/importing using drag&drop and task list context menu. So far, we have concluded that this is more frequent and easy way of exporting/importing task.
I'm wondering what the value of providing this via the File menu is. You would then have to find the task you wanted to import and export, so we would need to duplicate functionality that's already available in the Task List via the popup menu. Thoughts?
This is already provided in the Task List popup menu. So I remove my vote.
Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn
