<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2838" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=006342117-25032006><FONT face=Arial
color=#0000ff size=2>And "<FONT face="Times New Roman" color=#000000 size=3>
OpenCms 6.0 HtmlArea WYSIWYG editor plugin".</FONT></FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> opencms-dev-bounces@opencms.org
[mailto:opencms-dev-bounces@opencms.org] <B>On Behalf Of </B>Jonathan
Woods<BR><B>Sent:</B> 24 March 2006 05:53<BR><B>To:</B> 'The OpenCms mailing
list'<BR><B>Subject:</B> [opencms-dev] Answer: Minimum set of modules for base
6.0.4installation<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><SPAN class=775124505-24032006><FONT face=Arial size=2>A while back I
asked the list what people thought was the minimum set of modules required for a
clean installation, assuming that you're not using TemplateOne. Thanks to
those who responded.</FONT></SPAN></DIV>
<DIV><SPAN class=775124505-24032006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=775124505-24032006><FONT face=Arial size=2>After some
experimentation, and in case it's useful for anyone else, here's what I fixed
upon in the end:</FONT></SPAN></DIV>
<DIV><SPAN class=775124505-24032006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=775124505-24032006><FONT face=Arial size=2>- no documentation
modules<BR>- "OpenCms Editors: OpenCms 6.0 Common editors (1.0.2)"<BR>- "OpenCms
Online Help: OpenCms 6.0 Workplace english online help (1.0.2)" [or German
version, of course]<BR>- "OpenCms Online Help: OpenCms 6.0 Workplace online help
- Base module (1.0.2)"<BR>- all modules whose names begin "OpenCms
Workplace"<BR>- subsequent upload of FCKEdidtor module</FONT></SPAN></DIV>
<DIV><SPAN class=775124505-24032006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=775124505-24032006><FONT face=Arial size=2>After using the
set-up wizard to install only these modules, I've subsequently found it safe to
manipulate </FONT></SPAN><SPAN class=775124505-24032006><FONT face=Arial
size=2>opencms-modules.xml directly when developiing my own modules, defining
the opencms-modules.xml/<module> node in conjunction with creating the
module structure in the Workplace or via CmsShell. In other words OpenCms
takes opencms-modules.xml as the gospel truth for module attributes and doesn't
stash module metadata in the VFS, which makes IDE-driven development a whole lot
easier.</FONT></SPAN></DIV>
<DIV><SPAN class=775124505-24032006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=775124505-24032006><FONT face=Arial
size=2>Jon</FONT></SPAN></DIV>
<DIV><SPAN class=775124505-24032006><FONT face=Arial
size=2> </DIV></FONT></SPAN></BODY></HTML>