Talk:Read Etexts: Difference between revisions
Jump to navigation
Jump to search
HoboPrimate (talk | contribs) (Bundle Read and Read Etexts as one Read activity) |
|||
| Line 4: | Line 4: | ||
Is it too much of a hack if the Read activity had both yours and the evince program inside, launching each one depending on the file being opened?[[User:HoboPrimate|HoboPrimate]] 16:47, 7 May 2008 (EDT) |
Is it too much of a hack if the Read activity had both yours and the evince program inside, launching each one depending on the file being opened?[[User:HoboPrimate|HoboPrimate]] 16:47, 7 May 2008 (EDT) |
||
Regrettably it is. Activities pretty much have to set up their user interface BEFORE they receive the file they are to read. It is for this reason that View Slides and Read Etexts are separate programs, even though they share a fair amount of code and both can handle Zip files. |
|||
I think eventually Read will take over the functions of View Slides and Read Etexts by making modifications to evince. That's the only way I can see it working. |
|||
Revision as of 11:16, 8 May 2008
Do you use this activity? Got gripes, praise, or other feedback? Put it here.
Bundle Read and Read Etexts as one Read activity
Is it too much of a hack if the Read activity had both yours and the evince program inside, launching each one depending on the file being opened?HoboPrimate 16:47, 7 May 2008 (EDT)
Regrettably it is. Activities pretty much have to set up their user interface BEFORE they receive the file they are to read. It is for this reason that View Slides and Read Etexts are separate programs, even though they share a fair amount of code and both can handle Zip files.
I think eventually Read will take over the functions of View Slides and Read Etexts by making modifications to evince. That's the only way I can see it working.