Community
Participate
Working Groups
afaik Mylyn uses query's name when exporting a query. Why not to use the same pattern for exporting individual tasks?
That sounds good to me. The current scheme uses a unique name, but we could truncate the name after n characters and append an increasing integer if there was a name clash. If anyone is interested in contributing this please post. I'll add it for bugday since it's a straightforward contribution.
(In reply to comment #1) > That sounds good to me. The current scheme uses a unique name, but we could > truncate the name after n characters and append an increasing integer if there > was a name clash. If anyone is interested in contributing this please post. > I'll add it for bugday since it's a straightforward contribution. Mik, what is about the following implementation? For the export filename we can use the name of the query followed by the taskid.
Created attachment 90008 [details] mylyn/context/zip
I'm concerned that query + name would look weird because we don't have a clear character for delimiting them. We could use "-", but I have a bunch of queries with that character in the name ;) How about we take the first 50 characters of the task's label as it appears in the Task List? I think that's likely enough to be unique. If it's not the user should be prompted whether or not to overwrite. Frank: are you interested in taking this one on?
Do we need a query name when exporting tasks?
(In reply to comment #4) > I'm concerned that query + name would look weird because we don't have a clear > character for delimiting them. We could use "-", but I have a bunch of queries > with that character in the name ;) What do you think about # to delimiting them? > > How about we take the first 50 characters of the task's label as it appears in > the Task List? I think that's likely enough to be unique. If it's not the user > should be prompted whether or not to overwrite. > > Frank: are you interested in taking this one on? Yes, I can start Thursday evening (have to finish my seminar first). Please tell me if I should use # as a delimiter or the first 50 character suggested.
(In reply to comment #6) > Yes, I can start Thursday evening (have to finish my seminar first). Cool :) > Please tell me if I should use # as a delimiter or the first 50 character suggested. Go ahead with the first 50 and ignore the query name. Query names are not related to the identity of tasks and a task can appear in multiple queries.
Created attachment 91077 [details] Patch
Created attachment 91078 [details] mylyn/context/zip
Nice! Patch applied, ip log updated.
Is it possible to add the task id to that file name?
We could prefix the name with the task ide "123 - my task". Thoughts?
Created attachment 94866 [details] updated patch the name is now build as described in comment 12
Created attachment 94867 [details] mylyn/context/zip
(In reply to comment #12) > We could prefix the name with the task ide "123 - my task". Thoughts? (In reply to comment #13) > the name is now build as described in comment 12 Thanks Great. Thnx guys.
Patch applied, Ip log updated. Also updated to apply the same name when multiple tasks are selected. Created bug#226214 to address file name differences between dnd and this export facility.
