The wxHTML library uses a virtual file systems mechanism similar to the one used in Midnight Commander, Dos Navigator, FAR or almost any modern file manager.
It allows the user to access data stored in archives as if they were ordinary files. On-the-fly generated files that exist only in memory are also supported.
Three classes are used in order to provide virtual file systems mechanism:
wx.FileSystem.ChangePathTo
and
wx.FileSystem.OpenFile
. This class is most often used by the
end user.wx.FileSystem.AddHandler
method. In the new handler you only
need to override the wx.FileSystemHandler.OpenFile
and
wx.FileSystemHandler.CanOpen
methods.Locations (aka filenames aka addresses) are constructed from four parts:
"http"
, "file"
or
"ftp"
."http://www.wxwidgets.org/index.html"
the right location is
"//www.wxwidgets.org/index.html"
."index.htm#chapter2"
the anchor is "chapter2"
.The left location precedes the protocol in the URL string.
It is not used by global protocols like HTTP but it becomes handy when nesting protocols - for example you may want to access files in a ZIP archive:
file:archives/cpp_doc.zip#zip:reference/fopen.htm#syntax
In this example, the protocol is "zip"
, right location is
"reference/fopen.htm"
, anchor is "syntax"
and left location is
file:archives/cpp_doc.zip
.
There are two protocols used in this example: “zip” and “file”.
The following virtual file system handlers are part of wxPython so far:
"archive.zip#zip:filename"
,
"archive.tar.gz#gzip:#tar:filename"
."document.ps.gz#gzip:"
."memory:myfile.htm"
.In addition, FileSystem itself can access local files.
Use wx.FileSystem.AddHandler
to initialize a handler, for
example:
def OnInit(self):
wx.FileSystem.AddHandler(wx.MemoryFSHandler())