28 Apr, 2010

3 commits


26 Apr, 2010

3 commits


19 Apr, 2010

1 commit


16 Apr, 2010

5 commits

  • (ActionItem1396)
    
    Signed-off-by: Antonio Terceiro <terceiro@colivre.coop.br>
    Rodrigo Souto
     
  • (ActionItem1455)
    Daniela Feitosa
     
  • * Folders are being filtered in the slideshow's block.
    
    (ActionItem1447)
    Rodrigo Souto
     
  • (ActionItem1482)
    Antonio Terceiro
     
  • * The registration has two validation type: region and admin.
    		+ Admin
    			- There is no validator to choose.
    			- The regions to choose are states (This might be changed
    			  in the future).
    			- The admins of the environment recieves the task to approve
    			  the registration of this new enterprise.
    			- The region field isn't displayed.
    		+ Region
    			- If there isn't any validator, shows a message that it's
    			  not possible to register any enterprise and don't show the
    			  form.
    			- Show only the regions where is registered at least one
    			  validator.
    			- The region field is displayed.
       	* The required fields are highlithed.
    	* The fields that are active or required are set through the
    	  administration panel.
    	* Only the fields name and identifier are always required.
       	* After registering a new enterprise, the user is set as an admin of
       	  it.
       	* The cancel button in the register form is working properly.
       	* In the "Validator" step, the radio button is choosing a default
       	  option.
       	* Cancel radio_button in the task validation has a "Rejection
       	  Explanation" field that is required.
       	* Some navigation buttons added.
       	* Changed some buttons to labelled buttons.
    	* The "Register a new enterprise" button is an admin option.
    
    (ActionItem1482)
    Rodrigo Souto
     

14 Apr, 2010

2 commits


08 Apr, 2010

1 commit

  • This commit introduces a lot of changes in the HTML generated by Nosfero
    with the intent of making it load faster on users' browsers. This
    includes:
    
      * Adding apache configuration for compression of text content and
        aggresive cache policy (caching assets for 1 month)
      * Drastically reducing the number of stylesheets and javascript files
        referenced in the HTML.
      * The remaining CSS and Javascript files are now cached in a single file
        (one CSS file and one Javascript file) so that clients will only
        request a single file instead of several ones (and thus requiring a
        single HTTP connection instead of several ones).
      * Making sure that all assets referenced in the code have a timestamp
        (?21083219837) in the end of the URL so that when they are updated the
        client will fetch them again.
    
    During the course of the implemeantion, some other changes were made:
    
      * Updated INSTALL file with documentation about apache configuration for
        production environments.
      * Marked as deprecated all methods that use stylesheet_import, as well
        as stylesheet_import itself.
      * Removed "better browser promotion" code. It sucks.
      * Unifyed Noosfero stylesheets)
      * Unifyed stylesheets in the base theme
      * Enhanced the sample-data script with the creation of random events.
        in a range of 60 days around the current date, so that there will be
        events in the previous month, in the current month and in the next
        month.
      * Removed unused cms.js
      * Updated .gitignore example to ignore cached CSS and Javascript files.
      * Updated git-upgrade script to remove cached CSS and Javascript files.
    
    (ActionItem1425)
    Antonio Terceiro
     

05 Apr, 2010

4 commits

  • Besides being faster, consumming less memory, and being thread-safe,
    fast_gettext's approach is cleaner than Ruby-GetText's because it does not
    mess with the Rails internals. That's probably due to the fact that
    fast_gettext was designed after Rails had proper I18N support, so that's
    not exactly Ruby-GetText's fault. Current versions of Ruby-GetText are
    claimed to be thread-safe as well, but I decided to go with fast_gettext
    regardless.
    
    I am messing with the Rails internals myself by copying some code from
    Ruby-Gettext, but that code will be dropped when we upgrade to a more
    recent Rails version with proper I18N. Code was copied from Ruby-GetText
    to implement:
    
        * per-language cache
        * validation error messages translation
    
    During initialization, the needed .mo files installed system-wide are
    symlinked locally.  By doing this we can take "similar" locales locally
    since fast_gettext does not seem to support loading of files from similar
    locales (e.g.  loading pt_BR/LC_MESSAGES/domain.mo when
    pt/LC_MESSAGES/domain.mo is not available).
    
    This hopefully will fix the long-standing bug with messed up translations
    due to high concurrency and non-thread-safety of the version of
    Ruby-GetText in Debian Lenny.
    
    (ActionItem1315)
    Antonio Terceiro
     
  • Antonio Terceiro
     
  • They are need in DocControlller tests as well in order to not depend on
    the docs being built during tests
    Antonio Terceiro
     
  • Antonio Terceiro
     

31 Mar, 2010

1 commit


30 Mar, 2010

1 commit


26 Mar, 2010

6 commits


24 Mar, 2010

1 commit


17 Mar, 2010

1 commit


15 Mar, 2010

1 commit


08 Mar, 2010

1 commit


05 Mar, 2010

1 commit


26 Feb, 2010

3 commits


08 Feb, 2010

1 commit


05 Feb, 2010

4 commits