Re: [binarycloud-dev] Revised entity definition xml

[John D. <jo...@we...>]

I think it makes most sense in the lister/editor definition for that entity.
These are presentation-oriented, whereas the entity definition was never really
meant to be. 

I'm not quite sure what you mean by default, every field has only one control
associated with it, which is determined based on the type. I could see
associating user-defined controls with user-defined types, or assigning a
custom control to a certain field. But in general it seems like type controls
aren't something people will have to do anything for when writing their editor,
only overriding with their custom field controls if necessary.

My $.02

John

On Tue, 21 Aug 2001, alex black wrote:

> >
> > > I like having the control definition in there, I think it's nice and
> > > convenient (and it gives you iron fisted control over default
> presentation)
> > >
> >
> > The entity definition really has nothing to do with presentation. I think
> even
> > the ptype is in the wrong place. These things are all meaningless to an
> XML
> > client, for example. Also, having a control definition inline like that
> means
> > it cannot be reused. I think that's evil :)
> 
> How would you do it?
> Assume the following:
>     -You want a default ui control assigned to each entity field
>     -you want to be able to assign them easily
> 
> where :)?
> 
> _a
> 
> 
> _______________________________________________
> binarycloud-dev mailing list
> bin...@li...
> http://lists.sourceforge.net/lists/listinfo/binarycloud-dev
> 
> 

-- 

John Donagher
Application Engineer, Intacct Corp.

Public key available off http://www.keyserver.net
Key fingerprint = 4024 DF50 56EE 19A3 258A  D628 22DE AD56 EEBE 8DDD