Squadly Dev Post #3, UI Polish and Git Tweaks

At this point someone using Squadly can:

  • Register/login/logout
  • Create Events

We're hoping to enable Squadly to advertise events via a user's Facebook or Twitter account, but that'll come wayyy later.

Anyways, Mike added some Bootstrap Magic to the plain pages I created. We're getting ready for a usability test where the class invites guests to try out their apps. During this testing phase, anything that is not yet implemented should be removed.

A requirement for this phase is to write a series of actions for the tester to exercise. We also need to ensure that the application can be used to the fullest extent. Nothing should break, so we need to make sure that the actions we create cover all of the above, taking note of the tester's experience along the way.

One problem we ran into recently was pushing code. Apparently, Mike couldn't push local commits to the VPS that Squadly is sitting on. The specific error Git Push Error: insufficient permission for adding an object to repository database. I cloned the repository from another VPS and tried making a push - no good. A Google search on the error revealed to us that we needed to do a bit of work to get the repo ready for multi-user use. First of all, we needed to make the repo a shared repository by executing git config core.sharedRepository group. Secondly, we needed to ensure that all files of the repo are apart of the same group of users that will be manipulating the files. This required us to add our accounts under a new primary group and change permission of all of the files in the repo to the same group. The Stack Overflow Thread that saved us hours of headache is here, checkout the example by Richard Hansen. After diagnosing the problem and following the steps, pushing to Squadly worked like a charm. The next task at the moment is adding AJAX support.

With about a week to go before the usability testing, we're hoping to get a few of the tiny but very important fixes in before the end of the weekend such as field validation and page flow (is that what it's called? The page 'flow' that a user can view when navigating the app).

What's Next
  • yet more polish
  • even more tweaking
  • APIs