@Jack,
Thanks for the kudos!
The jqtabcontrol.js is based on my own original, raw javascript for
what I refer to here at work as sliding tabs. Over the past year
since I originally wrote it, I've gradually pared down the file size
as I've tweaked the code. There isn't really a whole lot of
I have updated my examples pack. The new page is here:
http://education.llnl.gov/jQuery/
When I get the chance, I'm going to look through Kevin's great examples and
see what I can add. Thanks, Kevin!
[Shelane]
On 5/3/07 7:38 AM, Kevin Scholl [EMAIL PROTECTED] wrote:
@Jack,
Thanks for
Kevin, these are really nice, thanks for sharing them. Is the
jqtabcontrol.js based on any other plugins/libraries/yadda...? That's
the first that I've seen the more tabs handling in a jquery-based
tab library, very nice.
Thx,
Jack
Kevin Scholl wrote:
I have a number of such examples
OK, I have updated the examples pack to include these examples: Basic
AHAH!, Progressive Form (dynamic selects), RSS Feed Aggregator (with
Mike Alsup's plugin), Panel Collapse, Dynamic Update, Tooltips, and
Auto Complete (showing both the scriptaculous and the new autocomplete
beta plugin by
Shelane,
So far I only have one example complete although there are more to
come.
http://education.llnl.gov/jquery/ajax.html
You might not like this answer, but why not just use an iframe? :)
You'll be able to load a complete example that runs w/in it's own context. I
personally feel sometimes
I could. However, that would not solve another page problem I have outside
of this example where that really isn't a a possibility due to a complexly
structured web app.
On 4/27/07 8:59 AM, Dan G. Switzer, II [EMAIL PROTECTED] wrote:
Shelane,
So far I only have one example complete
here's my suggestion:
instead of embedding the $(document).ready code in your pages, create
Javascript classes for each page that receive as an argument a container DIV
that after they make the AJAX call for the page they are responsible for, they
put their content into.
Then, when that's
I'm going to admit that this is a bit over my head. I'm not really
sure what's going on in each of these sections. I'm not sure where
'#mydiv' is supposed to go. Does the url have to hard coded?
Currently the menu is built and reads the value of the href to
determine the page to load. Where
Ariel Jakobovits wrote:
instead of embedding the $(document).ready code in your pages, create
Javascript classes for each page that receive as an argument a container DIV
that after they make the AJAX call for the page they are responsible for, they
put their content into.
Then, when that's
I have not attempted to make any of Ariel's changes. Scott, I would
say that yes that would be the goal. The only thing I haven't done
for that is to include the jQuery src file on the subsequent pages.
That would be my intent to check if jQuery isn't there, to load it.
Meanwhile, I have these
absolutely.
if Javascript is enabled anyway, your pages can simple create that lone object
and provide the body as the container.
- Original Message
From: Scott Sauyet [EMAIL PROTECTED]
To: jquery-en@googlegroups.com
Sent: Friday, April 27, 2007 1:04:14 PM
Subject: [jQuery] Re: jQuery
11 matches
Mail list logo
