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-----
