Comments on: Introducing FlexPaper – PDF viewing for Adobe Flex

By: Ashwin

Ashwin — Sat, 06 Feb 2010 18:15:38 +0000

Hi Eric,

Good to see the print options and like wise many of the parameters for customization. I have one suggestion as I am loading TIFF images the search would not work for me. So It would be good if even this could be optional. ie Parameterised.

Keep up the great work.

Thanks in advance.

By: Erik

Erik — Thu, 04 Feb 2010 22:06:05 +0000

@kanu
try using the command line instead of the user interface when converting your document.

you can see the latest recommended parameters to use here:
http://code.google.com/p/flexpaper/wiki/Converting_Documents

By: kanu kukreja

kanu kukreja — Thu, 04 Feb 2010 10:38:02 +0000

That problem resolved but getting
Unhandled IOErrorEvent:. text=Error #2124: Loaded file is an unknown type.
Trying Ahmad’s solution but don’t know how to set it to ‘No viewer’ setting.

By: RoyTuckler

RoyTuckler — Fri, 29 Jan 2010 18:44:23 +0000

Erik writes:
>>Roy, yeah I’ve also visited that idea, the problem is that it is quite easy to fake a referrer. Http calls are in the end plain text and can be manipulated quite easy.

>> On top of that, the swf file in this case which gets loaded up inside the viewer will probably also end up in the users cache and it would be easy to extract it from there.

I wonder if the same is then valid also for the files displayed by the scibd or similar sites? I think they have a database handle for the file, so it does not sit in some directory, but if it is in the cache, then it may be the same problem? In that case, there really is no 100% safe solution.

However, being able to disable download and printing, plus turning file access off in the htaccess, will probably prevent 90+ % of the regular users from accessing the file in another way than intended.

For that last 1-10% of users (who know to program), the content of the file would have to be of such high value to make it worth their while.

By: Erik

Erik — Fri, 29 Jan 2010 03:00:27 +0000

@Roy, yeah I’ve also visited that idea, the problem is that it is quite easy to fake a referrer. Http calls are in the end plain text and can be manipulated quite easy.

On top of that, the swf file in this case which gets loaded up inside the viewer will probably also end up in the users cache and it would be easy to extract it from there.

By: Roy

Roy — Fri, 29 Jan 2010 02:36:34 +0000

I also would like to see a way to get the print button disabled.

Erick said: >>Anything that gets displayed in the browser can be downloaded and manipulated by someone with the right skills. Just so you are aware.

I was researching this issue a few days ago. There are ways around it. If you are running apache, you can prevent access in the htaccess file. There are ways to test for the referer (or for direct access URL), and if it is not from the same site, redirect the request. That way, you can never get the direct file.

By: needim

needim — Wed, 27 Jan 2010 16:42:42 +0000

Thanks Erik. This is great work.

By: Erik

Erik — Tue, 26 Jan 2010 03:34:53 +0000

@needim good idea I’ll try to fit it into the upcoming release

By: needim

needim — Sat, 23 Jan 2010 14:25:29 +0000

What about scale variable?

Such as;

var params = {
SwfFile : “01h-test-7_2.swf?v=1.1b1″,
Scale : ‘fit-width’
}

Is it possible for now? Or next release?

By: Gorav

Gorav — Thu, 21 Jan 2010 10:00:06 +0000

Great stuff.

When you are planning to implement “Lazy loading mechanism to be able to load very large pdf/swfs”

Thanks