Mailing-List: contact user-help@cayenne.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cayenne.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <20080122081521.631c1292@localhost.localdomain>
References: <E62B36ED-C00E-42AA-9213-1B460ED3AB4A@mac.com>
 <20080122081521.631c1292@localhost.localdomain>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <F05A3C96-6EDB-4B82-9F9A-F7634B4B8009@mac.com>
Content-Transfer-Encoding: 7bit
From: Florijan Stamenkovic <flor385@mac.com>
Subject: Re: Databinding library released
Date: Tue, 22 Jan 2008 12:03:53 -0400
To: user@cayenne.apache.org

Adrian,

On Jan 22, 2008, at 03:15, Adrian Wiesmann wrote:

> Hello Florijan
>
> Nice work.

Thanks.

>> I am hoping that some of you Cayenne users would chip in the hour or
>> two needed for implementing Cayenne support. The website describes in
>> detail how this can be done.
>
> Could be interesting to look into your Databinding together with  
> what was
> already done with DataViews. I had a quick look and my first  
> impression is
> it that there are at least similarities.
>
> But I am walking into another direction right now. I am working on a
> declarative UI and DataBinding framework in which you design the UI  
> in an
> XML formatted file (similar to HTML) and directly define the data  
> binding
> within that XML structure. A renderer does then take that XML file and
> renders a Swing, Wicket or FOP representation from the defined  
> structure.
> A code-behind class handles events and stuff.
>
> Said so I will have a look into your binding framework to see if I  
> could
> remove my own binding mechanism and use yours instead. The main  
> problem I
> currently see is that we have to parse the binding information and
> translate this to a binding information which your framework would
> understand.

Well, I suppose binding information can only vary so much, in the end  
you always connect a property of a data carrying object with a user  
interface element. I think the complexity of what you want to do  
depends on other issues. For example, would you go for a completely  
generated user interface, or would you combine XML binding with user  
interfaces laid out by hand? If it is all generated, does your XML  
also contain "hints" as to how the user interface should be  
generated? If it does not, how do you control the layout of the  
interface? In my opinions these are some of the tough questions when  
one is designing what I understand you are. But I'm pretty sure you  
could integrate JBND into it.

Flor