Nabble - Lenya

Re: Shipping the docu as default publication

2008-08-30T03:52:37Z

Hi all

> Andreas Hartmann schrieb:
>
> > Thomas Comiotto schrieb:
>
> > On Aug 25, 2008, at 5:15 PM, Richard Frovarp wrote:
> >
> >> Andreas Hartmann wrote:
> >>> Hi Lenya devs,
> >>>
> >>> there seems to be a consensus that it would be a good idea to ship
> >>> the docu publication as an example instead of the default
> publication.
> >
> > I think it's important to ship Lenya with both default and docu
> > publication. They have different target domains (i.e. tech-docu
> vs. web
> > publishing) and both serve as showcase and template for people
> building
> > their own customized publications. Shipping Lenya with docu
> publication
> > only will lead to the first impression that you deal with a system
> for
> > technical documentation only.

That's a very convincing point of view - but might take more resources
for maintenance.

>
> I agree to these points. But instead of shipping multiple independent
> sample publications, I'd rather suggest to emphasize the modularity of
> Lenya and the publication templating concept.
>
> Here's another random thought:
>
> - Create a "base" pub defining all page generation pipelines
> - Use the base pub as a template for both docu and example pub
> - Use different layouts for docu and example pub (see below)
> - Enable the news module (and other upcoming modules) in the example
> pub
>
> All editors should work out of the box in all publications derived
> from
> the base pub. We can tell people that they risk breaking the editor
> support if they don't use the base pub as template. Since the base pub
> defines the page flow and the other publications only override the
> XSLTs, this should be no problem (given that the editors support the
> resource types).

I hear the «we have too many editors and should get rid of some» bell.

>
> This way we would keep the "concrete" publications (docu and example)
> minimal. I can imagine this makes it easier to get started with a new
> publication.
>
> By using different layouts for docu and example pub, we show how the
> layout can be customized.

This sounds very tempting.

But this approach might also add a bit more complexity and dependencies.

We could do the design contest step by step:

1) start with the redesign of the docu pub (regardless of merging with
default pub or not)
2) if we do not merge and develop a web publishing publication, we'll
style that publication in the same way - maybe ask the designer to
help us with it.

WDYT?

Jürgen

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Lenya - Dev

Re: Website update for 2.0.2 release?

2008-08-29T12:40:24Z

Richard Frovarp wrote:

> Andreas Hartmann wrote:
>>
>> I have updated the website. Will you find the time to send the
>> announcements? IMO this should be done by you so that you'll get the
>> credits for doing the release.
>>
> Thanks. Things got a bit crazy with the beginning of the school year.
> I have posted the announcement out to the email addresses posted.
> Having issues with javalobby and theserverside.com sites.
>
> Richard

Okay, I just got theserverside.com to work and updated wikipedia versions.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Lenya - Dev

Re: Website update for 2.0.2 release?

2008-08-29T12:36:35Z

Andreas Hartmann wrote:
>
> I have updated the website. Will you find the time to send the
> announcements? IMO this should be done by you so that you'll get the
> credits for doing the release.
>
Thanks. Things got a bit crazy with the beginning of the school year. I
have posted the announcement out to the email addresses posted. Having
issues with javalobby and theserverside.com sites.

Richard

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Lenya - Dev

[Announce] Apache Lenya 2.0.2 released

2008-08-29T12:06:50Z

Apache Lenya 2.0.2 released
=====================

The Apache Lenya development community is proud to announce the 2.0.2
release of Apache Lenya.

Apache Lenya is an Open Source Java/XML Content Management System and
comes with revision control, site management, scheduling, search,
WYSIWYG editors, and workflow.

