Working on second Release part #2

Posted: February 7, 2014 in Programming
Tags: , , , , , ,

Hello Friday!

It’s time to summarize my work for the last two weeks. My first part I described in my previous post, so I would like to give you new information on the bugs and features I am working on right now.
Honestly, I am becoming more and more supportive to the Open Source Development. 🙂

I continue my contribution to the CSP Implementation to the different webmaker components. Right now I’m helping with popcorn. The whole CSP feature was separated into the small bugs, to let the process goes more efficiently and easy to follow. I fixed these two bugs:

  • bug 965048 – changing Soundcloud protocols to https://
  • bug 965049 – changing Vimeo protocols to https://

This is a step to the CSP Implementation, I would be happy to be involved to the more difficult and more back end programming, either with CSP or pre CSP stages.

The other type of work I am working on, and right now waiting for the review and more info is the login.webmaker.org component. I found a bug on bugzilla -> bug 963305, that is saying that there should be a user profile page (e.g. user.makes.org) shown inside the user profile page. I decided to implement that. So the steps are:

  • Add HTML so the user can see his/her profile page in text – Done
  • Set the profile link in account.js file, that adds a new class – Done
  • Create a new environmental variable and parse it to the login page – Done, waiting for review
    • Create a new var in .env and env.sample files
    • Parse var into page with nodejs’s habitat module -> more info on habitat module here and express module, locals method -> more info here. Basically requiring habitat module gives you access to the varName.get(exportedVarName);, method that parses the exported variable.
      http.locals({
          AUDIENCE: env.get("AUDIENCE"),
          profile: env.get("PROFILE"),
          supportedLanguages: i18n.getLanguages(),
          listDropdownLang: i18n.getSupportLanguages()
        });//exported variable 'PROFILE' assigned to variable 'profile'
    • Assign parsed variable to the user profile page in text:
      $( ".wm-page").text( username + "{{ profile }}" );

      – where ‘profile’ is a parsed variable.

    • Show it on the profile page:
      <li><span class="field-label">{{ gettext('My profile') }}</span><span class="wm-page"></span></li>

Looking for more bugs and more involvement into Open Source Environment.
See you.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s