Hello everyone,

Now that we have an open ssh port on our server, individuals can log on and look at the code structure or play around with their own development folder. Once you have a username, you should log onto the server and change your password for security reasons.

Using SSH to Gain Access to the Server

The easiest way to gain access to the server and change your password is to use SSH. If you are using a windows machine you should install putty. Once you have putty installed you can place the url in the server field and leave the port on 22. When the prompt shows up enter your username and then type your password. If you are using windows or mac, you can SSH from a terminal by typing ssh username@server and then type your password when prompted. Be aware that you won’t be able to see any characters when typing your password but it’s being entered.

Changing your Password

Once you’re logged onto the server which is running CentOS you can easily change your password by typing passwd and hitting enter. This will prompt you for the current password and then you can type your new password. Again no characters will show up but this is normal.

In Your Home Folder

You should see one directory in your home folder, which is where you can place all the files that you want to test through the web server. This is a folder that is sim linked to a folder in the webroot. In order to test any code that you place in here you can go to cstest.worcester.edu/development/your_username or simply go to cstest.worcester.edu and navigate to your folder from there.

If you have any questions, please blog about them or send out a message on the ListServ.

From the blog CS 401 - Object Oriented Design » cs-wsu by dillonmurphy10 and used with permission of the author. All other rights reserved by the author.

We had another class meeting today on IRC chat. Where we discussed our goals from the previous week and tasks that everyone should be working on this week. Our previous weeks goal was to get everything into the developmental branch on GitHub even if it was just a blank template. Our goal was to have a working application for this week. We were very close in hitting this.

For work on the puzzle, after class I started to re work the directory structure of the puzzle application. I figured this way it would be much easier for somebody to read the directories and to get a feel of how it all works. So I basically changed the structure to now have a folder called utilities. This utilities folder holds all of the images, jQuery tools, and the puzzle pieces depending on the size of the game. From there inside the puzzle folder holds just the 3 HTML, CSS, and JavaScript files. I figured this was a good start into cleaning up and getting the code much more organized. So this way my team or anyone else in the class can follow it better.

That is all for tonight, along with learning more about this entire puzzle application that was free for use off of the web. The licenses and copyrights are stored inside each file of the application.

Will be posting more as the week goes on.

From the blog rwilliams5262 » cs-wsu by rwilliams5262 rwilliams5 and used with permission of the author. All other rights reserved by the author.

We had another class meeting today on IRC chat. Where we discussed our goals from the previous week and tasks that everyone should be working on this week. Our previous weeks goal was to get everything into the developmental branch on GitHub even if it was just a blank template. Our goal was to have a working application for this week. We were very close in hitting this.

For work on the puzzle, after class I started to re work the directory structure of the puzzle application. I figured this way it would be much easier for somebody to read the directories and to get a feel of how it all works. So I basically changed the structure to now have a folder called utilities. This utilities folder holds all of the images, jQuery tools, and the puzzle pieces depending on the size of the game. From there inside the puzzle folder holds just the 3 HTML, CSS, and JavaScript files. I figured this was a good start into cleaning up and getting the code much more organized. So this way my team or anyone else in the class can follow it better.

That is all for tonight, along with learning more about this entire puzzle application that was free for use off of the web. The licenses and copyrights are stored inside each file of the application.

Will be posting more as the week goes on.

From the blog rwilliams5262 » cs-wsu by rwilliams5262 rwilliams5 and used with permission of the author. All other rights reserved by the author.

As most of you probably know, I pushed everything everyone has done so far (excluding the puzzle, Ryan already pushed it) to the developmental branch. I took the homepage, article viewer and coloring app from everyones private repos (hopefully they don’t mind). I also updated the homepage to link to the respected app. Hopefully we can now get this thing rolling for some testing!

Other than that, I’ll be making some tweaks to the slideshow app. Hopefully James and I can get that thing shaped up to what it is suppose to be over the next few days. I may also look into adding the homepage button to each app. Although, I might not touch it since I think Joe wants control over that?

It’s looking good guys and gals!

From the blog Sean » cs-wsu by shorton1 and used with permission of the author. All other rights reserved by the author.

As most of you probably know, I pushed everything everyone has done so far (excluding the puzzle, Ryan already pushed it) to the developmental branch. I took the homepage, article viewer and coloring app from everyones private repos (hopefully they don’t mind). I also updated the homepage to link to the respected app. Hopefully we can now get this thing rolling for some testing!

Other than that, I’ll be making some tweaks to the slideshow app. Hopefully James and I can get that thing shaped up to what it is suppose to be over the next few days. I may also look into adding the homepage button to each app. Although, I might not touch it since I think Joe wants control over that?

It’s looking good guys and gals!

From the blog Sean » cs-wsu by shorton1 and used with permission of the author. All other rights reserved by the author.

This week I was tasked to look into a way to notify our web server whenever changes are made in our Github repository, so that we may automatically pull and sync the new code in order to update our application. I found out that this can be done using Github’s Post-Receive Hooks. The first step that has to be done in this is to update our Administrators Github settings page, under the WebHooks URL section and update that section with the URL to our webserver. Once a commit is made to github they send JSON encrypted script to the webserver, based on a template in Ruby that contains the payload data.

If I understand things correctly we can either go about it in the previous manner, or use a slightly different approach using an SSH key.. I will go over this later when we all meet in class..

From the blog CS:401 » CS-WSU by dcarlin2013 and used with permission of the author. All other rights reserved by the author.

