feklee / presvg Goto Github PK

In Chrome 19.0, the SVG doesn't appear. Yet there is no error message in the developer tools console.

Just some tweaks.

Possible example URL: index.html#presentation=demo&pathPos=5&view=default

Then also put settings in a separate file, such as settings.js in the same location as the SVG file.

Possibilities:

• CSS (webkit): Take a look at Google mail's scroll bar in Chrome.
• JavaScript: jScrollPane looks interesting.

In any case: The most important is that the scroll bar works smoothly in all supported browsers and on all devices, including tablets and perhaps mobile phones.

About svgweb: http://code.google.com/p/svgweb/

Currently, the SVG file has to have the same base URL as the HTML file into which it is included. See README.md.

Once the SVG file can be positioned anywhere:

• Use new structure for demo:

  demo.html
  demo/presentation.ai
  demo/presentation.svg
  demo/texts/...
  demo/images/...
  

• Update README.md.

Some presentations contain one frame several times, for example to repeatedly show "the big picture". However, in print mode, showing the same frame several times appears superfluous. Instead the following system could be used:

• Attache numbers to frames.
• Reference existing frames by number.

Sample printout structure:

+--(1)
|   |
+---+

  ↓

+--(2)
|   |
+---+

  ↓

 (1)

  ↓

+--(3)
|   |
+---+

How to replicate:

1. Load the presentation.
2. Open SVG window.
3. Close SVG window.
4. Click on the slider. It will jump to the selected position but then go all the way back to the previous position.

The problem is that in step 4, the script tries to also update the path position in the other window. This fails when calling $('#slider').slider('value', pathPos); for that window. Due to the error, script execution is stopped, and consequently for the current window not all code is executed.

SVG supports animation by a technology called SMIL. Using SMIL may be a good idea because then the SVG renderer knows explicitly that it should animate. Thereby the renderer is possibly able to display resource friendly and smooth animations.

… for example by adding loupe buttons to the navigation bar at the bottom. Or create a navigation control like on Google Maps or Earth, which would allow panning, zooming, and rotating.

… simply by dragging it.

Provide: default view, SVG view (for presentation), and print view.

… so that they show up quicker. The probably means using the YouTube iframe API. Could mean more resource use, though.

Scenario: User opens SVG view, which shows the presentation in a separate window. This view is synchronized with the default view: Any changes in the position within the presentation path are mirrored. However, if the user reloads either the default or the SVG view, then the connection between the windows is lost. They are not in sync anymore.

Perhaps by default print each frame on one page. Example HTML code which I hacked into a specific presentation to achieve that effect:

<style type="text/css" media="print">
    html.printView div.frame, html.printView div.footnoteLinks {
        page-break-after: always;
        page-break-inside: avoid;
        margin-bottom: 20cm;
    }
</style>

Also, consider offering a remove-duplicates option.

Only the upper left hand part of the SVG is visible.

There seems to be a simpler alternative: https://developer.mozilla.org/en/DOM/window.opener