GSOC15 adventuring

Setting Up Environment: Hosting Test Site on Heroku via Github

I found that I can use Heroku's services from Github for free. I can try to serving WebLogo on Heroku so I can test changes while I work. Heroku apparently is fussy at first, and it can require a high learning curve. I practiced using powershell with Git and I'm thinking that I may not continue with Komodo after the trial period if I manage with powershell.

Community Bonding: Introduction

I introduced myself to the WebLogo discussion board. I introduced my project on working on the front-end and updating the API. I'm interested in hearing what the community's needs are. I think I should set up a test hosting environment as a place to invite the weblogo community to test functions.

Setting Up Environment: Reinstalling Python

I reinstalled Python to work with the Komodo IDE. Installation was error free and the ide worked as expected. I wrote some test python script for a web server and I could run the script and debug from the ide and get responses from the local host. The ActiveState installation seems more robust than the canopy install.

setting up environment: testing ide

I downloaded and installed komodo's trial use ide for my windows machine to see if it would be useful in a windows environment. I tried running some test python script, but it didn't work. I was hoping for something that would be as easy and intuitive out of the box. I'll give it go for the trial period, but if there is too much wrangling with preferences and setting of paths, I'll forego an ide altogether. In communicating with WebLogo's main author, he thought that setting up WebLogo up on Google Cloud might not be a sound idea b/c it might not be around in 10 years. As evidenced by shutting down its code storage and other side projects' services, Google may not be committed to hosting software in the long term. It's revealing to see a long-term perspective on projects and technologies.

Setting Up Environment: Reading Codebase

I tried to look through the existing codebase. I have a good understanding about the front end code. Figuring out how the core python code fits together by myself is problematic. I reviewed tips on getting started in a codebase , and I made an appointment with the main author for a code walk through. He admitted figuring it out would be hard.

setting up environment: learning subversion

I started reading the documentation for Subversion for version control. I practiced using git with online tutorials. I started reviewing the core python code for WebLogo. I unintentionally started a little flame war last week on the gsoc mailing list. I'm processing what are the teaching and learning moments from the experience.

Community Bonding: Needs

I looked into WebLogo's google group site to check what the community needs were. Improved API documentation is on the needs list (and on my project goals), and there was a suggestion about outlining the letters in the sequence visualizations. I explored a possible solution using processing js, but I'm pretty sure that the internal guts of the visualization is not in Javascript.

Setting Up Environment: Komodo IDE investigation

I've been exploring IDE suites that would consolidate my development environment for Windows 7. I tried Enthought's Canopy, but one couldn't make full use of all python libraries without paying the full license fee. I stumbled onto Komodo IDE by ActiveState that may solve my problems with installing Python and Apache's Subversion. I think I may be able to push to changes github and WebLogo's server without leaving the development environment.

Server Up

WebLogo's server is up again. Going to read the manual. Still working on loading Subversion to my machines. Windows OS is not very friendly. Still exploring best way to use python on windows. Exploring IDE options like Komodo.

Hosting WebLogo issues

The rackspace server is messed up;WebLogo has been down for almost a week. There were discussions on moving WebLogo to Amazon Web Services or the possibility of putting WebLogo 3 on the same Berkeley Server as WebLogo 2.

Syndicate content