[add-art dev] splash screen // greasemonkey "library"

[Jamie Wilkinson]

I'll give this a shot shortly! Glad we have prefs & downloading  
working, I'm loath to include any more dependencies than absolutely  
necessary.

Re: download format -- I'm on the fence. JSON is nicer to read and  
quicker  to parse into JS. But we could also just use an RSS feed from  
the site (!) as the "show XML" and use DOMParser

Steve, is this easier on the add-art.org side? I imagine using RSS is  
riper for remixing/transclusion/etc. If it's all the same then I'd  
vote JSON

-jamie

On Jun 2, 2008, at 11:15 AM, Matt Katz wrote:

> Yeah - we've got that bit working.
>
> Actually this is something that would be a really big help from all  
> the
> folks on the add-art mailing list.  Can you folks check out the branch
> called versionsplah?  Build it using either the compile.sh in there  
> or the
> build.bat and install it - do you get a tab opening up pointing to
> add-art.org?
>
> Let us know what you get - steve was having problems with it, it  
> worked on
> my machine and it worked on a random mac in the eyebeam lab.
>
> Thanks all!
>
>> I don't think writing has been our problem, it's just getting all the
>> javascript right in versionsplash.js.  But yeah, I think we are
>> successfully writing to about:config without much trouble.  Matt you
>> agree?
>>
>> I'd love to get this working reliably by thursday for the new show so
>> we can "talk" to our users.
>>
>> Steve
>>
>> --
>> Steve Lambert
>> http://visitsteve.com
>> Eyebeam Senior Fellow
>> http://eyebeam.org
>>
>>
>>
>>
>> On Jun 2, 2008, at 1:50 PM, Tobias Leingruber wrote:
>>
>>> hey addies,
>>> in the attachment I have the overlay-splash-screen-script (it's a
>>> greasemonkey compatible file for testing porposes)
>>> the problem is, I still don't know how-to store data in the
>>> about:config, it's just very complicated.
>>> we need to store the information, that the splash-screen was shown,
>>> otherwise it'll show up all the time.
>>>
>>> something to talk about:
>>> is it an idea to use greasemonkey as a library for our add-on?
>>> because greasemonkey has seriously good functions, like for ajax
>>> requests or in this case a super easy function to store user data.
>>> I recently talked about this with Dan (shiftspace add-on), and I
>>> think the "greasemonkey library" could save us alot of work in the
>>> future.
>>> - to do this, (I hope) we basically just have to check out a simple
>>> compiled greasemonkey xpi file, and see where the "library" gets
>>> called.
>>>
>>> so, shall we try to "missuse" greasemonkey as a library, or should
>>> we "keep it real", as we already made it this far without it?
>>>
>>> greez from germany,
>>> tobi<inserts a
>>> splashscreen.rar>_______________________________________________
>>> 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
>>
>
>
> _______________________________________________
> Supperclub mailing list
> Supperclub at lists.add-art.org
> http://lists.add-art.org/listinfo.cgi/supperclub-add-art.org