optional _properties keys 'title' and 'descr'

The suggested features can easily be implemented in 3.party-Products. Introdrucing a new "description"-property for all SimpleItems will probably break existing products / installations...

Suggestion: Issue should be closed.

Status: Pending => Rejected

> The suggested features can easily be implemented in 3.party-Products.

Of course it can; but it would be nice to have a standard, preventing the wheel getting re-invented 100s of times.

> Introdrucing a new "description"-property for all SimpleItems will
> probably break existing products / installations...

I doubt this! These are *optional* property keys. Other products which override the propertyManager themselves are not affected.

Status: Rejected => Pending

> = Comment - Entry #4 by to_be on May 19, 2003 5:47 am
>
> > The suggested features can easily be implemented in
> 3.party-Products.
>
> Of course it can; but it would be nice to have a standard,
> preventing the wheel getting re-invented 100s of times.
>
> > Introdrucing a new "description"-property for all
> > SimpleItems will
> > probably break existing products / installations...

This issue isn't about adding "properties" to objects; it is
about adding "meta-properties" to properties.

> I doubt this! These are *optional* property keys. Other
> products which override the propertyManager themselves are
> not affected.

Agreed. Just so that we are clear about what is proposed:

  - Currently, OFS.PropertyManager (and PropertySheets) use
    a sequence of mappings to define the properties on a given
    sheet:

    class Foo( OFS.PropertyManager ):

        prop1 = 'one'
        prop2 = 2
        prop3 = ( 'one', 'two', 'three' )

        _properties = (
          { 'id' : 'prop1', 'type' : 'string', 'mode' : '' }
        , { 'id' : 'prop2', 'type' : 'int', 'mode' : '' }
        , { 'id' : 'prop3', 'type' : 'lines', 'mode' : '' }
        )

The proposal is to change the 'manage_propertiesForm' UI (and
other UI generated for propertysheets) such that it looks for
two new keys, 'title' and 'description', in each mapping.

If present, they would be used to present a more usable
form to the user. If absent (as everything would be, at first),
the UI would look exactly as it does today. So, to amend the
example::

    class Foo( OFS.PropertyManager ):

        prop1 = 'one'
        prop2 = 2
        prop3 = ( 'one', 'two', 'three' )

        _properties = (
          { 'id' : 'prop1', 'type' : 'string', 'mode' : '',
            'title' : 'Property 1' }
        , { 'id' : 'prop2', 'type' : 'int', 'mode' : '',
            'description' : 'This is an integer ....' }
        , { 'id' : 'prop3', 'type' : 'lines', 'mode' : '' }
        )

This *can't* be done in 3rd party code without a monkey-patch.
It also can't break any existing code.

PropertyManager already has a hook to display a human-readable
title, it's called propertyLabel().

CMF's SimpleItemWithProperties uses this hook for the 'label'
field of properties. I propose to reuse this rather than
'title', as it is an existing established standard for CMF.
But 'description' should be added.

Or at least, if we use 'title', be backward-compatible with 'label'.

'label' and 'description' would be OK for me. Thanks for your comments!

Sorry for bringing this up to the radar, but I did misunderstand the original request. I thought, that the something like some additional metadata per object should be added.

I'm fine with Tres' interpretation...:)

Hi, continues even with the problems in the newer versions?

Fix now merged to 2.9 branch:

 http://svn.zope.org/Zope/branches/2.9/?rev=86454&view=rev

2.10 branch:

 http://svn.zope.org/Zope/branches/2.10/?rev=86455&view=rev

2.11 branch:

 http://svn.zope.org/Zope/branches/2.11/?rev=86456&view=rev

and trunk:

 http://svn.zope.org/Zope/trunk/?rev=86457&view=rev

Included in 2.10.6 and 2.11.0.

<a href="http://www.aaa-ch.net/">風俗</a>
 <a href="http://www.aaa-ch.net/">デリヘル</a>
 <a href="http://www.aaa-ch.net/m/">風俗</a>
 <a href="http://www.aaa-ch.net/area.php?category=2000">デリヘル 風俗</a>
 <a href="http://www.akibain.com/">エロゲー</a>
 <a href="http://www.pure-soapland.com/i/">ソープランド</a>
 <a href="http://www.pure-soapland.com/i/">吉原 ソープランド</a>
 <a href="http://chuh.jp/">出会い</a>
 <a href="http://pc.chuh.jp/">出会い</a>
 <a href="http://www.erogle.net/m/">デリヘル</a>
 <a href="http://www.pure-soapland.com/chiiki/susukino/">すすきの ソープラン
