Re: [mylar-dev] Integrating Mylar with web repositories instead of the o

[Eugene Kuleshov <eu@xxxxxxxx>]

Erkki,

 Please note that the original goal of generic web repository connector 
was to bring list of tasks into Mylar's Task List view and automatically 
receive updates on those tasks. All the editing, besides traditional 
*online* browser integration is out of scope and that is what 
repository-specific connectors for.

 So, all in all it is better to not overcomplicate UI and functionality 
of the web repository connector. However you can probably use its code 
as a starting point to build a repository-specific connector.

 regards,
 Eugene

PS: btw, there is ongoing major rewrite for the web connector UI that 
suppose to significantly simplify end-user experience for configuring 
web connector and its queries...

PPS: it should be possible to handle drag-n-drop from the browser to 
(for example) Task List view and detect that it is a context archive.

PPPS: As for the patches, there is an ongoing investigation in scope of 
Bugzilla connector about applying patches via drag-n-drop. Though API 
for applaying patches had been only added into Eclipse 3.3M3 (released 
today).



Erkki Lindpere wrote:
> After I finally started using Mylar for my real work (with a very
> basic ChangeLogic integration through the sandbox's web repository
> support), and Mik's comment in
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=162885, I have some
> questions about whether it would be beneficial to develop better
> generic web repository support...
>
> For example,
> Creating a rich editor for a particular repository (I'm not aware of
> the status of this, is there a generic editor in development?)
> vs.
> Hooking Mylar into the internal browser to work better with the
> repository's existing UI.
>
> Is the latter possible? For example, could Mylar detect that when the
> user is opening an URL with a certain content type or file name, it's
> actually the zipped task context? And the same with patches.
>
> Extra fine would be if uploading task context could be simplified
> somehow, but I doubt that hooking into the browser's file chooser is
> possible.
>
> Erkki