Dynamic Table

[Spritemarkiv]

Just did a full cache clearing in IE Tester and 8,9 started working with TableTools in Dynamic Table v0.2.0.  IE7 and below throw errors.
I cleared the cache and cookies through Internet explorer options->Browser History->Delete  The Refresh Complete(no cache) button was not enough.

[Argos]

Table Tools work perfectly in IE7/8/9 on the original datatables script demo, so there's not a problem as far as I can see.

Sorting works also fine in IE7/8/9 now, without javascript errors. However, my Kaspersky antivirus now gives alerts with the WB module version about invader code injecting stuff, but it doesn't do that on the original datatables script demo.

And then there's a new error in IE7/8/9: all headers are displayed double.

And to make matters even worse: sorting doesn't work in Firefox, Chrome. I didn't try other browers.

It seems this module is not blessed with good fortune, and I must abandon it for my project now, and use a standalone script. But I hope it will work flawlessly someday, and I will keep on testing new versions.

[Spritemarkiv]

Argos,
Thanks for the feedback, however I can not duplicate any of the errors you are describing.  Sorry, it didn't work out for you.  I will continue to work it improve this module.

Could you move this topic back to the modules section?  Or is their a specific reason it was moved this thread about a module to JQuery?

[Argos]

Argos,
Thanks for the feedback, however I can not duplicate any of the errors you are describing.  Sorry, it didn't work out for you.  I will continue to work it improve this module.

No prob, thanks for your work!

Could you move this topic back to the modules section?  Or is their a specific reason it was moved this thread about a module to JQuery?

Well, it's very much a jQuery module, so this would seem to be a more appropriate place. Don't you think? But I must admit there's no clear boundary in this case. Would you like to have it back in the Modules section?

[Spritemarkiv]

Yes, it is heavily a jQuery module, but so are many other WB modules.  Most WB users are non-programers looking for a module to install to do what they want. I think these users would more easily find the information they are looking for if the threads for all modules are kept together.

For me the jQuery section should be for raw jQuery that has not been ported to a module form.  Perhaps, a new section just for jQuery Modules would be appropriate.

When I first started using WB (pre AMASP) I would search through the modules section of the forum looking for new modules to see what was possible with WB.  Things have changes a lot since then, perhaps my thinking needs to as well.

You are right, it is a new area without a clear boundary.  As you are the moderator of the forum, I will leave it to you to decide.  I was mostly curious as to why.

Thanks

[Argos]

Thanks for your extensive reply, I appreciate that. You have convinced me that the Modules section is more appropriate, but only because most people will look in the regular Modules section more often than in the "technical" jQuery section. So I will move it back  

Actually the best setup, strictly speaking, would be this:
- Regular modules
- Regular snippets & droplets
- jQuery snippets
- jQuery modules
- jQuery Admin module & plugins

But it's probably too complex

And there is always some overlap ofcourse. I mean, does a little bit of jQuery in a module make it a jQuery module? The Dynamic Table moduel however, relies heavily on jQuery, making it a typical jQuery module. That's why I moved it to the jQuery section. But you're right that less people will come there. Hm...

[pcwacht]

nevertheless it stays a module


module = a module wich could be used as a page type
admin module = a module for backend tool stuff
snippet = installs as a module wich give wb extra template functions
droplet = snippet of code to be used in template or content from within the droplet-admin-module

This one is in my dictionary a module, even if it ias hardly any php

my 2 cents,
John

[Argos]

There was no discussion (in my opinion) if this is a module or not. This *is* a module.

The discussion was if this module should be discussed in the general modules forum, or in the jQuery forum, because the distinctive character of the module is the jQuery functionality. All it does is adding jQuery stuff to a HTML table. So: is this a jQuery subject that should be discused in the jQuery forum, or a module subject that belongs in the Modules forum, that's the question...

That goes for other jQuery modules as well. It's difficult to draw a line.

[pcwacht]

hmmm

I would keep modules to modules, if I was searching for a module I would look in modules
JQuery stuff is for jquery stuff, like mootools is mootools, javascript is javascript and others

This is first a module, wich makes use of jquery, that's true but still it is just another module

Maybe put a sticky on top of jquery wich lists and links modules with jquery?
Then you have best of both

Again, just my 2 cents, nothing more.

John

[nuke]

Hello,

I upgraded to 2.8.2 and and also to v0.2 of the script I now get a warning with this module:

Warning: mysql_fetch_array(): supplied argument is not a valid MySQL result resource in /home/user/public_html/framework/class.database.php on line 99

Warning: mysql_fetch_array(): supplied argument is not a valid MySQL result resource in /home/user/public_html/framework/class.database.php on line 99

Now this is directly related to the change I did in the view.php below, adding:

"aaSorting": [[ 0, "desc" ]],

When that is removed I do not get the "Warning: mysql_fetch_array(): supplied argument is not a valid MySQL result" ... thoughts on how I can get rid of this?

Thanks,
-Mike

Look here for more info:
http://www.datatables.net/examples/basic_init/table_sorting.html

Thanks John for that speedy reply, helped a lot - for others I just added
      "aaSorting": [[ 0, "desc" ]],
Around

//load  DataTable

(I placed it between "bSortClasses": true, and "bAutoWidth":true )

In the view.php - it works great!

-Mike

[marmot]

Hi,

Now this is directly related to the change I did in the view.php below, adding:
"aaSorting": [[ 0, "desc" ]],
When that is removed I do not get the "Warning: mysql_fetch_array(): supplied argument is not a valid MySQL result" ... thoughts on how I can get rid of this?

The problem seems to be that wb is resolving [[ ]] as a droplet. So just insert a space between the brackets and everything is fine:

Code:

"aaSorting": [ [ 0, "desc" ] ],

regards

[nuke]

Thank you very much Marmot! That worked perfectly!

-Mike