Passing Arguments for Components

jcobb — Sat, 15 Aug 2009 19:08:56 GMT

Not strictly share development - I'm working on a surf application. I'm pretty new to the idea of components / dashlets / widgets etc.Let's say I have a component that's a clock, and it can display time either digital or analogue. I can use post or get arguments to change the display. I also have an

Re: Passing Arguments for Components

jcobb — Sun, 16 Aug 2009 19:11:19 GMT

OK so to update my post:

One tip from Share is to minimise page reloads from the server - which means using javascript on the client to interact with the user. In particular use of the yahoo gui. So for instance when browsing the document tree in share, the url might be

http://server:8080/share/page/site/siteName/documentlibrary#path=%252FdocumentFolder&page=1

That way javascript on the client can 'reload' the component, without a page reload.

Another tip from browsing share sources is to use the Preference Service - see wiki pages. This can be used to hold user preferences both within and across sessions - for example whether the document library opens in simple view or not. This would be the solution to my example of a clock widget having different display options.

I've also discovered some references to session data - eg

request.getSession().setAttribute(SESSION_CURRENT_THEME_ID, themeId);

in the AbstractRequestContext -to set a theme.

Is that something one can use in a surf application to pass session variables without using the url, where one doesn't need the cross-session persistence of using the preference service?

James

topic Re: Passing Arguments for Components in Alfresco Archive

Passing Arguments for Components

Re: Passing Arguments for Components