Week 11( what we did in the class)

At beginning of the class on ( April/ 7/2014)  , the same thing with every other class, the group leader presented the group status . Our group still get stuck on the ticket  TRUNK- 243, that is why , we need more time to working on  it.  Fortunately, I  found the file (PersonAttributeHelper.java ) of the project ( openMRS-core-master ) on the git-hub , that may have some information to solve the problem of the ticket TRUNK-243.

From the blog herangoc » cs@worcester by emtrieu and used with permission of the author. All other rights reserved by the author.

Posted in CS@Worcester | Comments Off

Final Push

The previous past couple of weeks I have been neglecting the Modify Dosage System ticket due to switching gears and reading (skimming through parts) the Head First Design Pattern book. I found the book to be enjoyable to read and full of useful information. It would be a great book to somehow integrate into the new software development track. Design patterns play such an essential role in developing software that is efficient and maintainable that I believe it would be a great benefit for freshmen to become familiar with them. I enjoyed listening to everyone’s presentations, it was a great way to find out the books material without having to read it yourself. I believe that for the most part everyone enjoyed this project learned a great deal from their own and other’s presentations.
With book presentations over my plans for the final week is to (with help from above) be able to figure out how to correctly connect our new modify dosage system to the existing database that the current drug dosage system is using. The last time I was working on it I was able to input information but when I attempted to save the new dose it would get replaced with the current dose instead. I get the feeling that some function is being triggered dynamically somewhere which leads to my input getting reverted to the original dose. The calendar input box will select the date and save correctly and the save button also functions the way we want it to, so it’s really just the dosage button that is being a nuisance. Hopefully this week we can put some significant time towards this issue, I prefer to leave this class with my head held high and a modify dosage system works! TR and I plan to meet for a full day to see if we can resolve this issue. We also plan to work on our presentation so it would be great if we could get the system to actually work before Wednesday’s class.
Till Next Time,
ML

From the blog mlopatka by matthewlopatka and used with permission of the author. All other rights reserved by the author.

Comments Off

Live Asset Reloading with guile-2d

Guile-2d provides a dynamic environment in which a developer can build
a game incrementally as it runs via the Guile REPL. It’s nice to be
able to hot-swap code and have the running game reflect the changes
made, but what about the game data files? If an image file or other
game asset is modified, it would be nice if the game engine took
notice and reloaded it automatically. This is what guile-2d’s live
asset reloading feature does.

The new (2d live-reload) module provides the live-reload
procedure. live-reload takes a procedure like load-texture
and returns a new procedure that adds the live reload magic. The new
procedure returns assets wrapped in a signal, a time-varying value. A
coroutine is started that periodically checks if the asset file has
been modified, and if so, reloads the asset and propagates it via the
signal. Game objects that depend on the asset will be regenerated
immediately.

Here’s some example code:

(define load-texture/live
  (live-reload load-texture))

(define-signal texture
  (load-texture/live "images/p1_front.png"))

