Thank you Marcos Sánchez for added properties. Work like a charm in Netbeans 6.9.1 =)

Attila

So when using Qcodo Updater, you will see the warning/note about qcodo-updater trying to deleted an extraneous includes/qcodo/_core/qform/QDateTimePicker.class.php file.  As long as you have never manually edited QDateTimePicker.class.php, you should feel free to have qcodo-updater delete it.

• a completely revamped QEmailServer class
• a new SQLite3 Database adapter (“SqLite”)
• key improvements on i18n, specifically around dates, times and datetime controls
• and many other improvements (see the changelog for more information)

There was also some confusion that we've had as to what “minimum” PHP version we should be supporting -- folks did some great analysis and cleanup work, and I'm happy to say that we're making sure that Qcodo should work on any PHP installation from PHP 5.1.2 to the current PHP 5.3.3 (and beyond).  Although note that there may be a few functionality might not work in earlier versions (specifically on the 5.1.x branch), at least Qcodo itself should install and work.

Thanks to Marcos for all of his contributions, and I also wanted to give a quick thanks to klucznik for the work he's been doing in cleaning up and improving on a lot of the front-end code which has not made it into core yet (feel free to checkout his commits on github if you want to see more).  I'm hoping to get most of his improvements into core soon -- but since it'll take a bit of effort to merge many of his changes in, my hope is to work with him on that shortly after we get the current set of dev revisions into a stable release.

Please feel free to post with any questions or comments... feedback is always greatly appreciated.  Also, we're starting to get a bit of issues posted -- if you have some time, any code contributions for fixes would also be greatly appreciated.  Best way to submit would be to commit fixes to a specific issue to your own qcodo repository on GitHub (it's free to register), and then send me a pull request.  Thanks!

As a FYI, We run all of our web properties (including qcodo.com =) on MediaTemple without any issues whatsoever.

<?php
class QWaitPanel extends QDialogBox {
    protected $blnMatteClickable = false;
    public function __construct($objParentObject, $strControlId = null) {
        //LLAMADA A CONSTRUCTOR DEL PADRE
        parent::__construct($objParentObject, $strControlId);

        //DATOS DEL DIALOG BOX
        $this->strText    = '<div class="waitcontrol">Wait a momment please...<br /><br /></div>';

        $this->blnDisplay  = false;
        $this->strFontSize = '16px';
        $this->strHeight = "80px";
        $this->strPadding = "20px";
    }
}
?>

and this is the way how i use it (i create a form base for all my other forms like qcodo site):

<?php
class GeneralForm extends QForm {
    protected $strPageTitle;
    
    protected $intModulo;

    protected function Form_Create() {
        QApplication::Authenticate();
        if(!empty($this->intModulo))
           if(!Session::TieneAccesoProceso($this->intModulo)) die("NO TIENE ACCESO A ESTE MODULO");

        //Wait Panel
        $this->objDefaultWaitIcon = new QWaitPanel($this);
        //Wait Icon
        //$this->objDefaultWaitIcon = new QWaitIcon($this);
    }
}
?>

then i extend the base form like this:

<?php
require_once '../includes/prepend.inc.php';

class IngresoArticulo extends GeneralForm{
    protected function Form_Create() {
        parent::Form_Create();
        ...
    }
    ....
}
?>

and in my template:

<?php 
require_once __INCLUDES__."/header.inc.php";
$this->RenderBegin();
//my own controls with custom html...
$this->objDefaultWaitIcon->Render();
$this->RenderEnd();
require_once __INCLUDES__."/footer.inc.php";
?>
.bc

http://github.com/klucznik/qcodo/commit/b4372d787d8fde711e6fc9c7be045fc009054911

might be useful.

Only firefox. It's a link to a PDF and Safari opens it in the same window.
Firefox gives the “save as” dialog.

best regards
Geert

Thank you for taking the time to respond.

There are no disableactions what so ever on the panel/form.

This problem has been reported before by vexed panda:
http://www.qcodo.com/forums/forum.php/0/2143/?search=ajax+not+working

Hope there is a solution for this and I don't need to redirect.

Are there any events that disable actions on the buttons at some point in the process flow? What triggers the loading of the panels?

Patrick

It has been to long....

I now come to you with a new problem.

I have a datagrid in which I render some links (to an php file that generates a PDF). The links work fine and a PDF gets printed

However when I click on one of the links all QCodo generated buttons don't posback to the server anymore! So nothing works.

Maybe it's worth to mention that the datagrid gets renderd inside a QPanel that in itself gets loaded with Ajax.

Any help will be greatly appreciated!

best regards
GEert

on line 171:

// Hid the WaitIcon (if applicable)
if (qcodo.objAjaxWaitIcon){
    if(qcodo.objAjaxWaitIcon.hideDialogBox)
        qcodo.objAjaxWaitIcon.hideDialogBox();
    else
        qcodo.objAjaxWaitIcon.style.display = 'none';
}

and after that change go to line 193 and replace as follows:

// Display WaitIcon (if applicable)
if (strWaitIconControlId) {
    this.objAjaxWaitIcon = this.getWrapper(strWaitIconControlId);
    if (this.objAjaxWaitIcon){
        if(this.objAjaxWaitIcon.showDialogBox)
            this.objAjaxWaitIcon.showDialogBox();
        else
            this.objAjaxWaitIcon.style.display = 'inline';
    }
};

Maybe it could be integrated on the new realease...

Greetings

See the Examples Site Page on datagrids for more info.

I've removed any of the old version_check code for PHP 5.0.x (e.g. including the references to QQuery.class.php you made above).  Now, the only version_check we do is with regards to checking for 5.2.0 or later, and using QDateTime or QDateTime-Legacy based on that (in qcodo.inc.php).

Any other post-5.1.2 functionality should now be checked against function_exists() first -- so for example, any code that references memory_get_peak_usage (which requires PHP 5.2.0 or later) is only called after verifying function_exists().  Since any calls to memory_get_peak_usage in Qcodo are “nice to have” but not critical to core functionality, I think keeping the official “Minimum PHP Version” at 5.1.2 will be fine.

If you have any comments or questions about this, please don't hesitate to post!

Otherwise, all these code cleanups should be in the 0.4.17 release.