-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm going to create a jira ticket for static deployment of demo gadgets. This has the advantages of putting the gadgets under version control. I'll treat dynamic deployment issues (such as depositing a zip file) as a separate story.
Marlon On 9/2/11 7:50 AM, Franklin, Matthew B. wrote: >> -----Original Message----- >> From: Scott Wilson [mailto:[email protected]] >> Sent: Friday, September 02, 2011 4:17 AM >> To: [email protected] >> Subject: Re: [Discuss] More demo gadgets >> >> >> On 2 Sep 2011, at 07:17, Jasha Joachimsthal wrote: >> >>> On 1 September 2011 20:04, Marlon Pierce <[email protected]> >> wrote: >>> >>>> -----BEGIN PGP SIGNED MESSAGE----- >>>> Hash: SHA1 >>>> >>>> Hi all-- >>>> >>>> Ankur Goyal has compiled a list of gadgets (mostly simple) from the OGCE >>>> Gadget Container that can be ported straightforwardly into Rave. These >>>> include some useful ones (facebook, gmail clients, google talk) and some >>>> that at least have instructive potential. Do we want to include these in >>>> Rave trunk? If so, where? For simplicity and reliability, I suggest these >>>> be deployed into the Rave tomcat server under new webapp ("demo- >> gadgets"). >>>> >>> >>> Hosting our own widgets is a very useful addition to the portal. You can add >>> them as static resources, but why don't we add them to the existing >> database >>> of the portal? We can either extend the existing Widget bean with fields to >>> contain the actual definition, thumbnail and screenshot. Or we split up the >>> current Widget bean: a widget that is hosted by a 3rd party and a widget we >>> host ourselves. Just like we have a form to add a new externally hosted >>> widget, we can have a form to add a new widget we want to host from the >>> portal with different fields because administrators should be able to >>> upload/paste the images and widget definition. >>> Then you don't need a new webapp for only hosting our own widgets. >> >> In Wookie we have a "deploy" folder where we drop packaged W3C Widgets >> (.wgt) files to deploy them - this means we can have collections of widgets >> in >> the project that we can deploy during the build process by copying the files >> with an Ant task. (No forms required) >> >> For OpenSocial gadgets, can you use a similar process? So package up the >> gadget's resources and XML descriptor in a zip and drop it into a watched >> location for Rave to unpack and host locally? > > It is not part of the spec, so anything we introduce would be specific to > Rave. A zip file could work. > >> >>> >>> Jasha > -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.16 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOZhbnAAoJEEfVXEODPFIDyB4IAI9VUzEXwFEJkjZfHJq/xKJD 6JoCwwO9xuSK7A0SHwI0AbwByyzDgZptxXdKnPubKJeq8ctvBmLKgDXOTy1PtsSf /nmnNWo8H/QuK63jTnajy26+M37xlfKAwoTiB8qF2RxEJHRgz0ZeMGcvHSf0JXVx haarDAU21yklT9TrOB3f9xdqPViUfrUAul8lLrc7rAvyuKI8FOXbS9kO4Xs3Bkh4 TaQ8KIPnrHidKtURJ1YcZbz2ITswtqAR+JfzXwXI7LZ1TCt7kA4Daoq1XXeuYMg7 s553bBL37DHsy8rdg5XQSHv8CVAdelzGYQlwHLGUsmlVx9t5YezDCLrBz5UpyK8= =fAwx -----END PGP SIGNATURE-----
