Hi Gonzalo, --- On Fri, 11/20/09, Gonzalo Aguilar Delgado <[email protected]> wrote:
> From: Gonzalo Aguilar Delgado <[email protected]> > Subject: Re: Progress... > To: "Jetspeed Developers List" <[email protected]> > Date: Friday, November 20, 2009, 9:46 AM > > > El jue, 19-11-2009 a las 19:46 -0800, David Sean Taylor > escribió: > > > > On Nov 19, 2009, at 4:06 PM, Gonzalo Aguilar > Delgado wrote: > > > > > >> I've done several changes to the code. I'm > near form the whole > > >> change. > > >> > > >> But, I have a problem with the panel. I don't > know what's the best > > >> way to put > > >> portlet information on web. > > >> > > >> It's supposed that I have to use the table > already created but I > > >> don't know how > > >> te set information via YUI3: > > >> > > >> +<table id="portlet-body-html" > style="border-collapse: collapse; > > >> width: 100%; margin-top: 0px; margin-bottom: > 0px; float: left;"> > > >> + <tr> > > >> + <td > rowspan="2" width="20%" class="portlet-section-body"> > > >> + > <img src='${portalContextPath}' /> > > >> + </td> > > >> + <td > id="name" width="80%" > class="portlet-section-body">#</td> > > > > We should be careful about node ids, id='name' is not > the best choice, > > could use some namespace or prefixing > > Also we will be getting a whole set of nodes with the > same id, not > > sure if that was the desired effect or not... > > > I know, I cannot handle this correctly because not enough > knowledge of > YUI. That's why I > requested help. I suppose that we should pass context in a > variable and > change ids via YUI. > > Any other way to do it? > > > > > > >> + </tr> > > >> + <tr> > > >> + <td > class="portlet-section-body"> > > >> + > <a href="#">Preview</a> > > >> + > <a href="#">Add</a> > > > > Propose using the addportlet api for these two hrefs > (there is no > > preview written, yet) > > (The addportlet api will require the portlet name from > the json result) > > > I have a question. How do we handle preview? Is there any > way of doing > preview "on the fly"? I think you can try Jetspeed portlet pipeline urls like the following example: http://localhost:8080/jetspeed/portlet/?entity=demo::PickANumberPortlet&portlet=demo::PickANumberPortlet The servlet path, '/portlet/*', is handled by Jetspeed portlet pipeline. The entity parameter should be unique and portlet parameter is the unique name of the portlet definition. You can just read responseText from the url response in your AJAX codes. We need to think it over for a better solution anyway, but I think it would be okay for now. Kind regards, Woonsan > > Tnx > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
