100% zoom for documents

[GoogleCodeExporter]

It's impossible to read the text in a A4 word document or 
is ugly when the user increases the image.

Two solutions are possible :
- Generate an image with 100% zoom
- Convert the office documents to pdf format, and convert the pdf to swf
with  pdf2swf : http://www.swftools.org/

The big interest of the second solution is that it will be possible to zoom
on the document without the lost of the quality, because it will be a
vector graphic.

Original issue reported on code.google.com by gml...@gmail.com on 13 Jul 2007 at 8:53

[GoogleCodeExporter]

http://www.swftools.org/ is released under the GPL. We cannot distribute 
Openmeetings
with it.

OpenOffice I think can generate swf's directly i think. I'll have to take a 
look at
the docs.

Original comment by seba.wag...@gmail.com on 13 Jul 2007 at 12:49

[GoogleCodeExporter]

For OpenOffice, I know that it's possible with odg and odp, but I don't know 
for odt.

About license problems for swftools, no problems for openmeetings, while you 
use the
tool by command line. GPL applies only when you add GPL code in your source 
code.

Original comment by gml...@gmail.com on 13 Jul 2007 at 1:08

[GoogleCodeExporter]

to make all fonts fully visible the density of the converting must be increased.

But its a very big image then.
This Issues would be solved with that, but its useless to increase the image 
sice if
you have no chance in handling large pictures in the whiteboard.

There must be some kind of document-viewer-tool in the whiteboard to 
navigate/zoom
through a docuement.

To generate a custom swf i would prefer generating a swf-file by 
OpenLaszlo-copmiler
 rather then doing it with external stuff.

Original comment by seba.wag...@gmail.com on 17 Jul 2007 at 11:32

[GoogleCodeExporter]

I have fund a more suitable library:

http://www.flagstonesoftware.com/transform/index.html

its fully Java written and fits better into the application.

Original comment by seba.wag...@gmail.com on 18 Jul 2007 at 11:14

[GoogleCodeExporter]

okay also http://www.flagstonesoftware.com/transform/index.html will not be 
useable
or make improvements .. basically its all about the quality of the image
processing/converting.
Direct converting to swf is not possible:
* I have looked into http://www.swftools.org/ ... they have a bunch of 
dependencies
its not useable for us and the build process is rather advanced. Also i did not 
see
any results so far. Also this will not solve the hole problem. And i 

What i proposed/started is:

There will be a second toolbar menu on top of it with tools for navigating and
zooming into a document.
Each time you load a slide of a document the tool bar and its tools will get 
activated.
The image's of the pdf's will be processed with a much higher density (maybe 
also
higher then necessary)
The user loads the slide and it will be scaled to fit the screen, he can zoom 
and
navigate with teh toolbar.
if the quality is still too bad (cause density and file-size depend on qech 
other ..
you cannot make desnity *endless* big .. cause filesize will grow also to 
endless)
he will be able to recompile the image by its original with a higher density.

Original comment by seba.wag...@gmail.com on 20 Jul 2007 at 1:30

[GoogleCodeExporter]

About swftools, I had installed this on my computer.
I have no problems to install this, what's the problem for you ? Do you need 
some help ?
If you think that it will be difficult to install, I can provide static 
binaries of this.

I have added an example of a swf file generated by pdf2swf tool. You can see 
that the
quality is good when you zoom.

The use of bitmap files for this will increase the needs of bandwidth.

Original comment by gml...@gmail.com on 20 Jul 2007 at 3:54

Attachments:

• oo-welcome.swf
• oo-welcome2.swf

[GoogleCodeExporter]

I have no problems to install this, what's the problem for you ? Do you need 
some help ?

=> i don't wan't no more 3third party tools. swftools depend on 3 other libs 
and so
on... you cannot distribute it with the app cause it has too many dependencies. 
So a
binary does not help if the dependencies are not there.

Original comment by seba.wag...@gmail.com on 20 Jul 2007 at 3:59

[GoogleCodeExporter]

can you documentate which library's swftools need to run and add a binary file 
here
sothat i can test?

Original comment by seba.wag...@gmail.com on 20 Jul 2007 at 4:00

[GoogleCodeExporter]

but file size and scaling is really good so lets see if a precompiled binary 
can be
run on most of the systems. Can you check if windows version will also work?
we need swftools for windows, mac and linux-distro's
I think windows should not be a problem with dependencies.

