It
needs to recognize and specify how users can utilize portlets in both a
server-centric manner and a client-centric manner.
I think this is a good statement. A portal and especially a portal spec
should support both technologies. The developer can than decide which
technology he/she uses.
I agr
Raphael,
I know you're unconvinced by any of the client-side technology
arguments. But I will say that you should consider that the history of
java is replete with examples of users rejecting "one-size fits all"
solutions. They were many great "one size fits all" technologies that
users did not
Raphael,
I know you're unconvinced by any of the client-side technology
arguments. But I will say that you should consider that the history of
java is replete with examples of users rejecting "one-size fits all"
solutions. They were many great "one size fits all" technologies that
users did not
>What do you mean exactly by "usability not being taken into account" ?
>It's not a very useful comment without further explanation of where you
>find usability lacking.
maybe i should have used the word "accessibility", in fact. (using html4
being a lack in this case) iframes lack accessibility
De : Helmut Tammen [mailto:[EMAIL PROTECTED]
>
> Sorry,
>
> I´ve forgot to say that this version of the PDK is only
> running with IE,
> but the release 6.0 of SAP Enterprise Portal should be browser
> independent (I´ve heard). Unfortunetly there is no PDK available yet.
>
> I didn´t want you to s
Sorry,
I´ve forgot to say that this version of the PDK is only running with IE,
but the release 6.0 of SAP Enterprise Portal should be browser
independent (I´ve heard). Unfortunetly there is no PDK available yet.
I didn´t want you to switch from Jetspeed to SAP EP neither did I want
to leave t
De : Gregory Joseph [mailto:[EMAIL PROTECTED]
>
> Raphaël Luta wrote:
> >I just registered to check it out and, of course, it simply doesn't
> >recognize my Mozilla Firebird as a supported client so I get a very
> >ugly site. Thanks for reminding me why I so dislike client-side
> >technologies :)
Raphaël Luta wrote:
>I just registered to check it out and, of course, it simply doesn't
>recognize my Mozilla Firebird as a supported client so I get a very
>ugly site.
>Thanks for reminding me why I so dislike client-side technologies :)
Same with Mozilla1.4 (even without taking the pain to regi
Hi Raphael,
--- "Luta, Raphael (VUN)" <[EMAIL PROTECTED]> wrote:
>
> If I understand correctly your request in regards to the
> JSR 168, you would like to be able to develop a client based portal
> that leverages the portlet components developped against the JSR168
> API. Is that correct ?
>
>
De : Gerry Reno [mailto:[EMAIL PROTECTED]
>
> Hi Raphael,
>
> --- "Luta, Raphael (VUN)" <[EMAIL PROTECTED]> wrote:
> >
> > If I understand correctly your request in regards to the
> > JSR 168, you would like to be able to develop a client based portal
> > that leverages the portlet components dev
> Not exactly, the main user interface window would have in this model
> a single DOM with no IFRAME (ie true content aggregation), the hidden
> iFrame being used as a backround content cache to be used by the main
> window to load content.
And act as the physical requestor back to the server. Bu
11 matches
Mail list logo
