On Tue, Oct 28, 2008 at 10:57 PM, Aaron Boodman <[EMAIL PROTECTED]> wrote:
>
> On Tue, Oct 28, 2008 at 10:27 PM, Khookie <[EMAIL PROTECTED]> wrote:
>> Fantastic, captureBlob looks more promising. Hopefully it works for
>> my case :-)
>>
>> Any dates on 0.5?
>
> Sorry, not sure.
But "before the end of the year" is a safe bet. Hopefully that helps
you with schedule planning more than an open-ended answer!
> Chris Prince, did you understand what Chris Khoo is trying to do with
> the blob?
Yes.
> It contains text that he wants to parse and insert into the DB.
You may have misunderstood. He did ask about doing that, but the root
purpose was to import / export files.
Parsing the content manually was a hack to get around missing APIs.
It's better to solve his problem the right way, instead of relying on
weird hacks (despite this being a long-standing tradition among JS
developers).
See his earlier comment for context:
"I would like to import & export files on client-side Javascript when a
Gears application is disconnected.
"Example: when it's connected, it's not hard to do through something
like ... setting the Content-Disposition header for downloads & using
<INPUT TYPE="file" for uploads)... but I would like that capability
when it's disconnected."
> http://code.google.com/p/gears/wiki/BlobWebAPIPropsal (see "Reading Blob
> Data")
Khookie, keep in mind much of that doc is pretty out of date. For
example, the file-input-element idea was a short-lived proposal that
should no longer be considered valid.
