Hans Bakker wrote:
> Yes we should seriously look at this. These "gadgets" are based on the
> apache shindig (http://incubator.apache.org/shindig/) project. perhaps
> we can also use this in ofbiz? Shindig is an implementation of the
> opensocial (http://code.google.com/apis/opensocial/) standard
>
That's really interesting. As a power usage - the Atlassian tools
implementation of these "gadgets" is really useful and powerful in their tools.
Cheers,
Ruppert
--
Tim Ruppert
HotWax Media
http://www.hotwaxmedia.com
o:801.649.6594
f:801.649.6595
On Jan 1, 2010, at 6:06 PM, Hans Bakker wrot
Yes we should seriously look at this. These "gadgets" are based on the
apache shindig (http://incubator.apache.org/shindig/) project. perhaps
we can also use this in ofbiz? Shindig is an implementation of the
opensocial (http://code.google.com/apis/opensocial/) standard
so ofbiz portlets can be us
" sequenceNum="1"/>
>>>>>>>> >>>>>>> portalPortletId="party" portletSeqId="1" columnSeqId="1"
>>>>>>>> sequenceNum="0"/>
>>>>>>>> >&g
;>>>>> columnSeqId="1" sequenceNum="1"/>
>>>>>>> >>>>>> portalPortletId="partyRelAccounts" portletSeqId="1"
>>>>>>> columnSeqId="1" sequenceNum="2"/>
>>>
s many seed data that create a dependence
from many other components.
This is done because the seed data create the default MyPortal
portalPages that include several portlets from all other
components.
For example:
How can we have a conditional seed da
sequenceNum="1"/>
>>>>>>>>>> >>>>>>>>> portalPortletId="Calendar" portletSeqId="1"
>>>>>>>>>> columnSeqId="1"
>>>>>>>>>> sequenceNum="2"/>
>>>>
"/>
portalPortletId="UserLogin" portletSeqId="1"
columnSeqId="2"
sequenceNum="1"/>
portalPortletId="Attributes" portletSeqId="1"
columnSeqId="2"
sequenceNum="2"/>
How can we have a conditional seed data loading that would load only
seed data for the portlets really available in the system?
I mean, could we have something like this:
or is there any other tecnique to do this?
Many thanks,
Bruno
probably all replaced with opensocial: http://www.opensocial.org/?
On Thu, 2009-12-31 at 12:17 -0600, Adam Heath wrote:
> David E Jones wrote:
> > Bring confusion in the future? That's like saying you shouldn't use
> > the term object-relational mapping unless you're talking about JPA.
> >
> > J
David E Jones wrote:
> Bring confusion in the future? That's like saying you shouldn't use
> the term object-relational mapping unless you're talking about JPA.
>
> Just like object-relational mapping is a general term with many
> variations and implementations, and supporting the JPA interfaces i
"6"/>
portalPortletId="UserLogin" portletSeqId="1"
columnSeqId="2"
sequenceNum="1"/>
portalPortletId="Attributes" portletSeqId="1"
columnSeqId="2"
sequenceNum="2"/>
many other components.
This is done because the seed data create the default MyPortal
portalPages that include several portlets from all other components.
For example:
How can we have a conditional seed data loading that would load
wrote:
Hi,
the MyPortal component has many seed data that create a dependence
from many other components.
This is done because the seed data create the default MyPortal
portalPages that include several portlets from all other components.
For example:
mnSeqId="1" sequenceNum="2"/>
>>>>>> >>>>> portalPortletId="contact" portletSeqId="1" columnSeqId="1"
>>>>>> sequenceNum="3"/>
>>>>>> >>>&g
um="3"/>
>>>>> >>>> portalPortletId="LoyaltyPoints" portletSeqId="1"
>>>>> columnSeqId="1" sequenceNum="4"/>
>>>>> >>>> portalPortletId="PaymentMethods" po
seed data that create a dependence
from many other components.
This is done because the seed data create the default MyPortal
portalPages that include several portlets from all other components.
For example:
Ho
al
portalPages that include several portlets from all other components.
For example:
How can we have a conditional seed data loading that would load only
seed data for the portlets really available i
etId="PaymentMethods" portletSeqId="1"
>>>> columnSeqId="1" sequenceNum="5"/>
>>>> >>> portalPortletId="AvsSettings" portletSeqId="1" columnSeqId="1"
>>>> sequenceNum=&
;
>>> sequenceNum="1"/>
>>> >> portalPortletId="Attributes" portletSeqId="1" columnSeqId="2"
>>> sequenceNum="2"/>
>>>>> portalPortletId="Visits" portletSeqId="
1" columnSeqId="2"
>> sequenceNum="2"/>
>> > portalPortletId="Visits" portletSeqId="1" columnSeqId="2"
>> sequenceNum="3"/>
>> > portalPortletId="Content" portletSeqId=&q
; portalPortletId="Visits" portletSeqId="1" columnSeqId="2"
> sequenceNum="3"/>
> portalPortletId="Content" portletSeqId="00001" columnSeqId="2"
> sequenceNum="4"/>
> portalPortlet
:
How can we have a conditional seed data loading that would load only
seed data for the portlets really available in the system?
I mean, could we have something like this:
or is there any other tecnique to do this?
Many
23 matches
Mail list logo
