Dear Wiki user, You have subscribed to a wiki page or wiki category on "Rave Wiki" for change notification.
The "MeetupApacheConNa2013" page has been changed by ErinNoePayne: http://wiki.apache.org/rave/MeetupApacheConNa2013?action=diff&rev1=7&rev2=8 === What is our added value? === - * collections of gadges + * collections of gadges === Rest APIS === @@ -48, +48 @@ Plan architecture of rave javascript refactor. Decouple rave core and rave portal functionality. '''Rave Core''' - * responsible for core rave functionality associated with getting & rendering widgets + * responsible for core rave functionality associated with getting & rendering widgets - * manage apis for interacting with rest apis + * manage apis for interacting with rest apis - * manage a rave.ajax namespace that wraps ajax library and can be overlaid to decouple core functionality from a dependency on jquery + * manage a rave.ajax namespace that wraps ajax library and can be overlaid to decouple core functionality from a dependency on jquery - * manage registration of providers and widgets + * manage registration of providers and widgets - * manage a 'widget' abstract class that all providers will implement + * manage a 'widget' abstract class that all providers will implement - * manage pluggable providers that isolate interaction with opensocial, wiki, and any future providers + * manage pluggable providers that isolate interaction with opensocial, wiki, and any future providers - * manage the rendering & dom manipulation needed to insert widgets and support any ui functionality (add, remove, show, hide, collapse, expand etc). This file isolates all dependencies on a dom library and acts as the integration point for any implementer + * manage the rendering & dom manipulation needed to insert widgets and support any ui functionality (add, remove, show, hide, collapse, expand etc). This file isolates all dependencies on a dom library and acts as the integration point for any implementer '''Rave Portal''' - * responsible for functionality and ui associated with the rave portal, including pages, profiles, permissions etc. + * responsible for functionality and ui associated with the rave portal, including pages, profiles, permissions etc. - * build portal so that it ''can'' support being run as a traditional web app (full page reloads), single page application (ajax driven), or real time + * build portal so that it ''can'' support being run as a traditional web app (full page reloads), single page application (ajax driven), or real time - * manage client side templates, mvc architecture, to support a rave portal that could be + * manage client side templates, mvc architecture, to support a rave portal that could be
