On Thu, 10/30/08, zaheer ahmad <[EMAIL PROTECTED]> wrote: > iam working on implementing save page functionality. Looks > like its not > already supported in the core.
Apple's Mac port saves ".webarchive" files. The format is specific to the CoreFoundation framework, but there is platform-specific code that does this nevertheless. > Following are some high > level ideas and iam > not sure if some or all of these are the right approaches > to this problem > > - write the page data to the file system as and when is > received - but this > is not optimal since this incurs constant overhead on page > load Don't do this. > - apis to retreive the source (html, js, css) and > image/object data > (original form) from the document. I think the > parsers/loaders incrementally > handle the data and throw off the parsed text - pls > validate my > understanding here. There should be API to do this already. Look at how content for .webarchive files is retrieved. > - parse and convert all the html absolute/relative URIs to > relative URIs on > the file system Bug 7211: Support save as "Web page, complete" in Firefox format https://bugs.webkit.org/show_bug.cgi?id=7211 > - any other optimized storage methods - e.g. storing the > entire page as a > single file using multipart content Bug 7169: Support exporting of MHTML web archives https://bugs.webkit.org/show_bug.cgi?id=7169 I would strongly encourage you to reuse an existing format rather than inventing your own. (In my opinion the Firefox format is preferred because it's readable by all web browsers.) Dave _______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
