What if we just host a very simple "Hello World" gadget spec on opensocial.org?
-Chris On Mon, Sep 21, 2009 at 1:40 PM, Arne Roomann-Kurrik <[email protected]>wrote: > Suffers from the same back-end problem that the labpixies gadget has, > although I appreciate being thought of :) > ~Arne > > > > On Mon, Sep 21, 2009 at 1:35 PM, Lane LiaBraaten <[email protected] > >wrote: > > > What about the OpenSocial Developer App? (http://osda.appspot.com/) > > > > Pros: OSDA is targeted at developers who want to write small code > snippets > > to test the functionality of a given container > > > > Cons: It's a bit complex and maybe not the best "Hello World" solution > > > > > > -Lane > > > > > > On Mon, Sep 21, 2009 at 3:11 AM, Chris Chabot <[email protected]> > wrote: > > > >> So I've changed the remote content fetcher to now do a <input charset> > -> > >> utf8 conversion, even if the input charset=utf8, which causes the > invalid > >> utf8 sequences that labpixies had in their message bundles to be > filtered > >> out. > >> > >> As such the todo gadget is rendering again, however they've changed it > so > >> that it now uses a back-end server for storing lists, which requires the > >> container to be registered... so it's still not a working example, doh > :) > >> > >> Anyone have any suggestions to what would make a great out-of-the-box > demo > >> gadget? > >> > >> -- Chris > >> > >> On Mon, Sep 14, 2009 at 6:43 PM, Yonas <[email protected]> wrote: > >> > >> > Hi devteam, > >> > > >> > The Labpixies gadget has a problem that took some other clever ppl to > >> > figure out. Could you use another example gadget in the README until > >> > Labpixies fixes their gadget? Thanks, > >> > > >> > Yonas > >> > > >> > On Mon, 2009-09-14 at 17:01 +0200, Chris Chabot wrote: > >> > > This error is due to the todo gadget having a message bundle xml > file > >> > that > >> > > contains UTF-8 codes, but the server sends a different type of char > >> > encoding > >> > > header, so the encoding gets all mixed up and the xml parser errors > >> out > >> > on > >> > > it. > >> > > > >> > > The HttpUtil is being called to display the error, and that seems to > >> have > >> > a > >> > > duplicate class definition, which is why it displayed that error > >> instead > >> > of > >> > > the actual one. > >> > > > >> > > As long as there's no errors in the xml files (like the hello world > >> one > >> > Arne > >> > > linked), it should render perfectly though. > >> > > > >> > > >> > > >> > > > > > -- Chris Schalk, Google Developer Advocate
