Scott, My apologies for coming at this a little strongly. I didn't intend to offend anyone. My comments about the usability of the IFramePortlet were actually intended to show that the IFramePortlet can be made perfectly usable if we change the view interaction model that's all.
Gerry --- "Weaver, Scott" <[EMAIL PROTECTED]> wrote: > I have to admit, Gerry, your initial approach came off quite, um, > combative. Telling us that things in the portal are virtually > useless is NOT the way to become a constructive member of an open > source community. I have fairly thick skin as do most of the > developers here (it's a requirement to become a committer don't ya > know ;), so I wasn't to put off. > > > "You b*tch, you get the job" > - Jon Scott Stevens > > The thing you will need to remember, as with any proposal, is that > you be willing to take full responsibility for it. This means expect > to dig long and hard into the guts of Jetspeed, you will have to be > willing to learn how it works. > > The more people working on Jetspeed, the better it becomes. If you > show genuine interest in making Jetspeed a better project, you will > get more help than you know what to do with, complain and we will all > turn a deaf ear to your criticisms. > > > That's just the way it is, > *===================================* > * Scott T Weaver * > * Jakarta Jetspeed Portal Project * > * [EMAIL PROTECTED] * > *===================================* > > > > > -----Original Message----- > > From: Aurelien Pernoud [mailto:[EMAIL PROTECTED] > > Sent: Friday, July 18, 2003 10:30 AM > > To: 'Jetspeed Users List' > > Subject: RE: JSR-168 Comments > > > > Gerry Reno a ecrit : > > > > > The spec is dictating a server-side UI > > > > > > This is, I think, the exact kind of mail that will make jetspeed > dev not > > read any one single more mail from you. At least that's what I > would do. > > > > I'm sorry, but devs and specs have taken time, you just come by > there and > > say "Hey guys, jetspeed su*, portlet api su*, listen to me". > > > > There are many ways to change the current jetspeed (1.4-cvs) to be > able to > > do what you'd like (user side actions for portlets) and still keep > the old > > way that many users want (changing the rendering while maximized is > simply > > great, sorry). It requires time too, you could be the one to make > the > > changes necessary (yes, that's where open-source begins) and then > provide > > a > > patch. > > Currently the control actions is a little too hard-coded in > jetspeed, but > > things change you know. The only thing you have to provide to get > your > > patch > > applied is : > > 1. Interest of the patch > > 2. Backward Compatiblity (I don't want to see my work lost because > someone > > jsut decided to change the behavior of maximize, minimize... and > I'm not > > alone in this case) > > > > Devs are watching for good ideas, patchs, whatever, when time > allows it. > > But > > just don't come and yell, you won't be listen to. > > > > Aurelien > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > For additional commands, e-mail: > [EMAIL PROTECTED] > __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