(define-signal sprite
  (signal-map
   (lambda (texture)
     (make-sprite texture
                  #:position (vector2 320 240)))
   texture))

load-texture/live loads textures and reloads them when they change
on disk. Every time the texture is reloaded, the sprite is
regenerated using the new texture.

Here’s a screencast to see live reloading in action:

Guile-2d is ever-so-slowly approaching a 0.2 release. Stay tuned!

From the blog dthompson by David Thompson and used with permission of the author. All other rights reserved by the author.

Posted in FOSS, gamedev, gnu, guile, scheme, WSU | Comments Off

Week 8

During the week 8, we completed all the tickets we were assigned to and also went over the list of the tickets to double check with each member in the group. We were all satisfy with the results and the team leader submitted a pull request on git-hub to the original ticket owner.

We were also introduced to the J-Unit testing concept during the week 8 period and we worked on a code given by the professor. we were given the task to test each method of the code so we can get the hang of it. We also started to work on our book report and get ready for the presentation next week.

From the blog ~~~ACordor Blog~~~~ » CS@Worcester by juwee05 and used with permission of the author. All other rights reserved by the author.

Posted in CS@Worcester | Comments Off

Moving in a new direction

This week we have still not heard back from the OpenMRS admins about our issue. As we are running out of time in the class, the decision has been made to move in a different direction and come up with documentation to add the project into Eclipse, which I understand to be the way that most people use this product. In my opinion Xcode is much better to use, but not a lot of people have Macs, and it is probably more practical to make it into Eclipse. The plan is to come up with this method soon, and then the OpenMRS people can do with it what they will, except and use it, or ignore it like our other contributions. Additionally, I plan to finish up on reading the book on Git for the 5th. 

From the blog ckelley6 » CS401 by ckelley6 and used with permission of the author. All other rights reserved by the author.

Posted in CS401 | Comments Off

Hiatus on Project while Reading Book

This week I made little to no progress on the modify dosage system. I have spent most my time on reading  the Head First Design Patten book. Seeing that the book is about 620 pages I was unable to truly read through all of the content, so I had to pick and choose certain sections to read and skim through the rest. My first impression of the Book was that I was intrigued by the outline of the book. The book does a great job keeping you interested by a variety of ways. Some of which include crossword puzzles, humor and plenty of interactive diagrams. The book also teaches in more of a conversational problem solving manner giving you the feel that you are actually working through problems with other programmers instead of dry technical explanation for the examples. The patterns covered in the text include the Strategy, Observer, Decorator, Singleton, Iterator, Composite, Factory, Facade, State, Proxy, Command and Template Method. An appendix provides a very quick rundown on a few more that didn’t make it into the main text. These patterns are introduced in a gently gradually growing manner that adds additional objects to extend the patterns as you gain the idea of and master array of patterns. I liked the way that the book made you think about and decide which pattern would most effectively solve the problem at hand. Throughout the book they introduce real-life problems that the author has you consider many possible solutions. He even has you consider solutions that aren’t the best idea. After the consideration of the solutions the author will even describe to you why the bad solutions are as such. The entire books examples are written in java so it fits in well with Worcester States courses seeing that the majority of the programming classes are java based. I feel that introducing design patterns in a freshmen course would be beneficial seeing that design patterns are used in every real world application. The book continuously stresses the idea of favoring composition over inheritance in most cases, as well as programming to an interface. The author tries to stress a “Has A” relationship is much better than an “IS A” relationship. The book uses a great example of this; the example states that not all bathrooms have bathtubs, so we probably don’t want to include a bathtub in a Bathroom class. I wish I would have had more time to actually be able to read the entire book, but with all of my other classes and final project going on I just didn’t have the time. I also want to try to finish the modify dosage system before this semester ends, so TR and I are going to try to find a decent amount of time to get together and work on it. We are still having trouble correctly data binding some of our textboxes and drug selection drop downs. A lot of the code comes from several levels of classes, so it is difficult finding exactly where implementation is needed. As I stated in my last post I was able to create a drug concept and add it to a current patient, so I will start to work on this project after this upcoming Monday.

From the blog mlopatka by matthewlopatka and used with permission of the author. All other rights reserved by the author.

Comments Off

Week 10 ( what we are doing in the class)

March /31/2014

At beginning of the  class, every group’s leader presented the group status. After that, the professor ask us to create the Junit test for the student class and the Degree Audit class,   which is belong to  a J Unit lab master project we got from the git hub on the website: github.com. First, fork the J Unit-lab Repository :

1. Go to the J Unit-lab repository at https://github.com/kwurst/junit-lab
2. Fork the J Unit-Lab repository to your account.
3. Add your instructor and partner(s) as collaborators

Second, download the J Unit lab Repository:

1. In Eclipse, choose File:Import
2. Choose Git:Projects from Git
3. Choose Clone URI
4. Paste the SSH clone URL from GitHub
5. Set the protocol to SSH

6. Select the master branch
7. Choose the directory you want to clone into.
8. Select Use the New Project Wizard
9. Choose Java:Java Project
10. Enter a project name.

After reading the code of J unit-lab code, then create the Student test class and the Degree Audit test class, then I write the test method for every method in  each class. making sure the tests are run correctly, I run to test every single method after I wrote the code for that method. If the test pass it result will display the green bar or the test fail the result will display the red bar.

 

From the blog herangoc » cs@worcester by emtrieu and used with permission of the author. All other rights reserved by the author.

Posted in CS@Worcester | Comments Off