GSOC15 adventuring

checking out code

I had a check in with the main author. He still has to give me rights to check-in/check out code with subversion, but he will also try to give me github access. I think he's unfamiliar with the pull request format of github or i'm unfamiliar with the checkout/check-in features. I demo'd the index page of weblogo and he likes improved look. He wants to keep the minimal look and isn't looking for major changes to overall design. I got the fluid divs to scale properly using the firefox inspector console in time for the check-in demo

Fluid container divs

The div demarcations is progressing. I used CSS to help delineate and troubleshoot where all the div containers end and begin. Controlling where boxes within boxes within boxes sit on the page become a difficult mental abstract. Bootstrap uses jquery to help control the fluid actions of the page, and in my current implementation the divs are not yet fluid and do not scale properly yet.

Laying Divs for about page

Worked out more sorting out divs on Bootstrap's grid system for fluid containers. Researched Dropbox's drop-in API for inclusion for the front-end.

laying out html and consulting with Amazon Web Services

I started to play with setting up div tags to replace the hard coded table tags. nesting divs can be tricky and visualizing where the divs sit are harder than hard coded table tags. I scheduled a code walkthrough with the main author, and I proposed a consultation with AWS consultants at the Amazon's "pop-up" loft since porting WebLogo is main goal for the project.

research: no .cgi on heroku

After the initial fail to push to heroku for the .cgi script, I wrote a stripped down flask app to initialize all the html pages to push to heroku. I left the .cgi file in the root directory however. After some serious snooping on stack overflow and the web, it looks like .cgi files require deep knowledge of heroku's platform and python. I'll try deleting the file from the folder I'm trying to push to heroku. I also reviewed the documentation for the bootstrap framework. I'll be using their responsive design grids and classes for WebLogo.

Flask app to consolidate front-end

I worked on a flask app to consolidate the WebLogo html pages for porting to heroku. I'm using flask as a proof of concept to skip the .cgi layer to show the main author. Today is a holiday in the United States, but I contacted the main author to confirm a code review session for the python engine.

Setting up Enviroment: Hardware and Investigating Code respositories

I'm upgrading my physical coding environment to work from home. I currently only work on my laptop, but this would be injurious for a long term project. I've been to physical therapy twice already for neck & shoulder problems. I'm improving my ergonomic setup with a monitor a separate keyboard and mouse. I'm considering a monitoring arm as well. I have to remember to make the machine adapt to me instead adapting me to machine. I also queried a mentor about different code repositories since WebLogo needs to be ported before the end of the summer. GitLab appears easier to use & BitBucket is free, the consensus was that GitHub was where the hive mind has accumulated and congregated. Hosting code here could lead to more collaboration and interest in WebLogo.

Setting Up Environment: reading Flask docs

I read python's flask documentation to try to resolve the push to Heroku problem. I'm wondering if I can just "trick" Heroku's servers into accepting all the files as a Flask web app. The problem got me thinking whether recoding how the front end works with the back end should be part of this summer's project. The .cgi solution feeds the html form's information to the python-run engine predates python-based Flask or Django solutions. Refactoring how the back end handles serving the WebLogo tool is out of the scope of this summer's project. Refactoring probably invites a host of new problems, but it removes a layer of complexity for WebLogo for the future. However, if it ain't broke...

Setting Up Environment: push to Heroku

I worked through the Heroku getting started tutorial to launch python apps. I set completed the set up properly, but failed to push the current working code to Heroku. I think Heroku doesn't know how to read the .cgi files to launch the complete WebLogo app? I'm wondering if updating the current code to integrate python's flask web app library will be a part of the this summer's project.

Setting Up Environment: Heroku tutorial

I'm working on learning how to push code from github to heroku. I downloaded the toolbelt for windows for install and will be working through the heroku python tutorial.

Syndicate content