Original comment by seba.wag...@gmail.com on 20 Jul 2007 at 4:04

[GoogleCodeExporter]

If the binary is statically compiled, no other libs will be necessary to use 
this.

What is your linux distribution ? debian etch ? ubuntu-server ?

Original comment by gml...@gmail.com on 20 Jul 2007 at 4:06

[GoogleCodeExporter]

does that matter?

Original comment by seba.wag...@gmail.com on 20 Jul 2007 at 4:24

[GoogleCodeExporter]

The binary for ubuntu 7.04.

The dependencies :
libc6 (>= 2.5-0ubuntu14 ), libfreetype6 (>= 2.2.1-5ubuntu1.1 ), libjpeg62 (>= 
6b-13
), python2.5 (>= 2.5.1-0ubuntu1 ), python-imaging (>= 1.1.6-0ubuntu3 ), zlib1g 
(>= 1 )

Original comment by gml...@gmail.com on 20 Jul 2007 at 6:33

Attachments:

• pdf2swf

[GoogleCodeExporter]

arg .. this is kind of horrible:

7.) How do I compile swftools on Mac OS X?

    You need to get fink (http://fink.sourceforge.net), and install it.
    After this, you need to install all the required libs (jpeg, freetype, lame):

    fink install libjpeg libjpeg-shlibs freetype2 freetype2-shlibs lame lame-shlibs

    Then, you have to inform configure of where they are:

    LDFLAGS="-L/sw/lib" CPPFLAGS="-I/sw/include -I/sw/include/lame" ./configure
    make
    sudo make install

    If this doesn't work, especially if you want to use the python library and
    get weird exceptions, try to remove all versions of jpeglib, freetype and
    lame from /usr/lib and /usr/local/lib, and then run configure / make / make install
    again.

    If you also want to use the python interface, you may have to copy the
    Imaging headers (Imaging.h, ImPlatform.h, ImConfig.h) to
    /System/Library/Frameworks/Python.framework/Versions/2.3/include/python2.3/
    before running configure.

Original comment by seba.wag...@gmail.com on 21 Jul 2007 at 12:43

[GoogleCodeExporter]

*want to use the python interface*

=> do we really need *python2.5, python-imaging* as dependecies?

Original comment by seba.wag...@gmail.com on 21 Jul 2007 at 1:01

[GoogleCodeExporter]

No, it isn't necessary.

Original comment by gml...@gmail.com on 21 Jul 2007 at 2:58

[GoogleCodeExporter]

this tool maybe works but i could not compile/run it on MAC OSx. Maybe its a 
good
tool but with all these dependencies and configuration its in-acceptable and 
will be
as horrible as xvfb/OpenOffice installation vor non-geeks.
I really would like to use or simply test that tool but i could not even get it
running on Mac (attached is my logfile).

The tool really has to be installable also for non-technical people and swftool 
is
definitely not installable if you don't know who to handle make/configure and 
how to
set LDFLAGS for various systems and distro's. I cannot even test it on Mac so 
what
should i do with that tool?

Original comment by seba.wag...@gmail.com on 22 Jul 2007 at 12:12

Attachments:

• log.rtf

[GoogleCodeExporter]

i will try to use it in windows seems that it works there without problems.

Original comment by seba.wag...@gmail.com on 22 Jul 2007 at 12:34

[GoogleCodeExporter]

for intergration of swf-tools the hole converting must be changed, cause the 
images
are not needed any more and the hole convertign must be splitted into several 
files
(already done) otherwise the code gets confusing and not well structured (done 
so far).

Original comment by seba.wag...@gmail.com on 23 Jul 2007 at 11:23

[GoogleCodeExporter]

one part of the integration is done.

Original comment by seba.wag...@gmail.com on 24 Jul 2007 at 9:04

• Changed state: Started

[GoogleCodeExporter]

Original comment by seba.wag...@gmail.com on 25 Jul 2007 at 3:53

• Added labels: Component-SWFPresenationViewer

[GoogleCodeExporter]

Original comment by seba.wag...@gmail.com on 26 Jul 2007 at 9:04

• Added labels: Component-SWFPresentationViewer
• Removed labels: Component-SWFPresenationViewer

[GoogleCodeExporter]

The feature is basically in the SVN now

Original comment by seba.wag...@gmail.com on 2 Aug 2007 at 3:48

• Changed state: Review