[Seaside] Question about div

[Boris Popov]

Same here, I replaced stock lightbox with YUI's panels here as well as
added a date picker to our date fields, but its always tough to find
time to clean it up to the point of sharing although I do try
(SeasideYUI in Public Store).

Cheers!

-Boris

-- 
+1.604.689.0322
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5

boris at deepcovelabs.com

CONFIDENTIALITY NOTICE

This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any
attachments.

Thank you.

-----Original Message-----
From: seaside-bounces at lists.squeakfoundation.org
[mailto:seaside-bounces at lists.squeakfoundation.org] On Behalf Of Ramon
Leon
Sent: Tuesday, October 10, 2006 10:59 PM
To: The Squeak Enterprise Aubergines Server - general discussion.
Subject: Re: [Seaside] Question about div

>> Ah, I use very few built in components, nor the old render.  In fact,

>> I only
>> use the pager, and a custom subclass of it at that.  Most of the
stuff 
>> I do
>> relies heavily on script.aculo.us to do any real work, and YUI for 
>> widgets,
>> the seaside ones are just too plain.
> 
> 
> Anything to share for the YUI widgets? How did you integrate them? Do
> they work together with script.aculo.us?
> 
> Lukas

LOL, I don't have your energy, when I say I use the YUI widgets, I mean 
just a few... I don't port entire libraries like you. :)

However, I use the calendar, and the dialog class, and they seem well 
built and quite configurable.  Everything's factored into a few reusable

javascript libraries.  Each widget having various dependencies on 
different parts of those core libraries and a few css files to skin it.

I haven't had a single computability problem with prototype, 
script.aculo.us, google maps, or anything really.  I use em all and so 
far it's been seamless.  I've been rather lazy so far; When I want to 
use a component, I simply wrap it in a WAComponent, and make the bare 
minimum parameters configurable, to get the widget up and running.  I 
only have one main project I'm using them in, so I don't bother making 
them truly reusable and wrapping them totally like you did with 
script.aculo.us.

_______________________________________________
Seaside mailing list
Seaside at lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside