[add-art dev] Perhaps useful afterall

[Ethan Ham]

Sure, that sounds good...

So the preference is for the images to be downloaded as individual files
rather than one file that contains them all?  Or is either way ok?

Regarding the download trigger, sounds good. So each download will contain a
"timeout" date after which the extension will check to see if a new set of
images is available.  I'm thinking that if no new set is available after the
timeout, then the extension will start checking for a new download every
time it starts up until a new one is available.

Ethan

On 6/2/08 8:28 PM, "Matt Katz" <matthew.katz at morelightmorelight.com> wrote:

> Hey Ethan!  NICE!
> Yeah - ticket 44 was just the bare minimum of being able to download a
> file.  I think it makes sense to keep doing development in the
> downloadafile branch as it isn't yet ready to merge into the trunk.
> 
> I think you want to download a lightweight xml file that contains urls.
> I think you want the lightweight file in either RSS format for greater
> mashability or if custom perhaps it should have a version number.
> 
> Newer version of the gallery xml should trigger a series of background
> image downloads that you write out to file to save on startup time etc in
> the future.
> 
> As for how often - we currently have shows that are 2 weeks long, but it
> seems to me that the file itself should have an attribute that tells you
> how long to wait before you do the next one.  That's what rss does and it
> seems pretty reasonable to me.
> 
> Sound good to you?
>> Sorry to keep starting new threads... I've turned off digest so that I can
>> respond to particular threads.
>> 
>> I was looking at the codebase and I think the code I wrote will be useful
>> afterall... it looks like ticket 44 was just for accessing a file from a
>> server, but the branch doesn't yet handle saving the file, etc. The code I
>> wrote actually saves out the jpeg information (I don't leave it in xml
>> format, but rather convert them to jpegs for saving locally) according to
>> filenames in the xml file.
>> 
>> If desired, I can created a branch with this code in it and extend it to
>> include the tool tip info (I actually have that info in the xml file, but
>> am not yet saving it locally).
>> 
>> Is it desired to keep the jpegs in the xml file?  If so, I can do that...
>> but it seems simpler to convert it to jpeg format once (on download)
>> rather than everytime the browser launches.
>> 
>> Also, any thoughts about how often to download the xml file?  If desired,
>> I could make it so that there's a very lightweight xml file (e.g., <10k)
>> that is downloaded on launch that indicates the current jpeg set.  If the
>> local machine has an older set, then it could download the heavier XML
>> that contains the jpeg info.
>> 
>> 
>> 
>> 
>> _______________________________________________
>> Supperclub mailing list
>> Supperclub at lists.add-art.org
>> http://lists.add-art.org/listinfo.cgi/supperclub-add-art.org
>> 
> 
> 
> _______________________________________________
> Supperclub mailing list
> Supperclub at lists.add-art.org
> http://lists.add-art.org/listinfo.cgi/supperclub-add-art.org
>