It's been a very busy last couple of weeks, unfortunately busy with roadblocks. Progress has been slow but I feel like I've been learning a lot about the OHM codebase and that this will help further down the line.
Week 3: June 2 to June 9[edit | edit source]
- Snagged TimeSlider code from themusictree.net website
- Continuing work on getting the slider integrated into the website and I'm learning:
- Building consensus can be hard - there are a lot of differing opinions over what the TimeSlider should look like and how it should function.
- While I know Rails, finding one's way around a new code base can be tricky, to say the least. I'm using the Rails UI Wiki page and this Guide to Erubis to try to lead the way.
- I'm still working on getting the slider working but I've got the text fields showing, at least.
- They needed a lot of tweaking to fix and flex to the space of the site. My branch is posted on Github.
Week 4: June 9 - June 15
- After consultation with my mentor, we were both stumped so we reached out to the author of the slider for tips and toward the end of the week, we finally synced and got the slider working! The slider required a change from rendering a single object to iterating through a group of divs to create the sliders.
- While I was waiting to work with the slider-creator, I started investigating methods for having a form in Rails have two separate actions, depending on the button clicked. It's apparently a little non-REST-full, but there are some REST-like options:
- using the params and embedding if statements into the controller or
- capturing the name of the button that is clicked.
- I also cast about for other options that might be more understandable for me (this was a plan Z option, in case I never was able to connect with the original author.) I found a few nice options including nouislider.
- Received a last-minute invite to the OHM/OSM Hangout at the @SotMEU Conference on June 13th.