Personal tools
You are here: Home > CS 342 Blog Entries > Folder with blog entries for Cooper Walbrun > Blog Entry for Week Ending March 3

Blog Entry for Week Ending March 3

by Walbrun, Cooper last modified Mar 03, 2017 03:22 PM

This week, I uncovered a very helpful source that will serve as the foundation for the project that Cory, Levi, and myself will be undergoing this semester. The project (which is found on GitHub) implements a basic system that stores badge information per each user in a Plone site, and displays them in the user's information page. Badges have features such as a name, an expiration, and a description.

After I found this wonderful project online, I compiled a document for my group that details aspects about its source code, such as where the code pertaining to badges themselves dwells (i.e. the Badge class), where testing methods are written, and where/how the badges are displayed on the web interface. Additionally, I wrote up a list of questions to ask our class's designated Plone guru, Kim, during our lab session on Wednesday, and as a result my group feels more comfortable than ever to dive into programming our project. This document, which I am henceforth calling the Resource Hub for our group, contains helpful links to Plone's documentation, which we will need to refer to frequently when we begin programming our feature.

Anothing thing I did this week, which actually proved quite difficult, was the documentation of my individual project description. As you may recall from my previous blog entry, I decided on doing the open source project that involved statistical sampling of data for video game purposes, e.g. generating items and calculating damage to deal to monsters. Since this Sampler is very math- and statistics-oriented, it was initially challenging for me to come up with ways I could expand it, but after re-reading Chapter 18 from the AOSA book several times, I realized the current means of interacting with the Sampler is very inconvenient for the user, and in fact the only way to deal with it at all is to hard-code values and method calls and run the Python program to see the results in a command prompt. I also realized that I know exactly how to make Python-based Graphical User Interfaces (GUIs) from previous programming experience, so I decided I would make that the target of my project. My users will be able to enter in values in designated boxes, click a few buttons, and be able to retrieve "pretty formatted" output from the Sampler. I will be writing more about this in future blog posts when I actually get to the development phase, but it is important to note at this stage how long it took to come up with a viable means of improving the Sampler.

Next week, I aim to get a good start on (and possibly finish) the official Project Proposal for my group's Plone add-on. Naturally, this will take a lot of deliberation and studying of Plone's documentation. I have already gotten in touch with Cory and Levi in regards to setting up a time to meet in our online chatroom to discuss the proposal and the project in general, and my main desire for next week will be at least to feel fully comfortable tackling the code of our Gamification add-on. As another side goal (though no less important), I want to start designing the GUI for my Sampler project, because I think this will simultaneously give me some direction when it comes time to give it some back-end code and help me to understand more about how the Sampler works (and especially how it handles parameters).

by Walbrun, Cooper last modified Mar 03, 2017 03:22 PM
CS emphasis accredited by

ABET logo

Contact Us

Computer Science Department
UW Oshkosh
800 Algoma Blvd.
Oshkosh, WI 54901

Phone: (920) 424-2068
Fax: (920) 424-0045
Building: Halsey Science Hall


Rooms: 229 (general office), 221 (David Furcy, chair)

Email: Send mail to chair at cschair@uwosh.edu