My favorites | Sign in
Logo
             
Details: Show all Hide all

Yesterday

  • 31 hours ago
    issue 206 (Unregister clientside validators from manager if container o...) commented on by godzill...@gmx.net   -   Nice idea - much more elegant and more performant on the server side - thanks :D
    Nice idea - much more elegant and more performant on the server side - thanks :D
  • 32 hours ago
    issue 206 (Unregister clientside validators from manager if container o...) commented on by google...@pcforum.hu   -   It would be probably easier to do the opposite, ie. ask the client side manager / registry itself - after an update - to validate each and every validator it has registered. This could be done by forcing each rendered and active validator to emit a <span> with a unique id in-place into the page code, and then asking the registry to look up the id's of each of it's registered validator in the DOM. If it can't find any elements with the specified id, it should dispose of the validator previously registered into it, as the validator is no more part of the page (or is disabled). Just an idea.
    It would be probably easier to do the opposite, ie. ask the client side manager / registry itself - after an update - to validate each and every validator it has registered. This could be done by forcing each rendered and active validator to emit a <span> with a unique id in-place into the page code, and then asking the registry to look up the id's of each of it's registered validator in the DOM. If it can't find any elements with the specified id, it should dispose of the validator previously registered into it, as the validator is no more part of the page (or is disabled). Just an idea.

