Florent Guillaume wrote:
On 2 Jun 2006, at 09:00, yuppie wrote:
Florent Guillaume wrote:
Sorry to beat a dead horse, but can't we have "cmf" as a domain
everywhere and be done with it? There's really no point in separating
cmf_default from cmf_somethingelse.
The point is to use CMFCalendar a
On 6/2/06, Florent Guillaume <[EMAIL PROTECTED]> wrote:
> But -1 for merging 'cmf_default' and 'cmf_calendar'.
Why? Because you lose the example of changing the domain? Isn't that
what docs are for?
Well, CMFCalendar is quite separate from the rest of the CMF in many
ways, and if we merge the
On 2 Jun 2006, at 09:00, yuppie wrote:
Florent Guillaume wrote:
Sorry to beat a dead horse, but can't we have "cmf" as a domain
everywhere and be done with it? There's really no point in
separating cmf_default from cmf_somethingelse.
The point is to use CMFCalendar as an example add-on prod
Florent Guillaume wrote:
Sorry to beat a dead horse, but can't we have "cmf" as a domain
everywhere and be done with it? There's really no point in separating
cmf_default from cmf_somethingelse.
The point is to use CMFCalendar as an example add-on product that shows
how to use a different dom
Sorry to beat a dead horse, but can't we have "cmf" as a domain everywhere
and be done with it? There's really no point in separating cmf_default from
cmf_somethingelse.
Florent
Yvo Schubbe wrote:
Log message for revision 68423:
- fixed the i18n domain
Changed:
U CMF/trunk/CMFCore/brow
