[xwiki-devs] [Discussion] Office Presentation Viewer
Hi devs, Currently when we import an office presentation the office importer module generates an image for each slide and inserts it into the wiki syntax: image:myPresentation-slide0.jpg ... image:myPresentation-slideN.jpg Some users have complained that: * when the presentation has many slides (e.g. 100) the page is heavy because all the slide images are requested at page load time. * there's no way to switch slides using an user friendly UI. See http://jira.xwiki.org/jira/browse/XWIKI-5785 . One simple way to fix this is to group the images and to add a class name to the group. Then it will be easy to integrate an image gallery that replaces the group (found by its class name). I made a simple image gallery to demonstrate this. Please check http://incubator.myxwiki.org/xwiki/bin/view/Improvements/OfficePresentationV... . The class name used by the office importer module should be configurable and should have a default value (e.g. "gallery"). The office viewer macro can then be changed to have an optional cssClass parameter. It would be nice if the office importer/viewer would also use a default image gallery, i.e. request on demand the JavaScript code and the CSS for the default image gallery when the class name (e.g. cssClass parameter) is not specified. WDYT? Thanks, Marius
On 01/06/2011 10:37 AM, Marius Dumitru Florea wrote:
Hi devs,
Currently when we import an office presentation the office importer module generates an image for each slide and inserts it into the wiki syntax:
image:myPresentation-slide0.jpg ... image:myPresentation-slideN.jpg
Some users have complained that: * when the presentation has many slides (e.g. 100) the page is heavy because all the slide images are requested at page load time. * there's no way to switch slides using an user friendly UI. See http://jira.xwiki.org/jira/browse/XWIKI-5785 .
One simple way to fix this is to group the images and to add a class name to the group. Then it will be easy to integrate an image gallery that replaces the group (found by its class name).
I made a simple image gallery to demonstrate this. Please check http://incubator.myxwiki.org/xwiki/bin/view/Improvements/OfficePresentationV...
I like this approach, my +1
.
The class name used by the office importer module should be configurable and should have a default value (e.g. "gallery").
I don't find this really needed at this point.
The office viewer macro can then be changed to have an optional cssClass parameter.
The way I implemented these cssClass params for container is to add a class value to the existing default class, instead of replacing it -> it allows default behaviour + customizations. I followed the implementation of box macro wrt this, so I would suggest this behaviour. However, I have a little bug with the current impl, on my machine which has non default, smaller fonts in FF. See: http://incubator.myxwiki.org/xwiki/bin/download/Improvements/OfficePresentat... for a print screen, the presentation images are too low, overlapping the text under. Happy coding, Anca
It would be nice if the office importer/viewer would also use a default image gallery, i.e. request on demand the JavaScript code and the CSS for the default image gallery when the class name (e.g. cssClass parameter) is not specified.
WDYT?
Thanks, Marius _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Hi Marius, looks good to me. Maybe you should add a "gallery" or a "slideshow" macro that automatically to encapsulate the current code: {{slideshow attachment="wiki30-wysiwyg.odp"/}} would be equal to: {{velocity}} $xwiki.ssx.use('OfficePresentationViewer')## $xwiki.jsx.use('OfficePresentationViewer')## {{/velocity}} (% class="gallery" %)((( {{office attachment="wiki30-wysiwyg.odp"/}} ))) WDYT? Guillaume On Thu, Jan 6, 2011 at 11:36, Anca Luca <[email protected]> wrote:
On 01/06/2011 10:37 AM, Marius Dumitru Florea wrote:
Hi devs,
Currently when we import an office presentation the office importer module generates an image for each slide and inserts it into the wiki syntax:
image:myPresentation-slide0.jpg ... image:myPresentation-slideN.jpg
Some users have complained that: * when the presentation has many slides (e.g. 100) the page is heavy because all the slide images are requested at page load time. * there's no way to switch slides using an user friendly UI. See http://jira.xwiki.org/jira/browse/XWIKI-5785 .
One simple way to fix this is to group the images and to add a class name to the group. Then it will be easy to integrate an image gallery that replaces the group (found by its class name).
I made a simple image gallery to demonstrate this. Please check
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/OfficePresentationV...
I like this approach, my +1
.
The class name used by the office importer module should be configurable and should have a default value (e.g. "gallery").
I don't find this really needed at this point.
The office viewer macro can then be changed to have an optional cssClass parameter.
The way I implemented these cssClass params for container is to add a class value to the existing default class, instead of replacing it -> it allows default behaviour + customizations. I followed the implementation of box macro wrt this, so I would suggest this behaviour.
However, I have a little bug with the current impl, on my machine which has non default, smaller fonts in FF. See:
http://incubator.myxwiki.org/xwiki/bin/download/Improvements/OfficePresentat... for a print screen, the presentation images are too low, overlapping the text under.
Happy coding, Anca
It would be nice if the office importer/viewer would also use a default image gallery, i.e. request on demand the JavaScript code and the CSS for the default image gallery when the class name (e.g. cssClass parameter) is not specified.
WDYT?
Thanks, Marius _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
And yeah, me speak English no good today ;-) Guillaume On Fri, Jan 7, 2011 at 11:06, Guillaume Lerouge <[email protected]> wrote:
Hi Marius,
looks good to me.
Maybe you should add a "gallery" or a "slideshow" macro that automatically to encapsulate the current code:
{{slideshow attachment="wiki30-wysiwyg.odp"/}}
would be equal to:
{{velocity}} $xwiki.ssx.use('OfficePresentationViewer')## $xwiki.jsx.use('OfficePresentationViewer')## {{/velocity}} (% class="gallery" %)((( {{office attachment="wiki30-wysiwyg.odp"/}} )))
WDYT?
Guillaume
On Thu, Jan 6, 2011 at 11:36, Anca Luca <[email protected]> wrote:
On 01/06/2011 10:37 AM, Marius Dumitru Florea wrote:
Hi devs,
Currently when we import an office presentation the office importer module generates an image for each slide and inserts it into the wiki syntax:
image:myPresentation-slide0.jpg ... image:myPresentation-slideN.jpg
Some users have complained that: * when the presentation has many slides (e.g. 100) the page is heavy because all the slide images are requested at page load time. * there's no way to switch slides using an user friendly UI. See http://jira.xwiki.org/jira/browse/XWIKI-5785 .
One simple way to fix this is to group the images and to add a class name to the group. Then it will be easy to integrate an image gallery that replaces the group (found by its class name).
I made a simple image gallery to demonstrate this. Please check
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/OfficePresentationV...
I like this approach, my +1
.
The class name used by the office importer module should be configurable and should have a default value (e.g. "gallery").
I don't find this really needed at this point.
The office viewer macro can then be changed to have an optional cssClass parameter.
The way I implemented these cssClass params for container is to add a class value to the existing default class, instead of replacing it -> it allows default behaviour + customizations. I followed the implementation of box macro wrt this, so I would suggest this behaviour.
However, I have a little bug with the current impl, on my machine which has non default, smaller fonts in FF. See:
http://incubator.myxwiki.org/xwiki/bin/download/Improvements/OfficePresentat... for a print screen, the presentation images are too low, overlapping the text under.
Happy coding, Anca
It would be nice if the office importer/viewer would also use a default image gallery, i.e. request on demand the JavaScript code and the CSS for the default image gallery when the class name (e.g. cssClass parameter) is not specified.
WDYT?
Thanks, Marius _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Hello Marius, I like a lot the proposition. Features that are presented are what are needed : Next slide, previous slide, full screen. Same remark as Guillaume, making a slideshow macro (or even better current office preview, with a slideshow option) manage call to extensions, etc. makes sense. -- Thibaut On Fri, Jan 7, 2011 at 2:38 PM, Asiri Rathnayake <[email protected]
wrote:
+1
- Asiri _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Hi Marius, Very nice your gallery. My only observation is "Show previous image" | "Show next image" titles: "image" is kind of restrictive, you could use "slide". Thanks, Caty On Fri, Jan 7, 2011 at 17:30, Thibaut Camberlin <[email protected]
wrote:
Hello Marius,
I like a lot the proposition. Features that are presented are what are needed : Next slide, previous slide, full screen. Same remark as Guillaume, making a slideshow macro (or even better current office preview, with a slideshow option) manage call to extensions, etc. makes sense.
-- Thibaut
On Fri, Jan 7, 2011 at 2:38 PM, Asiri Rathnayake < [email protected]
wrote:
+1
- Asiri _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On 01/07/2011 06:00 PM, Ecaterina Moraru (Valica) wrote:
Hi Marius,
Very nice your gallery.
My only observation is "Show previous image" | "Show next image" titles: "image" is kind of restrictive, you could use "slide".
The only reason for this is that the gallery widget is not restricted to office presentation slides. It is a general purpose image gallery. The title for next/previous could be made configurable though. Thanks, Marius
Thanks, Caty
On Fri, Jan 7, 2011 at 17:30, Thibaut Camberlin<[email protected]
wrote:
Hello Marius,
I like a lot the proposition. Features that are presented are what are needed : Next slide, previous slide, full screen. Same remark as Guillaume, making a slideshow macro (or even better current office preview, with a slideshow option) manage call to extensions, etc. makes sense.
-- Thibaut
On Fri, Jan 7, 2011 at 2:38 PM, Asiri Rathnayake< [email protected]
wrote:
+1
- Asiri _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On Fri, Jan 7, 2011 at 8:59 PM, Marius Dumitru Florea < [email protected]> wrote:
On 01/07/2011 06:00 PM, Ecaterina Moraru (Valica) wrote:
Hi Marius,
Very nice your gallery.
My only observation is "Show previous image" | "Show next image" titles: "image" is kind of restrictive, you could use "slide".
The only reason for this is that the gallery widget is not restricted to office presentation slides.
IMO using one office macro with style option makes sense. When style is set to slideshow it would display the slideshow.
It is a general purpose image gallery.
We can still have a macro for galleries. I guess using the same code or not is an implementation issue.
The title for next/previous could be made configurable though.
Thanks, Marius
Thanks, Caty
On Fri, Jan 7, 2011 at 17:30, Thibaut Camberlin<
wrote:
Hello Marius,
I like a lot the proposition. Features that are presented are what are needed : Next slide, previous slide, full screen. Same remark as Guillaume, making a slideshow macro (or even better current office preview, with a slideshow option) manage call to extensions, etc. makes sense.
-- Thibaut
On Fri, Jan 7, 2011 at 2:38 PM, Asiri Rathnayake< [email protected]
wrote:
+1
- Asiri _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On 01/08/2011 11:21 AM, Thibaut Camberlin wrote:
On Fri, Jan 7, 2011 at 8:59 PM, Marius Dumitru Florea< [email protected]> wrote:
On 01/07/2011 06:00 PM, Ecaterina Moraru (Valica) wrote:
Hi Marius,
Very nice your gallery.
My only observation is "Show previous image" | "Show next image" titles: "image" is kind of restrictive, you could use "slide".
The only reason for this is that the gallery widget is not restricted to office presentation slides.
IMO using one office macro with style option makes sense. When style is set to slideshow it would display the slideshow.
Yes, that is my intention. I just have to figure out what's the best way to import the JavaScript and CSS style sheet from the macro code. Thanks, Marius
It is a general purpose image gallery.
We can still have a macro for galleries. I guess using the same code or not is an implementation issue.
The title for next/previous could be made configurable though.
Thanks, Marius
Thanks, Caty
On Fri, Jan 7, 2011 at 17:30, Thibaut Camberlin<
wrote:
Hello Marius,
I like a lot the proposition. Features that are presented are what are needed : Next slide, previous slide, full screen. Same remark as Guillaume, making a slideshow macro (or even better current office preview, with a slideshow option) manage call to extensions, etc. makes sense.
-- Thibaut
On Fri, Jan 7, 2011 at 2:38 PM, Asiri Rathnayake< [email protected]
wrote:
+1
- Asiri _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Very +1 for having only one simple macro to achieve the style. In my view I prefer {{office attachment="wiki30-wysiwyg.odp" style="xxx" /}} Ludovic Le 07/01/11 11:06, Guillaume Lerouge a écrit :
Hi Marius,
looks good to me.
Maybe you should add a "gallery" or a "slideshow" macro that automatically to encapsulate the current code:
{{slideshow attachment="wiki30-wysiwyg.odp"/}}
would be equal to:
{{velocity}} $xwiki.ssx.use('OfficePresentationViewer')## $xwiki.jsx.use('OfficePresentationViewer')## {{/velocity}} (% class="gallery" %)((( {{office attachment="wiki30-wysiwyg.odp"/}} )))
WDYT?
Guillaume
On Thu, Jan 6, 2011 at 11:36, Anca Luca<[email protected]> wrote:
On 01/06/2011 10:37 AM, Marius Dumitru Florea wrote:
Hi devs,
Currently when we import an office presentation the office importer module generates an image for each slide and inserts it into the wiki syntax:
image:myPresentation-slide0.jpg ... image:myPresentation-slideN.jpg
Some users have complained that: * when the presentation has many slides (e.g. 100) the page is heavy because all the slide images are requested at page load time. * there's no way to switch slides using an user friendly UI. See http://jira.xwiki.org/jira/browse/XWIKI-5785 .
One simple way to fix this is to group the images and to add a class name to the group. Then it will be easy to integrate an image gallery that replaces the group (found by its class name).
I made a simple image gallery to demonstrate this. Please check
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/OfficePresentationV...
I like this approach, my +1
.
The class name used by the office importer module should be configurable and should have a default value (e.g. "gallery"). I don't find this really needed at this point.
The office viewer macro can then be changed to have an optional cssClass parameter. The way I implemented these cssClass params for container is to add a class value to the existing default class, instead of replacing it -> it allows default behaviour + customizations. I followed the implementation of box macro wrt this, so I would suggest this behaviour.
However, I have a little bug with the current impl, on my machine which has non default, smaller fonts in FF. See:
http://incubator.myxwiki.org/xwiki/bin/download/Improvements/OfficePresentat... for a print screen, the presentation images are too low, overlapping the text under.
Happy coding, Anca
It would be nice if the office importer/viewer would also use a default image gallery, i.e. request on demand the JavaScript code and the CSS for the default image gallery when the class name (e.g. cssClass parameter) is not specified.
WDYT?
Thanks, Marius _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost
participants (7)
-
Anca Luca -
Asiri Rathnayake -
Ecaterina Moraru (Valica) -
Guillaume Lerouge -
Ludovic Dubost -
Marius Dumitru Florea -
Thibaut Camberlin