6 Jan
2011
6 Jan
'11
10:37 a.m.
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/OfficePresentation…
.
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
6 Jan
6 Jan
11:36 a.m.
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/OfficePresentation…
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/OfficePresenta…
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
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
7 Jan
7 Jan
11:06 a.m.
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 <lucaa(a)xwiki.com> 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/OfficePresentation…
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/OfficePresenta…
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
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
11:07 a.m.
And yeah, me speak English no good today ;-)
Guillaume
On Fri, Jan 7, 2011 at 11:06, Guillaume Lerouge <guillaume(a)xwiki.com> 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 <lucaa(a)xwiki.com> 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/OfficePresentation…
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/OfficePresenta…
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
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
4:30 p.m.
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 <asiri.rathnayake(a)gmail.com
wrote:
+1
- Asiri
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
5 p.m.
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 <thibaut.camberlin(a)xwiki.com
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 <
> asiri.rathnayake(a)gmail.com
> wrote:
>
> > +1
> >
> > - Asiri
> > _______________________________________________
> > devs mailing list
> > devs(a)xwiki.org
> > http://lists.xwiki.org/mailman/listinfo/devs
> >
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
>
8:59 p.m.
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<thibaut.camberlin(a)xwiki.com
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<
> asiri.rathnayake(a)gmail.com
> wrote:
>
>> +1
>>
>> - Asiri
>> _______________________________________________
>> devs mailing list
>> devs(a)xwiki.org
>> http://lists.xwiki.org/mailman/listinfo/devs
>>
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
>
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
8 Jan
8 Jan
10:21 a.m.
On Fri, Jan 7, 2011 at 8:59 PM, Marius Dumitru Florea <
mariusdumitru.florea(a)xwiki.com> wrote:
On 01/07/2011 06:00 PM, Ecaterina Moraru (Valica)
wrote:
IMO using one office macro with style option makes sense. When style is set
to slideshow it would display the slideshow.
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.
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
Guillaume,
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
Thanks,
Caty
On Fri, Jan 7, 2011 at 17:30, Thibaut Camberlin<
thibaut.camberlin(a)xwiki.com
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 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<
asiri.rathnayake(a)gmail.com
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs wrote:
+1
- Asiri
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
10:27 a.m.
On 01/08/2011 11:21 AM, Thibaut Camberlin wrote:
On Fri, Jan 7, 2011 at 8:59 PM, Marius Dumitru
Florea<
mariusdumitru.florea(a)xwiki.com> 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
Guillaume,
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
Thanks,
Caty
On Fri, Jan 7, 2011 at 17:30, Thibaut Camberlin<
thibaut.camberlin(a)xwiki.com
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 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<
asiri.rathnayake(a)gmail.com
> wrote:
> +1
>
> - Asiri
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
>
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs 
7 Jan
7 Jan
5:07 p.m.
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<lucaa(a)xwiki.com> wrote:
--
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
On 01/06/2011 10:37 AM, Marius Dumitru Florea wrote:
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
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/OfficePresentation…
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/OfficePresenta…
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
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
5000
days inactive
5002
days old
10 comments
7 participants
participants (7)
-
Anca Luca -
Asiri Rathnayake -
Ecaterina Moraru (Valica) -
Guillaume Lerouge -
Ludovic Dubost -
Marius Dumitru Florea -
Thibaut Camberlin