Quick links: Content - sections - sub sections
EN FR

Trace:

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
en:changelog:1.4 [2012/05/10 07:58] – laurenten:changelog:1.4 [2012/06/09 07:48] – laurent
Line 26: Line 26:
 ===== Migrating from Jelix 1.3.x ===== ===== Migrating from Jelix 1.3.x =====
  
-  * **READ THE [[en:manual-1.4:installation:migrate|MIGRATION TUTORIAL]]**. (not available yet)+  * **READ THE [[http://docs.jelix.org/en/manual-1.4/installation/migrate|MIGRATION TUTORIAL]]**.
  
   * your entrypoints should be changed:   * your entrypoints should be changed:
Line 34: Line 34:
   * you are encouraged to replace all your $gJConfig/$gJCoord use by jApp::config() and jApp::coord().   * you are encouraged to replace all your $gJConfig/$gJCoord use by jApp::config() and jApp::coord().
  
-===== Details of changes in 1.4a1pre =====+===== Details of changes in 1.4b1 =====
  
 ==== Enhancements ==== ==== Enhancements ====
Line 43: Line 43:
     * New HTTP cache API on response object: cleanCacheHeaders(), setExpires(), setLifetime(), isValidCache(). @FlorianLB     * New HTTP cache API on response object: cleanCacheHeaders(), setExpires(), setLifetime(), isValidCache(). @FlorianLB
     * jXmlResponse allow now to specify your own mime type. @Thomas PT      * jXmlResponse allow now to specify your own mime type. @Thomas PT 
-    * in the configuration, we can indicate a response class which is in a module. Syntax: @@{responsetype}=module:{modulename}:{classname}@@. And the response class should be store into a @@F@{modulename}/responses/{classname}.class.php@@.+    * in the configuration, we can indicate a response class which is in a module. Syntax: @@{responsetype}=module:{modulename}~{classname}@@. And the response class should be store into a @@F@{modulename}/responses/{classname}.class.php@@.
     * Methods isModuleEnabled and getModulePath have been moved from jCoordinator to jApp. These methods are still availabled on jCoordinator but deprecated     * Methods isModuleEnabled and getModulePath have been moved from jCoordinator to jApp. These methods are still availabled on jCoordinator but deprecated
     * new class jAutoloader, to be used as a class autoloader     * new class jAutoloader, to be used as a class autoloader
Line 75: Line 75:
  
   * none   * none
 +
 +
 +===== Details of changes in 1.4pre =====
 +
 +==== Enhancements ====
 +
 +==== Bugs fixed ====
 +
 +  * none
 +
  
 ---- ----

en/changelog/1.4.txt · Last modified: 2012/08/30 11:21 by laurent

Recent changes RSS feed Creative Commons License