Hi, I like your approach and maybe its a better module than Modal Frame as you mention. But now I have a little luxury problem of freedom of choice and don't know what to do:

ModalFrame:
Highly Recommended: onBeforeUnload API (enhances synchronization of parent/child windows). See reference: #669436: In search for alternatives to the unload event.
=> onBeforeUnload API also recommended for jQuery UI Dialog ?
Builtin support for: Dirty Forms.
Modules using Modal Frame API: Modal Frame Contrib Package (includes mini-modules that implement the Modal Frame API to enhance the usability of a few day to day tasks in every Drupal site), Node Relationships, Modal Frame CCK Editor, Subnodes by Taxonomy.
=> these depending modules aren't working with your module?

Both a feature request for having the same depending modules that do the same AND request for explaning on the projects page that certain combination's cause errors (or not) and what decision of modules one should make under different circumstances.

If these issues can be resolved, maybe your module should get into:
jQuery libraries - http://drupal.org/project/jquery ?

How about D7 (I won't use until end of 2011) and jQuery UI Dialog ?
The Modal Frame page states that their features probably will be in D7.

Comments

EugenMayer’s picture

EugenMayer CreditAttribution: EugenMayer commented

Those modules are not working with this module, but i guess it would not be hard getting them working - but it is not planned (and i cant see a reason for it).

This module should be as slim as possible and as browser-compatible as possible. It should not cut down the API of jquery ui (dialog), it should only help developers getting stuff ( a full drupal bootstrap) loaded in a dialog.

i cant see something like "dirty forms" support being part of this module. If it is build on the drupal-api it will work with this module.

For D7, well jquery_ui_dialog will get a port, like all my other modules, but i will start working with D7 4-6 months after the stable release.
Iam building a lot of things on top of this module ( http://drupal-wiki.com ) which are not released. So you can expect quiet some developement and support on jquery_ui_dialog in the feature.

As D7 will have jquery ui part of the core, part of this module might get obsolete. But as this module adds the iframe implementation (though its optional) it still could have its use case.

As jquery ui dialog is build ontop of jquery 1.3 i expect to have it working in D7 out of the box probably.

Hopefully your questions got answered

ClearXS’s picture

ClearXS CreditAttribution: ClearXS commented

Thanks for the explanation; I understand that the other mentioned modules should be changed to work with your modules instead?
or a php programmer seeing use in making new modules that do the similar)

EugenMayer’s picture

EugenMayer CreditAttribution: EugenMayer commented

Well yet it seems there is a new general "popup api". It should be shared accross all popup implementations, which makes sense to me. Iam expecting to implement this api for jquery ui dialog. If the other modules (i think it will be that way) will use this API, they will work with jquery ui dialog.

But if the other modules are using the moduleframe api (specific) you have to change the modules to get them working.

As modalframe and jquery_ui_dialog are having the same dependencies and using the same jquery techn. there might be no problem installing both at the same time, seeing them as different interfaces for different modules. Of course its not the best integration, as the dialogs look different depending on which you open, eventhough jquery_ui_dialog support to be style by the site-wide theme-roller theme for jquery ui.

lpalgarvio’s picture

lpalgarvio CreditAttribution: lpalgarvio commented

subscribing