You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Alex Romayev <ro...@yahoo.com> on 2003/07/02 16:16:40 UTC
The new portal framework: questions and thoughts
Hi,
I've posted this on the users list a few days ago, but
got no replies, so I'm re-posing it here, especially
hoping to get Carsten's attention.
I have been using portal-fw for a year now. Overall,
I�m very happy with it. It is well designed and
contains all of the critical features you need to
build a portal. It�s been lacking some of the nice to
have's, but I�d rather have something to work with now
and wait for the new features to come out. So I�ve
been looking forward to the enhancements.
I have a few questions/wish list items (directed at
Carsten):
1. Can you share with us the drivers for creating the
new portal?
- Why are you not extending the current portal-fw?
- Is it going to be compatible with portal-fw?
- What are the differences/new features in the new
portal?
2. Layout
I've noticed that you are changing the layout
configuration, which is definitely a welcome change.
The column layout worked fine, but was even behind
WebLogic/WebSpere portals, which at least allow
spanning columns. However, I find even the spanning
design very limiting.
I prefer to use CSS2 and take advantage of DIV tags,
so that the coplets can be placed based on the
absolute and relative positioning. For example, there
is a place on my site where I would like the coplets
to overlap, which is currently impossible.
In general, I'd like to be able to leave "hooks" for
the CSS classes. For example, I would like to be able
to break down a page into areas. When a coplet is
"DIVed" in such area, it is "styled" according to the
area's rules. For example, all coplets in the
"related-links" area have a light-gray background and
"Helvetica" font (defined in a CSS stylesheet, but
assigned by the portal config). A single coplet,
however, should be able to override the style.
3. Application configuration
I am probably "misusing" the portal, but in any case,
this is what I do. I like to treat each page on the
site as a portal page. Why? Well, I like to be very
user-friendly, so that rather than letting the users
customize the main page only, I want the to be able to
do this on every page. Also, I�d like to have
"site-editor" coplets on every page, which allow
editing page content. Clearly, these coplets should
only be available to the site editors.
So, here is my problem. For a page to be a "portal"
page, it needs to have an application configuration in
the sitemap. So if I have 200 pages, I need to have
200 page configurations in my sitemap, which is
unwieldy. It would be great to be able to do one of
the two:
- Make application configuration work with patterns,
just like the rest of the sitemap
- Allow this to be externalized from the sitemap into
another configuration file
By the way, at the moment adding a new application
configuration requires to bounce Tomcat, which is bad
(every time I add a page, I have to restart!)
Thoughts?
Cheers,
-Alex
Re: Please remove me from maillist!
Posted by Steven Noels <st...@outerthought.org>.
On 3/07/2003 3:32 steeven wrote:
> Please remove me from maillist!
>
> Can NOT unsubscribe the list :(
Here you go (hopefully). If not, please get back to us. Being a bit
friendlier would be nice, though, since there's a good chance you've
subscribed yourself.
</Steven>
--
Steven Noels http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at http://blogs.cocoondev.org/stevenn/
stevenn at outerthought.org stevenn at apache.org
Please remove me from maillist!
Posted by steeven <st...@dealeasy.com>.
Please remove me from maillist!
Can NOT unsubscribe the list :(
RE: The new portal framework: questions and thoughts
Posted by Alex Romayev <ro...@yahoo.com>.
Thanks Carsten, I'll look forward to the rest ;)
--- Carsten Ziegeler <cz...@s-und-n.de> wrote:
> Alex Romayev wrote:
> >
> > I've posted this on the users list a few days ago,
> but
> > got no replies, so I'm re-posing it here,
> especially
> > hoping to get Carsten's attention.
> :) Must have missed it...
>
> > 1. Can you share with us the drivers for creating
> the
> > new portal?
> Yes, of course - it's publically. The initial
> version has been
> a joined development effort by BASF IT-Services and
> s&n.
> We used input from various users and customers.
> When we got a running (but by far not completed
> version)
> we donated it to Cocoon, now everyone can help
> in making it better.
> Currently, BASF IT-Services and we will continue the
> development in Cocoon in the next weeks and months;
> but we hope that others step in.
>
> >
> > - Why are you not extending the current
> portal-fw?
> The design of the old portal, well, is good for the
> tasks it
> does, but is not that extensible. So designing a new
> version
> from scratch is a better/cleaner solution.
>
> > - Is it going to be compatible with portal-fw?
> Currently, not fully. The new portal will have the
> same features,
> but the XML describing a portal looks different.
> However
> by using a stylesheet it's possible to maintain
> compatibility.
>
> > - What are the differences/new features in the
> new
> > portal?
> - Flexible Publishing Engine
> - Component oriented architecture
> - event handling
> - pluggable
>
> >
> > 2. Layout
> >
> > I've noticed that you are changing the layout
> > configuration, which is definitely a welcome
> change.
> > The column layout worked fine, but was even behind
> > WebLogic/WebSpere portals, which at least allow
> > spanning columns. However, I find even the
> spanning
> > design very limiting.
> It's only a demo and can be improved/customized :)
>
> That's for today...
>
> Carsten
>
>
RE: The new portal framework: questions and thoughts
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Alex Romayev wrote:
>
> I've posted this on the users list a few days ago, but
> got no replies, so I'm re-posing it here, especially
> hoping to get Carsten's attention.
:) Must have missed it...
> 1. Can you share with us the drivers for creating the
> new portal?
Yes, of course - it's publically. The initial version has been
a joined development effort by BASF IT-Services and s&n.
We used input from various users and customers.
When we got a running (but by far not completed version)
we donated it to Cocoon, now everyone can help
in making it better.
Currently, BASF IT-Services and we will continue the
development in Cocoon in the next weeks and months;
but we hope that others step in.
>
> - Why are you not extending the current portal-fw?
The design of the old portal, well, is good for the tasks it
does, but is not that extensible. So designing a new version
from scratch is a better/cleaner solution.
> - Is it going to be compatible with portal-fw?
Currently, not fully. The new portal will have the same features,
but the XML describing a portal looks different. However
by using a stylesheet it's possible to maintain compatibility.
> - What are the differences/new features in the new
> portal?
- Flexible Publishing Engine
- Component oriented architecture
- event handling
- pluggable
>
> 2. Layout
>
> I've noticed that you are changing the layout
> configuration, which is definitely a welcome change.
> The column layout worked fine, but was even behind
> WebLogic/WebSpere portals, which at least allow
> spanning columns. However, I find even the spanning
> design very limiting.
It's only a demo and can be improved/customized :)
That's for today...
Carsten