You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rave.apache.org by Marlon Pierce <mp...@cs.indiana.edu> on 2011/09/01 20:04:24 UTC
[Discuss] More demo gadgets
-----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").
Marlon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.16 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJOX8koAAoJEEfVXEODPFIDjrgH/2ej+0oVHP+9G2j9I7d6rhPk
dlHWeVWqpt7op9CTA5GNHyMZbb6pvyIkxNh+SCfxxA7LoymQxP129paVVWdVR4rv
XFYuTsotNxfdC9PCK5/F1yUUr/3tK0r1YBUkS/u1Ajx5CIMp6sD+xIGyFpbRPHnS
NlOOfJt//qfPKOrZiRRDAaLAQo9DGjLe/upf1cqaRYAA4U99xY9xbLWakW6gprfB
IBMhmjqsG80o9utvjXFFPSYD2FbD2CTlYgUPXOv46u6jqt4LhfSjUPZIox7ZjbVq
b0cpRY641q1qvnXyx1sxN59g/BbKQydYHPLGLMOq2KNf0JDefVFAdtVoiScMAoc=
=urN7
-----END PGP SIGNATURE-----
Re: [Discuss] More demo gadgets
Posted by Jasha Joachimsthal <j....@onehippo.com>.
On 2 September 2011 11:46, Scott Wilson <sc...@gmail.com>wrote:
> On 2 Sep 2011, at 10:34, Ross Gardler wrote:
>
> > On 2 September 2011 10:17, Jasha Joachimsthal
> > <j....@onehippo.com> wrote:
> >> On 2 September 2011 10:55, Scott Wilson <scott.bradley.wilson@gmail.com
> >wrote:
> >
> > ...
> >
> >>>>> 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?
> >>>>>
> >>>>>
> >>>> You could build that but why wouldn't you store this information in
> the
> >>>> database? Then you can do runtime CRUD operations on the widget
> through a
> >>>> management interface. We can create urls that follow a pattern to
> return
> >>> the
> >>>> widget definition, image etc.
> >>>> Just my €0.02
> >>>
> >>> The watcher script unpacks the widget, parses the definition and adds
> the
> >>> metadata to the database.
> >>>
> >>> That required access to a filesystem location for both the server and
> the
> >> administrator.
> >
> > Yes. For a development environment that will always be the case, for a
> > live environment one assumes there would be a mechanism for deploying
> > the widgets securely, otherwise how would they get there.
> >
> > We have found that this is the most flexible approach, but there is
> > still a form to upload widgets directly to a live server. The key is
> > how easy it is for developers on their first deployment.
>
> We ended up with three deployment mechanisms for widgets:
>
> - by dropping into to the /deploy folder
> - by POSTing to /widgets/
> - by uploading via a web form
>
> (They all ultimately do the same thing)
>
Ahh so there are more ways to add a new widget. Thanks for the clarification
:)
Re: [Discuss] More demo gadgets
Posted by Scott Wilson <sc...@gmail.com>.
On 2 Sep 2011, at 10:34, Ross Gardler wrote:
> On 2 September 2011 10:17, Jasha Joachimsthal
> <j....@onehippo.com> wrote:
>> On 2 September 2011 10:55, Scott Wilson <sc...@gmail.com>wrote:
>
> ...
>
>>>>> 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?
>>>>>
>>>>>
>>>> You could build that but why wouldn't you store this information in the
>>>> database? Then you can do runtime CRUD operations on the widget through a
>>>> management interface. We can create urls that follow a pattern to return
>>> the
>>>> widget definition, image etc.
>>>> Just my €0.02
>>>
>>> The watcher script unpacks the widget, parses the definition and adds the
>>> metadata to the database.
>>>
>>> That required access to a filesystem location for both the server and the
>> administrator.
>
> Yes. For a development environment that will always be the case, for a
> live environment one assumes there would be a mechanism for deploying
> the widgets securely, otherwise how would they get there.
>
> We have found that this is the most flexible approach, but there is
> still a form to upload widgets directly to a live server. The key is
> how easy it is for developers on their first deployment.
We ended up with three deployment mechanisms for widgets:
- by dropping into to the /deploy folder
- by POSTing to /widgets/
- by uploading via a web form
(They all ultimately do the same thing)
>
> Ross
>
>
> --
> Ross Gardler (@rgardler)
> Programme Leader (Open Development)
> OpenDirective http://opendirective.com
Re: [Discuss] More demo gadgets
Posted by Ross Gardler <rg...@opendirective.com>.
On 2 September 2011 10:17, Jasha Joachimsthal
<j....@onehippo.com> wrote:
> On 2 September 2011 10:55, Scott Wilson <sc...@gmail.com>wrote:
...
>> >> 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?
>> >>
>> >>
>> > You could build that but why wouldn't you store this information in the
>> > database? Then you can do runtime CRUD operations on the widget through a
>> > management interface. We can create urls that follow a pattern to return
>> the
>> > widget definition, image etc.
>> > Just my €0.02
>>
>> The watcher script unpacks the widget, parses the definition and adds the
>> metadata to the database.
>>
>> That required access to a filesystem location for both the server and the
> administrator.
Yes. For a development environment that will always be the case, for a
live environment one assumes there would be a mechanism for deploying
the widgets securely, otherwise how would they get there.
We have found that this is the most flexible approach, but there is
still a form to upload widgets directly to a live server. The key is
how easy it is for developers on their first deployment.
Ross
--
Ross Gardler (@rgardler)
Programme Leader (Open Development)
OpenDirective http://opendirective.com
Re: [Discuss] More demo gadgets
Posted by Jasha Joachimsthal <j....@onehippo.com>.
On 2 September 2011 10:55, Scott Wilson <sc...@gmail.com>wrote:
>
> On 2 Sep 2011, at 09:50, Jasha Joachimsthal wrote:
>
> > On 2 September 2011 10:17, Scott Wilson <scott.bradley.wilson@gmail.com
> >wrote:
> >
> >>
> >> On 2 Sep 2011, at 07:17, Jasha Joachimsthal wrote:
> >>
> >>> On 1 September 2011 20:04, Marlon Pierce <mp...@cs.indiana.edu>
> 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?
> >>
> >>
> > You could build that but why wouldn't you store this information in the
> > database? Then you can do runtime CRUD operations on the widget through a
> > management interface. We can create urls that follow a pattern to return
> the
> > widget definition, image etc.
> > Just my €0.02
>
> The watcher script unpacks the widget, parses the definition and adds the
> metadata to the database.
>
> That required access to a filesystem location for both the server and the
administrator.
Re: [Discuss] More demo gadgets
Posted by Scott Wilson <sc...@gmail.com>.
On 2 Sep 2011, at 09:50, Jasha Joachimsthal wrote:
> On 2 September 2011 10:17, Scott Wilson <sc...@gmail.com>wrote:
>
>>
>> On 2 Sep 2011, at 07:17, Jasha Joachimsthal wrote:
>>
>>> On 1 September 2011 20:04, Marlon Pierce <mp...@cs.indiana.edu> 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?
>>
>>
> You could build that but why wouldn't you store this information in the
> database? Then you can do runtime CRUD operations on the widget through a
> management interface. We can create urls that follow a pattern to return the
> widget definition, image etc.
> Just my €0.02
The watcher script unpacks the widget, parses the definition and adds the metadata to the database.
>
> Jasha
Re: [Discuss] More demo gadgets
Posted by Jasha Joachimsthal <j....@onehippo.com>.
On 2 September 2011 10:17, Scott Wilson <sc...@gmail.com>wrote:
>
> On 2 Sep 2011, at 07:17, Jasha Joachimsthal wrote:
>
> > On 1 September 2011 20:04, Marlon Pierce <mp...@cs.indiana.edu> 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?
>
>
You could build that but why wouldn't you store this information in the
database? Then you can do runtime CRUD operations on the widget through a
management interface. We can create urls that follow a pattern to return the
widget definition, image etc.
Just my €0.02
Jasha
Re: [Discuss] More demo gadgets
Posted by Marlon Pierce <mp...@cs.indiana.edu>.
-----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:scott.bradley.wilson@gmail.com]
>> Sent: Friday, September 02, 2011 4:17 AM
>> To: rave-dev@incubator.apache.org
>> Subject: Re: [Discuss] More demo gadgets
>>
>>
>> On 2 Sep 2011, at 07:17, Jasha Joachimsthal wrote:
>>
>>> On 1 September 2011 20:04, Marlon Pierce <mp...@cs.indiana.edu>
>> 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-----
RE: [Discuss] More demo gadgets
Posted by "Franklin, Matthew B." <mf...@mitre.org>.
>-----Original Message-----
>From: Scott Wilson [mailto:scott.bradley.wilson@gmail.com]
>Sent: Friday, September 02, 2011 4:17 AM
>To: rave-dev@incubator.apache.org
>Subject: Re: [Discuss] More demo gadgets
>
>
>On 2 Sep 2011, at 07:17, Jasha Joachimsthal wrote:
>
>> On 1 September 2011 20:04, Marlon Pierce <mp...@cs.indiana.edu>
>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
Re: [Discuss] More demo gadgets
Posted by Scott Wilson <sc...@gmail.com>.
On 2 Sep 2011, at 07:17, Jasha Joachimsthal wrote:
> On 1 September 2011 20:04, Marlon Pierce <mp...@cs.indiana.edu> 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?
>
> Jasha
Re: [Discuss] More demo gadgets
Posted by Jasha Joachimsthal <j....@onehippo.com>.
On 1 September 2011 20:04, Marlon Pierce <mp...@cs.indiana.edu> 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.
Jasha
Re: [Discuss] More demo gadgets
Posted by Raminderjeet Singh <ra...@gmail.com>.
On Sep 1, 2011, at 4:26 PM, Carlucci, Tony wrote:
> I like the idea of bundling some widgets with Rave, especially for testing and demo purposes. While I was working on the Edit Preferences work last month I was using a generic Edit Prefs gadget that I had developed in-house to test and verify a lot of the functionality (required prefs, non-required prefs, strings, enums, lists, booleans, etc) I think it would great to be able to package it in some manner with Rave so we can test and demo those features.
>
> Perhaps a new rave-demo-gadgets maven module that can deploy to Tomcat under a "demo-gadgets" web context, as Marlon suggested?we
+1 for this. that way its more clean and we will be able to share gadgets. Later we cam provide a interface in rave to upload your own gadget to users which can be deployed in this web application.
>
> Tony
>
> ---
> Anthony Carlucci | SW App Dev Eng, Sr. | R501 / KW App Development & Maint
> e: acarlucci@mitre.org | v: 781.271.2432 | f: 781.271.3299
> The MITRE Corporation | 202 Burlington Rd | Bedford, MA 01730-1420
>
>
> -----Original Message-----
> From: Marlon Pierce [mailto:mpierce@cs.indiana.edu]
> Sent: Thursday, September 01, 2011 2:04 PM
> To: rave-dev@incubator.apache.org
> Subject: [Discuss] More demo gadgets
>
> -----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").
>
>
> Marlon
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.16 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQEcBAEBAgAGBQJOX8koAAoJEEfVXEODPFIDjrgH/2ej+0oVHP+9G2j9I7d6rhPk
> dlHWeVWqpt7op9CTA5GNHyMZbb6pvyIkxNh+SCfxxA7LoymQxP129paVVWdVR4rv
> XFYuTsotNxfdC9PCK5/F1yUUr/3tK0r1YBUkS/u1Ajx5CIMp6sD+xIGyFpbRPHnS
> NlOOfJt//qfPKOrZiRRDAaLAQo9DGjLe/upf1cqaRYAA4U99xY9xbLWakW6gprfB
> IBMhmjqsG80o9utvjXFFPSYD2FbD2CTlYgUPXOv46u6jqt4LhfSjUPZIox7ZjbVq
> b0cpRY641q1qvnXyx1sxN59g/BbKQydYHPLGLMOq2KNf0JDefVFAdtVoiScMAoc=
> =urN7
> -----END PGP SIGNATURE-----
RE: [Discuss] More demo gadgets
Posted by "Carlucci, Tony" <ac...@mitre.org>.
I like the idea of bundling some widgets with Rave, especially for testing and demo purposes. While I was working on the Edit Preferences work last month I was using a generic Edit Prefs gadget that I had developed in-house to test and verify a lot of the functionality (required prefs, non-required prefs, strings, enums, lists, booleans, etc) I think it would great to be able to package it in some manner with Rave so we can test and demo those features.
Perhaps a new rave-demo-gadgets maven module that can deploy to Tomcat under a "demo-gadgets" web context, as Marlon suggested?
Tony
---
Anthony Carlucci | SW App Dev Eng, Sr. | R501 / KW App Development & Maint
e: acarlucci@mitre.org | v: 781.271.2432 | f: 781.271.3299
The MITRE Corporation | 202 Burlington Rd | Bedford, MA 01730-1420
-----Original Message-----
From: Marlon Pierce [mailto:mpierce@cs.indiana.edu]
Sent: Thursday, September 01, 2011 2:04 PM
To: rave-dev@incubator.apache.org
Subject: [Discuss] More demo gadgets
-----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").
Marlon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.16 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJOX8koAAoJEEfVXEODPFIDjrgH/2ej+0oVHP+9G2j9I7d6rhPk
dlHWeVWqpt7op9CTA5GNHyMZbb6pvyIkxNh+SCfxxA7LoymQxP129paVVWdVR4rv
XFYuTsotNxfdC9PCK5/F1yUUr/3tK0r1YBUkS/u1Ajx5CIMp6sD+xIGyFpbRPHnS
NlOOfJt//qfPKOrZiRRDAaLAQo9DGjLe/upf1cqaRYAA4U99xY9xbLWakW6gprfB
IBMhmjqsG80o9utvjXFFPSYD2FbD2CTlYgUPXOv46u6jqt4LhfSjUPZIox7ZjbVq
b0cpRY641q1qvnXyx1sxN59g/BbKQydYHPLGLMOq2KNf0JDefVFAdtVoiScMAoc=
=urN7
-----END PGP SIGNATURE-----