Rework Theme Developer so it use a file based cache for the variables. This avoids max_packet_size error on mysql.

#267204 by ksenzee. fix some render problems in theme developer by emitting span around page using js instead of php.

Theme developer now has its variables back and all is fast and memory efficient. For those that choose to move their krumo subdir out of the way or otherwise disable krumo(), there is a bug in devel_print_object() where it seems not to handle recursion properly and even without recurssion, the popup does not properly expand its output when clicked.

First half of rework of Theme Developer to be faster and less memory intensive. Instead of sending all the variables for all theme calls in each request, we save the variables to a cache table on the server. In the next commit, the popup will retrieve the variables on demand if the user cares to view them. The menu callback for this AJAX request is done - just need javascript work now.

patch by moshe weitzman. avoid krumo() when outputting simple variables. only used for arrays and objects.

add modified krumo package to devel. no longer is a separate download required. i made minor changes to config method so it uses variable_get(). also a change so that the backtrace file/line number make sense. lets try this out for a while and if it is successful, we'll rip out the conditional has_krumo() code in devel.module

further cleanup of bulk node generation. modules may now participate using standard hook_form_alter() and hook_nodapi(). See devel_generate_nodeapi() for an example. content_field('presave') is another example.

rework devel_generate so that modules can cleanly form_alter themselves into the creation process. i have not changed comment, taxonomy, and upload to work like that yet. i will do so, and then add OG functionality so that group posts get properly affiliated with group nodes.