[EMAIL PROTECTED] wrote:
Um, I already made search a usecase. That was necessary to maintain
visitor language information.
true, but this refers to the new-style usecases in 1.4.
While the crawler is good if you want to index non-Lenya websites, it
is poor design for Lenya. It feels like someone got lazy and used the
DefaultIndexer for HTML rather than use the ConfigurableIndexer for
true integration with Lenya, or maybe there are historical reasons
such as the ConfigurableIndexer not being available when Lucene was
first integrated. I expect the website crawler to disappear, rather
than be a priority improvement.
i added your comment to
http://issues.apache.org/bugzilla/show_bug.cgi?id=33702
My project is moving into production. Incremental indexing and
integration with the CMS GUI are priorities. I want the index to be
updated x minutes after updates are completed, delaying if another
save happens before it starts. The indexer needs to be started from a
scheduler. I need to integrate with the scheduler, and from the
number of issues about the scheduler in the mailing lists, may need to
revise it.
agreed.
---
I heartily agree the editors should be improved. I have only used
Kupu, and not very much, but some improvements:
- Adding graphics (assets) should be possible on the content editing
screen. It takes 4 clicks to open the "Add Asset" chooser, if a user
can even find it. Then it takes 4 clicks to get back to editing the
content where the asset is needed.
- Control over TABLEs should also be improved. Setting BORDER="0"
required editing source, and users cannot be expected to know HTML.
These may be Kupu issues, but they greatly affect the ease-of-use for Lenya.
can you file bugs for these?
The whole CMS GUI needs a usability review. The "Site" and
"Authoring" tabs may be combined. The Title and Subject should be
easily changed while viewing the content, not 2 clicks away.
and for these too?
All configuration files should be editable through the GUI. Implement
security so content editors cannot ruin the site structure, but add
the ability to edit CSS, XSLTs, and maybe even XMAPs. Try to remove
reasons anyone would need access to the file system.
agreed, see also http://issues.apache.org/bugzilla/show_bug.cgi?id=28924
you have many good ideas, now we only need to get them into bugzilla so
that they are not lost ;)
thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
