I have just determined that stashing every method for rendering views in a django project into a single file is not scalable.
Over the past few weeks, we have continued to work on the overall structure of the website while trying to make it into a social networking website. We are also working on creating some other pages on the website including a page that will directly lead the user to the club's page. We also worked on having the user change information about their account. Hence, this has been our current focus and work on rClubs.
Review URL: https://codereview.appspot.com/180200043
git-svn-id: http://dynamorio.googlecode.com/svn/trunk@3024 49cc7528-f6fd-11dd-9d1a-b59b2e1864b6
Adds an additional argument to instr_create_Ndst_Msrc_vardst(), and instr_create_Ndst_Msrc_varsrc() indicating at what position the varying list of operands should be inserted, supporting more than just having them at the end.
git-svn-id: http://dynamorio.googlecode.com/svn/trunk@3023 49cc7528-f6fd-11dd-9d1a-b59b2e1864b6
Refactors the existing reg_check_reg_fixer() into a general decode_debug_checks() which calls into the encoder and decoder to verify the sizes of various arrays and sanity check the decoding tables.
For ARM, adds checks of the encoder chains and checks that register lists obey certain limitations to make decoding and encoding simpler.
git-svn-id: http://dynamorio.googlecode.com/svn/trunk@3022 49cc7528-f6fd-11dd-9d1a-b59b2e1864b6
Shifts top-level encoding routines to encode_shared.c with the single core routine arch-specific.
Adds an end-to-end implementation of the ARM encoder but only fills in operand-type-specific code for registers. Immediates, register lists, and memory operands will be added later.
Adds an encoding error message feature on ARM as an attempt to provide more specific error messages, as figuring out why encoding failed was always difficult with our x86 encoder.
git-svn-id: http://dynamorio.googlecode.com/svn/trunk@3021 49cc7528-f6fd-11dd-9d1a-b59b2e1864b6
Fixes an off-by-one predicate check error. Fixes some build errors when using a different version of gcc. Adds DR_REG_CR* to reg_get_size().
git-svn-id: http://dynamorio.googlecode.com/svn/trunk@3020 49cc7528-f6fd-11dd-9d1a-b59b2e1864b6
library needed to run servos
of the code, requires a lot of initialization on the terminal window before using the program.
Since my last post, Android 5.0 Lollipop came out for current Nexus devices, and will soon be rolling out to other devices! Since I have a Nexus 5, I was able to get Android Lollipop as soon as it came out. As such, I wanted our app to adopt the design principles of the new version as quickly as possible. This was simple enough for devices running Lollipop, but I soon realized that it would not be as easy for non-Lollipop devices.
Initially, I had 2 different designs for devices on SDK level 21 and those on other SDK levels. However, I decided that the original design looked really bad by comparison, so I wanted to port over the design to lower API levels as well. This should have been fairly simple, given that Google provides the appcompat library for us to use. It should have been as easy as just switching the parent theme to AppCompat, but nope. Apparently calling getActionBar() returns null with AppCompat theme on SDK levels below 21. And since we're using a tab based interface, the way we add tabs is by using actionBar.setNavigationMode(ActionBar.NAVIGATION_MODE_TABS). Since actionBar is null, we get a NullPointerException. How fun. The first thing I'm thinking of trying is switching over to a SupportActionBar, which might fix it. Otherwise, I'm not really sure. Maybe I'll post on StackOverflow about it.
Also, one of the features I added was creating rides. Users create rides by pressing the FAB (Floating Action Button) on the RidesFragment, but some of the methods used to create the FAB are SDK 21 only. And the methods I could use to make it work on lower API levels were deprecated upon the release of API 21. I'll just go bang my head on a wall for a little while.
A light appears in the darkness, though. Someone released an open source library which claims to bring easier implementation of Material Design to Android levels as low as 2.2 (https://github.com/navasmdc/MaterialDesignLibrary). We're only supporting Android levels as low as 4.0.3, so this would definitely be an awesome library to use. I'm going to try to implement use of this library over Thanksgiving break.
Review URL: https://codereview.appspot.com/175670043
git-svn-id: http://dynamorio.googlecode.com/svn/trunk@3019 49cc7528-f6fd-11dd-9d1a-b59b2e1864b6
Mike and I found a little bit of time to work on the interface. I assigned him the task of creating functions to change the mote variables directly, while I worked on the JSON API. Mike ran into some difficulties, so we only managed to get the JSON API done (with test data). We presented it, but our code did not work on Windows. I quickly found the problem: since the string-ified JSON from the request put a Unicode tag on all strings (u"cat" instead of just "cat"), the JSON decoder did not...
Fixed sample template, looks descent. Modifying editor so it can fit page. Probably going to just have client "render" page then upload back to server for hosting. NEED TO ADD SECURITY!!!!
Review URL: https://codereview.appspot.com/176140043
git-svn-id: http://dynamorio.googlecode.com/svn/trunk@3018 49cc7528-f6fd-11dd-9d1a-b59b2e1864b6
DrMemory on Windows 8.1 seems to crash for very many people when doing anything pointer heavy (... for Data Structures), and so most people have to resort to Cygwin or to a virtual machine. However, it seems that when running DrMemory using the option -light there is no internal crash.
From the help option on DrMemory: -light Enables a lightweight mode that detects only critical errors.
Usage: drmemory -light -- hw8-m32.exe
Re-did the way I make and store table cells, along with creating them and then viewing them afterwards
In my iOS app I implemented a slide menu for easy navigation.
Created a test document.
This blog post is written because of the LITEC LEDs.
I may, or may not, have "borrowed" some to be used in this project.
While I was setting up the LED, I tried measuring the characteristics of the LED using a multi-meter because LITEC doesn't have any datasheets for these LEDs that I know of currently.
More accurate data will be provided once I get it, but I noticed from my testing that: Forward voltage was equal to 2.1 V Forward current was equal to 10 mA
Which means that the ideal resistor connected for the LED is 290 Ohms at 5 V.
This was, by no means, a rigorous test, but it was the best analysis that I could do at that point in time.
The Auduino project itself came from my (mis)adventures during Hack RPI 2014.
I wanted to use the Arduino to create some type of project where I could send data from my laptop to the Arduino and have it spit out relevant information using a TFT color screen. At first, I tried to code PONG using C#. Unfortunately, there seems to be some type of bug in C# that somehow skips code at the most inopportune moments (i.e. when the ball is supposed to bounce away from the bottom of the screen.)
This bug was so frequent, yet random that I simply gave up on the idea out of frustration.
Near me, a friend of mine (who I will name if he wants me to) wanted to do an audio project for his Raspberry Pi. (I can't really remember the specifics of the project.)
After putting two and two together and asking this friend for some spare hardware, I made a simple project that sends data through serial to the Arduino and have that Arduino react to the data.
This project will definitely not be some full-scale project that leads to groundbreaking progress. This will be more of an exploratory project to see how to solve problems involving the Arduino, serial communication, and audio data. If this project doesn't change the world, at the very least, I can change how I see the world.
This project kinda goes with the theme of "I want to make this project because it interests me and I think I'll use it" projects that I have seemingly been chasing around.
This project involves music/sound and hardware, two of the things that I love the most.
Here's to a brand new start and another development project!
More descriptive readme. No actual changes to code.
The program currently monitors CPU, Memory, Network, and Disk I/O usage. It graphs this data based on user input using WPF (Windows Presentation Foundation). We've also implemented python scripting for custom monitoring. One of the biggest enhancements we've developed is background monitoring. The user can have Check Up run in the background and it logs the data it collects to a .csv file so the user can later analyze, graph, or use the data for whatever he/she may need to. This program utilizes the .NET framework performance counters so it uses 0% CPU while running in the background after the initial CPU load of loading the performance counters.
Currently, the background monitoring only logs information about specific processes. In the future we hope to implement OS level monitoring in the background. Another addition we hope to implement is an even better looking GUI. Since we started using WPF, the GUI has definitely improved a lot, but adding Custom skins/color palettes could take that to the next level. Lastly, we'd like to make some performance improvements during the loading screen. Currently it takes around 10 seconds to load the performance counters so we want to find a way to cut down on that time.
As stated in one of my earlier posts, I started work on getting the "week of" date. This is important not only because it provides valuable information to the user but it is also necessary for determining the dynamic URL that points to the menu data.
At first my plan was to accomplish this was to use 'datetime' library to find the current date of the computer running the code and from that determine the most recent Monday (the date that corresponds to the menu URL). This seemed like sloppy coding practice however because it rely's on Sodexo always entering their menus on the same date. The method I am currently working on scrapes the date information off a separate page on Sodexo's website, so that assuming they maintain their system for naming menus "week of mm/dd/yr" there should be no problems.
So far I have set up a separate scraping file and identified the pertinent tags in the HTML to give me the date that I want, now I just have to integrate that with our larger file and debug.
Progress has been going fairly well concerning the integration of the Dining Hall Menu with the RPI Mobile Android application. So far, I've managed to fix the bug causing the app to crash when selecting a dining hall. In order to fix this I had to basically change the way the ListViews worked on both the dining hall menu fragment as well as the fragment displaying all of the meal items. An unfortunate consequence from this rework is that the JSON parsing is not running asynchronously anymore; it currently just runs on the main thread. However, I don't see this as a huge issue since it only needs to load this information roughly once a week; not every time the specific fragment is viewed.
I have also fixed a bug that caused dining hall menus to duplicate themselves every time the DiningHallMenuFragment was opened. I also cleaned up the code a great deal, and plan on adding more comments to accurately describe how this feature is implemented so people who want to work on it in the future can jump into it easily.
My next step is to fix up the UI in the FoodItems fragment and display all relevant information pertaining to a food item (time of day being served, attributes like vegetarian/vegan, station, etc..)
We presented for the RCOS poster session with a nice poster designed in InDesign. We have been looking to better the UI and features. Nathan is tasked with setting up email so that our service can handle emailling and confirming emails. Should be implemented soon. We also have a quick add assignment feature from Joey coming in.
Parser is now fixed with temporary hard coded urls. The next step will be to create a system to auto adjust the urls.
Parser is now fixed with temporary hard coded urls. The next step will be to create a system to auto adjust the urls.
Review URL: https://codereview.appspot.com/181830043
git-svn-id: http://dynamorio.googlecode.com/svn/trunk@3016 49cc7528-f6fd-11dd-9d1a-b59b2e1864b6
JSON-based query submission via POSTman
Review URL: https://codereview.appspot.com/175430044
git-svn-id: http://dynamorio.googlecode.com/svn/trunk@3011 49cc7528-f6fd-11dd-9d1a-b59b2e1864b6
This reverts commit 951b9af9a7cae8d863252fafadee5d4707598b45.
Hello everyone, I'd like to welcome Burke Livingston to our team. He will be working on creating the installer/executable for the game later. With this new addition, we will be able to make more progress in the project.We've been adding a ton of content to the game. Unfortunately, the game will not be able to move into Beta status by the end of this semester. We continued to add features, but this required much refactoring of the code and it also takes a while to obtain all the assets for a full...
To make writing the prediction class easier I have added a person class that can hold a persons ids on different social media networks as well as their connections on those sites. Next we need to give the crawler the ability to add and remove friends while scraping and we need to write our prediction algorithm.
Review URL: https://codereview.appspot.com/179080043
git-svn-id: http://dynamorio.googlecode.com/svn/trunk@3009 49cc7528-f6fd-11dd-9d1a-b59b2e1864b6
Review URL: https://codereview.appspot.com/175390043
git-svn-id: http://dynamorio.googlecode.com/svn/trunk@3008 49cc7528-f6fd-11dd-9d1a-b59b2e1864b6