Hi again
First of all, I've finally partly solved my problem with the migration to 0.8.1. It may be evident, but *i had not cleared the "cache"* between 0.8 and 0.8.1 and that was making python errors in the dependancyloader. If anyone encounters the problem.. :-) Now the build version is working good but.... the source is not!! Again, I've checked and rechecked but it seems to me that in source mode, my libraries URI are not computed correctly. I've tried skipping the "uri" key (like it's now authorized in 0.8.1) or putting it back, there's no way, the generated source does not locate correctly the classes that are in the library, thus the application won't load. My libraries are defined by me (not contrib ones) and located in a different folder that the one containing the source.
Has anyone tested that?
Thanks
Charles

PS : Interesting parts of my config.json below :

 "let" :
 {
   "APPLICATION"  : "org.argeo.ria",
   "QOOXDOO_PATH" : "src/main/webapp/qooxdoo-0.8.1-sdk",
   "QXTHEME"      : "qx.theme.Modern",
   "QXICONTHEME"  : ["Tango"],
   "API_EXCLUDE"  : ["qx.legacy.*"],
   "LOCALES"      : [ "en" ],
   "ROOT"         : "src/main/webapp/argeo-ria-src",
   "BUILD_PATH"   : "src/main/webapp/argeo-ria",
   "RIA_LIB_PATH" : "src/main/webapp/argeo-ria-lib",
   "RIA_LIB_URI"  : "../argeo-ria-lib",
   "CACHE"           : "cache-0.8.1" ,
   "CUSTOM_PACKAGE" : "org.argeo.slc.web"
 },

 "jobs" :
 {
   "common" :
   {
     "library" :
     [
       {
         "manifest" : "${QOOXDOO_PATH}/framework/Manifest.json"
       },
       {
         "manifest" : "${RIA_LIB_PATH}/slc-web/Manifest.json",
         "uri"         : "${RIA_LIB_URI}/slc-web"
       },
       {
         "manifest" : "${RIA_LIB_PATH}/slc/Manifest.json",
         "uri"         : "${RIA_LIB_URI}/slc"
       },
       {
         "manifest" : "${ROOT}/Manifest.json"
       }
     ],

     "include" :
     [
       "${APPLICATION}.Application",
       "${CUSTOM_PACKAGE}.*",
       "${QXTHEME}"
     ],

     "cache" :
     {
       "compile" :  "${CACHE}"
     },

     "settings" :
     {
       "qx.version"     : "${QXVERSION}",
       "qx.theme"       : "${QXTHEME}",
       "qx.application" : "${APPLICATION}.Application",
"ria.StartupPerspective":"org.argeo.slc.web.LauncherPerspective" }
   },

   // -- source jobs --------------------------------------------------

   "source-script" :
   {
     "extend" : ["common"],

     "compile-source" :
     {
       "file" : "${ROOT}/script/${APPLICATION}.js",
       "locales" : "${LOCALES}",
       "root" : "${ROOT}",
       "gzip" : false
     }
   },




Derrell Lipman (via Nabble) a écrit :
On Sun, Jan 18, 2009 at 10:36 AM, Charlie_fr <charle...@... <http://n2.nabble.com/user/SendEmail.jtp?type=node&node=2177373&i=0>> wrote:


    But to
    stick to the initial topic of this message, I've tried the close()
    method
    and terminate() method of my Application class, and it seem to me
    that the
    terminate() is still never called. Is the bug really verified for
    0.8.1 ?
    The close() method is working good.


It seems that at least in Firefox, the "beforeunload" event which causes the close() method to be called gets fired, but the "shutdown" event which is supposed to cause the terminate() method to be called does not. This was tested by putting an alert() call in each of the low-level handlers in qx.core.Init. Maybe there's some event other than "shutdown" that must be listened for in Firefox, for an after-unload event.

Maybe you can make due with the close() method which is fired immediately before the page is unloaded? What do you need to do that must occur after the page is entirely unloaded?

Derrell
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-de...@... <http://n2.nabble.com/user/SendEmail.jtp?type=node&node=2177373&i=1>
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel


------------------------------------------------------------------------
This email is a reply to your post @ http://n2.nabble.com/Window-unload-action-tp2161752p2177373.html
You can reply by email or by visting the link above.


------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to