Qwaygon [Qwaygon]

this is the module

time past, and supported ahah (qtools_ahah) module that was suposed to fit the needs of QMenu become the real essence of my desires, and probably more valuable than QMenu itself, i DO belive that it worth at least looking at becouse as for me it so useful and flexible that i will definetly use it to the rest of my life, even that it only provide some api, it is well self-documented clean and coder say its ok, it pass all checks here http://drupal.org/node/59. i don't write separate example module but QMenu is used its features so QMenu can be an example module

so here is a question what should i do since QMenu forms manipulation significally changed in backend according to qtools_ahah new features:

a) add reworked code to this issue with (the changes does not affect any functionality or logic, only form ahah handling part, it become more secure, more clean, more flexible and less coded) (i will actually do this)

b) write here an appication for qtools_ahah moving to CVS (i'd be happy to maintain both, but dont want abuse CVS, so if i have to choose with one is more important for me and community i belive its "qtools_ahah") from its name you can think that its just another "ahah_helper" module but i saw code for ahah_helper, and this module much more than that, so much that if i want to comaintain "ahah_helper" it will has to be rewriting from scratch, here i use completly different way, much more flexible, richer, and secure. since qtools_ahah module is well self documented - please glance on it and if you thinks that it "might" be ok for CVS - i will write complete application here or create a new one . from now "qtools_ahah" dont have any dependencies, and completly 100% finished standalone module, QMenu included in this acrhive is an example of using "qtools_ahah" module, if you decide to give it a chance - start straight from qtools_ahah.module there is a dosens of comment there (grammar may be horroble and a lot of typo in coments, but if this goes to CVS its obviouse will be fixed)

p.s. i don't mean any harm for "ahah_helper" its just accomplish different goals

whell mostly yes for now, the reason it is so - its becouse i can't just extend Drupal.ahah.prototype.success function without changing original drupal files (and that would be not in drupal way) so i have to cut whole function in to my file to inject a little loop for each "extra" piece, at the time of this writings injection also allow evaluting js on client side and look like this

    //================================================================================QTOOLS_AHAH_EXTRA
    //================================================================================
    //================================================================================
    //======================== start loop
if (response.qtools_ahah_targets){
    //alert(response.qtools_ahah_targets);
    for (var key in response.qtools_ahah_targets){
        //======================== opening iteration, presetting our variables
        qt_target = response.qtools_ahah_targets[key];
        //alert(qt_target);
        var qt_element = eval('response.'+qt_target);
		if (qt_element.type == 'script')
		{
			if ((qt_element.prefix != null) && (qt_element.suffix != null)){
				str = qt_element.prefix + 'qt_element.data'+qt_element.suffix;
			}
			else {
				str = qt_element.data;
			}
			//alert(qt_element.type);
			eval(str);
			continue;
		}
        //alert(qt_element.target);
        //alert(qt_element.data);
        var wrapper = $(qt_element.target);
        var new_content = $('<div></div>').html(qt_element.data);
        //======================== drupl code

doesn't look very shiny but do its job and future is depend on eaither it goes to CVS

with this feature comes i've change a 4.4 part of qtools_ahah_page_callback doc

  4.4) calling all <callback> = 'output' with list of params ($output, $tmp_extra, $form, $form_state, $ahah_key)
 * this is where modules can actualy set a respond that will be sended to browser $form, $form_state, $ahah_key
 * is self explained, lets look at $output
 *  this is associative array where module should add a key corresponding to module name and a value that will be 
 * converted to json, for example $output['test_module'] = drupal_render($form['changed part']); after this callback
 * the actual output will be $output = implode('', $output); and the imploded output will be send as 
 * assigned to 'data' json key
 *
 * $extras - this is what this module all about! you probably shoudn't use this module unless you need to use extra, but if
 * you do - you probably will leave $output blank and set '#ahah' target to unexisting id, managing all ahah trough extras
 * $output is only here for capability purpose and easing rebuilding existing forms for use with this module
 *   $extra is an associative array, where each module should add keys (if needed of course) according to module name, 
 *   and the value should be an array of extras that module should output, with following parametres, example
 *   for extra html chunk (like default ahah aoutput)
 *
 *   $extra['test_module'][<delta>] = array( //<delta is just a key, no actual using anywhere>
 *       'target' => '#target_extra_id', //(data will be put in shis selector container)
 *       'data' => 'data' //(this is the same meaning as output data, here should be html that must be inserted into 'target' selector)
 *   )
 *
 *   for extra js
 *
 *   $extra['test_module'][<delta>] = array( //<delta is just a key, no actual using anywhere>
 *       'type' => 'script', //(flag this extra as js extra)
 *       'data' => 'data', //(in case you didnt specify 'prefix' or 'suffix' fields this vill be eval'ed at the client side)
 *       'prefix' => //if is set and 'suffix' is set the evaled string vill be as follow: preffix+'data'+suffix, so you can pass data as a parametr to some function without escaping quotas and control charasters
 *       'suffix' => 'see prefix above'
 *   )
 *   JS Over AHAH is another cool feature of this module that gives you complete control over page displayed,
 *   however while you can print any script through this feature - its design and purpose was to let you send 
 *   a little pieses of js that will gives your clientside scripts and objects a clue about what hapened, 
 *   as an example jcarousel, you can rewrite <li>'s with your content but you probably want to tell jcarousel
 *   to readjust size or reset its content before inserting new one, becouse if you dont - it will be looks broken in many cases
 ... so with this module its all is essential as a part of comunicating with a browser.
 * after all extras are sullpied upper two levels of array will be merged with $extra_key = ['test_module'.'_'.<delta>]

and just in case we have switched from QMenu to qtools_ahah here are demo site for you
url: http://dp.in-place.org.ua/
user: barefoot
pass: but.smart

nevermind about what happening on the site since it was a demo for my friend, BUT it also uses all features of qtools_ahah to aka "server side" managing of jcarousel
when you in, go to http://dp.in-place.org.ua/node/14/manage there will be managing interface for my implementation for galleries and images , what we are interesting about is bottom 2 regions
1st - QImage already attached to this gallery...
2nd - QImage that are not attached to any QGallery

so lets see qtools_ahah in action
a) select some images in 2nd region and press attach, qtools_ahah will refresh 4 separated div-s (2 selects for paging and 2 ul-s from jcarousels) this is multiply extras test, the target on actual button's '#ahah' property is set to unexisted ID and all 4 pieses goes trough extras

and after you do that you will note that 1st region while contain added images looks broken, thats becouse we just print content inside a carousel but the initial size of carousel stay unchanged and result in "vertical row" of images

b) attach ALL images to the gallery (so the 2nd region become empty) and refresh the page, now 2nd regions jcarousel size is set to 1 (ther are single message)... now select some images from 1st region and press detach. This time items goes to the bottom jcarousel and all looks fine, becouse in this time we add another 2 extras

    $extra['qgallery'][] = array(
        'type' => 'script',
        'data' => " Drupal.settings.jcarousel['#detached-list-target'].jcarousel.size(". $count .");",
    );
    $extra['qgallery'][] = array(
        'type' => 'script',
        'data' => "Drupal.settings.jcarousel['#detached-list-target'].jcarousel.reset();",
    );

