GSOC15 adventuring

Research Github

Exporting the Google discussion forums is not possible according to the Github support. They punted back the issue back to Google as Github did not provide a migration path for this feature of Google code. The Github exporter will port issue tracking of 1000 items or less. Projects tracking over 1000 issues will have to be exporter manually. And they confirmed the feature that my fellow PSU GSOC-er lead me saying that tarballs are hosted under Github's release feature. Lastly, GitHub doesn't provide download counts for repository archive files, and only provides download counts for release assets. I updated the main author with these results, and hopefully we will accomplish this project benchmark this week.

Mid-term Evaluation

I submitted the Mid-term Evaluation today. I'm glad Professor Massey sent out the reminder. I knew the evaluation was due soon in the abstract, but the email reminder prompted me to hoist the evaluation to the top of the day's priorities. I had a little trouble finding the link in the melange site, and maybe Google administrators should let GSOC-ers know that the evaluation link can be found under "My Dashboard" link. I kept following links to the FAQ and timeline to roundabout dead-ends. Nevertheless,I'm glad to for a way to register my appreciation of the GSOC opportunity and of the PSU community's support and good will. Otherwise, I'm chipping away at the Github export issue, and a fellow PSU GOSC-er gave me a good lead on hosting tarballs under Github's "release" function. I'm grateful for the helpful community PSU is cultivating. He beat Github to delivering a solution to that question.

More Github Research

I'm still researching how to port all the features that the main author wants from Google Code to Github. Some of them I don't think are possible. For example, hosting tarballs so Weblogo can be easily installed without forking or checking out code is a feature i've never seen on Github. Exporting issue tracking may be possible, but you have to write and execute a separate python function. These porting issues are all beyond my current experience using Github, and Google may not be highly invested in writing good documentation for a project it's expiring. Given the lack of documentation, I reached out to someone at Github for more assistance. While the issue is being researched, I'll keep plugging away at sorting the Dropbox bug.

Dropbox drop-in

I'm working on the create page incrementally as I study the github documentation. I'm trying to add the dropbox function using it's drop-in javascript code. I've having trouble getting the function appear in the DOM. I'll keep on debugging the dropbox integration.

Github research

I'm reading Github docs and stack overflow regarding Github migration. Also, I'm experimenting with layouts for the create.html page.

Github migration

I've been tasked with researching migrating weblogo's code to github. I was finally added as a contributor to the github repository. Porting the code to a new repository is central goals of the GSOC project. Unfortunately it's not as easy as copying the repository. The main author asked me to research: how to port discussion forum to github, how to port issue tracking transfer from google code to github, how to track downloads, how to host tarballs for installation on github.

First Design Review session

I'm in the middle of refactoring the the create.html pages. I have two working drafts, one horizontally and another vertically oriented. With these pages in hand, I did a check-in with the main author. The improved layout for the manual page was acceptable. I now have feedback on the organization of the elements of the create.html page. The sequence input window needs to be at least 80 characters wide, which I hadn't known before, because the data sets are often wide. My horizontal layout privileges the WebLogo Controls at the sacrifice of the sequence data input. However,there isn't a need to have all the control elements be in a vertical orientation. I mocked up a large button that would replace the two small buttons that were needed when the page scrolled vertically. He said the large button was ok as long as people see the button. I'll have to plot out a new layout that takes these restrictions into consideration.

Dropbox integration

I had a check-in with the main author & he's pleased with the progress. He still needs to get me access to properly checkout/check-in code. We decided on the javascript implementation of the Dropbox API for opening files. I made an appointment with an Amazon Web Services Engineer to discuss options for porting and hosting WebLogo for next week. I will start working on the buttons and forms for the create page.

Studying Cloud Storage

I've started studying the documentation for Dropbox's API for inclusion into the create page, while I work on the create page divs. I need to open a discussion with the main author about whether to choose the javascript option for the frontend or the python option. Integrating Dropbox python api with the main WebLogo functions may be problematic. I think keeping the dropbox function within the front-end functions may be the optimal choice. I may also experiment with the google drive api as well.

studying UX

WebLogo's interface was designed in the age of smaller monitors. It scrolls vertically, and all the options fall "under the fold" to use a printing term. Most of the space is occupied by a large textbox. Such a large textbox isn't necessary, and I'm trying to layout the options so everything on the page can seen immediately. It's a complicated system of nested divs, and the heights of the columns aren't even. So i'm working on that. The current scope is to only make the create page responsive, but I'm hoping to have horizontal and vertical pages for possible testing by the WebLogo community. I contacted someone familiar with User Experience design for advice on making the interface feel more intuitive.

Syndicate content