I have looked around the web and have found that appending #page=?? to the end of a PDF link will automatically take the visitor to that specific page in the PDF file.
I was wondering if this is still best practice as it doesn't seem to be working for me (Chrome on Windows 7). Also, all the articles I have found so far date back to 2006-2008, have things changed recently?
This is still valid code but it may require that some version of Acrobat (Reader, Pro, etc) be installed as a plugin on the browser in order for it to work as expected. Since multiple commonly-used browsers now have a built-in reader (Chrome, Safari for iOS are the big two that come to mind) support for direct page linking is somewhat spotty now. You can still do it...the worst case scenario is that the PDF just opens to the first page for those users but I would advise to just leave off the direct page link. If the page is that important, extract it to a separate PDF and link to that.
Related
So I am trying to print a webpage with javascript:window.print();. Rest of the website works perfectly fine. There is this one page where the data is coming from 3rd party sources which might be the culprit but I am not sure at this moment. But when I try to print this page the print window shows 'Loading preview...' and total number of pages are astonishing 31000+. When it should hardly be a 3 page print.
When I turn OFF my VPN (which allow me to access those 3rd party sources and fetch and render the data on the page) the access is revoked from the 3rd party sources, making the print work fine with only 1 page.
I tried searching on the internet for this issue but no luck.
The application is built in Drupal 9 having twig as template engine. So I simply fixed html indentation and found out it was an extra </div> tag which was causing this issue. So guys always indent your code and be careful with writing lots of html in a single template. :)
How can I print .docx,doc,xls,csv in rails 4?
I tried window.open and window.print using javascript, but each time when it invokes window.open it downloads the file.
I tried to embed that in an iframe, that also fails.
Displaying a specific type of file isn't something that relies on your application it relies on the browser. In common browsers there is no support to display the file formats you mentioned.
What you can do is implementing some document viewers based on js if they are available for your usage. For example I know there is a plugin viewer.js that provides functionality to convert office and pdf to html. That might help you out... https://developers.box.com/viewer-js-tutorial/
I tried doing this some time back and this is the blog which i refereed. Helped a great deal.
Hope this helps.
Today we got one version of the system for desktop and we got one version with jQueryMobile.
The goal is to only have one system/page for desktop, tablets and mobiles.
I know that bootstrap is a good css/js framework and it is responsive. That will soulve the todays problem with the desktop version of our system.
As I said we have one mobile version as well. But today it gives us some "double work". And it is made in webforms.
My thought was to use bootstrap for both desktop and mobile. But my boss like jQuerymobile look and functionality.
We belive that our main users will be mobile/tablet users. So the best solution will perhaps be to remake the jquerymobile page and build it with MVC?
The main content of the system is for eployees to check their scheme, accept work-suggestions from their bosses and so on... This is in a calender.
There will be some more functionality in this calendar futher on.
Ofc there is some other stuff in the system but this calendar is the biggest.
My question is what direction we will go with this. The goal is to have one page/system for both mobile and desktop users.
If you are using JqueryMobile, I normally use another kind of windows events, but i have tried those events in normal pc browser and they tend to work okay. So why dont you build the system base on jquery mobile and just change the layout depending on who is making the request with a agent request.
I currently use a PDF-to-Flash to allow for users to flip thru pages of uploaded PDFs. However, with so many using iPhones/iPads I would like to switch this to a solution which works with any browser.
The site is developed in Ruby on Rails and I have looked into using pdf-toolkit and rmagick to convert the PDFs to images but it's not enough since I want the pages to scale with the browser window - SVG is not an option since I need for it to work w/ IE6 ;)
Any ideas?
Thx,
G
Why don't you use http://docs.google.com/viewer ?
http://googlesystem.blogspot.com/2009/09/embeddable-google-document-viewer.html
It's really simple, and it isn't Flash (can serve iPhone users too :D). Just add this to the view:
<iframe src="http://docs.google.com/viewer?url=#{YOUR_PDF_URL}&embedded=true"
style="width:600px; height:500px;" frameborder="0"></iframe>
Another option is a digital publishing platform like the one from Zmags. It converts a PDF to Flash, but when viewed on mobile devices it transforms into a swipeable version. Loads fast too.
Does anybody use bare .SWF files as webpages?
I know it's possible; it seems to work fine for me.
Why would I embed a SWF inside an HTML page if it's just going to be full screen (I mean the size of the browser's normal viewable page area, not COMPLETELY fullscreen)?
Is there a lack of browser support?
Or is this functionality determined by the browser's Flash plugin?
If you embed it in html page and the client doesn't have the flash plugin, most browsers show a missing plugin message. If u directly host the swf, a plugin-less browser might consider it as a download link and try to download the swf into the client machine instead of showing the missing plugin message.
My opinion is that if the browser has the Flash plugin it will render it, and it's up to you to implement how the swf behaves when you scale/resize the browser window/etc.
You can embed a swf in an HTML page and have it full browser screen offcourse, and you could interact with the browser a bit better ( some nice javascript/flash action going on ), not mention it would be more SEO/standards friendly.
I would recommend using SWFObject. Have a look at the fullpage demo.