Ticket #2530 (s3a_implementation_started bug)
[html] Create unsupported content type frame
Reported by: | deyan | Owned by: | antoni |
---|---|---|---|
Priority: | major | Milestone: | Y1 |
Component: | uncategorized | Version: | 2.0 |
Keywords: | Cc: | ||
Category: | unknown | Effort: | |
Importance: | Ticket_group: | ||
Estimated Number of Hours: | 0 | Add Hours to Ticket: | 0 |
Billable?: | yes | Total Hours: | 0 |
Analysis_owners: | Design_owners: | ||
Imp._owners: | Test_owners: | ||
Analysis_reviewers: | Changelog: | Changelog | |
Design_reviewers: | Imp._reviewers: | ||
Test_reviewers: | Analysis_score: | 0 | |
Design_score: | 0 | Imp._score: | 0 |
Test_score: | 0 |
Description
When exporting frames that are not supported in Sophie, an exception is thrown. Implement a mechanism to handle unsupported content type export.
Change History
comment:2 Changed 13 years ago by antoni
- Status changed from s1b_analysis_finished to s2a_design_started
comment:3 Changed 13 years ago by antoni
- Status changed from s2a_design_started to s2b_design_finished
comment:5 Changed 13 years ago by antoni
- Owner set to antoni
- Status changed from s2c_design_ok to s3a_implementation_started
comment:6 Changed 13 years ago by antoni
Stub of PDF frames JSON persister is added.
Content of frames is not exported yet, only borders and styles of frame.
However exception is not thrown anymore when we try to export book with PDF frames to HTML.
Code is commited in revision [10062].
comment:7 Changed 13 years ago by antoni
PDF frame JSON persister is implemented.
Now every page of PDF file is exported as single image.
These images are stored in images folder.
Path to sources of images are listed in "pdfPages" field of frame JSON object data.
Code is commited in revision [10072].
Thing to do(improve):
Renderer in HTML reader is not imlpemented.
Check whether paths of new exported images are added to manifest.xml file.
May be progress bar for PDF frames must be implemented, to show current exported page of pdf (for large pdf files).