Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 363864 - [epub] UI command for converting to EPUB should use previous settings
Summary: [epub] UI command for converting to EPUB should use previous settings
Status: CLOSED MOVED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Torkild Resheim CLA
QA Contact: Torkild Resheim CLA
URL:
Whiteboard:
Keywords:
Depends on: 332122
Blocks:
  Show dependency tree
 
Reported: 2011-11-15 15:08 EST by Torkild Resheim CLA
Modified: 2013-04-16 16:38 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Torkild Resheim CLA 2011-11-15 15:08:51 EST 
When converting a markup file to EPUB one has to fill out certain fields before being allowed to continue. When converting the same file again, the process has to be repeated. It would be helpful if the values entered would be stored and reused when displaying the wizard again.
Comment 1 Torkild Resheim CLA 2012-03-12 18:24:24 EDT 
I can see two different approaches to solving this issue. One is to unpack the already present EPUB (if there is one) and obtain the information required from there (easy). And another is to store the information when executing the wizard to a specification file (more work). However these are quite different. The latter will result in a small file that can and should be committed to a RCS, the prior should never be checked in as it is the end result.

If the prior approach is chosen it could be a good idea to actually generate a subset of the Ant script (everything within the <epub> element) and store this to a file. The code could later be used to actually generate the Ant script if the user desires so. Similar to what the PDE "export to deployable..." does.
Comment 2 Torkild Resheim CLA 2012-03-12 18:35:40 EDT 
(In reply to comment #1)
> If the prior approach is chosen it could be a good idea to actually generate a
> subset of the Ant script (everything within the <epub> element) and store this
> to a file. The code could later be used to actually generate the Ant script if
> the user desires so. Similar to what the PDE "export to deployable..." does.
This should of course read the "latter approach". Another benefit could be that it should be possible to drive the assembly using Ant instead of having another implementation that does pretty much the same job just for for the UI. This could lead to much more advanced features more easily implemented in the wizard without having to do anything but the UI.
Comment 3 Torkild Resheim CLA 2012-05-11 03:12:32 EDT 
Moving to new EPUB component.
Comment 4 Torkild Resheim CLA 2013-04-16 16:38:49 EDT 
After given this some more thought I think the best approach would be to reuse the existing data model. One could subclass elements in dc.ecore, ocf.recore and opf.ecore as required for adding extra information where appropriate. This would enable to UI command to make use of both the existing API and the entire data space.
Comment 5 Eclipse Webmaster CLA 2022-11-15 11:45:08 EST 
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