Changes between Version 26 and Version 27 of GSOCWebSetupImplementation


Ignore:
Timestamp:
04/06/11 03:49:22 (11 years ago)
Author:
anubhav
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GSOCWebSetupImplementation

    v26 v27  
    77==== Def setting(): ====
    88
    9 These will be imported into the models of the web setup so will run before the models .The settings layout needs to be stored in here.
    10 The settings is a dict with keys as the:
     9We will copy this file from Eden ( s3cfg can be changed to generated this file during its run )into the modules of Web Setup and make it run. These would be locally imported in the Models so they will be executed first:
    1110             “categary”.”field_id”
    1211                   
     
    2726These are really useful for views as this provide the information regarding input type, the value to select from, the field name and the validation requirement. These layouts are mostly for the views. Some of these like port will also contain a validation field for the range of accepted values.
    2827
    29 These will be added in the modules of Eden so that they can be later be used to reduce the redundant code from s3cfg and 000_config.py.
    30 We will copy that file into the modules of Web Setup and run this file.
    31 
     28==== Change in s3nfig to generate the dict shown above ====
     29
     30{{{
     31
     32changing s3cfg to generate this dict
     33
     341. Write
     35    a."settings = {" in the starting of the dict
     36    b.settings_type + "." + settings_name in each get function
     37    c.also specify the details like input type over there.
     38   
     39
     40}}}
     41
     42Thus only s3cfg will contaon all the dict .
     43
     44After gsoc we can also change s3cfg in the starting to generate 000_config if it is the first time of run
    3245
    3346==== Def modules() : ====