that tels our carousel that we going to manipulate images so it can rearange itself.

in attachment you will find current qtools_ahah used module on that site and a part from qgallery module that contain complete hook_qtools_ahah_access(); implemenation for whole page, and handling AHAH key = 'qgallery/manage/detach/%' section (as you can note both "detach" and "attach" buttons use same function for refreshing page).

p.s. qtools_ahah.module doesn't have many changes, just add a hook_perm and extend coments for main function

yes but it IS changed... hm... i downloaded modules2.zip from #2 post just to check , unpack and look at qtools_ahah.js it contain changed part that hard to be missed with huge coment

    //================================================================================QTOOLS_AHAH_EXTRA
    //================================================================================
    //================================================================================
    //======================== start loop
if (response.qtools_ahah_targets){
    //alert(response.qtools_ahah_targets);
    for (var key in response.qtools_ahah_targets){
        //======================== opening iteration, presetting our variables
        qt_target = response.qtools_ahah_targets[key];
        //alert(qt_target);
        var qt_element = eval('response.'+qt_target);
        //alert(qt_element.target);
        //alert(qt_element.data);
        var wrapper = $(qt_element.target);
        var new_content = $('<div></div>').html(qt_element.data);
        //======================== drupl code

the send.zip from #4 have even more changed text (see first code snippet in #4 coment) while that are not "1000 lines of chage" they ARE nessesary (nvm for all comented alerts)

so i don't realy understand what do you mean by "there isn't the need to copy the functions that are not changed." while that clearly has a point :) it does not apply to this case, becouse this function definetly CHANGED in qtools_ahah.js