I can see why you create your lists as you do, but I agree with both the
amendments. I use the topic plugin all the time and occasionally the
smiley plugin. (I will document it some time and would use it more if I
knew how to invoke some of the odder smileys (particularly the smug one.))
I personally think the ConvertLineBreaksPlugin produces terrible HTML
and is hard to incorporate into a theme and inhibits the formating of
code and tables (which I also oppose in blog articles), so would suggest
that it is an extra not core.
The customers, i.e. people who make the plugins available for use are
the site managers, but removing it would mean that people will have to
learn HTML. You can survive with <P>, <A> and <IMG> though how hard is that?
Dave Johnson wrote:
On 8/29/06, Allen Gilliland <[EMAIL PROTECTED]> wrote:
2. Move all plugins which are shipped with Roller into the core src
directory so they are actually part of the main build.
3. Remove all plugins which are *not* going to be shipped with Roller
from being included in a standard build. They can stay in the contrib
area and just be built separately, or possibly moved elsewhere like the
Roller support project.
anyone object to any of these steps?
+1 on this idea
keep in core:
ConvertLineBreaksPlugin
BookmarkPlugin
ObfuscateEmailPlugin
I'd replace the BookmarkPlugin with TopicTagPlugin, based on popularity.
- Dave
--
Dave
<http://www.sun.com> * David Levy *
*Sun Microsystems Ltd.*
55, King William St.,
London EC4R 9ND United Kingdom
Phone +44 (0) 20 7469 9908/x18308
Mobile +44 (0) 7710-360922
Blog http://blogs.sun.com/DaveLevy
Email [EMAIL PROTECTED]
Sun Proprietary & Confidential . This e-mail message is for the sole use
of the intended recipient(s) and may contain confidential and
privilidged information. Any unauthorised review, use, disclosure or
distribution is prohibited. If you are not the intended recepient,
please contact the sender by reply e-mail and destroy all copies of the
original message.
