[Wonder-disc] new scriptaculous + rico

[Mike Schrag]

It also looks like there might be some problems with rico and the new
prototype. I get strange invalid browser requests on any page that
uses rico and prototype together (it would appear that rico hasn't
been updated to work with prototype > 1.4). The major impact here is
rounded corners and accordion on a page with ajax updates.

ms

[Timo Hoepfner]

Post by Mike Schrag
It also looks like there might be some problems with rico and the new
prototype. I get strange invalid browser requests on any page that
uses rico and prototype together (it would appear that rico hasn't
been updated to work with prototype > 1.4). The major impact here is
rounded corners and accordion on a page with ajax updates.

Ok, took some time to reproduce that one. Yes, you're right. Looks
like the prototype from scriptacolous 1.6.5 also breaks this one. The
one from SVN doesn't fix it. So we should revert to 1.6.4.

Timo

[Timo Hoepfner]

Or switch to a prototype-based implementation of those classes ...
We only use rico for round corners and accordian (neither probably
all that popular, actually).

Just started using the accordion, but I'm not too happy with it. What
I really could use is some modernized wocollapsiblecomponentcontent.
I think Cornelius built one a while ago...

The rounded corners look cool, but they didn't work well the first
time i tried to use them in a real scenario.

Talking about dropping some stuff. There is an unused Prototype
Window script (http://prototype-window.xilinus.com) in the WS-
Resources of the Ajax framework. So we should either build a
component for it or drop it. Locally I have a half-baked component
for it, but the problem is the CSS for the themes. If added via
AjaxUtils.addResourceInHead, the images referenced therein won't be
found, at least not when using rapid turnaround or direct connect.

Timo

[Cornelius Jaeger]

Hi Timo

Post by Timo Hoepfner
Just started using the accordion, but I'm not too happy with it. What
I really could use is some modernized wocollapsiblecomponentcontent.
I think Cornelius built one a while ago...

it's not an accordion, ie no animation, but that could probably be
added pretty easily using Effect, etc.
have a look and let me know what you think. just replace VF with ERX,
since i'm working in another namespace etc.
plus you need two images for open and closed state.
and you need to replace the VFCopyImage with a WOImage. Sorry for the
inconvenience, if it's too much trouble i have time next week to make
it ERX conform.

Post by Timo Hoepfner
The rounded corners look cool, but they didn't work well the first
time i tried to use them in a real scenario.

ditto.

Post by Timo Hoepfner
Talking about dropping some stuff. There is an unused Prototype
Window script (http://prototype-window.xilinus.com) in the WS-
Resources of the Ajax framework. So we should either build a
component for it or drop it. Locally I have a half-baked component
for it, but the problem is the CSS for the themes. If added via
AjaxUtils.addResourceInHead, the images referenced therein won't be
found, at least not when using rapid turnaround or direct connect.

had the same problem, i was wondering whether it might not be worth
just rolling our own. the code didn't look so tough and the prototype
window library is actually pretty cool. the snazz other people add is
seldom crossbrowser compatible and the phenomenal thing about the
components here is that they get bashed on so many platforms that
they are the highest quality i've seen to date.
i even had trouble with the yui library.
just my 2cents.

on a related note, mike mentioned a AjaxD2W look, or some such, is
anyone here working on that, is there interest or time to work on
this? that would be a real show stopper.

many regards

Cornelius

[Mike Schrag]

Post by Timo Hoepfner
Just started using the accordion, but I'm not too happy with it. What
I really could use is some modernized wocollapsiblecomponentcontent.
I think Cornelius built one a while ago...

I agree, I didn't like rico accordion either. It was an early
exercise in wrapping things in the framework. It's not even Ajax,
anyway, so if it went away, it wouldn't hurt my feelings.

Anyone opposed to AjaxRoundEffect or AjaxAccordion (and friends)
going away, or at least being replaced by more useful implementations?

Post by Timo Hoepfner
The rounded corners look cool, but they didn't work well the first
time i tried to use them in a real scenario.

Yeah, rico's implementation is kind of strange. If you put more than
one on a page it will double-apply, etc.

Post by Timo Hoepfner
Talking about dropping some stuff. There is an unused Prototype
Window script (http://prototype-window.xilinus.com) in the WS-
Resources of the Ajax framework. So we should either build a
component for it or drop it. Locally I have a half-baked component
for it, but the problem is the CSS for the themes. If added via
AjaxUtils.addResourceInHead, the images referenced therein won't be
found, at least not when using rapid turnaround or direct connect.

If it's not used, I'm fine getting rid of it. I don't think we
should be responsible for carrying around .js files just in case
someone might want to wrap them in their own code.

Just so you know, for the CSS, you can use Anjo's new ERXStyleSheet
component (w/ caching) and create a .wo of the stylesheet. It turns
into a direct action behind the scenes so browsers can cache it, but
it looks like a regular component.

ms

[Clark Mueller]

Post by Mike Schrag

Post by Timo Hoepfner
Just started using the accordion, but I'm not too happy with it. What
I really could use is some modernized wocollapsiblecomponentcontent.
I think Cornelius built one a while ago...

I agree, I didn't like rico accordion either. It was an early
exercise in wrapping things in the framework. It's not even Ajax,
anyway, so if it went away, it wouldn't hurt my feelings.
Anyone opposed to AjaxRoundEffect or AjaxAccordion (and friends)
going away, or at least being replaced by more useful implementations?

I find AjaxAccordion to be handy in providing a quasi "wizard" style
of interface. But that having been said, I can't say that I've
actually looked around too much at the alternatives, and I certainly
wouldn't argue against a more useful implementation. I agree with
seeing an "AjaxCollapsibleComponentContent" type of widget. I also
would really like an Ajax tab component, and have it on my wish/to-do
list, but I haven't had any time to sit down and try and figure out
how to tackle a new Ajax component myself (if you have any pointers
on getting started with building components that will be consistent
with how you've been building them, Mike, I would most definitely
like to start looking at maybe building some).

Post by Mike Schrag

Post by Timo Hoepfner
The rounded corners look cool, but they didn't work well the first
time i tried to use them in a real scenario.

Yeah, rico's implementation is kind of strange. If you put more than
one on a page it will double-apply, etc.

Agreed.

Post by Mike Schrag

Post by Timo Hoepfner
Talking about dropping some stuff. There is an unused Prototype
Window script (http://prototype-window.xilinus.com) in the WS-
Resources of the Ajax framework. So we should either build a
component for it or drop it. Locally I have a half-baked component
for it, but the problem is the CSS for the themes. If added via
AjaxUtils.addResourceInHead, the images referenced therein won't be
found, at least not when using rapid turnaround or direct connect.

If it's not used, I'm fine getting rid of it. I don't think we
should be responsible for carrying around .js files just in case
someone might want to wrap them in their own code.
Just so you know, for the CSS, you can use Anjo's new ERXStyleSheet
component (w/ caching) and create a .wo of the stylesheet. It turns
into a direct action behind the scenes so browsers can cache it, but
it looks like a regular component.

This is the first I've seen of it, but this is another one that I
wouldn't mind trying to build a decent reusable component for. I'm
not a big fan of the existing AjaxModalDialog.

Clark

[Mike Schrag]

Post by Clark Mueller
I find AjaxAccordion to be handy in providing a quasi "wizard" style
of interface. But that having been said, I can't say that I've
actually looked around too much at the alternatives, and I certainly
wouldn't argue against a more useful implementation. I agree with
seeing an "AjaxCollapsibleComponentContent" type of widget. I also
would really like an Ajax tab component, and have it on my wish/to-do
list, but I haven't had any time to sit down and try and figure out
how to tackle a new Ajax component myself (if you have any pointers
on getting started with building components that will be consistent
with how you've been building them, Mike, I would most definitely
like to start looking at maybe building some).

I'd be interested to find a prototype/scriptaculous-based accordion
component so that we could start to consolidate libraries. I
honestly haven't looked at alternatives that much either, but someone
must have a scriptaculous version. There's no requirement for
accordion to go away immediately, but with incompatibilities between
rico and prototype looming, i would say its days are kind of numbered
unless rico releases a new version on the latest prototype.

Ajax Tabbed Pane should be pretty simple to do, actually. You would
be sitting on top of the core components, so there isn't even
anything really odd about it -- Just make a repetition of
AjaxUpdateLinks that refresh the main body AjaxUpdateContainer when
selected. Basically if you write it in the "old stye", then just
switch out your WOHyperlinks for AjaxUpdateLinks, that generally
works out.

Post by Clark Mueller
This is the first I've seen of it, but this is another one that I
wouldn't mind trying to build a decent reusable component for. I'm
not a big fan of the existing AjaxModalDialog.

Check out YUIPanel in the PW YUI.framework. This is very new, but it
wraps some of the core components in the Yahoo User Interface
toolkit. Yahoo provides a bunch of nice higher-level javascript UI
components (like panels, dialogs, etc). There's not a lot wrapped in
there yet, mainly because it hasn't generated quite as much interest
as Ajax framework yet.

ms