[Okular-devel] [Bug 136574] Wish; Show videos in a pdf
https://bugs.kde.org/show_bug.cgi?id=136574 Albert Astals Cid tsdg...@terra.es changed: What|Removed |Added Status|NEW |RESOLVED CC||tsdg...@terra.es Version Fixed In||4.9.0 Resolution|--- |FIXED --- Comment #27 from Albert Astals Cid tsdg...@terra.es --- Agreed with Oliver -- You are receiving this mail because: You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 300051] New: Movie doesn't autostart in pdf created with LaTeX multimedia and pdflatex
https://bugs.kde.org/show_bug.cgi?id=300051 Bug ID: 300051 Severity: normal Version: 0.12.5 Priority: NOR Assignee: okular-devel@kde.org Summary: Movie doesn't autostart in pdf created with LaTeX multimedia and pdflatex Classification: Unclassified OS: Linux Reporter: san...@mi.fu-berlin.de Hardware: Compiled Sources Status: UNCONFIRMED Component: PDF backend Product: okular Movies embedded into pdf files using latex and the 'multimedia' package do not autostart even though being told to do so if the tex sources are compiled using pdflatex. Note: it does work when you compile the tex sources with latex - dvips - ps2pdf. That's a different code path. You need latex-beamer (which multimedia.sty is a part of) in at least version 3.18. See the discussion here: https://bitbucket.org/rivanvx/beamer/issue/188/autostart-of-video-files-not-working This may actually be a poppler issue. Please apologize if I posted in the wrong spot. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 300051] Movie doesn't autostart in pdf created with LaTeX multimedia and pdflatex
https://bugs.kde.org/show_bug.cgi?id=300051 --- Comment #1 from Oliver Sander san...@mi.fu-berlin.de --- Created attachment 71098 -- https://bugs.kde.org/attachment.cgi?id=71098action=edit Test file that reproduces the error -- You are receiving this mail because: You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 300051] Movie doesn't autostart in pdf created with LaTeX multimedia and pdflatex
https://bugs.kde.org/show_bug.cgi?id=300051 --- Comment #2 from Oliver Sander san...@mi.fu-berlin.de --- Created attachment 71099 -- https://bugs.kde.org/attachment.cgi?id=71099action=edit tex sources -- You are receiving this mail because: You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 300051] Movie doesn't autostart in pdf created with LaTeX multimedia and pdflatex
https://bugs.kde.org/show_bug.cgi?id=300051 --- Comment #3 from Oliver Sander san...@mi.fu-berlin.de --- The actual movie I used in the pdf is too large to upload it here. I put it on http://page.mi.fu-berlin.de/sander/data/test_movie.mpg -- You are receiving this mail because: You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
Re: [Okular-devel] Okular active
On Monday 14 May 2012 21:04:49 Marco Martin wrote: Hi all, (please maintain CC: since not everybody is subscribed to both lists) Looking at the current status of applications that are shipped with Plasma active (and will be on the first device) we seen that there wasn't a satisfying application for reading ebooks. Okular is preinstalled, but with a touch screen has some problems, especially small screens. Another application was developed, tablet reader but had some problems (wasn't really integrated with kde or plasma active, no possibility to open remote files, had a custom file selection dialog, two separate declarative views) But, looking at the Okular core library, we seen that is very widget-agnostic, clean and gives all for free (multiple types, tables of contents..) in the branch mart/okularActive, there is: * a qml plugin that depends only on okularcore (only had to duplicate pagepainter from ui/ hopefully will be possible to avoid that) * a small qml application that uses plasma components and the small app library from Plasma Active (conditional build over that library) Since doesn't have particular dependencies the component can be used not only in plasma active byt anywhere in qml. The app is purposedly very barebone, so far looks like this: http://wstaw.org/m/2012/05/14/plasma-desktopXi3533.png It is supposed to view a single document, still very basic, (is just possible to see a page or a thumbnail grid of all pages, things like table of contents, bookmarks, annotations will come eventually), and is supposed to be launched by clicking on a file on a filemanager (or the active file browser) so it's hidden from the menu and doesn't even start alone. The qml components just let to paint pages for now, i hope will be possible soon to add search, table of contents and support for hyperlinks (maybe the api will have to be changed a bit to have that) Cheers, Marco Martin So is this based on Bogdan's work to integrate the Okular libraries into tabletReader or did he abandon this work or was it wasted because the result is just being discarded? And is there already a package in the OBS for testing it? If so, what's its name? The screenshot looks nice, but I'd like to see it in action so I can give feedback. Cheers, Thomas Pfeiffer ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
Re: [Okular-devel] Review Request: Use the left/right arrow keys to change the page
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/104596/#review13863 --- Hi Thomas, seems the patch does not apply cleanly anymore (or so says reviewboard when i press the View Diff button) can you please rebase it and update it here? - Albert Astals Cid On May 1, 2012, 4:53 p.m., Thomas Etter wrote: --- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/104596/ --- (Updated May 1, 2012, 4:53 p.m.) Review request for Okular and Albert Astals Cid. Description --- If no horizontal scrollbar is visible, change pages using the left/right arrow keys. In facing mode, move two pages per key press. Diffs - ui/pageview.cpp 4be5e6b Diff: http://git.reviewboard.kde.org/r/104596/diff/ Testing --- Works on my system Thanks, Thomas Etter ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
Re: [Okular-devel] Okular active
On Tuesday 15 May 2012, Albert Astals Cid wrote: El Dilluns, 14 de maig de 2012, a les 21:04:49, Marco Martin va escriure: Hi all, Hi (please maintain CC: since not everybody is subscribed to both lists) Looking at the current status of applications that are shipped with Plasma active (and will be on the first device) we seen that there wasn't a satisfying application for reading ebooks. Okular is preinstalled, but with a touch screen has some problems, especially small screens. Another application was developed, tablet reader but had some problems (wasn't really integrated with kde or plasma active, no possibility to open remote files, had a custom file selection dialog, two separate declarative views) But, looking at the Okular core library, we seen that is very widget-agnostic, clean and gives all for free (multiple types, tables of contents..) in the branch mart/okularActive, there is: * a qml plugin that depends only on okularcore (only had to duplicate pagepainter from ui/ hopefully will be possible to avoid that) * a small qml application that uses plasma components and the small app library from Plasma Active (conditional build over that library) Since doesn't have particular dependencies the component can be used not only in plasma active byt anywhere in qml. The app is purposedly very barebone, so far looks like this: http://wstaw.org/m/2012/05/14/plasma-desktopXi3533.png It is supposed to view a single document, still very basic, (is just possible to see a page or a thumbnail grid of all pages, things like table of contents, bookmarks, annotations will come eventually), and is supposed to be launched by clicking on a file on a filemanager (or the active file browser) so it's hidden from the menu and doesn't even start alone. The qml components just let to paint pages for now, i hope will be possible soon to add search, table of contents and support for hyperlinks (maybe the api will have to be changed a bit to have that) Looks great, I'm thinking that since okularcore headers are installed it might make sense in the future for it to live in separate repo (once the potential issues you might find with the library are ironed out). yeah, I agree, moving it outside would be better, and if it helps making okular core an independent library it's a plus ;) biggest issues atm i think are needing pagepainter (perhaps simplified and in okular core?) and the association between document and viewers (limited number, hardcoded ids) but i'm just looking at the okularcore library for the first time, so probably i forgotten details, I'm using the 1% of it, probably is going to stay quite minimal tough. i'm not sure about the qml bindings, i guess for bindings of various stuff the alternative is to put each one in the repo they depend on, or doing a repo of bindings (of which kde-runtime is kinda doing the task atm but not optimal) with each of them built conditionally, both have advantages and disadvantages, but this is for another thread ;) Cheers, Marco Martin ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
Re: [Okular-devel] Okular active
El Dimarts, 15 de maig de 2012, a les 23:07:07, Marco Martin va escriure: On Tuesday 15 May 2012, Albert Astals Cid wrote: El Dilluns, 14 de maig de 2012, a les 21:04:49, Marco Martin va escriure: Hi all, Hi (please maintain CC: since not everybody is subscribed to both lists) Looking at the current status of applications that are shipped with Plasma active (and will be on the first device) we seen that there wasn't a satisfying application for reading ebooks. Okular is preinstalled, but with a touch screen has some problems, especially small screens. Another application was developed, tablet reader but had some problems (wasn't really integrated with kde or plasma active, no possibility to open remote files, had a custom file selection dialog, two separate declarative views) But, looking at the Okular core library, we seen that is very widget-agnostic, clean and gives all for free (multiple types, tables of contents..) in the branch mart/okularActive, there is: * a qml plugin that depends only on okularcore (only had to duplicate pagepainter from ui/ hopefully will be possible to avoid that) * a small qml application that uses plasma components and the small app library from Plasma Active (conditional build over that library) Since doesn't have particular dependencies the component can be used not only in plasma active byt anywhere in qml. The app is purposedly very barebone, so far looks like this: http://wstaw.org/m/2012/05/14/plasma-desktopXi3533.png It is supposed to view a single document, still very basic, (is just possible to see a page or a thumbnail grid of all pages, things like table of contents, bookmarks, annotations will come eventually), and is supposed to be launched by clicking on a file on a filemanager (or the active file browser) so it's hidden from the menu and doesn't even start alone. The qml components just let to paint pages for now, i hope will be possible soon to add search, table of contents and support for hyperlinks (maybe the api will have to be changed a bit to have that) Looks great, I'm thinking that since okularcore headers are installed it might make sense in the future for it to live in separate repo (once the potential issues you might find with the library are ironed out). yeah, I agree, moving it outside would be better, and if it helps making okular core an independent library it's a plus ;) biggest issues atm i think are needing pagepainter (perhaps simplified and in okular core?) I'm unsure that pagepainter belongs into the okularcore library since the core library tries to be UI agnostic and the pagepainter is all but UI agnostic (as it *draws* stuff :D) and the association between document and viewers (limited number, hardcoded ids) Yep, that shall be easy to fix with a register call + return integet id instead of hardocded ids but i'm just looking at the okularcore library for the first time, so probably i forgotten details, I'm using the 1% of it, probably is going to stay quite minimal tough. There is also the problem of the settings class not being accessible from the outside but Bogdan is working on a patch to fix that (sitting in reviewboard waiting for me). Albert i'm not sure about the qml bindings, i guess for bindings of various stuff the alternative is to put each one in the repo they depend on, or doing a repo of bindings (of which kde-runtime is kinda doing the task atm but not optimal) with each of them built conditionally, both have advantages and disadvantages, but this is for another thread ;) Cheers, Marco Martin ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
Re: [Okular-devel] Review Request: Default settings file is separated in two files corresponding to the back end and the front end
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/104947/#review13868 --- Why is EnableCompositing in core if it is only used in ui? - Albert Astals Cid On May 14, 2012, 5:29 p.m., Bogdan Cristea wrote: --- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/104947/ --- (Updated May 14, 2012, 5:29 p.m.) Review request for Okular. Description --- Default settings file should be separated in two different files in order to have a better separation between okular core library (back end) and the front end (https://bugs.kde.org/show_bug.cgi?id=299526). This review request includes only the separation of okular.kcfg in two files: -okular.kcfg (front end) -okular_core.kcfg (back end) Diffs - CMakeLists.txt 0034cf3 conf/okular.kcfg 6ad0e19 conf/okular_core.kcfg PRE-CREATION conf/settings_core.kcfgc PRE-CREATION Diff: http://git.reviewboard.kde.org/r/104947/diff/ Testing --- No Thanks, Bogdan Cristea ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
Re: [Okular-devel] Review Request: Default settings file is separated in two files corresponding to the back end and the front end
On May 15, 2012, 9:38 p.m., Albert Astals Cid wrote: Why is EnableCompositing in core if it is only used in ui? It belongs to Dlg Performance group, same as MemoryLevel entry which is used in core, because I have tried to keep groups intact. If that is ok, I could split the groups too, using as group name in the core something like Core Performance instead of Dlg Performance. It seems to be rather easy to split everything if the respective entry is used or not in the core. I'll submit another patch with these changes if you agree with splitting groups also. - Bogdan --- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/104947/#review13868 --- On May 14, 2012, 5:29 p.m., Bogdan Cristea wrote: --- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/104947/ --- (Updated May 14, 2012, 5:29 p.m.) Review request for Okular. Description --- Default settings file should be separated in two different files in order to have a better separation between okular core library (back end) and the front end (https://bugs.kde.org/show_bug.cgi?id=299526). This review request includes only the separation of okular.kcfg in two files: -okular.kcfg (front end) -okular_core.kcfg (back end) Diffs - CMakeLists.txt 0034cf3 conf/okular.kcfg 6ad0e19 conf/okular_core.kcfg PRE-CREATION conf/settings_core.kcfgc PRE-CREATION Diff: http://git.reviewboard.kde.org/r/104947/diff/ Testing --- No Thanks, Bogdan Cristea ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
Re: [Okular-devel] Review Request: Use the left/right arrow keys to change the page
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/104596/ --- (Updated May 15, 2012, 10:31 p.m.) Review request for Okular and Albert Astals Cid. Changes --- Rebased patch on current master Description --- If no horizontal scrollbar is visible, change pages using the left/right arrow keys. In facing mode, move two pages per key press. Diffs (updated) - ui/pageview.cpp 4be5e6b Diff: http://git.reviewboard.kde.org/r/104596/diff/ Testing --- Works on my system Thanks, Thomas Etter ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