Last 7 days

  • Nov 04, 2009
    issue 206 (Unregister clientside validators from manager if container o...) reported by godzill...@gmx.net   -   What steps will reproduce the problem? - add TValidationSummary to TActivePanel - add TPanel to TActivePanel - add TTextBox & TRequiredFieldValidator to TPanel - add TActiveLinkButton with CausesValidation=true to TActivePanel - add TActiveLinkButton with CausesValidation=false to TActivePanel - click TActiveLinkButton with CausesValidation=true => TValidationSummary will be displayed - click TActiveLinkButton with CausesValidation=false and set TPanel.Visibile=false on callback What is the expected output? No validation message is displayed What do you see instead? Validation message is shown. Solution: Unregister clientside validators from manager if container of validator becomes invisible after callback
    What steps will reproduce the problem? - add TValidationSummary to TActivePanel - add TPanel to TActivePanel - add TTextBox & TRequiredFieldValidator to TPanel - add TActiveLinkButton with CausesValidation=true to TActivePanel - add TActiveLinkButton with CausesValidation=false to TActivePanel - click TActiveLinkButton with CausesValidation=true => TValidationSummary will be displayed - click TActiveLinkButton with CausesValidation=false and set TPanel.Visibile=false on callback What is the expected output? No validation message is displayed What do you see instead? Validation message is shown. Solution: Unregister clientside validators from manager if container of validator becomes invisible after callback
  • Nov 04, 2009
    r2736 (Minor corrections to avoid runtime notice with php 5.3, and ...) committed by Christophe.Boulain   -   Minor corrections to avoid runtime notice with php 5.3, and function rename in TDbConnection
    Minor corrections to avoid runtime notice with php 5.3, and function rename in TDbConnection
  • Nov 02, 2009
    r2735 (added missing package description in TActiveFileUpload ) committed by rojaro   -   added missing package description in TActiveFileUpload
    added missing package description in TActiveFileUpload
  • Nov 01, 2009
    r2734 (added a few more snippets to the textmate bundle ) committed by rojaro   -   added a few more snippets to the textmate bundle
    added a few more snippets to the textmate bundle
  • Nov 01, 2009
    r2733 (added missing package description ) committed by rojaro   -   added missing package description
    added missing package description
  • Nov 01, 2009
    r2732 (added a few new snippets to the textmate bundle ) committed by rojaro   -   added a few new snippets to the textmate bundle
    added a few new snippets to the textmate bundle
  • Nov 01, 2009
    r2731 (added old prado textmate bundle ) committed by rojaro   -   added old prado textmate bundle
    added old prado textmate bundle
  • Nov 01, 2009
    r2730 (TEnumerable can now be iterated as suggested by FragMaster B...) committed by rojaro   -   TEnumerable can now be iterated as suggested by FragMaster B
    TEnumerable can now be iterated as suggested by FragMaster B
  • Nov 01, 2009
    r2729 (Added ability to set width and height for images in both THy...) committed by rojaro   -   Added ability to set width and height for images in both THyperLink and THyperLinkColumn (plus the imageurl for the latter) as suggested by junkee in http://www.pradosoft.com/forum/index.php?topic=8745.0
    Added ability to set width and height for images in both THyperLink and THyperLinkColumn (plus the imageurl for the latter) as suggested by junkee in http://www.pradosoft.com/forum/index.php?topic=8745.0
  • Nov 01, 2009
    r2728 (merged fix for proper errorhandling when the size of the upl...) committed by rojaro   -   merged fix for proper errorhandling when the size of the uploaded file exceeds the limit see http://www.pradosoft.com/forum/index.php?topic=11850.0
    merged fix for proper errorhandling when the size of the uploaded file exceeds the limit see http://www.pradosoft.com/forum/index.php?topic=11850.0
  • Nov 01, 2009
    r2727 (merged fix for asynchronous callback requests from http://ww...) committed by rojaro   -   merged fix for asynchronous callback requests from http://www.pradosoft.com/forum/index.php?topic=12179.0
    merged fix for asynchronous callback requests from http://www.pradosoft.com/forum/index.php?topic=12179.0
  • Nov 01, 2009
    r2726 (merged quotestring utf8 patch ... see http://www.pradosoft.c...) committed by rojaro   -   merged quotestring utf8 patch ... see http://www.pradosoft.com/forum/index.php?topic=11700.msg51530;topicseen#msg51530
  • Nov 01, 2009
    r2725 (merged active record default value bug fix which got lost wh...) committed by rojaro   -   merged active record default value bug fix which got lost when moving from trac to googlecode - see http://www.pradosoft.com/forum/index.php?topic=10603.0
    merged active record default value bug fix which got lost when moving from trac to googlecode - see http://www.pradosoft.com/forum/index.php?topic=10603.0
  • Nov 01, 2009
    r2724 (added Dreamweaver extension so it doesnt get "lost" again ) committed by rojaro   -   added Dreamweaver extension so it doesnt get "lost" again
    added Dreamweaver extension so it doesnt get "lost" again
  • Nov 01, 2009
    r2723 (fixed error handler to detect changes in the error reporting...) committed by rojaro   -   fixed error handler to detect changes in the error reporting level after initialisation as suggested by acron in http://www.pradosoft.com/forum/index.php?topic=12226.0
    fixed error handler to detect changes in the error reporting level after initialisation as suggested by acron in http://www.pradosoft.com/forum/index.php?topic=12226.0

Last 30 days

  • Oct 19, 2009
    issue 205 (Feature Request: Add support for fully qualified URL-matchin...) commented on by google...@pcforum.hu   -   I've implemented this feature in the attached file (source based on stock 3.1.6 sources). TUrlMappingPattern (and thus the <url> tags in the mapping config) now have a new property named 'UrlMatchMode', which defaults to 'PathInfo', but if set to 'Full', it will match the Pattern property against the pathinfo+querystring, parts instead of just the pathinfo part itself of the request. It will also escape the "?" character for the regular expr. matching in the Pattern if there's one. I've tested and need this only in EnableCustomUrl=false mode (eg. only to divert calls to pages based on the params, not construct any urls using those), so it will have to be tested with EnableCustomUrl=true yet, whether it works as expected.
    I've implemented this feature in the attached file (source based on stock 3.1.6 sources). TUrlMappingPattern (and thus the <url> tags in the mapping config) now have a new property named 'UrlMatchMode', which defaults to 'PathInfo', but if set to 'Full', it will match the Pattern property against the pathinfo+querystring, parts instead of just the pathinfo part itself of the request. It will also escape the "?" character for the regular expr. matching in the Pattern if there's one. I've tested and need this only in EnableCustomUrl=false mode (eg. only to divert calls to pages based on the params, not construct any urls using those), so it will have to be tested with EnableCustomUrl=true yet, whether it works as expected.
  • Oct 19, 2009
    issue 205 (Feature Request: Add support for fully qualified URL-matchin...) commented on by google...@pcforum.hu   -   I've implemented this feature in the attached file (source based on stock 3.1.6 sources). TUrlMappingPattern (and thus the <url> tags in the mapping config) now have a new property named 'UrlMatchMode', which defaults to 'PathInfo', but if set to 'Full', it will match the Pattern property against the pathinfo+querystring, parts instead of just the pathinfo part itself of the request. It will also escape the "?" character for the regular expr. matching in the Pattern if there's one. I've tested and need this only in EnableCustomUrl=false mode (eg. only to divert calls to pages based on the params, not construct any urls using those), so it will have to be tested with EnableCustomUrl=true yet, whether it works as expected.
    I've implemented this feature in the attached file (source based on stock 3.1.6 sources). TUrlMappingPattern (and thus the <url> tags in the mapping config) now have a new property named 'UrlMatchMode', which defaults to 'PathInfo', but if set to 'Full', it will match the Pattern property against the pathinfo+querystring, parts instead of just the pathinfo part itself of the request. It will also escape the "?" character for the regular expr. matching in the Pattern if there's one. I've tested and need this only in EnableCustomUrl=false mode (eg. only to divert calls to pages based on the params, not construct any urls using those), so it will have to be tested with EnableCustomUrl=true yet, whether it works as expected.
  • Oct 19, 2009
    issue 205 (Feature Request: Add support for fully qualified URL-matchin...) commented on by google...@pcforum.hu   -   I've implemented this feature in the attached file (source based on stock 3.1.6 sources). TUrlMappingPattern (and thus the <url> tags in the mapping config) now have a new property named 'UrlMatchMode', which defaults to 'PathInfo', but if set to 'Full', it will match the Pattern property against the pathinfo+querystring, parts instead of just the pathinfo part itself of the request. It will also escape the "?" character for the regular expr. matching in the Pattern if there's one. I've tested and need this only in EnableCustomUrl=false mode (eg. only to divert calls to pages based on the params, not construct any urls using those), so it will have to be tested with EnableCustomUrl=true yet, whether it works as expected.
    I've implemented this feature in the attached file (source based on stock 3.1.6 sources). TUrlMappingPattern (and thus the <url> tags in the mapping config) now have a new property named 'UrlMatchMode', which defaults to 'PathInfo', but if set to 'Full', it will match the Pattern property against the pathinfo+querystring, parts instead of just the pathinfo part itself of the request. It will also escape the "?" character for the regular expr. matching in the Pattern if there's one. I've tested and need this only in EnableCustomUrl=false mode (eg. only to divert calls to pages based on the params, not construct any urls using those), so it will have to be tested with EnableCustomUrl=true yet, whether it works as expected.
  • Oct 19, 2009
    issue 205 (Feature Request: Add support for fully qualified URL-matchin...) commented on by google...@pcforum.hu   -   I've implemented this feature in the attached file (source based on stock 3.1.6 sources). TUrlMappingPattern (and thus the <url> tags in the mapping config) now have a new property named 'UrlMatchMode', which defaults to 'PathInfo', but if set to 'Full', it will match the Pattern property against the pathinfo+querystring, parts instead of just the pathinfo part itself of the request. It will also escape the "?" character for the regular expr. matching in the Pattern if there's one. I've tested and need this only in EnableCustomUrl=false mode (eg. only to divert calls to pages based on the params, not construct any urls using those), so it will have to be tested with EnableCustomUrl=true yet, whether it works as expected.
    I've implemented this feature in the attached file (source based on stock 3.1.6 sources). TUrlMappingPattern (and thus the <url> tags in the mapping config) now have a new property named 'UrlMatchMode', which defaults to 'PathInfo', but if set to 'Full', it will match the Pattern property against the pathinfo+querystring, parts instead of just the pathinfo part itself of the request. It will also escape the "?" character for the regular expr. matching in the Pattern if there's one. I've tested and need this only in EnableCustomUrl=false mode (eg. only to divert calls to pages based on the params, not construct any urls using those), so it will have to be tested with EnableCustomUrl=true yet, whether it works as expected.
  • Oct 19, 2009
    issue 205 (Feature Request: Add support for fully qualified URL-matchin...) reported by google...@pcforum.hu   -   TUrlMapping (well, actually TUrlMappingPattern) currently only supports mapping based on the "pathinfo" part of the url, and provides no way to provide any mapping which also considers any parameters passed to the script in the "querystring" part of the url. I however fail to see why this limitation is there. Without this, one must fall back to use .htaccess rewrite techniques, contradicting the primary purpose of Prado's url mapping (which in my understanding is allowing developers to avoid those url rewrites from config, and moving that logic integral to the application), in cases where for ex. you want to have calls diverted to different pages based on specific query parameter values in the url. (For ex. you might have moved the functionality once implemented in the same page now apart, to two more pages, without invalidating already created and stored urls in the application, in search engines, etc.) This limitation, however, could be easily overcomed would TUrlMappingPattern provide a way to use the result of $request- >getRequestUri() instead of $request->getPathInfo(). Therefore I propose to add a new property to the latter class, which would enable developers to make use of that extra part of the url, too, in match-checks (againt the pathinfo+querystring part of the url), while also preserving backwards compatibility (matching against only the path info).
    TUrlMapping (well, actually TUrlMappingPattern) currently only supports mapping based on the "pathinfo" part of the url, and provides no way to provide any mapping which also considers any parameters passed to the script in the "querystring" part of the url. I however fail to see why this limitation is there. Without this, one must fall back to use .htaccess rewrite techniques, contradicting the primary purpose of Prado's url mapping (which in my understanding is allowing developers to avoid those url rewrites from config, and moving that logic integral to the application), in cases where for ex. you want to have calls diverted to different pages based on specific query parameter values in the url. (For ex. you might have moved the functionality once implemented in the same page now apart, to two more pages, without invalidating already created and stored urls in the application, in search engines, etc.) This limitation, however, could be easily overcomed would TUrlMappingPattern provide a way to use the result of $request- >getRequestUri() instead of $request->getPathInfo(). Therefore I propose to add a new property to the latter class, which would enable developers to make use of that extra part of the url, too, in match-checks (againt the pathinfo+querystring part of the url), while also preserving backwards compatibility (matching against only the path info).
  • Oct 16, 2009
    issue 204 (Pradosoft.com domain expired) Status changed by rojaro   -   Seems that this was a temporary problem at godaddy.com.
    Status: Invalid
    Seems that this was a temporary problem at godaddy.com.
    Status: Invalid
  • Oct 16, 2009
    issue 204 (Pradosoft.com domain expired) reported by ctrlaltca   -   What steps will reproduce the problem? 1. Point your browser to the official prado website What is the expected output? What do you see instead? Expected output: prado website; instead, i see a domain register webpage. What version of the product are you using? On what operating system? --- Please provide any additional information below. Domain Name: PRADOSOFT.COM Registrar: GODADDY.COM, INC. Whois Server: whois.godaddy.com Referral URL: http://registrar.godaddy.com Name Server: NS29.DOMAINCONTROL.COM Name Server: NS30.DOMAINCONTROL.COM Status: clientDeleteProhibited Status: clientRenewProhibited Status: clientTransferProhibited Status: clientUpdateProhibited Updated Date: 16-oct-2009 Creation Date: 05-feb-2005 Expiration Date: 05-feb-2011
    What steps will reproduce the problem? 1. Point your browser to the official prado website What is the expected output? What do you see instead? Expected output: prado website; instead, i see a domain register webpage. What version of the product are you using? On what operating system? --- Please provide any additional information below. Domain Name: PRADOSOFT.COM Registrar: GODADDY.COM, INC. Whois Server: whois.godaddy.com Referral URL: http://registrar.godaddy.com Name Server: NS29.DOMAINCONTROL.COM Name Server: NS30.DOMAINCONTROL.COM Status: clientDeleteProhibited Status: clientRenewProhibited Status: clientTransferProhibited Status: clientUpdateProhibited Updated Date: 16-oct-2009 Creation Date: 05-feb-2005 Expiration Date: 05-feb-2011
  • Oct 14, 2009
    issue 203 (->CallbackClient->click doesn't work in IE7 and IE8) reported by mcsakoff   -   Test.page: ... <com:TActiveButton ID="activeButton" Text="Fire Callback" OnClick="onActiveButtonClicked" /> <com:TButton ID="passiveButton" Text="Fire Postback" OnClick="onButtonClicked" /> ... Test.php: ... public function onActiveButtonClicked( $sender, $param ) { print "onActiveButtonClicked"; $this->CallbackClient->click( $this->passiveButton ); } public function onButtonClicked( $sender, $param ) { print "onButtonClicked"; } ... 2. Click "Fire Callback" button. The page should be reloaded and "onButtonClicked" displayed on it. That works fine in FF and Opera but not in IE7 and IE8. On IE it prints to JavaScript console: HTTP 200 with response : onCallbackClicked Actions : {"Prado.Element.click":["ctl0_ctl0_body_main_passiveButton"]} but the button is not actually clicked. I found two problems here. IE doesn't like when client side function is called "click". I've fixed that renaming function to something like "click_on": TCallbackClientScript.php,113: ... /** * Client script to click on an element. <b>This client-side function * is unpredictable.</b> * @param TControl control element or element id */ public function click($control) { $this->callClientFunction('Prado.Element.click_on', $control); } ... scriptaculous-adapter.js,251: ... /** * Trigger a click event on a DOM element. * * @function ? * @param {string} element - Element id */ click_on : function(element) { var el = $(element); if(el) Event.fireEvent(el,'click'); }, ... Second problem is that as promised the client side function is unpredictable. So, I've just changed Event.fireEvent(el,'click') to simple el.click(); Of course that works for buttons only, but at least that works! click_on : function(element) { var el = $(element); el.click(); }, --- Prado 3.1.6, Gentoo x86.
    Test.page: ... <com:TActiveButton ID="activeButton" Text="Fire Callback" OnClick="onActiveButtonClicked" /> <com:TButton ID="passiveButton" Text="Fire Postback" OnClick="onButtonClicked" /> ... Test.php: ... public function onActiveButtonClicked( $sender, $param ) { print "onActiveButtonClicked"; $this->CallbackClient->click( $this->passiveButton ); } public function onButtonClicked( $sender, $param ) { print "onButtonClicked"; } ... 2. Click "Fire Callback" button. The page should be reloaded and "onButtonClicked" displayed on it. That works fine in FF and Opera but not in IE7 and IE8. On IE it prints to JavaScript console: HTTP 200 with response : onCallbackClicked Actions : {"Prado.Element.click":["ctl0_ctl0_body_main_passiveButton"]} but the button is not actually clicked. I found two problems here. IE doesn't like when client side function is called "click". I've fixed that renaming function to something like "click_on": TCallbackClientScript.php,113: ... /** * Client script to click on an element. <b>This client-side function * is unpredictable.</b> * @param TControl control element or element id */ public function click($control) { $this->callClientFunction('Prado.Element.click_on', $control); } ... scriptaculous-adapter.js,251: ... /** * Trigger a click event on a DOM element. * * @function ? * @param {string} element - Element id */ click_on : function(element) { var el = $(element); if(el) Event.fireEvent(el,'click'); }, ... Second problem is that as promised the client side function is unpredictable. So, I've just changed Event.fireEvent(el,'click') to simple el.click(); Of course that works for buttons only, but at least that works! click_on : function(element) { var el = $(element); el.click(); }, --- Prado 3.1.6, Gentoo x86.
  • Oct 14, 2009
    r2722 (added TActiveMultiView ) committed by rojaro   -   added TActiveMultiView
    added TActiveMultiView
  • Oct 12, 2009
    issue 202 (cache got error after i delete the runtime ) reported by setiawan.ricky   -   What steps will reproduce the problem? 1. I Add <modules> <module id="cache" class="System.Caching.TSqliteCache" /> </modules> in application.xml 2. i delete the runtime What is the expected output? What do you see instead? TConfigurationException Description TContent 'LOGO' does not have a matching TContentPlaceHolder. Source File C:\MyFolder\XAMPP\htdocs\aa\protected\AppCode\lib\framework\pradolite.php (5646) 5635: } 5636: public function injectContent($id,$content) 5637: { 5638: if(isset($this->_placeholders[$id])) 5639: { 5640: $placeholder=$this->_placeholders[$id]; 5641: $controls=$placeholder->getParent()->getControls(); 5642: $loc=$controls->remove($placeholder); 5643: $controls->insertAt($loc,$content); 5644: } 5645: else 5646: throw new TConfigurationException('templatecontrol_placeholder_inexistent',$id); 5647: } 5648: protected function initRecursive($namingContainer=null) 5649: { 5650: $this->ensureChildControls(); 5651: if($this->_masterClass!=='') 5652: { 5653: $master=Prado::createComponent($this->_masterClass); 5654: if(!($master instanceof TTemplateControl)) 5655: throw new TInvalidDataValueException('templatecontrol_mastercontrol_invalid'); 5656: $this->_master=$master; 5657: $this->getControls()->clear(); 5658: $this->getControls()->add($master); Stack Trace #0 C:\MyFolder\XAMPP\htdocs\aa\protected\AppCode\lib\framework\pradolite.php(5661): TTemplateControl->injectContent('LOGO', Object(TContent)) #1 C:\MyFolder\XAMPP\htdocs\aa\protected\AppCode\lib\framework\pradolite.php(6199): TTemplateControl->initRecursive() #2 C:\MyFolder\XAMPP\htdocs\aa\protected\AppCode\lib\framework\pradolite.php(6194): TPage->processNormalRequest(Object(THtmlWriter)) #3 C:\MyFolder\XAMPP\htdocs\aa\protected\AppCode\lib\framework\pradolite.php(8333): TPage->run(Object(THtmlWriter)) #4 C:\MyFolder\XAMPP\htdocs\aa\protected\AppCode\lib\framework\pradolite.php(8299): TPageService->runPage(Object(m_ProductType), Array) #5 C:\MyFolder\XAMPP\htdocs\aa\protected\AppCode\lib\framework\pradolite.php(9285): TPageService->run() #6 C:\MyFolder\XAMPP\htdocs\aa\protected\AppCode\lib\framework\pradolite.php(8887): TApplication->runService() #7 C:\MyFolder\XAMPP\htdocs\aa\index.php(23): TApplication->run() #8 {main} What version of the product are you using? On what operating system? 3.16 Please provide any additional information below. My Name is Ricky I still nubie in prado , i want to make my project application performance more smooth. Please help me setiawan.ricky@gmail.com
    What steps will reproduce the problem? 1. I Add <modules> <module id="cache" class="System.Caching.TSqliteCache" /> </modules> in application.xml 2. i delete the runtime What is the expected output? What do you see instead? TConfigurationException Description TContent 'LOGO' does not have a matching TContentPlaceHolder. Source File C:\MyFolder\XAMPP\htdocs\aa\protected\AppCode\lib\framework\pradolite.php (5646) 5635: } 5636: public function injectContent($id,$content) 5637: { 5638: if(isset($this->_placeholders[$id])) 5639: { 5640: $placeholder=$this->_placeholders[$id]; 5641: $controls=$placeholder->getParent()->getControls(); 5642: $loc=$controls->remove($placeholder); 5643: $controls->insertAt($loc,$content); 5644: } 5645: else 5646: throw new TConfigurationException('templatecontrol_placeholder_inexistent',$id); 5647: } 5648: protected function initRecursive($namingContainer=null) 5649: { 5650: $this->ensureChildControls(); 5651: if($this->_masterClass!=='') 5652: { 5653: $master=Prado::createComponent($this->_masterClass); 5654: if(!($master instanceof TTemplateControl)) 5655: throw new TInvalidDataValueException('templatecontrol_mastercontrol_invalid'); 5656: $this->_master=$master; 5657: $this->getControls()->clear(); 5658: $this->getControls()->add($master); Stack Trace #0 C:\MyFolder\XAMPP\htdocs\aa\protected\AppCode\lib\framework\pradolite.php(5661): TTemplateControl->injectContent('LOGO', Object(TContent)) #1 C:\MyFolder\XAMPP\htdocs\aa\protected\AppCode\lib\framework\pradolite.php(6199): TTemplateControl->initRecursive() #2 C:\MyFolder\XAMPP\htdocs\aa\protected\AppCode\lib\framework\pradolite.php(6194): TPage->processNormalRequest(Object(THtmlWriter)) #3 C:\MyFolder\XAMPP\htdocs\aa\protected\AppCode\lib\framework\pradolite.php(8333): TPage->run(Object(THtmlWriter)) #4 C:\MyFolder\XAMPP\htdocs\aa\protected\AppCode\lib\framework\pradolite.php(8299): TPageService->runPage(Object(m_ProductType), Array) #5 C:\MyFolder\XAMPP\htdocs\aa\protected\AppCode\lib\framework\pradolite.php(9285): TPageService->run() #6 C:\MyFolder\XAMPP\htdocs\aa\protected\AppCode\lib\framework\pradolite.php(8887): TApplication->runService() #7 C:\MyFolder\XAMPP\htdocs\aa\index.php(23): TApplication->run() #8 {main} What version of the product are you using? On what operating system? 3.16 Please provide any additional information below. My Name is Ricky I still nubie in prado , i want to make my project application performance more smooth. Please help me setiawan.ricky@gmail.com

Earlier this year

  • Oct 07, 2009
    r2721 (Add TActiveTableCell & TActiveTableRow) committed by Christophe.Boulain   -   Add TActiveTableCell & TActiveTableRow
    Add TActiveTableCell & TActiveTableRow
  • Oct 05, 2009
    issue 187 (Documentation Errors) Labels changed by Christophe.Boulain   -   1. The both page, even if almost identical, are different. The first one talks about Content Tag (tag that can be used in template), the second one talks about Properties tag (ie, tag that can be used in component property). 2. The sqlmap tutorial shares the same theme than the quickstart tutorial, and, because the title is an image, and not a text, it shows the image from quickstart. We may fix this later, if we have some time, but it's really not the priority :) I remove the milestone information, but keep this issue opened.
    Labels: Type-Task Priority-Low Type-Defect Priority-Medium Milestone-3.1.7
    1. The both page, even if almost identical, are different. The first one talks about Content Tag (tag that can be used in template), the second one talks about Properties tag (ie, tag that can be used in component property). 2. The sqlmap tutorial shares the same theme than the quickstart tutorial, and, because the title is an image, and not a text, it shows the image from quickstart. We may fix this later, if we have some time, but it's really not the priority :) I remove the milestone information, but keep this issue opened.
    Labels: Type-Task Priority-Low Type-Defect Priority-Medium Milestone-3.1.7
  • Oct 05, 2009
    issue 193 (Problem with some dates in TDatePicker) Status changed by Christophe.Boulain   -   Can't reproduce. See screenshot of TDatePicker in QST.
    Status: Invalid
    Can't reproduce. See screenshot of TDatePicker in QST.
    Status: Invalid
  • Oct 05, 2009
    r2720 (Quick Fix from 3.1) committed by Christophe.Boulain   -   Quick Fix from 3.1
    Quick Fix from 3.1
  • Oct 05, 2009
    issue 189 (Page State corrupted - continued) changed by Christophe.Boulain   -   This issue was closed by revision r2719.
    Status: Fixed
    This issue was closed by revision r2719.
    Status: Fixed
  • Oct 05, 2009
    r2719 (Fixed Issue#189) committed by Christophe.Boulain   -   Fixed Issue#189
  • Oct 04, 2009
    issue 201 (title tag inserted before content type definition) reported by rojaro   -   If you have a content type definition in a template within a <com:THead> block, and you use $this->setTitle('foo') from within the page class (e.g. onPreInit), then the title tag will be inserted before the existing content-type definition. This is problematic if the title contains UTF-8 characters as most browsers interpret the header data in sequence ... therefore the title will be displayed before the browser knows that it contains UTF-8 chars and the output will be garbled.
    If you have a content type definition in a template within a <com:THead> block, and you use $this->setTitle('foo') from within the page class (e.g. onPreInit), then the title tag will be inserted before the existing content-type definition. This is problematic if the title contains UTF-8 characters as most browsers interpret the header data in sequence ... therefore the title will be displayed before the browser knows that it contains UTF-8 chars and the output will be garbled.
  • Oct 02, 2009
    r2718 (added Testing namespace is now being ignored when the docume...) committed by rojaro   -   added Testing namespace is now being ignored when the documentation is being generated to avoid class name conflicts
    added Testing namespace is now being ignored when the documentation is being generated to avoid class name conflicts
  • Oct 02, 2009
    r2717 (changed include('API_index.php') to lowercase api_index.php ...) committed by rojaro   -   changed include('API_index.php') to lowercase api_index.php as most non-Windows platforms are case- sensitive about filenames.
    changed include('API_index.php') to lowercase api_index.php as most non-Windows platforms are case- sensitive about filenames.
  • Oct 02, 2009
    r2716 (php 5.3 compatibility fixes ) committed by rojaro   -   php 5.3 compatibility fixes
    php 5.3 compatibility fixes
  • Oct 02, 2009
    r2715 (upped memory limit of phpDocumentor ) committed by rojaro   -   upped memory limit of phpDocumentor
    upped memory limit of phpDocumentor
  • Oct 02, 2009
    r2714 (upped memory limit for phpDocumentor ) committed by rojaro   -   upped memory limit for phpDocumentor
    upped memory limit for phpDocumentor
  • Oct 02, 2009
    r2713 (added missing prado::using() call for TCallback ) committed by rojaro   -   added missing prado::using() call for TCallback
    added missing prado::using() call for TCallback
  • Oct 02, 2009
    r2712 (updated the phpdoc package namespace ) committed by rojaro   -   updated the phpdoc package namespace
    updated the phpdoc package namespace
  • Oct 02, 2009
    issue 173 (Improvement: coordinates and key status for drag&drop) Status changed by Christophe.Boulain   -   Thanks, that's was my idea, after looking at sourcecode of dragdropextras. So, commited in r2771. It should be mostly compatible with previous version. At least, running the QST demo without modifying anything still works. Many thanks to you "googlenews" :)
    Status: Fixed
    Thanks, that's was my idea, after looking at sourcecode of dragdropextras. So, commited in r2771. It should be mostly compatible with previous version. At least, running the QST demo without modifying anything still works. Many thanks to you "googlenews" :)
    Status: Fixed
  • Oct 02, 2009
    r2711 (Enhancement on drag & drop controls.) committed by Christophe.Boulain   -   Enhancement on drag & drop controls.
    Enhancement on drag & drop controls.
  • Oct 02, 2009
    issue 173 (Improvement: coordinates and key status for drag&drop) commented on by google...@pcforum.hu   -   Yeah, this is because with superghosting a new copy of the original "control" (DOM node) is created, so it can be moved outside/independent of it's original parent (parent in the DOM). Therefore the control ID you will get in the drop zone will that of the clone's, not that of the original. I have implemented a work-around for that in my dropcontainer-descendant, which is not bullet-proof, but should work as long as you don't create any droppable's with and id beginning with 'clone_'. That should be stated in the docs.
    Yeah, this is because with superghosting a new copy of the original "control" (DOM node) is created, so it can be moved outside/independent of it's original parent (parent in the DOM). Therefore the control ID you will get in the drop zone will that of the clone's, not that of the original. I have implemented a work-around for that in my dropcontainer-descendant, which is not bullet-proof, but should work as long as you don't create any droppable's with and id beginning with 'clone_'. That should be stated in the docs.
  • Oct 02, 2009
    issue 173 (Improvement: coordinates and key status for drag&drop) commented on by Christophe.Boulain   -   I won't commit till I found why the ID is not good. If you want to test, apply the attached patch, against latest trunk, from framework dir. Go the drag&drop qst demo, and add Ghosting="SuperGhosting" property to the draggables item. And look at firebug console when dropping an item.
    I won't commit till I found why the ID is not good. If you want to test, apply the attached patch, against latest trunk, from framework dir. Go the drag&drop qst demo, and add Ghosting="SuperGhosting" property to the draggables item. And look at firebug console when dropping an item.
  • Oct 02, 2009
    issue 173 (Improvement: coordinates and key status for drag&drop) commented on by Christophe.Boulain   -   I just made some test. It seems everything works, except superghosting. If I vardump my callbackparameter, here's what I got : stdClass#1 ( [DragElementID] => 'clone_ctl0_body_ProductList_ctl1_ctl0' [ScreenX] => 326 [ScreenY] => 602 [ClientX] => 326 [ClientY] => 471 [AltKey] => false [CtrlKey] => false [ShiftKey] => false ) Look at the DragElementId, it's clone_XXX. Is this normal ? It's ok with basic "ghosting".
    I just made some test. It seems everything works, except superghosting. If I vardump my callbackparameter, here's what I got : stdClass#1 ( [DragElementID] => 'clone_ctl0_body_ProductList_ctl1_ctl0' [ScreenX] => 326 [ScreenY] => 602 [ClientX] => 326 [ClientY] => 471 [AltKey] => false [CtrlKey] => false [ShiftKey] => false ) Look at the DragElementId, it's clone_XXX. Is this normal ? It's ok with basic "ghosting".
  • Oct 02, 2009
    issue 173 (Improvement: coordinates and key status for drag&drop) commented on by Christophe.Boulain   -   Like said above, I changed the Event parameter to put the id of dropped control instead of the full control. But to stay compatible, I added a method in the event parameter which try to get the dropped control, if possible. I changed the type of Ghosting property to an enum of 'None','Ghosting','SuperGhosting', but I also allow "true" or true, or "false" or false, still, to stay at most compatible as possible. I'll certainely commit the stuff before the end of the afternoon (GMT+2)
    Like said above, I changed the Event parameter to put the id of dropped control instead of the full control. But to stay compatible, I added a method in the event parameter which try to get the dropped control, if possible. I changed the type of Ghosting property to an enum of 'None','Ghosting','SuperGhosting', but I also allow "true" or true, or "false" or false, still, to stay at most compatible as possible. I'll certainely commit the stuff before the end of the afternoon (GMT+2)
  • Oct 01, 2009
    issue 173 (Improvement: coordinates and key status for drag&drop) commented on by google...@pcforum.hu   -   There you are. In this component I added an extra Superghosting property in the class, which can be used to turn the extra feature on. However, the best would be to change the original Ghosting property of TDraggable to an enumerated type (from the boolean) to accomodate support for both simple ghosting and superghosting as they're conflicting - mutually exclusive - settings. This would break compatibility of course, but would be a more straightforward solution than using two independent boolean fields.
    There you are. In this component I added an extra Superghosting property in the class, which can be used to turn the extra feature on. However, the best would be to change the original Ghosting property of TDraggable to an enumerated type (from the boolean) to accomodate support for both simple ghosting and superghosting as they're conflicting - mutually exclusive - settings. This would break compatibility of course, but would be a more straightforward solution than using two independent boolean fields.
  • Oct 01, 2009
    issue 200 (TShellApplication / startService) reported by stbland   -   The code below fails if the page service isn't defined in the XML configuration file because the startService method is called $application=new TShellApplication($configurationPath); $application->run(); To bypass this problen, I use the code below : class TBatchApplication extends TShellApplication { public function startService($serviceID) { // Starts nothing, don't start page service } } $application=new TBatchApplication($configurationPath); $application->run(); -- Prado version : 3.1.6.r2699
    The code below fails if the page service isn't defined in the XML configuration file because the startService method is called $application=new TShellApplication($configurationPath); $application->run(); To bypass this problen, I use the code below : class TBatchApplication extends TShellApplication { public function startService($serviceID) { // Starts nothing, don't start page service } } $application=new TBatchApplication($configurationPath); $application->run(); -- Prado version : 3.1.6.r2699
  • Oct 01, 2009
    issue 173 (Improvement: coordinates and key status for drag&drop) commented on by rojaro   -   Yes please :)
    Yes please :)
 
Hosted by Google Code