+1 to David's -1 :)
I totally agree with these points, to me the name change is very minor
and not worth the pain which it will cause.
Andrew
On Apr 23, 2009, at 1:39 PM, David E Jones wrote:
-1.
In fact, a big huge -1. I don't think those names make it easier to
understand but rather more difficult, and then they are also not
grouped so well in the entity data maintenance and other webtools
pages, etc.
If this was a case where the names were misleading or plain wrong
then we might consider it. However, changing entities names causes
lots of problems, and results in a database change that is not
backwards-compatible, which also means people upgrading OFBiz will
have to shut down their entire system in order to update past such a
revision.
So no, I don't think this even comes close to being enough of an
improvement to be worth it.
-David
On Apr 23, 2009, at 4:28 AM, Vikas Mayur wrote:
Hi,
I would like to propose change in name of the following entities in
Portal. This would also result in changing the name of few keys.
PortalPortlet --> Portlet (since this is just about a portlet)
PortletPortletCategory --> PortletCategoryMember (as in
ProductCategoryMember)
IMO, they are more logical and clear names. I will open a jira
issues if no body see any objections.
Vikas
