[mashup-dev] mashup screens

[Ruwan Linton]

Hi,

There are advantages of using a portal server in this case, but I don't 
know how this is going to fit in with the mashup server.

If you use a portal server then you don't have to worry about 
maximizing, minimizing these small portions (obviously you will have to 
maximize these in the mashup server), adding new portion and also the 
single sign on(if required). Those tasks will be handled by the portal 
server.

But as far as I know there is a draw back of using portal servers in 
this case. Here is a scenario for the mashup server.

You want to edit a particular protlet (a service UI) in maximized mode 
without saving the changes, you want to go in to another portlet in 
maximized mode and edit things in that, comeback to the former. In this 
case the changes that you have done to that portlet earlier will be lost 
since portal server keeps only one maximized portlet in its session. I 
have no experiences with Liferay but in eXo this is the case.

So better look in to these aspects of portal servers before going to use 
them.

Somehow, I think it is better to get these maximizing minimizing tasks 
get done from an available framework and use our AJAX client model 
inside these small portions (most probably these portions should be iframes)

Thanks,
Ruwan.

Sanjiva Weerawarana wrote:
> Hi Sumedha,
>
> I agree that each service is very much like a portlet. What we want 
> however is for each service's UI to be the portlet. Each widget is 
> really driving the service using AJAX + our wsclient javascript code.
>
> I'm familiar with WS-RP but am not at all a fan of it .. but I'd like 
> to understand your perspective of it more.
>
> Sanjiva.
>
> sumedha rubasinghe wrote:
>> Dear Thilina,
>> The screens look more like portal pages to me. ( defined by JSR 168 
>> [1], Another version of portal specification is being developed in 
>> par with web 2.0 concepts.)
>>
>> IMHO You do not have to implement this kind of UI. There are many 
>> open source portal servers available.
>> Liferay [2] is one such leading open source portal server. Please see 
>> the attached image I created out of their demo site. You will see 
>> many fundamental similarities between this & Amal's pages.
>>
>> Apache has two portal server implementations called 'Pluto' [3] & 
>> 'Jetspeed' [4]. Jboss also has a  portal server implementation [5].
>>
>> Widgets in Amal's screenshots are analogous to 'Portlets' in portal 
>> server.  The developers write portlets & portal server deals with 
>> portlet life cycle management, layout, themes, etc...
>>
>> You can even load a portlet using data from a web service. (WS-RP [6])
>> I think Liferay is also working on a Meshup solution [7].
>>
>> I have an instance of liferay running, if you want to get a closer look.
>>
>> [1] http://jcp.org/aboutJava/communityprocess/review/jsr168/
>> [2] http://www.liferay.com
>> [3] http://portals.apache.org/pluto/
>> [4] http://portals.apache.org/jetspeed-1/
>> [5] http://labs.jboss.com/portal/jbossportal/?prjlist=false
>> [6] http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrp
>> [7] http://www.liferay.com/web/guest/products/mesh
>>
>> /sumedha
>>
>>
>>
>> Thilina Gunarathne wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> Hi all,
>>> We had a small discussion yesterday regarding the UI for the mashup
>>> tool.. We decided to deviate a bit from the look and feel of our other
>>> products (ESB, WSAS)..
>>>
>>> Our initial suggestion is to have a widgets based UI, something similar
>>> to personalized google home page. The idea is to support a small scale
>>> UI per mashup service, which can also be referred by a URL so that the
>>> users can add it to their sites by using URL. As a start these widgets
>>> can contain some details about the service (State, EPR, URL of the 
>>> TryIt
>>> etc..),later we can allow some way for the user to provide it..
>>>
>>> Attached are some sketches created by Amal to elaborate the ideas we
>>> came up with.
>>>
>>> ScreenShot01 : Home screen with services listing folded
>>> Monitor tab bar will provide stats, logs, tracer, etc..
>>> Screenshot 1 fullscreen: Home screen with full services listing.. (We
>>> need to come up with some icons for the start|stop)..
>>> popup: Dialog box for editing & creating the mashups...
>>>
>>> Thanks,
>>> Thilina
>>>
>>>
>>> -----BEGIN PGP SIGNATURE-----
>>> Version: GnuPG v1.4.2.2 (GNU/Linux)
>>>
>>> iD8DBQFF5siWTt0cKycFPQgRAjvHAJ4pz0Zo8F/vMZeXoEUDnXajDx6jZgCfQhe3
>>> Dv+y4dOdW7l43nOQbAbTiUU=
>>> =qHU2
>>> -----END PGP SIGNATURE-----
>>>  
>>> ------------------------------------------------------------------------ 
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------ 
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------ 
>>>
>>>
>>>
>>> ------------------------------------------------------------------------ 
>>>
>>>
>>> _______________________________________________
>>> Mashup-dev mailing list
>>> Mashup-dev at wso2.org
>>> http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
>>>   
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Mashup-dev mailing list
>> Mashup-dev at wso2.org
>> http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
>