Re: [binarycloud-dev] entity definition format

[Alex B. <en...@tu...>]

> -- Quoting the R2 draft spec --
> Default ui controls are assigned to each entity based on its type
> declaration, which means the system is capable of generating default
> forms.

Oh, really!

Heh, apparently I have already thought of this! :)

> To facilitate such a great feature, it would be required to define these
> markup values in the entity definition.  I would like to see the
> defaults defined here, as you mentioned, but tolerant for overriding
> values in the templates.

Which is exactly what I had envisioned. I don't view it as a 'breach of
style' to have UI components associated with fields in an entity definition.

Imagine defining a set of xml files, and being able to basically say "ok,
make me a set of database tables and default modules + pages" and _bing_ a
default site is built for you, which you can take and customize to fit the
application.


> jason
> 
> 
> Andreas Aderhold wrote:
>>>> 2. i noticed <maxlength> which i can forsee being used for setting a
>>>> maxlength in a input field (HTML), and for possibly determining the
>>>> field length in the database.  (is this correct?)  BUT, there was no
>>> 
>>> Correct on both accounts.
>>> 
>>>> LENGTH value anywhere.  if HTML forms are to be built on the entities,
>>>> having a MAXLENGTH as well as a LENGTH would be desired.
>>> 
>>> Yes, I see your point. I was toying with the idea of associating
>>> UI controls with each field type. That may still happen, so:
>>> <!-- look here -->
>>>             <uicontrol>
>>>                 <name>TextField</name>
>>>                 <params>
>>>                     <length>20</length>
>>>                 </params>
>>>             </uicontrol>
>>>         </field>
>> Hmm. But isn't that markup stuff something for the template engine/up to the
>> designer? I'm not quite sure if integrating the UI stuff with the entities
>> is wise or not.
>> Imagine you use the size/length attribute of an input field within more
>> contextes. So you have a from_a with size="20" is fine, in form_b using the
>> same entitiy size="20" does not fit, you need size="40" in form_c you need
>> style="width: 80px" and the so on...
>> Ok, maybe you can override this in the template and the etydef values are
>> defaults or whatever. Anyway, I think markup stuff does not belong here.
> 
> _______________________________________________
> binarycloud-dev mailing list
> bin...@li...
> http://lists.sourceforge.net/lists/listinfo/binarycloud-dev
>