Show
Ignore:
Timestamp:
03/26/07 02:43:56 (20 months ago)
Author:
alex
Message:

adding note about configuration option change. Still haven't decided on new name for djConfig if it is going to be moved.

Files:
1 modified

Legend:

Unmodified
Added
Removed
  • branches/api-spec/alex/refactor.txt

    r7720 r7791  
    426426by Eugene. 
    427427 
     428configuration: 
     429-------------- 
     430 
     431Earlier versions of Dojo allowed the djConfig variable to provide a 
     432"allowQueryConfig" boolean flag in order to take debugging information from an 
     433easily modified location. This, however, required explicit permission from the 
     434djConfig flag which itself required its own <script> block. This was onerous 
     435and rarely used. It is also being replaced in 0.9 with a simpler system. 
     436 
     437Instead of requiring at *least* one extra <script> tag to configure Dojo, the 
     438system now supports a djConfig attribute on the <script> element which is used 
     439to include Dojo into the page. The value of this attribute much be well-formed 
     440JavaScript object literal syntax. Previously, putting Dojo into debugging mode 
     441required syntax such as this: 
     442 
     443    <script type="text/javascript"> 
     444        djConfig = { 
     445            isDebug: true, 
     446            useXDomain: true 
     447        }; 
     448    </script> 
     449    <script type="text/javascript" src="/path/to/dojo.js"></script> 
     450 
     451Could now be written as: 
     452 
     453    <script type="text/javascript"  
     454        djConfig="isDebug: true, useXDomain: true" 
     455        src="/path/to/dojo.js"></script> 
     456 
     457Note that the prior syntax is still available, but is not likely to be 
     458advantageous since the new variation is smaller and easier to use. 
    428459 
    429460The Split: