Fw: [Seaside] Form support

[tblanchard@mac.com]

--Apple-Mail-2-732273664
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed


On Friday, December 6, 2002, at 12:20  AM, Avi Bryant wrote:
> On Thu, 5 Dec 2002, Adrian Lienhard wrote:
>
>> The thing above could also be used for database mapping(?)
>
> Database mappings have to be a little more specialized (in terms of 
> also
> having the column names and all that), and O/R frameworks tend to come
> with their own metamodel.  However, I can definitely see deriving a 
> rough
> Seaside metamodel from, say, a GLORP or Tantalus metamodel.

We currently do this with EOF in WebObjects.  We have ui components 
that check the EOModel and put little red stars next to them if they 
are not allowed to be null, etc...

And of course,  there is the direct to web framework to steal ideas 
from.


--Apple-Mail-2-732273664
Content-Transfer-Encoding: 7bit
Content-Type: text/enriched;
	charset=US-ASCII



On Friday, December 6, 2002, at 12:20  AM, Avi Bryant wrote:

<excerpt>On Thu, 5 Dec 2002, Adrian Lienhard wrote:<color><param>0000,6363,1212</param>

</color>

<excerpt>The thing above could also be used for database mapping(?)

</excerpt>

Database mappings have to be a little more specialized (in terms of
also

having the column names and all that), and O/R frameworks tend to come

with their own metamodel.  However, I can definitely see deriving a
rough

Seaside metamodel from, say, a GLORP or Tantalus metamodel.

</excerpt>

We currently do this with EOF in WebObjects.  We have ui components
that check the EOModel and put little red stars next to them if they
are not allowed to be null, etc...


And of course,  there is the direct to web framework to steal ideas
from.



--Apple-Mail-2-732273664--