Archive
Image Gallery from a list of URLs
Problem
I have several scrapers that extract images. How to visualize them? One way is to open each one in a new browser tab but it’s slow and who wants to have several hundreds of tabs? Is there a way to browse these images in one single tab?
Solution
A primitive solution would be to create an HTML page that lists all the images one below the other. But again, what if you have lots of images?
A better way is to organize the images in a gallery. There are tons of image gallery generators out there but most of them work with local images. I want to browse remote images when only their URLs are available. So I made my own image gallery generator that works with URLs. Available on github.
There is also a live demo, check it out.
The software is written in Python. See the README file for usage examples.
Put a text on the clipboard from your webpage
Problem
From an HTML page you want to copy some text on the clipboard by pressing a button.
Example: on a page you present a list of URLs. Next to each URL there is a button. If the user clicks on the button, the corresponding URL is copied to his/her clipboard.
Solution
You can use clippy for this task. “Clippy is a very simple Flash widget that makes it possible to place arbitrary text onto the client’s clipboard.“
Here is an HTML template that you must paste in your HTML: clippy.html. Simply replace “{{ clippy_text }}” and “{{ bgcolor }}” with the values you want.
Update (20130103)
GitHub also used clippy but recently they switched to ZeroClipboard. Here is their announcement.
Youtube audio player
At http://www.labnol.org/internet/youtube-audio-player/26740/ I found a nice trick to embed just a part of the Youtube Flash player, thus the player looks like an audio player. All you need is a little CSS trick:
Codecademy – learn HTML, CSS, Javascript
“Codecademy is the easiest way to learn how to code. It’s interactive, fun, and you can do it with your friends.“
Scraping AJAX web pages (Part 3)
Don’t forget to check out the rest of the series too!
In Part 2 we saw how to download an Ajax-powered webpage. However, there was a problem with that approach: sometimes it terminated too quickly, thus it fetched just part of a page. The problem with Ajax is that we cannot tell for sure when a page is completely downloaded.
So, the solution is to integrate some waiting mechanism in the script. That is, we need the following: “open a given page, wait X seconds, then get the HTML source”. Hopefully all Ajax calls will be finished in X seconds. It is you who decides how many seconds to wait. Or, you can analyze the partially downloaded HTML and if something is missing, wait some more.
Here I will use Splinter for this task. It opens a browser window that you can control from Python. Thanks to the browser, it can interpret Javascript. The only disadvantage is that the browser window is visible.
Example
Let’s see how to fetch the page CP002059.1. If you open it in a browser, you’ll see a status bar at the bottom that indicates the download progress. For me it takes about 20 seconds to fully get this page. By analyzing the content of the page, we can notice that the string “ORIGIN” appears just once, at the end of the page. So we’ll check its presence in a loop and wait until it arrives.
#!/usr/bin/env python
from time import sleep
from splinter.browser import Browser
url = 'http://www.ncbi.nlm.nih.gov/nuccore/CP002059.1'
def main():
browser = Browser()
browser.visit(url)
# variation A:
while 'ORIGIN' not in browser.html:
sleep(5)
# variation B:
# sleep(30) # if you think everything arrives in 30 seconds
f = open("/tmp/source.html", "w") # save the source in a file
print >>f, browser.html
f.close()
browser.quit()
print '__END__'
#############################################################################
if __name__ == "__main__":
main()
You might be tempted to check the presence of ‘</html>’. However, don’t forget that the browser downloads a plain source first starting with ‘<html><body>…’ until ‘</body></html>’. Then it starts to interpret the source and if it finds some Ajax calls, they will be called, and these calls will expand something in the body of the HTML. So you’ll have ‘</html>’ right at the beginning.
Future work
This is not bad but I’m still not fully satisfied. I’d like something like this but without any browser window. If you have a headless solution, let me know. I think it’s possible with PhantomJS and/or Zombie.js but I had no time yet to investigate them.
Scraping AJAX web pages (Part 2)
Don’t forget to check out the rest of the series too!
In this post we’ll see how to get the generated source of an HTML page. That is, we want to get the source with embedded Javascript calls evaluated.
Here is my solution:
#!/usr/bin/env python
"""
Simple webkit.
"""
import sys
from PyQt4 import QtGui, QtCore, QtWebKit
class SimpleWebkit():
def __init__(self, url):
self.url = url
self.webView = QtWebKit.QWebView()
def save(self):
print self.webView.page().mainFrame().toHtml()
sys.exit(0)
def process(self):
self.webView.load(QtCore.QUrl(self.url))
QtCore.QObject.connect(self.webView, QtCore.SIGNAL("loadFinished(bool)"), self.save)
def process(url):
app = QtGui.QApplication(sys.argv)
s = SimpleWebkit(url)
s.process()
sys.exit(app.exec_())
#############################################################################
if __name__ == "__main__":
#url = 'http://simile.mit.edu/crowbar/test.html'
if len(sys.argv) > 1:
process(sys.argv[1])
else:
print >>sys.stderr, "{0}: error: specify a URL.".format(sys.argv[0])
sys.exit(1)
You can also find this script in my jabbapylib library.
Usage:
./simple_webkit.py 'http://dl.dropbox.com/u/144888/hello_js.html'
That is, just specify the URL of the page to be fetched. The generated HTML is printed to the standard output but you can easily redirect that to a file.
Pros
As you can see, it’s hyper simple. It uses a webkit instance to get and evaluate the page, which means that Javascript (and AJAX) calls will be executed. Also, the webkit instance is not visible in a window (headless browsing).
Cons
This solution is not yet perfect. The biggest problem is that AJAX calls can take some time and this script doesn’t wait for them. Actually, it cannot be known when all AJAX calls are terminated, so we cannot know for sure when the page is completely loaded :( The best way could be to integrate a waiting mechanism in the script, say “wait 5 seconds before printing the source”. Unfortunately I didn’t manage to add this feature. It should be done with QTimer somehow. If someone could add this functionality to this script, please let me know.
Challenge:
Try to download this page: CP002059.1. If you open it in Firefox for instance, at the bottom you’ll see a progress bar. For me the complete download takes about 10 sec. The script above will only fetch the beginning of the page :( Some help: the end of the downloaded sequence is this:
ORIGIN //
If you can modify the script above to work correctly with this particular page, let me know.
Another difficulty is how to integrate this downloader in a larger project. At the end, “app.exec_()” must be called, otherwise no output is produced. But if you call it, it terminates the script. My current workaround is to call this script as an external command and catch its output on stdout. If you have a better idea, let me know.
Resources used
- Downloading a page’s content with python and WebKit :: Downloading a page’s content after the javascript executed
- PyQt save DOM to file @ SO
Update (20110921)
I just found an even simpler solution here. And this one doesn’t exit(), so it can be integrated in another project easily (without the need for calling it as an external command). However, the “waiting problem” is still there.
What’s next
In the next part of this series we will see another way to download an AJAX page. In Part 3 we will address the problem of waiting X seconds for AJAX calls. Stay tuned.
Troubleshooting
If you get the following error message:
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
Then install this package:
sudo apt-get install gtk2-engines-pixbuf
This tip is from here.
Scraping AJAX web pages (Part 1.5)
Don’t forget to check out the rest of the series too!
Before attacking Part 2, I think it would be useful to investigate what the generated source of a page looks like.
Consider the following source:
<html>
<body>
<script>document.write("Hello World!");</script>
</body>
</html>
If you open it, you’ll see the text “Hello World!”. It’s not a big surprise :) But what is the generated source? How is the original html above interpreted by the browser?
Option A:
<html> <body> Hello World! </body> </html>
Option B:
<html>
<head></head>
<body>
<script>document.write("Hello World!");</script>Hello World!
</body>
</html>
Well, the correct answer is B. If you install the Web Developer add-on to Firefox, you’ll be able to see both sources: the original one (that is downloaded from the web server), and the generated one (which is produced by the browser after interpreting the original source).
If you don’t want to install Web Developer, there is another option. In Firefox, you can save a page in two different ways. If you save it as “Web Page, complete”, you’ll get the generated source. If you choose “Web Page, HTML only”, you’ll get the original source. However, if you save the “Hello World!” example as “Web Page, complete” and you open it from your local machine, you’ll see the text “Hello World!” twice! When you open the generated source, the embedded Javascript code will be executed again.
So, if you scrape AJAX pages, don’t be surprised if the resulting HTML source is still full of Javascript codes. But if you use an intelligent method that understands Javascript, then the interpreted result will be in the source too. In the next part we will see how to download webpages with Python and webkit.