Apache Lenya is based on Apache Cocoon (http://cocoon.apache.org). You
can use Cocoon features such as robust caching, multi-channel output,
it's many connectivity options to quickly build customized solutions to
meet your specific needs that are not already covered by Apache Lenya today.

Check out the Apache Lenya website (http://lenya.apache.org) for more
information.

The Apache Lenya Community

Bug Fixes in Apache Lenya 2.0.2
===============================

* Miscellaneous smaller bugfixes
* Miscellaneous performance enhancements
* Fixes for web tests
* Fixed infinite loop caused by unsynchronized HashMap
* Removed old multiple inheritance code that wasn't functional
* Enhanced / Fixed layout for asset overview

New Features in Apache Lenya 2.0.2
==================================

* New navigation module for more flexibility (it's use is optional)
* Added meta data search capabilities (e.g. image search)
* Added checkin of live sitetree
* Added report to find broken internal links
* Added session monitoring
* Display file size in overview

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@...
For additional commands, e-mail: user-help@...

From forum: Lenya - Users

[Announce] Apache Lenya 2.0.2 released

2008-08-29T12:06:50Z

Apache Lenya 2.0.2 released
=====================

The Apache Lenya development community is proud to announce the 2.0.2
release of Apache Lenya.

Apache Lenya is an Open Source Java/XML Content Management System and
comes with revision control, site management, scheduling, search,
WYSIWYG editors, and workflow.

Apache Lenya is based on Apache Cocoon (http://cocoon.apache.org). You
can use Cocoon features such as robust caching, multi-channel output,
it's many connectivity options to quickly build customized solutions to
meet your specific needs that are not already covered by Apache Lenya today.

Check out the Apache Lenya website (http://lenya.apache.org) for more
information.

The Apache Lenya Community

Bug Fixes in Apache Lenya 2.0.2
===============================

* Miscellaneous smaller bugfixes
* Miscellaneous performance enhancements
* Fixes for web tests
* Fixed infinite loop caused by unsynchronized HashMap
* Removed old multiple inheritance code that wasn't functional
* Enhanced / Fixed layout for asset overview

New Features in Apache Lenya 2.0.2
==================================

* New navigation module for more flexibility (it's use is optional)
* Added meta data search capabilities (e.g. image search)
* Added checkin of live sitetree
* Added report to find broken internal links
* Added session monitoring
* Display file size in overview

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Lenya - Dev

Re: Website update for 2.0.2 release?

2008-08-29T03:56:59Z

Richard Frovarp schrieb:

> Andreas Hartmann wrote:
>> Hi Richard,
>>
>> thanks a lot for doing the release!
>>
>> I have noticed that you have already uploaded the tarballs to the
>> download server. Can we proceed with updating the project website and
>> releasing the announcements?
>>
>> -- Andreas
>>
>>
> Yes. I've updated the pages on docu. I was going to give it a night for
> the mirrors to pick up the changes. However, things have been busy
> around here, so I haven't had a chance to dump the updated docu pages
> into svn. If you want to do it, go for it. If not, I should be able to
> find some time during my afternoon.

I have updated the website. Will you find the time to send the
announcements? IMO this should be done by you so that you'll get the
credits for doing the release.

-- Andreas

--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Lenya - Dev

Re: Shipping the docu as default publication

2008-08-29T03:52:49Z

Thomas Comiotto schrieb:

> On Aug 25, 2008, at 5:15 PM, Richard Frovarp wrote:
>
>> Andreas Hartmann wrote:
>>> Hi Lenya devs,
>>>
>>> there seems to be a consensus that it would be a good idea to ship
>>> the docu publication as an example instead of the default publication.
>
> I think it's important to ship Lenya with both default and docu
> publication. They have different target domains (i.e. tech-docu vs. web
> publishing) and both serve as showcase and template for people building
> their own customized publications. Shipping Lenya with docu publication
> only will lead to the first impression that you deal with a system for
> technical documentation only.

I agree to these points. But instead of shipping multiple independent
sample publications, I'd rather suggest to emphasize the modularity of
Lenya and the publication templating concept.

Here's another random thought:

- Create a "base" pub defining all page generation pipelines
- Use the base pub as a template for both docu and example pub
- Use different layouts for docu and example pub (see below)
- Enable the news module (and other upcoming modules) in the example pub

All editors should work out of the box in all publications derived from
the base pub. We can tell people that they risk breaking the editor
support if they don't use the base pub as template. Since the base pub
defines the page flow and the other publications only override the
XSLTs, this should be no problem (given that the editors support the
resource types).

This way we would keep the "concrete" publications (docu and example)
minimal. I can imagine this makes it easier to get started with a new
publication.

By using different layouts for docu and example pub, we show how the
layout can be customized.

WDYT?

-- Andreas

--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Lenya - Dev

Re: Website update for 2.0.2 release?

2008-08-28T06:41:03Z

Andreas Hartmann wrote:

> Hi Richard,
>
> thanks a lot for doing the release!
>
> I have noticed that you have already uploaded the tarballs to the
> download server. Can we proceed with updating the project website and
> releasing the announcements?
>
> -- Andreas
>
>

Yes. I've updated the pages on docu. I was going to give it a night for
the mirrors to pick up the changes. However, things have been busy
around here, so I haven't had a chance to dump the updated docu pages
into svn. If you want to do it, go for it. If not, I should be able to
find some time during my afternoon.

Richard

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Lenya - Dev

Website update for 2.0.2 release?

2008-08-28T05:39:37Z

Hi Richard,

thanks a lot for doing the release!

I have noticed that you have already uploaded the tarballs to the
download server. Can we proceed with updating the project website and
releasing the announcements?

-- Andreas

--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Lenya - Dev

Re: Shipping the docu as default publication

2008-08-27T06:33:24Z

Hi all

On Aug 25, 2008, at 5:15 PM, Richard Frovarp wrote:

> Andreas Hartmann wrote:
>> Hi Lenya devs,
>>
>> there seems to be a consensus that it would be a good idea to ship
>> the docu publication as an example instead of the default
>> publication.

I think it's important to ship Lenya with both default and docu
publication. They have different target domains (i.e. tech-docu vs.
web publishing) and both serve as showcase and template for people
building their own customized publications. Shipping Lenya with docu
publication only will lead to the first impression that you deal with
a system for technical documentation only.

Btw, the default publication could (should) be beefed up a bit to
better meet common expectations, say with a forum and a blog/
syndication module.

Bests
Thomas

------------------------------------------------------------------------
-----
Thomas Comiotto
thomas.comiotto@...

Universitaet Zuerich
Informatikdienste Tel: +41 44
63 54541
Winterthurerstrasse 190 +41 44
63 43333
CH-8057 Zuerich Fax: +41 44
63 54505

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Lenya - Dev

Re: Lenya redesign considerations

2008-08-26T10:16:08Z

Ciao Jürgen, hi Vik

Am 25.08.2008 um 11:31 schrieb Jürgen Ragaller:

Sorry, I am very late - but still want to express my agreement with
your proposal of a design contest, Jürgen!

There is also an issue that might be interesting in this context, see
below.

> Hi Vik
>
> Am 24.08.2008 um 18:34 schrieb Vik Tara:
>
>>>
>>>
>>> * What do you think of the general idea of redesigning lenya?

+1

>>>
>> A redesign would be great - but a templating system similar to that
>> available in other cms systems would surely be better?
>>
>>
>> Whilst we can create xhtml templates or hack the lenya xsl files - it
>> would be much more elegant to be able to create a template and
>> import it
>> into the authoring environment.

There are good reasons to do the layouting only on the css side - and
not in xsl files. We have come to the conclusion that only then it's
possible to maintain lenya sites with different layouts at reasonable
costs. (We produce lenya sites in five different layouts at the
moment - the layouting mostly done in the xsl files. Changes in the
presentation of a certain object have to be applied at five different
places.)

We plan to use a xhtml-structure conforming to YAML (http://
www.yaml.de/en/home.html) as the interface between content
aggregation and the layouting of the publication. So the same xsl
files are used - though the publications have different layouts.

The same issue will arise when you implement different design
templates in lenya. (What I find an appealing idea BTW.) The document
publication already produces a certain xhtml structure. This should
be sufficient for the design contest. But when it comes to implement
different layout proposals, something like YAML provides certainly
more flexibility, and is better tested and documented.

> [...]
>
> For me establishing a new templating mechanism and redesigning
> lenya are two different things.
>
> My personal taste is, that templating using xslt is one of lenyas
> great sides - a bit of a learning curve, but very flexible - and
> done in a standard way.
>
> If we'd like to attract designers we should provide a way to start
> with the design without any programming or templating knowledge
> (Photoshop, Fireworks templates).

I also think this is a good idea. That's how designers work, I guess.

> If the xhtml is clean, pretty much everything can go into css - so
> delivering a bit of xhtml should do it.
>
> A fun way of doing a contest for the default publication could be a
> publication where users can upload css files (and referenced
> images) - a css zen garden lenya publication - but that might be
> quite some work to setup.
>
>

Best regards

-michael

Michael Trindler
Informatikdienste
University of Zurich

>
> A much more demanding task is redesigning the cms authoring gui.
>
>
>
> Jürgen
>
>
> null-oder-eins GmbH Zürich
> web & graphic design
>
> www.null-oder-eins.ch
>
> ragaller@...
> Skype: callto://ragaller
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Lenya - Dev

Document changed: Open Source Content Management (Java/XML)

2008-08-25T09:22:59Z

Document: Open Source Content Management (Java/XML)
URL: https://lenya.zones.apache.org/cms/docu/live/index.html
Changed by user: Richard Frovarp (rfrovarp)

----
Removed: /document/body/section[1]/p[1]/text()[1]
The current stable version of Apache Lenya is 2.0. This is the recommended version for production use. You will at least need the Java 2 Platform, Standard Edition, version 1.4.2. Please follow the
----
Added: /document/body/section[1]/p[1]/text()[1]
The current stable version of Apache Lenya is 2.0.2. This is the recommended version for production use. You will at least need the Java 2 Platform, Standard Edition, version 1.4.2. Please follow the
----
Removed: /document/body/section[1]/ul/li[1]/text()[1]
Lenya 2.0
----
Added: /document/body/section[1]/ul/li[1]/text()[1]
Lenya 2.0.2
----
Removed: /document/body/section[1]/ul/li[2]/text()[1]
Lenya 2.0
----
Added: /document/body/section[1]/ul/li[2]/text()[1]
Lenya 2.0.2
----

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Lenya - Dev

Document changed: Download

2008-08-25T09:22:42Z

Document: Download
URL: https://lenya.zones.apache.org/cms/docu/live/docu20/installation20/download20.html
Changed by user: Richard Frovarp (rfrovarp)

----
Removed: /comment()[1]

Copyright 1999-2004 The Apache Software Foundation

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

----
Removed: /comment()[2]
$Id: index.xml 47563 2004-09-30 07:19:08Z michi $
----
Removed: /document/body/section[1]/ul/li[1]/text()[1]
Lenya 2.0
----
Added: /document/body/section[1]/ul/li[1]/text()[1]
Lenya 2.0.2
----
Removed: /document/body/section[1]/ul/li[2]/text()[1]
Lenya 2.0
----
Added: /document/body/section[1]/ul/li[2]/text()[1]
Lenya 2.0.2
----

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Lenya - Dev

Document changed: Release Management

2008-08-25T09:22:31Z

Document: Release Management
URL: https://lenya.zones.apache.org/cms/docu/live/docu/rm.html
Changed by user: Richard Frovarp (rfrovarp)

----
Removed: /comment()

Copyright 2002-2006 The Apache Software Foundation

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

----
Removed: /document/body/section[1]/section[4]/source[1]/text()
svn copy https://svn.apache.org/repos/asf/lenya/trunk\
https://svn.apache.org/repos/asf/lenya/tags/RELEASE_2_0_RC_2/\
-m "Tagging the 2.0 RC2."
----
Added: /document/body/section[1]/section[4]/source[1]/text()
svn copy https://svn.apache.org/repos/asf/lenya/trunk\ https://svn.apache.org/repos/asf/lenya/tags/RELEASE_2_0_RC_2/\ -m "Tagging the 2.0 RC2."
----
Removed: /document/body/section[1]/section[4]/source[2]/text()

svn co -r $REVISION https://svn.apache.org/repos/asf/lenya/branches/BRANCH_1_2_X
cd branches/BRANCH_1_2_X
svn copy branches/BRANCH_1_2_X tags/RELEASE_1_2_5
svn ci -m "Release 1_2_5 added" tags/RELEASE_1_2_5

----
Added: /document/body/section[1]/section[4]/source[2]/text()
svn co -r $REVISION https://svn.apache.org/repos/asf/lenya/branches/BRANCH_1_2_Xcd branches/BRANCH_1_2_Xsvn copy branches/BRANCH_1_2_X tags/RELEASE_1_2_5svn ci -m "Release 1_2_5 added" tags/RELEASE_1_2_5
----
Removed: /document/body/section[1]/section[5]/source[1]/text()

cd externals
svn propdel cocoon_2_1_x .
svn propset cocoon_2_1_10 https://svn.apache.org/repos/asf/cocoon/tags/cocoon-2.1/RELEASE_2_1_10 .

----
Added: /document/body/section[1]/section[5]/source[1]/text()
cd externalssvn propdel svn:externals .svn propset svn:externals "cocoon_2_1_10 https://svn.apache.org/repos/asf/cocoon/tags/cocoon-2.1/RELEASE_2_1_10" .
----
Removed: /document/body/section[1]/section[5]/source[2]/text()

cocoon.src.dir=externals/cocoon_2_1_10

----
Added: /document/body/section[1]/section[5]/source[2]/text()
cocoon.src.dir=externals/cocoon_2_1_10
----
Removed: /document/body/section[1]/section[5]/source[3]/text()

svn propset cocoon_2_1_x -r 608663 https://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X .

----
Added: /document/body/section[1]/section[5]/source[3]/text()
svn propset svn:externals "cocoon_2_1_x -r 608663 https://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X" .
----
Removed: /document/body/section[1]/section[8]/source/text()

svn add RELEASE-NOTES.txt
svn ci -m "release notes added" RELEASE-NOTES.txt

----
Added: /document/body/section[1]/section[8]/source/text()
svn add RELEASE-NOTES.txtsvn ci -m "release notes added" RELEASE-NOTES.txt
----
Removed: /document/body/section[1]/section[9]/source/text()

svn lock tags/RELEASE_1_2_5

----
Added: /document/body/section[1]/section[9]/source/text()
svn lock tags/RELEASE_1_2_5
----
Removed: /document/body/section[1]/section[10]/ul/li[1]/text()
Upload the tarballs. (FIXME: Instructions?)
----
Added: /document/body/section[1]/section[10]/ul/li[1]/text()
Create tarbals:
----
Added: /document/body/section[1]/section[10]/ul/li[1]/code
<code> (null)
----
Added: /document/body/section[1]/section[10]/ul/li[1]/code/text()
./build.sh dist-src
----
Added: /document/body/section[1]/section[10]/ul/li[2]
<li> (null)
----
Added: /document/body/section[1]/section[10]/ul/li[2]/text()
Sign the release archives/installers with your PGP/GPG key (see instructions below).
----
Added: /document/body/section[1]/section[10]/ul/li[3]
<li> (null)
----
Added: /document/body/section[1]/section[10]/ul/li[3]/text()[1]
Upload the release to
----
Added: /document/body/section[1]/section[10]/ul/li[3]/code
<code> (null)
----
Added: /document/body/section[1]/section[10]/ul/li[3]/code/text()
minotaur.apache.org:/x1/www/www.apache.org/dist/lenya/SOURCES
----
Added: /document/body/section[1]/section[10]/ul/li[3]/text()[3]
.
----

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Lenya - Dev

Document changed: Related Projects

2008-08-25T09:22:19Z

Document: Related Projects
URL: https://lenya.zones.apache.org/cms/docu/live/index/related-projects.html
Changed by user: Richard Frovarp (rfrovarp)

----
Removed: /comment()[1]

Copyright 1999-2004 The Apache Software Foundation

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

----
Removed: /comment()[2]
$Id: related-projects.xml 55543 2004-10-26 00:14:59Z gregor $
----
Removed: /document/body/section[2]
<section> (null)
----
Removed: /document/body/section[2]/title
<title> (null)
----
Removed: /document/body/section[2]/title/text()
Slide
----
Removed: /document/body/section[2]/p[1]
<p> (null)
----
Removed: /document/body/section[2]/p[1]/text()
The Slide project main module is a Content Management and Integration System, whichcan be seen as a low-level content management framework. Conceptually, it providesa hierarchical organization of binary content which can be stored into arbitrary,heterogenous, distributed data stores. In addition, Slide integrates security, locking,versioning, as well as many other services.
----
Removed: /document/body/section[2]/p[2]
<p> (null)
----
Removed: /document/body/section[2]/p[2]/a
<a> (null)
----
Removed: /document/body/section[2]/p[2]/a/@href
[attr] href=http://jakarta.apache.org/slide/ (null)
----
Removed: /document/body/section[2]/p[2]/a/text()
http://jakarta.apache.org/slide/
----

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Lenya - Dev

Document changed: WebDAV Servers

2008-08-25T09:21:58Z

Document: WebDAV Servers
URL: https://lenya.zones.apache.org/cms/docu/live/docu20/standardmodules/webdavmodulesection/webdavserver.html
Changed by user: Richard Frovarp (rfrovarp)

----
Removed: /comment()[1]

Copyright 1999-2004 The Apache Software Foundation

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

----
Removed: /comment()[2]
$Id: webdav.xml 55543 2004-10-26 00:14:59Z gregor $
----
Removed: /document/body/section[1]/source[1]/text()

wget http://www.webdav.org/mod_dav/mod_dav-1.0.3-1.3.6.tar.gz
cd /usr/local/src/mod_dav-1.0.3-1.3.6
./configure --with-apache=/usr/local/src/apache_1.3.24
make
make install
cd /usr/local/src/apache_1.3.24
find . -name "*dav*" -print
./configure --prefix=/usr/local/apache --activate-module=src/modules/dav/libdav.a
(./configure --prefix=/usr/local/apache --enable-module=proxy --activate-module=src/modules/dav/libdav.a)
make
su
make install
/usr/local/apache/bin/httpd -l

----
Added: /document/body/section[1]/source[1]/text()
wget http://www.webdav.org/mod_dav/mod_dav-1.0.3-1.3.6.tar.gzcd /usr/local/src/mod_dav-1.0.3-1.3.6./configure --with-apache=/usr/local/src/apache_1.3.24makemake installcd /usr/local/src/apache_1.3.24find . -name "*dav*" -print./configure --prefix=/usr/local/apache --activate-module=src/modules/dav/libdav.a(./configure --prefix=/usr/local/apache --enable-module=proxy --activate-module=src/modules/dav/libdav.a)makesumake install/usr/local/apache/bin/httpd -l
----
Removed: /document/body/section[1]/source[2]/text()

DAVLockDB /usr/local/apache/logs/DavLock
<Directory "/usr/local/build/apache/htdocs">
Dav On

----
Added: /document/body/section[1]/source[2]/text()
DAVLockDB /usr/local/apache/logs/DavLock<Directory "/usr/local/build/apache/htdocs">Dav On
----
Removed: /document/body/section[2]/source[1]/text()

./configure --prefix=/usr/local/apache2 --with-dav --enable-dav
(./configure --prefix=/usr/local/apache2 --with-dav --enable-dav --enable-proxy --enable-proxy-http)
make
make install
/usr/local/apache2/bin/httpd -l | grep dav

----
Added: /document/body/section[2]/source[1]/text()
./configure --prefix=/usr/local/apache2 --with-dav --enable-dav(./configure --prefix=/usr/local/apache2 --with-dav --enable-dav --enable-proxy --enable-proxy-http)make make install/usr/local/apache2/bin/httpd -l | grep dav
----
Removed: /document/body/section[2]/source[2]/text()

DAVLockDB /usr/local/apache2/logs/DavLock
<Directory "/usr/local/apache2/htdocs">
Dav On
</Directory>

----
Added: /document/body/section[2]/source[2]/text()
DAVLockDB /usr/local/apache2/logs/DavLock<Directory "/usr/local/apache2/htdocs">Dav On</Directory>
----
Removed: /document/body/section[3]/source/text()


<init-param>
<param-name>readonly</param-name>
<param-value>false</param-value>
</init-param>

----
Added: /document/body/section[3]/source/text()
<init-param> <param-name>readonly</param-name> <param-value>false</param-value></init-param>
----
Removed: /document/body/section[4]
<section> (null)
----
Removed: /document/body/section[4]/title
<title> (null)
----
Removed: /document/body/section[4]/title/text()
Apache Jakarta Slide
----
Removed: /document/body/section[4]/p
<p> (null)
----
Removed: /document/body/section[4]/p/text()[1]
Point your WebDAV client to
----
Removed: /document/body/section[4]/p/code[1]
<code> (null)
----
Removed: /document/body/section[4]/p/code[1]/text()
http://127.0.0.1:8080/slide/
----
Removed: /document/body/section[4]/p/text()[3]
. One needs to configure
----
Removed: /document/body/section[4]/p/code[2]
<code> (null)
----
Removed: /document/body/section[4]/p/code[2]/text()
Domain.xml
----
Removed: /document/body/section[4]/source
<source> (null)
----
Removed: /document/body/section[4]/source/@space
[attr] space=preserve (http://www.w3.org/XML/1998/namespace)
----
Removed: /document/body/section[4]/source/text()

<contentstore classname="slidestore.reference.FileContentStore">
<parameter name="rootpath">/usr/local/jakarta-tomcat-4.1.21-LE-jdk14/webapps/lenya/lenya/pubs/notimes/content/authoring/articles</parameter>
...

----
Removed: /document/body/comment()

<section>
<title>Zope</title>
<p>
<source>
<![CDATA[
...
]]>
</source>
</p>
</section>

----

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Lenya - Dev

Slide and OpenOffice

2008-08-25T09:21:43Z

The Slide project is no more. I have removed 2 of 3 references to it
from our site. The remaining one is at:
http://lenya.apache.org/docu12x/components/authoring/openoffice.html#N10079

Can anyone clean this up somehow? Are we somehow dependent on slide?

Richard

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Lenya - Dev

Document changed: WebDAV Servers

2008-08-25T09:09:48Z

Document: WebDAV Servers
URL: https://lenya.zones.apache.org/cms/docu/authoring/docu20/standardmodules/webdavmodulesection/webdavserver.html
Changed by user: Richard Frovarp (rfrovarp)

----
Removed: /comment()[1]

Copyright 1999-2004 The Apache Software Foundation

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

----
Removed: /comment()[2]
$Id: webdav.xml 55543 2004-10-26 00:14:59Z gregor $
----
Removed: /document/body/section[1]/source[1]/text()

wget http://www.webdav.org/mod_dav/mod_dav-1.0.3-1.3.6.tar.gz
cd /usr/local/src/mod_dav-1.0.3-1.3.6
./configure --with-apache=/usr/local/src/apache_1.3.24
make
make install
cd /usr/local/src/apache_1.3.24
find . -name "*dav*" -print
./configure --prefix=/usr/local/apache --activate-module=src/modules/dav/libdav.a
(./configure --prefix=/usr/local/apache --enable-module=proxy --activate-module=src/modules/dav/libdav.a)
make
su
make install
/usr/local/apache/bin/httpd -l

----
Added: /document/body/section[1]/source[1]/text()
wget http://www.webdav.org/mod_dav/mod_dav-1.0.3-1.3.6.tar.gzcd /usr/local/src/mod_dav-1.0.3-1.3.6./configure --with-apache=/usr/local/src/apache_1.3.24makemake installcd /usr/local/src/apache_1.3.24find . -name "*dav*" -print./configure --prefix=/usr/local/apache --activate-module=src/modules/dav/libdav.a(./configure --prefix=/usr/local/apache --enable-module=proxy --activate-module=src/modules/dav/libdav.a)makesumake install/usr/local/apache/bin/httpd -l
----
Removed: /document/body/section[1]/source[2]/text()

DAVLockDB /usr/local/apache/logs/DavLock
<Directory "/usr/local/build/apache/htdocs">
Dav On

----
Added: /document/body/section[1]/source[2]/text()
DAVLockDB /usr/local/apache/logs/DavLock<Directory "/usr/local/build/apache/htdocs">Dav On
----
Removed: /document/body/section[2]/source[1]/text()

./configure --prefix=/usr/local/apache2 --with-dav --enable-dav
(./configure --prefix=/usr/local/apache2 --with-dav --enable-dav --enable-proxy --enable-proxy-http)
make
make install
/usr/local/apache2/bin/httpd -l | grep dav

----
Added: /document/body/section[2]/source[1]/text()
./configure --prefix=/usr/local/apache2 --with-dav --enable-dav(./configure --prefix=/usr/local/apache2 --with-dav --enable-dav --enable-proxy --enable-proxy-http)make make install/usr/local/apache2/bin/httpd -l | grep dav
----
Removed: /document/body/section[2]/source[2]/text()

DAVLockDB /usr/local/apache2/logs/DavLock
<Directory "/usr/local/apache2/htdocs">
Dav On
</Directory>

----
Added: /document/body/section[2]/source[2]/text()
DAVLockDB /usr/local/apache2/logs/DavLock<Directory "/usr/local/apache2/htdocs">Dav On</Directory>
----
Removed: /document/body/section[3]/source/text()


<init-param>
<param-name>readonly</param-name>
<param-value>false</param-value>
</init-param>

----
Added: /document/body/section[3]/source/text()
<init-param> <param-name>readonly</param-name> <param-value>false</param-value></init-param>
----
Removed: /document/body/section[4]
<section> (null)
----
Removed: /document/body/section[4]/title
<title> (null)
----
Removed: /document/body/section[4]/title/text()
Apache Jakarta Slide
----
Removed: /document/body/section[4]/p
<p> (null)
----
Removed: /document/body/section[4]/p/text()[1]
Point your WebDAV client to
----
Removed: /document/body/section[4]/p/code[1]
<code> (null)
----
Removed: /document/body/section[4]/p/code[1]/text()
http://127.0.0.1:8080/slide/
----
Removed: /document/body/section[4]/p/text()[3]
. One needs to configure
----
Removed: /document/body/section[4]/p/code[2]
<code> (null)
----
Removed: /document/body/section[4]/p/code[2]/text()
Domain.xml
----
Removed: /document/body/section[4]/source
<source> (null)
----
Removed: /document/body/section[4]/source/@space
[attr] space=preserve (http://www.w3.org/XML/1998/namespace)
----
Removed: /document/body/section[4]/source/text()

<contentstore classname="slidestore.reference.FileContentStore">
<parameter name="rootpath">/usr/local/jakarta-tomcat-4.1.21-LE-jdk14/webapps/lenya/lenya/pubs/notimes/content/authoring/articles</parameter>
...

----
Removed: /document/body/comment()

<section>
<title>Zope</title>
<p>
<source>
<![CDATA[
...
]]>
</source>
</p>
</section>

----

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Lenya - Dev

Document changed: Related Projects

2008-08-25T09:05:37Z

Document: Related Projects
URL: https://lenya.zones.apache.org/cms/docu/authoring/index/related-projects.html
Changed by user: Richard Frovarp (rfrovarp)

----
Removed: /comment()[1]

Copyright 1999-2004 The Apache Software Foundation

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

----
Removed: /comment()[2]
$Id: related-projects.xml 55543 2004-10-26 00:14:59Z gregor $
----
Removed: /document/body/section[2]
<section> (null)
----
Removed: /document/body/section[2]/title
<title> (null)
----
Removed: /document/body/section[2]/title/text()
Slide
----
Removed: /document/body/section[2]/p[1]
<p> (null)
----
Removed: /document/body/section[2]/p[1]/text()
The Slide project main module is a Content Management and Integration System, whichcan be seen as a low-level content management framework. Conceptually, it providesa hierarchical organization of binary content which can be stored into arbitrary,heterogenous, distributed data stores. In addition, Slide integrates security, locking,versioning, as well as many other services.
----
Removed: /document/body/section[2]/p[2]
<p> (null)
----
Removed: /document/body/section[2]/p[2]/a
<a> (null)
----
Removed: /document/body/section[2]/p[2]/a/@href
[attr] href=http://jakarta.apache.org/slide/ (null)
----
Removed: /document/body/section[2]/p[2]/a/text()
http://jakarta.apache.org/slide/
----

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Lenya - Dev

Document changed: Release Management

2008-08-25T09:02:31Z

From forum: Lenya - Dev

Document changed: Download

2008-08-25T09:01:17Z

Document: Download
URL: https://lenya.zones.apache.org/cms/docu/authoring/docu20/installation20/download20.html
Changed by user: Richard Frovarp (rfrovarp)

----
Removed: /comment()[1]

Copyright 1999-2004 The Apache Software Foundation

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

----
Removed: /comment()[2]
$Id: index.xml 47563 2004-09-30 07:19:08Z michi $
----
Removed: /document/body/section[1]/ul/li[1]/text()[1]
Lenya 2.0
----
Added: /document/body/section[1]/ul/li[1]/text()[1]
Lenya 2.0.2
----
Removed: /document/body/section[1]/ul/li[2]/text()[1]
Lenya 2.0
----
Added: /document/body/section[1]/ul/li[2]/text()[1]
Lenya 2.0.2
----

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Lenya - Dev

Document changed: Open Source Content Management (Java/XML)

2008-08-25T08:59:51Z

Document: Open Source Content Management (Java/XML)
URL: https://lenya.zones.apache.org/cms/docu/authoring/index.html
Changed by user: Richard Frovarp (rfrovarp)

----
Removed: /document/body/section[1]/p[1]/text()[1]
The current stable version of Apache Lenya is 2.0. This is the recommended version for production use. You will at least need the Java 2 Platform, Standard Edition, version 1.4.2. Please follow the
----
Added: /document/body/section[1]/p[1]/text()[1]
The current stable version of Apache Lenya is 2.0.2. This is the recommended version for production use. You will at least need the Java 2 Platform, Standard Edition, version 1.4.2. Please follow the
----
Removed: /document/body/section[1]/ul/li[1]/text()[1]
Lenya 2.0
----
Added: /document/body/section[1]/ul/li[1]/text()[1]
Lenya 2.0.2
----
Removed: /document/body/section[1]/ul/li[2]/text()[1]
Lenya 2.0
----
Added: /document/body/section[1]/ul/li[2]/text()[1]
Lenya 2.0.2
----

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Lenya - Dev

Document changed: Release Management

2008-08-25T08:56:40Z

Document: Release Management
URL: https://lenya.zones.apache.org/cms/docu/authoring/docu/rm.html
Changed by user: Richard Frovarp (rfrovarp)

----
Removed: /document/body/section[1]/section[10]/ul/li[1]/text()
Upload the tarballs. (FIXME: Instructions?)
----
Added: /document/body/section[1]/section[10]/ul/li[1]/text()
Create tarbals:
----
Added: /document/body/section[1]/section[10]/ul/li[1]/code
<code> (null)
----
Added: /document/body/section[1]/section[10]/ul/li[1]/code/text()
./build.sh dist-src
----
Added: /document/body/section[1]/section[10]/ul/li[2]
<li> (null)
----
Added: /document/body/section[1]/section[10]/ul/li[2]/text()
Sign the release archives/installers with your PGP/GPG key (see instructions below).
----
Added: /document/body/section[1]/section[10]/ul/li[3]
<li> (null)
----
Added: /document/body/section[1]/section[10]/ul/li[3]/text()[1]
Upload the release to
----
Added: /document/body/section[1]/section[10]/ul/li[3]/code
<code> (null)
----
Added: /document/body/section[1]/section[10]/ul/li[3]/code/text()
minotaur.apache.org:/x1/www/www.apache.org/dist/lenya
----
Added: /document/body/section[1]/section[10]/ul/li[3]/text()[3]
.
----

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Lenya - Dev

Document changed: Release Management

2008-08-25T08:53:18Z

Document: Release Management
URL: https://lenya.zones.apache.org/cms/docu/authoring/docu/rm.html
Changed by user: Richard Frovarp (rfrovarp)

----
Removed: /comment()

Copyright 2002-2006 The Apache Software Foundation

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

----
Removed: /document/body/section[1]/section[4]/source[1]/text()
svn copy https://svn.apache.org/repos/asf/lenya/trunk\
https://svn.apache.org/repos/asf/lenya/tags/RELEASE_2_0_RC_2/\
-m "Tagging the 2.0 RC2."
----
Added: /document/body/section[1]/section[4]/source[1]/text()
svn copy https://svn.apache.org/repos/asf/lenya/trunk\ https://svn.apache.org/repos/asf/lenya/tags/RELEASE_2_0_RC_2/\ -m "Tagging the 2.0 RC2."
----
Removed: /document/body/section[1]/section[4]/source[2]/text()

svn co -r $REVISION https://svn.apache.org/repos/asf/lenya/branches/BRANCH_1_2_X
cd branches/BRANCH_1_2_X
svn copy branches/BRANCH_1_2_X tags/RELEASE_1_2_5
svn ci -m "Release 1_2_5 added" tags/RELEASE_1_2_5

----
Added: /document/body/section[1]/section[4]/source[2]/text()
svn co -r $REVISION https://svn.apache.org/repos/asf/lenya/branches/BRANCH_1_2_Xcd branches/BRANCH_1_2_Xsvn copy branches/BRANCH_1_2_X tags/RELEASE_1_2_5svn ci -m "Release 1_2_5 added" tags/RELEASE_1_2_5
----
Removed: /document/body/section[1]/section[5]/source[1]/text()

cd externals
svn propdel cocoon_2_1_x .
svn propset cocoon_2_1_10 https://svn.apache.org/repos/asf/cocoon/tags/cocoon-2.1/RELEASE_2_1_10 .

----
Added: /document/body/section[1]/section[5]/source[1]/text()
cd externalssvn propdel svn:externals .svn propset svn:externals "cocoon_2_1_10 https://svn.apache.org/repos/asf/cocoon/tags/cocoon-2.1/RELEASE_2_1_10" .
----
Removed: /document/body/section[1]/section[5]/source[2]/text()

cocoon.src.dir=externals/cocoon_2_1_10

----
Added: /document/body/section[1]/section[5]/source[2]/text()
cocoon.src.dir=externals/cocoon_2_1_10
----
Removed: /document/body/section[1]/section[5]/source[3]/text()

svn propset cocoon_2_1_x -r 608663 https://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X .

----
Added: /document/body/section[1]/section[5]/source[3]/text()
svn propset svn:externals "cocoon_2_1_x -r 608663 https://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X" .
----
Removed: /document/body/section[1]/section[8]/source/text()

svn add RELEASE-NOTES.txt
svn ci -m "release notes added" RELEASE-NOTES.txt

----
Added: /document/body/section[1]/section[8]/source/text()
svn add RELEASE-NOTES.txtsvn ci -m "release notes added" RELEASE-NOTES.txt
----
Removed: /document/body/section[1]/section[9]/source/text()

svn lock tags/RELEASE_1_2_5

----
Added: /document/body/section[1]/section[9]/source/text()
svn lock tags/RELEASE_1_2_5
----

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Lenya - Dev

Re: Shipping the docu as default publication

2008-08-25T08:15:03Z

Andreas Hartmann wrote:

> Hi Lenya devs,
>
> there seems to be a consensus that it would be a good idea to ship the
> docu publication as an example instead of the default publication.
>
> This raises the question how the content should be handled. A
> fundamental issue is that each installation would contain a fork of
> the website content. Do you consider this a problem? Could it cause
> confusion?
>
> There are several options:
>
> c) Use the content of the current default publication, i.e. share only
> the layout.
>

This one makes the most sense to me. Maybe update some of the content as
appropriate. It would seem appropriate to showcase the functionality of
the system in the default publication. Docu doesn't use the news module
for instance.

Richard

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Lenya - Dev

Shipping the docu as default publication

2008-08-25T07:49:47Z

Hi Lenya devs,

there seems to be a consensus that it would be a good idea to ship the
docu publication as an example instead of the default publication.

This raises the question how the content should be handled. A
fundamental issue is that each installation would contain a fork of the
website content. Do you consider this a problem? Could it cause confusion?

There are several options:

a) Use a separate SVN repository for the content which is shared by the
project website and the application (e.g., via svn:externals). This
would require to commit our website content (potentially cumbersome,
might be automated).

b) Don't include the full documentation content, but only a couple of
pages which aren't likely to change often, and try to keep these pages
up to date.

c) Use the content of the current default publication, i.e. share only
the layout.

d) Don't include any meaningful content at all, only some "Hello World"
pages. This would require only a minimum of maintenance.

e) …

WDYT?

-- Andreas

--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Lenya - Dev

Re: svn commit: r688711 - /lenya/trunk/src/webapp/lenya/resources/css/tabs.css

2008-08-25T06:06:26Z

Am 25.08.2008 um 14:55 schrieb andreas@...:
>
>
> #contentblock1 .lenya-box {
> - display: relative;
> + position: relative;
> }

ugh! - nice catch ;-) may have caused all kinds of funny things.

