like to see this in the commit log
Bruno Busco sent the following on 9/18/2010 12:46 PM:
I think there are already too many generic portlets.
The portlet attributes were not thought to be used to change the actual form
a generic portlet will render, the actual menu, etc. They were supposed to
be
I think there are already too many generic portlets.
The portlet attributes were not thought to be used to change the actual form
a generic portlet will render, the actual menu, etc. They were supposed to
be used by the end user to customiza the portlet just like JIRA does.
In any case I will start
Erwan, Bruno,
Do you agree on Nicolas's proposition, other opinions?
Jacques
From: "Nicolas Malin"
I think they are to different visions between you and erwan.
With a developper POV it's really easy to define new portlets as you do.
With a more functionnal POV, I know many person that prefer
I think they are to different visions between you and erwan.
With a developper POV it's really easy to define new portlets as you do.
With a more functionnal POV, I know many person that prefer create small
portlets by reusing existing code definition in database to design
customer sites instea
I would simply write:
And I could add more like groovy script calling, specific UILabel resources
loading etc.
It is not so much code...
-Bruno
2010/9/13 Bruno Busco
> I do
I do not see the benefit if you still need to add entity definition in the
XML data file.
2010/9/13 Erwan de FERRIERES
> Le 13/09/2010 15:11, Bruno Busco a écrit :
>
>> I connot see what is the purpose of a portlet like this:
>>
>>
>>
>>
>>
>>
Wow!
We should say Adam we do not need webslinger any more! ;-)
2010/9/13 Nicolas Malin
> I just understand it :)
>
> When you define a portlet you can use GenericScreenlet to locationScreen
> and pass formLocation and formName by portletAttribute. I think it's really
> useful for customer site
Le 13/09/2010 15:11, Bruno Busco a écrit :
I connot see what is the purpose of a portlet like this:
could you please help me?
Thank
I just understand it :)
When you define a portlet you can use GenericScreenlet to locationScreen
and pass formLocation and formName by portletAttribute. I think it's
really useful for customer site when you want to add quickly form in
PagePortlet without develop new specific file.
Nicolas
L
I connot see what is the purpose of a portlet like this:
could you please help me?
Thank you.
2010/9/13 Erwan de FERRIERES
> Le 13/09/2010 11:
Le 13/09/2010 11:19, Bruno Busco a écrit :
Erwan,
the portlet Attributes can already be edited by the user. When you go in the
Admin portal pages there is a little icon on each portlet (the pencil with
Hi,
technical parameters are today used in portletAttributes, but this
should be improv
Erwan,
the portlet Attributes can already be edited by the user. When you go in the
Admin portal pages there is a little icon on each portlet (the pencil with
the paper) that allows the user to access the parameter edit form. The icon
is only visible if the portlet has the edit form registered.
All
Le 12/09/2010 10:37, Bruno Busco a écrit :
Sorry to comment this commit very late.
I am looking into the PortalPortlet system how it is now. IMO it is now too
complicated with the portlet attribute feature not used as supposed by the
original design.
The generic portlets added with this commit u
Sorry to comment this commit very late.
I am looking into the PortalPortlet system how it is now. IMO it is now too
complicated with the portlet attribute feature not used as supposed by the
original design.
The generic portlets added with this commit use the Portlet Attribute system
to actually r
14 matches
Mail list logo
