Previously Jens Vagelpohl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 18, 2008, at 09:56 , Wichert Akkerman wrote:
I'm not the greatest artist in the world, if anyone dislikes a
particular icon please feel free to replace it with something that
makes sense to a normal
Hi Jens!
Jens Vagelpohl wrote:
This has now landed, in several chunks because it turned out to be
more work and a larger change set than expected, on the CMF trunk.
Silly me thinking most of my work was done when Yuppie thoughtfully
added a icon URL expression property to the new-style
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 18, 2008, at 11:13 , yuppie wrote:
- extend the old-style actions, those you see e.g. on a type
information Actions tab in the ZMI, to also have a field for an
icon
URL expression
That might have been the most pragmatic solution, but
Previously yuppie wrote:
I personally prefer to move all type info Actions to the actions tool. I
can't see a need to specify separate 'view', 'edit' or 'metadata'
Actions for each content type. That just makes it necessary to maintain
a lot of redundant configuration data. In how many
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jens Vagelpohl wrote:
On Sep 13, 2008, at 15:28 , Jens Vagelpohl wrote:
Question: Wouldn't it make sense to enable the new action icons
functionality in the various templates to show icons if an expression
for an icon is provided, and
Hi Martin!
Martin Aspeli wrote:
yuppie-4 wrote:
Wichert Akkerman wrote:
Previously yuppie wrote:
I personally prefer to move all type info Actions to the actions tool. I
can't see a need to specify separate 'view', 'edit' or 'metadata'
Actions for each content type. That just makes it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
yuppie wrote:
Hi Martin!
Martin Aspeli wrote:
yuppie-4 wrote:
Wichert Akkerman wrote:
Previously yuppie wrote:
I personally prefer to move all type info Actions to the actions tool. I
can't see a need to specify separate 'view', 'edit' or
yuppie wrote at 2008-9-18 11:13 +0200:
...
I personally prefer to move all type info Actions to the actions tool. I
can't see a need to specify separate 'view', 'edit' or 'metadata'
Actions for each content type. That just makes it necessary to maintain
a lot of redundant configuration data.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 14, 2008, at 06:35 , Wichert Akkerman wrote:
Previously Martin Aspeli wrote:
Jens Vagelpohl wrote:
Question: Wouldn't it make sense to enable the new action icons
functionality in the various templates to show icons if an
expression
Wichert Akkerman wrote:
Easier customization - no need to let people touch the action itself?
You can change a property of an action easily enough with GS or in the
ZMI. So, a separate registry is more isolated, but it's also harder to
guess which portal_actionicons thing you need to
Previously Martin Aspeli wrote:
Jens Vagelpohl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today I was looking at the CMFActionIcons product and wondered about a
few things. First of all, there's no obvious way to enable the actions
and include the template snippets that
11 matches
Mail list logo
