headers
Stéphane Bouchet | 8 Aug 09:06

Questions about xforms editor

Hi,

I am looking a bit around the XForms editor in eclipse.

I checked out from svn and installed it. it's working very good.

But after looking a bit more inside, i have a question :
Why the <Hint> element is mapped into an attribute of the parent element ?
it seems also that the mapping from <hint> element to swt tooltiptext is 
not working ?
this is due to the AttributeMap class that is not setting new values 
correctly....

finally, i am very interresed to the edit part of the editor also. ( add 
elements to the xform... )

Cheers,

Stéphane
Permalink | Reply |
headers
Dan Connelly | 11 Aug 15:39

Liferay integration ?

Has anyone used Apogee to support Liferay/Jackrabbit?
Permalink | Reply |
headers
Bogdan Stefanescu | 14 Aug 20:35

Re: Liferay integration ?


Currently only local jackrabbit repositories are supported.
Also, the Jackrabbit RMI is not supported because it is not compliant
with JCR API

We are working on a high level repository model (the default
implementation is build on top of Jackrabbit)
When this will be done Apogee will be updated to access both local and
remote repositories using this high level repository API

What are you interested in exactly about Liferay integration ?

Regards,
Bogdan

Dan Connelly wrote:
> Has anyone used Apogee to support Liferay/Jackrabbit?
> _______________________________________________
> Apogee mailing list
> Apogee@...
> http://lists.nuxeo.com/mailman/listinfo/apogee

--

-- 

Bogdan Stefanescu - Apogee project Team Leader

Nuxeo - Open Source ECM - www.nuxeo.com
Apogée - the rich client platform for ECM
http://apogee.nuxeo.org/ - http://www.nuxeo.com/en
(Continue reading)

Permalink | Reply |
headers
Bogdan Stefanescu | 14 Aug 19:57

Re: Questions about xforms editor


Stéphane Bouchet wrote:

Hi Stephane,

If I remember well the "Hint" is mapped to an attribute to ease the
generation of the SWT form
because usually a xforms control element is mapped to an eclipse control
(like XFInput to a text widget)
And the hint element is mapped to a tooltip which is not a swt controlb
but a widget property.
The same is used to store the label of a xform component by setting the
mLabel member of the parent control (XFLabeledControl)
instead of mapping it into a SWT label - this way we can easily put the
label widget before widget corresponding to the parent element in the
SWT form.

There are many things to be implemented and fix. (like the AttributeMap
bug you mention)

Unfortunately, I had no time to continue development on the XForms
engine these months - I hope this will change in the near future - when
the core part of Apogee will be done so that we can integrate the engine
into Apogee.

Anyway, anyone is welcome to contribute with fixes or new features.

A first change in the engine implementation I see is to integrate the
XSD engine from https://xsom.dev.java.net/
This is fully supporting XSD specs so the xforms engine may benefit of them.
(Continue reading)

Permalink | Reply |

Gmane