If I want it through xml file, then how should I do?
The xml file maybe seems like this:
<fields>
<field attribute='ChUrl' type='A' />
<field attribute= SupportedCharsets' type='A' />
<field attribute=' ServerID' type='A' />
<field attribute='ServerID' type='B' />
</fields>
While in form, we can get all the attributes of type A.
<form name="xxxxxx" type="single"
target="createProtocolAttribute?protocolid=${id}">
<field name="ChlUrl"><text/></field>
<field name="SupportedCharsets"><text/></field>
<field name="ServerID"><text/></field>
<field name="submitButton" title="Add Protocol">
<submit button-type="button"/>
</field>
</form>
-----Original Message-----
From: David E Jones [mailto:[email protected]]
Sent: 2009年2月18日 2:28
To: [email protected]
Subject: Re: Tricky! About fields in the form
Jack,
I suggested configuring these through entity fields instead of in the
database because that is what is supported right now.
If you want something that adds fields to a Form Widget form based on
data in the database that would have to be written as it currently
only feeds from the form definition XML files. That wouldn't be too
hard to do (ie add functionality to add fields based on the database).
We decided early on that we wanted these things configured from XML
files instead of being more database driven (like Compiere and certain
other frameworks are) because it is easier to revision control and
manage in a large-scale environment (especially for updates and
collaboration when multiple people are working on the applications).
So yes, it could certainly be developed as an extension to the current
Form Widget, but does not exist now.
-David
On Feb 17, 2009, at 6:46 AM, Jack Liu wrote:
> Are you sure what I want and you have a good solution?
> Again:
> What I want is not drop-down list
>
> In table attributetype:
> Id attribute type
> 1 ChUrl A
> 2 SupportedCharsets A
> 3 ServerID A
> 4 ServerID B
>
>
> While in form, we can get all the attributes of type A.
>
> <form name="xxxxxx" type="single"
> target="createProtocolAttribute?protocolid=${id}">
> <field name="ChlUrl"><text/></field>
> <field name="SupportedCharsets"><text/></field>
> <field name="ServerID"><text/></field>
> <field name="submitButton" title="Add Protocol">
> <submit button-type="button"/>
> </field>
> </form>
>
> Three fields ChlUrl, SupportedCharsets, ServerID are all fetched
> from table, not written by hand. Of course, the form maybe looks
> different, but can reach the same effect as above.
>
> Are you sure you can do it? If you can do it, money is not a
> problem, I think.
>
> -----Original Message-----
> From: BJ Freeman [mailto:[email protected]]
> Sent: 2009年2月17日 21:20
> To: [email protected]
> Subject: Re: Tricky! About fields in the form
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On the list I point people to places they can learn.
> however if you want personal help I will be glad to consult with you
> for
> a fee.
>
> Jack Liu sent the following on 2/17/2009 5:13 AM:
>> Could you give me an example in OFBiz?
>> I think it's very easy for you to find an example?
>>
>>
>> -----Original Message-----
>> From: BJ Freeman [mailto:[email protected]]
>> Sent: 2009年2月17日 20:51
>> To: [email protected]
>> Subject: Re: Tricky! About fields in the form
>>
>> find a page that has a drop down and look at the code.
>> preferably widget.
>> also look up views that use the org.ofbiz.common.enum entity
>> there are examples in code.
>> My comments are how ofbiz sees things.
>> it takes a while for a datbase centric person to see things the way
>> ofbiz does it. I speak from experience.
>> If you step back and let go of the Table Columnnames, it helps.
>>
>>
>>
>> Jack Liu sent the following on 2/16/2009 9:36 PM:
>>> Why would my attribute be enumerations?
>>> You mean attribute references an enumeration below?
>>
>>> <entity entity-name="protocolAttribute"
>>> <field name="id" type="id-ne"></field>
>>> <field name="protocolid" type="id"></field>
>>> <field name="attribute" type="long-varchar"></field>
>>> <field name="value" type="long-varchar"></field>
>>> <prim-key field="protocolid"/>
>>> <relation type="one" fk-name="ATTRIBUTE_ENUM" rel-entity-
>>> name="Enumeration">
>>> <key-map field-name="attribute" rel-field-name="enumId"/>
>>> </relation>
>>> </entity>
>>
>>> If a field is from an enumeration, in the page it will show a drop-
>>> down list.
>>> It's now what I want. What I want shows like below:
>>
>>> <form name="A" type="single"
>>> target="createProtocolAttribute?protocolid=${id}">
>>> <field name="ChlUrl"><text/></field>
>>> <field name="SupportedCharsets"><text/></field>
>>> <field name="ServerID"><text/></field>
>>> <field name="submitButton" title="Add Protocol">
>>> <submit button-type="button"/>
>>> </field>
>>> </form>
>>
>>> -----Original Message-----
>>> From: BJ Freeman [mailto:[email protected]]
>>> Sent: 2009t217
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFJmrlprP3NbaWWqE4RApi9AKCMLp29GUOlHpReAiEI6pON3Z0RfACgkdMg
> q1tPBF8EF5l1wOaQdz0fRY4=
> =OcS9
> -----END PGP SIGNATURE-----
