Rensselaer Center for Open Source Software

tom yang

Most of the last few weeks have been spent implementing various UX features for the Rails Application. Music, transitions, facebook auth, and exercise models are now fully implemented. Some problems encountered include browser compatibility issues for music and also encrypting local environmental variables for facebook authorization. Sometimes the facebook login still does not work due to an error reading the parameter app_id, and I am looking into using a Rails gem to help solve this issue. A functioning restful API is almost fully fleshed out with our Rails application and this will be used for the next stage in project development, IOS!

Today, I finally bought my first Macbook (so psyched) and can finally begin my IOS dev journey. Moving forward, I plan to build out a functional IOS app demo by the end of the semester. Right now I am going through various online IOS dev courses and since I've already spent time designing iChode UI, transitioning to app development should be very smooth; we're very excited to give all gym rats the app they deserve!

iChode • 18 hours ago
Derek Meer

So I got the code to compile and link today.  Hooray!

A slight problem, however.

The code currently uses 110% of the microcontroller's SRAM, so I'll probably need to spend some time making that value smaller. Perhaps we'll have to find a more suitable microcontroller.

That's going to happen in the next week while the boards are finalized and ordered. But hey, at least the code compiles!


Zaran Lalvani

This past week I've been working on the Sia Simulator application. Its purpose is to handle all Sia API calls in a controlled environment without actually using the Sia daemon. Specifically, I've been working on a few renter methods, which are needed for developing the new Dart Sia interface.

Blake Lingenau

So originally our database was updated using python. It would make the API calls and interpret the JSON that it returned and load it into the database. After timing it, this took 30 minutes. This seemed like too long f a time. I decided to give Node.js a try. I have never used javascript or Node.js so this was definitely a learning experience. I was having a lot of trouble with my code because I had no idea about the need for callbacks. In the end, I got a Node.js database updater up and running. When I timed this program, it only took 3 minutes to update every item's information. This was a big improvement over the python script. We will continue forward with Node.js to pull data from the database and display it on our website.

Peter Ryder

The next few weeks won't be about new feature but about cleaning up some of the old code specifically in respects to how the graph is displayed

Next Page