Sorry, I am new to this and am not sure if you have reviewed the Php_DB_Setup.php file I uploaded that should create a DB, add a super user, and create three tables. The first table, Users, is how you would identify someone who has signed up.
I made some slight changes to the html file here. Specifically removed the user name (can be a field in the database but many websites rely on an email address to log in), added First and Last name fields, and made it so that they had to enter their password twice to confirm it. Also I removed the link "< a >" from the signup.
I also completed a php script ( signup.php ) that adds the person who signed up to the database. I would have included an automated email; however I do not believe I can fully implement it on my local server. signup.php will be uploaded shortly.
Improves Facebook Timeline.
Improves the front page of Google.
Improves Facebook Timeline.
Improves Facebook Timeline.
Improves the Amazon home page.
Today our team worked hard on integrating the old iteration of our app's user interface with all the spanking new art we created for the game. Though we managed to make include our cuddly animated fitpet in with the old main page design we feel that we have to now redesign the store's interface into its own separate entity. Additionally, we're looking into creating a variety of fitpets so that in the event of its untimely death due to neglect it can be replaced by a different looking and behaving fitpet. Lastly, we've decided we need to clean up and organize our repository as well as commit a lot of the changes that as of now only exists on our local machines so be on the lookout for that.
Lapsus Linguae recieved an honorable mention at the UGRS banquet. Moving forward we have gotten our hands on a server and are looking to finish up an early version to release before summer. Work is being done to finalize audio recording functionality and save data
This was a bit of a difficult process since we've been using mySQL and sqLITE for the longest. It gives us a lot more freedom in our databasing schema, improving our ability to manage multiple users of the database, allocate different db's for development and testing, and giving us more tools to use and additional storage types.
Our original set of Rails ActiveRecord datatypes :binary :boolean :date :datetime :decimal :float :integer :primary_key :string :text :time :timestamp
Now we additionally have :hstore :array :cidr_address :ip_address :mac_address
The hStore and array types make it especially easy for our API to keep track of specific pieces of data in our Pokemons and Abilities controllers. Rather than make more 1:n relations to store things like movesets, abilities, or other peices of data with multiple values, we can use static arrays and associative arrays to our benefit. Thanks to PGsql's declarative programming model, we can also worry less about the underlying implementation of storage, indexing, and retrieval of data which makes our development all the faster.
Instructions on how to install PG and migrate from mySQL or sqLITE databases on Linux:
1) Grab your favorite package manager and install the pg package 2) Enter the PGsql shell using "sudo su -u postgres" 3) Create a user of the form "create role myapp with createdb login password 'password1';" 4) Create the postgres DB for the Rails application to use " create database "myapp" owner "myapp"; " 5) update your database.yml to reflect the new pg configurations and add PG into your list of gems 6) In the rails console, run migrations to reinitialize data from mySQL into PG's databasing scheme 7) Use those shiny new hStore and array types and have fun!
When modifying an exercise, the app would change the original date to the current date, which might be unintended.
Temporary::from_rooted() now takes an Assignable value.
We added two features to our app last week. The first feature is to draw the graph based on the data recorded. The second one is to allow users to edit their exercise data.
The client side function, based on JNA library, support windows status viewing by loading kernel32 and user32. Mac and linux are different, using C library which haven't started. Server side mainly only store the information of different devices, refresh device information and push information for responding request. It's not completed yet but the protocol might be socket.
Since the beginning of the year, when we first started the project, we have always tried to have an even number of iOS and Android developers. So we had 2 iOS devs and 2 Android devs. Unfortunately, during the first semester, our other Android developer decided to leave the project. No big deal. We can make do until next semester.
Well, the second semester came around, and we did in fact find a new Android developer. And again, this one left the project for various reasons. I am the only Android developer on the team who has actually worked on the project (or even stay with it for more than a semester!).
Also, my plan for the rest of the semester and this summer is to finish as much as I can in the app and move on to something different. I've just gotten a little burnt out on this, and want to try something new. I've done web development and now Android development, maybe next I'll do something for the desktop. But the point is, I will soon be leaving this project as well.
So why exactly is this? How come only one of the three total Android developers we've had on the team stayed and actually worked on the project? And the one left will be leaving soon? Honestly, I can only guess at this point. Maybe we made some poor choices as to who we brought onto the project, maybe it's not interesting enough for some people, or maybe we just got unlucky as to when we brought them on (busy schedules, graduating soon, etc).
Also an interesting question, why have we had the same 2 iOS developers throughout the project? Again, maybe we just got lucky on this front. Although, I have also noticed that at least one of our iOS developers, John, works on this a lot more than I do. He also seems to get burnt out less often than I do. Perhaps there's a fundamental difference in the work ethics of developers for different platform. Or maybe I'm just talking out of my ass, and this is all anecdotal. But it's definitely an interesting thing to think about.
Also, about the title, for whatever reason Observatory says we haven't updated our repository in over a month... That's just a blatant lie. So don't use that as a metric. We are in fact working.
The game layouts are almost completed. The card selection screen is the most troublesome at the moment. The cards have to be large enough to see well, but there must be a good number of cards to select from. Next is to make textures in Gimp, continue to integrate the game mechanics, and make our presentation for this Friday.
I am having some difficulty getting a calendar to display on the page. I downloaded angular-ui/ui-calendar form the github, but I think the problem is that I don't have ui-bootstrap. I am still trying to find a way to install ui-bootstrap.
I have been working on the reoccurring event sign up page. The page is laid out with tabs for each of the days of the week. There is a button for each of the volunteer options to click to 'volunteer now!' for that event. I'm working on the functionality of the buttons to ensure once the user clicks to volunteer it is marked as taken.
Early audio recording work
My recent commit adds an API for serving detailed information on each vehicle added to the fleet and the most recent update for each of these vehicles. This information is served via /updates and /vehicles, similar to the original tracker. I also worked on the admin dashboard to create a raw interface for adding new shuttles to the fleet with their unique tracker identifier and shuttle name.
So far, I have been learning a great deal about Go, AngularJS, Polymer, and MongoDB. Aside from the RPI Petitions site and some work on Concerto Signage, this will be my first project using some of these technologies altogether from scratch. I am really enjoying learning them all and creating something exciting in the process.