Hello again,

So there have been no new developments for the coloring page.  I have been waiting for concrete commitment on layout from the Worcester Art Museum but as of yet there seems to be no consensus as to how the page should ultimately look.  That said I was still busy this week.

I spent Monday night trying to understand why the puzzle teams code won’t load the image on the pieces.  Unfortunately I could not solve their problem, but I did find an alternative solution which even came with a few extra bells and whistles, like a timer and movement counter as well as snap positioning.  Its basically a javascript file built on top of jQuery which is provided as freeware by google.  I even showed of a pic of my dog Chewie, seen in the photo above.

Well, you might be wondering at this point, why the title of this article is Git Hub Headache.  I would answer that question with “Git Hub was a huge headache this week”.  I tried to learn the Git Hub command lines this week, which was not so bad.  Sompop’s Git Hub power point presentation was definitely helpful. I could clone the repository, I could add my files to a branch, but I could not figure out how to actually commit them.  After a while spent with no luck, I decided to change strategies.

I then tried to clone the repository with netbeans, but netbeans wanted me to make a project file which did not make sense seeing the 401Project is not being developed exclusively in netbeans.  After a few hours spinning my wheels… I decided to just go to the website thinking there must be some way to do this from that end.  I selected the development branch and cloned the repository.  Then I added my files and committed them to what I thought was the development branch.  However when I checked to see if it had uploaded correctly the changes had been made to the master branch.

At this point I was becoming thoroughly frustrated.  I looked for a few ,minutes for a way to remove the upload but then just moved on.  My last attempt was in the Git Hub app fro mac.  It took a bit of looking but I was able to branch off the development branch and commit my files.  However my branch contained all the file from the development branch an I was not sure If that was normal.  I suppose it would be, so you can run the whole application but only be change your particular part.  At this point I was just happy the files were uploaded.

Any way that was it for the week.  Hopefully next week will be more fruitful.

Till next time.

Jason Hintlian

From the blog jasonhintlian » cs-wsu by jasonhintlian and used with permission of the author. All other rights reserved by the author.

This week had our weekly class meeting and we all decided it was time to get a working version of the iPad application we have all been working on. Even if it was the basic framework, it was just something that we could deploy and for Tim and others at the Worcester Art Museum to view.

That was one of our goals this week was to get the puzzle demo up on GitHub for the development branch. A working demo is now deployed on the development branch as of this morning. We where having difficulty this week trying to get the puzzle activity application to work. We before had a demo that would allow the user to move puzzle pieces as the shape of squares around, but Tim was looking for the actual jigsaw piece type. So we had to go back to the drawing board and figure out how this could be done. I found online there was a tool called kinetic.js which allowed you to move pieces around by creating kinetic.shapes, objects, etc. I thought it was a very cool tool. If any of you want to look at it for future projects down the road or just for fun to learn here is the link:

http://www.html5canvastutorials.com/kineticjs/html5-canvas-drag-and-drop-tutorial/

We then found someone had an open source code that allowed the user to give it a image and it would separate them into many puzzle pieces that you could move. Unforutnatly we tried giving this a shot and every time the image would come out black. We asked another student in the class and they looked at it over night and still had no luck to get that to work. So this was then when we said we cannot use Kinetic.js any longer. Jason who looked at our puzzle activity code, pointed us to another open source code from Google that had everything we where exactly looking for. The link that he had sent out to us, I actually came across along my way at the beginning of researching how to create puzzles with HTML, JavaScript, and CSS. This one was using all of theses languages along with the jQuery UI tool. I think that was the key feature that we where missing. I had a feeling we where going to need to use jQuery at some point for this.

So after looking at the link for the open source code again, we had a working puzzle activity that can now be viewed by everyone on the CS401 Repository Development branch. Here is an screenshot of the layout:

It allows the user to move pieces all around on the screen, has a timer which I wanted to implement into the original first Demo we showed and tells you the number of movements. Along with bringing a nice frame around the puzzle. It has the snap feature so when the piece is in the correct location the frame lights up green and then snaps the piece there and you can move on to the next one.

That is all for this week. Looking forward to seeing this first deployment with everyone’s work together.

From the blog rwilliams5262 » cs-wsu by rwilliams5262 and used with permission of the author. All other rights reserved by the author.

Hello,

No matter how much time you have put into a project, is good to keep an open mind about going back to the drawing board and making changes. There are always new ideas, new improvements, new and exiting add ons.  I say this because, during the first part of the semester, there has been, at times, a little bit of miscommunication  with our client, and thus some of our ideas have probably not gone totally in the right direction. Well, I guess that is part of any software development process and definitively a part of the learning process as well; fortunately is still early in the semester and there should be plenty of time to correct for this.

Last week, our clients suggested they would like to have a brief intro to the coloring book and the puzzle sections. The intro would say something like “These sculptures are white but back in the day they used to have colors. Help us color these”. In response to that, one idea is to have a small slideshow of floating images and a brief legend next to them. Once the user wants to start coloring, there is a button that takes to the main coloring app.

The slideshow and the link to the page are working now, and the idea could be adopted in the coloring app or maybe adapted somewhere else in the main program, in any case, it can be further stylized with css. The images here provided are just  snapshots but the code will be available hopefully soon in the CS401 server.

Until next week.

Beto

From the blog betoluna » CS WSU by betoluna1 and used with permission of the author. All other rights reserved by the author.