on 2/2/01 4:50 AM, "Thomas F. Boehme" [EMAIL PROTECTED] wrote:
Folks,
a few minutes ago we (ie. Ingo) posted the javadocs for Portlet API 2. It is
in /proposals department in CVS. All those interested in a common standard
for portlets (hopefully even beyond Jetspeed implementations) are
on 2/2/01 1:16 PM, "[EMAIL PROTECTED]" [EMAIL PROTECTED] wrote:
the intent of this Portlet API is not only to be used in JetSpeed, we
envision this API to evolve into a standard.
+1
I'm an idiot.
-jon
--
--
To subscribe:
Raphael Luta wrote:
[EMAIL PROTECTED] wrote:
I volunteer to put together a Portlet API Requirements
List that we can put on the web site. Please post your
requirements to the JetSpeed list with the topic
"Portlet API Requirements", and I'll include them in the
document.
I'm
: 56.2.2040865
-Mensaje original-
De: Lerenc, Vedran [SMTP:[EMAIL PROTECTED]]
Enviado el: martes 7 de noviembre de 2000 7:41
Para: 'JetSpeed'
Asunto: RE: Portlet API
Hi,
I want to add some more words to the topic of incorporating documents from
the web into the portal. I am working
Mike,
This "philosophical thought train" is already on the go. Santiago's SAXlet
ideas go into the very same direction.
At the current stage, I am -1 on the idea, but that's mainly for lack for
examples. The nice thing about Santiago's approach is the fact that he still
wants to be open for the
[EMAIL PROTECTED] wrote:
Raphael Luta wrote:
[EMAIL PROTECTED] wrote:
I'm not sure what exactly you mean - wouldn't different forms in
different
portlets have different targets to which the parameters would get
posted ?
I'm not sure it's actually possible but if you have
[EMAIL PROTECTED] wrote:
snip a lot of stuff
a customization descriptor will be very useful. An example might be an
e-mail
portlet:
CUSTOMIZATION DESCRIPTOR
TITLEE-mail Portlet Settings/TITLE
ATTRIBUTE
NAMEMail Server Address/NAME
TYPEText/TYPE
David Sean Taylor wrote:
Im looking over your configuration design and it reminds of something I've
been meaning to research: Prowler.
Is anyone familiar with it? http://www.infozone-group.org/projects_main.html
+---+
|
-Original Message-
From: Raphael Luta [mailto:[EMAIL PROTECTED]]
Sent: Dienstag, 7. November 2000 06:20
To: JetSpeed
Subject: Re: Portlet API
[EMAIL PROTECTED] wrote:
.
For handling the second scenario, complicated mechanisms
for rewriting,
handling of cookies
"Lerenc, Vedran" wrote:
Of course things are much more complicated if we are talking about
portlets that include legacy pages and the targets are not portlets
that follow a certain programming model but arbitrary web
applications.
I guess the mails posted by Marcus Schwarz and Vedran
}
and you can use hello.append('alert(6)') which looks nicer. make sure hello exists...
/m
"Schwarz, Marcus" wrote:
-Original Message-
From: Raphael Luta [mailto:[EMAIL PROTECTED]]
Sent: Samstag, 4. November 2000 13:15
To: JetSpeed
Subj
s from
pre-existing sources, and I always need to edit it, rewrite urls etc, before
incorporating it in the portal.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Schwarz, Marcus
Sent: Sunday, November 05, 2000 12:21 PM
To: 'JetSpeed'
Subject: RE: P
Hi,
I want to add some more words to the topic of incorporating documents from
the web into the portal. I am working with Marcus and refereing to David
Sean Taylor's answer on Marcus' posting concerning an "advanced file
server".
Your discussion is very relevant to some of the problems I am
Raphael Luta wrote:
[EMAIL PROTECTED] wrote:
- the portal can't easily guarantee that the aggregated result will
display
correctly on a given device because the markup generated by one
portlet
may
alter the markup of the whole page.
Yes, to make it work, the portlets
-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED]
Sent: Monday, November 06, 2000 1:48 PM
To: JetSpeed
Subject: Re: Portlet API
Note: The most interesting part of this mail is at the end.
Micheal Rimov wrote:
snip snip
public void service( PortletRequest
?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Lerenc, Vedran
Sent: Monday, November 06, 2000 1:44 PM
To: 'JetSpeed'
Subject: RE: Portlet API
Hi,
I want to add some more words to the topic of incorporating documents from
the web into the portal. I am
Of course things are much more complicated if we are talking about
portlets that include legacy pages and the targets are not portlets
that follow a certain programming model but arbitrary web
applications.
I guess the mails posted by Marcus Schwarz and Vedran Lerenc
give a good
on in the past) -
right now our project doesn't give me much time, so I just can contribute
problems and our part-solutions (see also RE: Portlet API - Portlet
communication and portlet chaining/pipelining).
--
--
Please read the FAQ! http
Raphael Luta wrote:
[EMAIL PROTECTED] wrote:
- the portal can't easily guarantee that the aggregated result will
display
correctly on a given device because the markup generated by one portlet
may
alter the markup of the whole page.
Yes, to make it work, the portlets
-Original Message-
From: Raphael Luta [mailto:[EMAIL PROTECTED]]
Sent: Samstag, 4. November 2000 13:15
To: JetSpeed
Subject: Re: Portlet API
- this may create problems with form handling because the
portal *needs*
to
make sure there are no variable name
Raphael Luta wrote:
- the portal can't easily guarantee that the aggregated result will
display
correctly on a given device because the markup generated by one portlet
may
alter the markup of the whole page.
Yes, to make it work, the portlets have to follow some guidelines regarding
"Schwarz, Marcus" wrote:
- Locator provides methods to determine the current
location of a user's
device, e.g. longitude/latitude, country, state, city, ZIP code.
I don't think hooks should exist in a generic portlet API to
cater for this.
Too biased towards mobile devices
etSpeed" [EMAIL PROTECTED]
To: JetSpeed [EMAIL PROTECTED]
cc:
Subject: Re: Portlet API
[EMAIL PROTECTED] wrote:
(Seems this mail did not get delivered, I hope you don't receive it
twice)
It's good to see such a positive reaction on my first note about the
n
-Original Message-
From: Raphael Luta [mailto:[EMAIL PROTECTED]]
Sent: Freitag, 3. November 2000 00:53
To: JetSpeed
Subject: Re: Portlet API
"Schwarz, Marcus" wrote:
- Locator provides methods to determine the current
location of a user's
d
(Seems this mail did not get delivered, I hope you don't receive it twice)
It's good to see such a positive reaction on my first note about the
need for a standard Portlet API and that such a live discussion started.
I guess we should go into more detail now. The figure below shows a
portal
[EMAIL PROTECTED] wrote:
(Seems this mail did not get delivered, I hope you don't receive it twice)
It's good to see such a positive reaction on my first note about the
need for a standard Portlet API and that such a live discussion started.
Great, I don't have to write this anymore...
[EMAIL PROTECTED] wrote:
Same here since we would not be working on top of Turbine, but be using
Cocoon2 instead. I'm not sure whether a application neutral Portal API would
be a feasible thing, at least a common feature list should be possible.
I think an application neutral Portal API
Raphael Luta wrote:
I think an application neutral Portal API is possible but
would certainly leave
a lot of responsabilities on the portlet developers,
especially if we aim for
multi-device access. More on this when I have finished my
Jetspeed 2 paper...
Can't wait until then ;-)
I
[EMAIL PROTECTED] wrote:
Raphael Luta wrote:
I think an application neutral Portal API is possible but
would certainly leave
a lot of responsabilities on the portlet developers,
especially if we aim for
multi-device access. More on this when I have finished my
Jetspeed 2 paper...
Raphael Luta wrote:
I would think that a device negotiation layer as you could
call Cocoon would
be extremely helpful working towards different devices - it
does already
quite a lot of things in terms of user agent detection and the like.
The browser detection of Cocoon
Raphael Luta wrote:
My point is that you actually don't have to use all the
features offered
by a browser, just stick to standard stuff. Used any blink
tags lately ?
:)
Blink? Huh? :-)
You're right but unfortunately sometimes customers want all the latest stuff
possible with IE, and
31 matches
Mail list logo