ド</a>
 <a href="http://www.pure-soapland.com/chiiki/sonota/">新宿 ソープランド</a>
 <a href="http://www.pure-soapland.com/chiiki/chiba/">千葉 ソープランド</a>
 <a href="http://www.pure-soapland.com/chiiki/saitama/">埼玉 ソープランド</a>
 <a href="http://www.pure-soapland.com/chiiki/kanagawa/">神奈川 ソープランド
</a>
 <a href="http://www.pure-soapland.com/index2.html">吉原 ソープランド</a>
 <a href="http://avshop.jp/">sod</a>
 <a href="http://dreamynightshop.jp/">バイブ</a>
 <a href="http://onstyle.co.jp/">風俗求人 高収入</a>
 <a href="http://onstyle.co.jp/">都内 キャバクラ 全額日払い</a>
 <a href="http://ecsta.tv/">無料動画</a>
 <a href="http://kansai.bigdesire.co.jp/">大阪 風俗</a>
 <a href="http://kansai.bigdesire.co.jp/mobile/">大阪 風俗</a>
 <a href="http://kansai.yorutomo.net/i/">神戸 風俗</a>
 <a href="http://www.eroshima.com/">裏DVD</a>
 <a href="http://www.eroshima.com/mobile/">裏DVD</a>
 <a href="http://valentine-works.com/">風俗 求人</a>
 <a href="http://valentine-works.com/m/">風俗 求人</a>
 <a href="http://no1-shinjuku.jp/">デリヘル 新宿</a>
 <a href="http://no1-shinjuku.jp/">デリヘル 東京</a>
 <a href="http://www.55group.jp/">千代田区 デリヘル</a>
 <a href="http://www.55group.jp/">台東区 デリヘル</a>
 <a href="http://www.55group.jp/">墨田区 デリヘル</a>
 <a href="http://www.55group.jp/">中央区 デリヘル</a>

風俗
デリヘル
風俗
デリヘル 風俗
エロゲー
ソープランド
吉原 ソープランド
出会い
出会い
デリヘル
すすきの ソープランド
新宿 ソープランド
千葉 ソープランド
埼玉 ソープランド
神奈川 ソープランド
吉原 ソープランド
sod
バイブ
風俗求人 高収入
都内 キャバクラ 全額日払い
無料動画
大阪 風俗
大阪 風俗
神戸 風俗
裏DVD
裏DVD
風俗 求人
風俗 求人
デリヘル 新宿
デリヘル 東京
千代田区 デリヘル
台東区 デリヘル
墨田区 デリヘル
中央区 デリヘル

<a href="http://blog.goo-net.com/f1mania/">出会い</a>
<a href="http://blog.plaync.jp/level999.slog">出会い</a>
<a href="http://www.bloxster.net/kurohige/">家出少女 掲示板</a>
<a href="http://www.bloxster.net/shirohige/">セフレ</a>
<a href="http://nicorobinn.bravejournal.com/">セフレ</a>
<a href="http://tenka.hide-yoshi.net/">セフレ</a>
<a href="http://take.katsu-yori.com/">メル友</a>
<a href="http://kuro.kan-be.com/">家出サイト</a>
<a href="http://shoujyo.kage-tsuna.com/">家出少女 掲示板</a>
<a href="http://home.kane-tsugu.com/">家出少女 掲示板</a>
<a href="http://matsu.hisa-hide.com/">援交</a>
<a href="http://blog.qooza.hk/momotarou">メル友</a>
<a href="http://bookmarks.yahoo.com/pages/onelove_ruru/frequent">出会い</a>
<a href="http://bookmarks.yahoo.com/pages/fid/270">出会い</a>
<a href="http://net.p-wiki.jp/mailmail/">メル友</a>
<a href="http://net.p-wiki.jp/mailmail/index.php?%A5%E1%A5%EB%CD%A7">メル友</a>
<a href="http://mywiki.jp/aokiji/">メル友</a>
<a href="http://mywiki.jp/aokiji/%83%81%83%8B%97F/">メル友</a>
<a href="http://www.cmsinfo.org/blog/1841">出会い</a>
<a href="http://www.cmsinfo.org/node/15385">出会い</a>
処女
Thank you for your cooperation!!

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

 status invalid
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkseUTIACgkQ+gerLs4ltQ6spwCfYwyLAWv3peo3kLGflbLLOWv+
0R0AnA38CXxU39rG/upWgRHGVAINRXaX
=FaOo
-----END PGP SIGNATURE-----