Jürgen

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Lenya - Dev

DO NOT REPLY [Bug 45401] Authoring-GUI css bugs in Firefox 3

2008-08-25T05:59:53Z

https://issues.apache.org/bugzilla/show_bug.cgi?id=45401

--- Comment #1 from Andreas Hartmann <andreas@...> 2008-08-25 05:59:53 PST ---
(In reply to comment #0)

> - Font size of site tree widget: In some cases the font size of the entries in
> the site tree widget is not 11px (as written in css) but much bigger. This
> occurs randomly...

I think I have fixed this one, please test - TIA!

> Observation regarding CSS: In the authoring area the page.css has an influence
> on the looks of the table, wich IMO is bad. The rules in menu.css should
> describe all commonly used properties for the xhtml elements used in the tabs -
> even if the default is fine - in order not to be easily overwritable by a rule
> in a websites css.

That sounds reasonable, but wouldn't the CSS become very large?

--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Lenya - Dev

Re: Lenya redesign considerations

2008-08-25T05:49:08Z

Hi Thorsten

Am 25.08.2008 um 14:14 schrieb Thorsten Scherler:

>>
>>
>> IIUC a price for the winner would have to be sponsored by a company;
>> as Thorsten explained in Freiburg.
>> That would be nice of course...
>
> I personally would be against a price award because the ASF is about
> volunteer work and as you correctly pointed out this money would
> need to
> come from a company.

Jo - this is a sensistive point
- maybe it's more consequent to not price reward one type of work and
other not...

>
>
>>> * Besides the looks of the GUI, what aspects of the user interface
>>> with respect to usability should be considered while redesigning
>>> (use of ajax, changes in the workflow process etc.)? The design
>>> contest might be restricted to the current screens but could
>>> include a section for suggestions about changes.
>>
>> I think we should limit the contest to the web page design at the
>> moment.
>
> Mmh - still hesitating here...
>
> Limiting the process to the default/docu pub will simplify things a
> lot.
> We'd have to be careful though that «lenya» as a whole gets it's
> unique design for both authoring and docu publication.

+1; I was a bit unclear with my latest writing.
I'm all for dropping the default pub and replacing it with the docu pub.

What I meant is that the authoring gui and the docu=default pub should
share a common lenya look.

Jürgen

null-oder-eins GmbH Zürich
web & graphic design

www.null-oder-eins.ch

ragaller@...
Skype: callto://ragaller

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Lenya - Dev

Re: Lenya redesign considerations

2008-08-25T05:14:51Z

On Mon, 2008-08-25 at 13:48 +0200, Jürgen Ragaller wrote:

> Am 25.08.2008 um 12:22 schrieb Andreas Hartmann:
>
> [...]
>
> > We certainly have to try to give the contest as much visibility as
> > possible (social networks, forums, blogs, …). Should we offer some
> > kind of reward or credits, e.g. mentioning the designer on the
> > website etc.?
>
> We'd have to take care to follow the apache guidelines - might have to
> involve a step where the participants agree to follow the apache
> guidelines. Shurely the designer should be listed in our credits
> section - as is the case now already.

The contribution has to be granted to the ASF and cannot have any other
copyright then the one from the ASF. As soon the contribution will be
committed by one of us we need to point out the name and express our
thanks in the commit message (very important).

The listing of the other contribution I personally do not like very much
since it points out SOME people but leave OTHER out.

>
> IIUC a price for the winner would have to be sponsored by a company;
> as Thorsten explained in Freiburg.
> That would be nice of course...

I personally would be against a price award because the ASF is about
volunteer work and as you correctly pointed out this money would need to
come from a company.

>
>
> >> * Besides the looks of the GUI, what aspects of the user interface
> >> with respect to usability should be considered while redesigning
> >> (use of ajax, changes in the workflow process etc.)? The design
> >> contest might be restricted to the current screens but could
> >> include a section for suggestions about changes.
> >
> > I think we should limit the contest to the web page design at the
> > moment.
>
> Mmh - still hesitating here...
>
> Limiting the process to the default/docu pub will simplify things a lot.
> We'd have to be careful though that «lenya» as a whole gets it's
> unique design for both authoring and docu publication.

Actually as I pointed out in the meeting we should drop the default pub
in aid of the docu pub. This makes as well sure that we have a unique
CI.

salu2

>
>
> Jürgen
>
>
> null-oder-eins GmbH Zürich
> web & graphic design
>
> www.null-oder-eins.ch
>
> ragaller@...
> Skype: callto://ragaller
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

--
Thorsten Scherler thorsten.at.apache.org
Open Source Java consulting, training and solutions

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Lenya - Dev

Re: Lenya redesign considerations

2008-08-25T04:48:52Z

Am 25.08.2008 um 12:22 schrieb Andreas Hartmann:

[...]

> We certainly have to try to give the contest as much visibility as
> possible (social networks, forums, blogs, …). Should we offer some
> kind of reward or credits, e.g. mentioning the designer on the
> website etc.?

We'd have to take care to follow the apache guidelines - might have to
involve a step where the participants agree to follow the apache
guidelines. Shurely the designer should be listed in our credits
section - as is the case now already.

IIUC a price for the winner would have to be sponsored by a company;
as Thorsten explained in Freiburg.
That would be nice of course...

>> * Besides the looks of the GUI, what aspects of the user interface
>> with respect to usability should be considered while redesigning
>> (use of ajax, changes in the workflow process etc.)? The design
>> contest might be restricted to the current screens but could
>> include a section for suggestions about changes.
>
> I think we should limit the contest to the web page design at the
> moment.

Mmh - still hesitating here...

Limiting the process to the default/docu pub will simplify things a lot.
We'd have to be careful though that «lenya» as a whole gets it's
unique design for both authoring and docu publication.

Jürgen

null-oder-eins GmbH Zürich
web & graphic design

www.null-oder-eins.ch

ragaller@...
Skype: callto://ragaller

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Lenya - Dev

Re: Lenya redesign considerations

2008-08-25T04:36:37Z

Am 25.08.2008 um 12:28 schrieb Andreas Hartmann:

> Jürgen Ragaller schrieb:
>
> […]
>
>> If we'd like to attract designers we should provide a way to start
>> with the design without any programming or templating knowledge
>> (Photoshop, Fireworks templates).
>
> Is it really necessary to provide such templates? I have to admit
> that mentioning Photoshop and Fireworks templates still causes
> associations with fixed-width pages and image backgrounds …

With Photoshop / Fireworks templates folks with no knowledge in web
techniques can participate.

When I start a new design it firewoks first.

If the page layout is meant to be fixed width or scaleable will have
to go in a little readme - sometimes it might be obvious by looking at
the design..

[...]

>
> IMO the major challenge is to provide a clean, well-designed XHTML.
> The infrastructure isn't such a problem - we can probably just use
> the Zones server.

+1

> I guess it would be sufficient to let people send their CSS and
> image files to the list, it's not much work to put them on the
> server and add the link tags to the page.

+1; no need for sofisticated machinery... The layouts coming from the
template folks could be uploaded as images to the same publication.

Thanks for the feedback, Andreas!

Jürgen

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Lenya - Dev