Category Archives: cs-wsu

Article Viewer 0.1

The content viewer is referred to the article viewer now, there have been some additions and removals since the last update!
Here is an outline:
A link to the next article or chapter at  the top of the paragraphs.
New focus on paragraph div that is behind the paragraphs.
Scroll to change focus on image and paragraph.

Here is a screenshot of the final 0.1 product:

Linking was as simple as creating simple jQuery mobile buttons buttons.

Creating a “focus” on the current div per request of the client was a little more interesting.
So I didn’t want to create a simple function that would change the background color of the current paragraph tag because that isn’t elegant and just didn’t seem appropriate! So I created a stand alone div that would move and change height based on the height of the paragraph it was supposed to be highlighting! I also places this div behind the paragraphs so it wouldn’t interfere with the font settings. All of this was accomplished with the animate function and basic CSS selectors and attribute functions for jQuery. Here is a screenshot showing the function in action!

Here is the function that accomplishes the animation:

function animateActive(){
$(‘#active’).stop().animate({‘top’ : $(‘#article-display p:eq(‘+currentRow+’)’).position().top+10+’px’,
‘height’ : ($(‘#article-display p:eq(‘+currentRow+’)’).height()+20)+’px’}, animationTime);
}

The #active div is an absolutely positioned element that gets it height and width from the p attributes. it is completely dynamic with regard to sizing and position.

The other interesting part of this version is the trigger for that function; the function is activated by scrolling! the initial proff of concept for this was not a viable option because I created the function to animate based on when the top of the page passed the top of the P tag, this doesn’t work for sections that are  a the bottom of the page so I created the following function:

$(window).scroll(function(){
if($(window).scrollTop() == $(‘.ui-page’).height()-window.innerHeight){ //potential null value if numRow does not divide nicely into the page height-windowInnerView
currentRow = numRow-1;

Uncaught ReferenceError: numRow is not defined (repeated 2 times)
animateActive();
slideY($(‘#row-wrapper’), -currentRow*imageHeight, animationTime);
}
else if(currentRow != Math.floor(($(window).scrollTop())/scrollSwap)){
currentRow = Math.floor($(window).scrollTop()/scrollSwap);
animateActive();
slideY($(‘#row-wrapper’), -currentRow*imageHeight, animationTime);
}
});
The $(window).scrollTop() function gives you the current position of the window in pixels.
The actual height of the page is obtained through $(‘.ui-page’).height() and the height of the users viewport (the height of their browser) is obtained by window.innerHeight. I use the two values to figure out how many pixels the page will be scrolling before it hits the bottom. This is calculated by $(‘.ui-page’).height()-window.innerHeight.I use this value to calculate the variable “scrollSwap” which is essentially the number of pixels the user needs to scroll to switch paragraph focus. scrollSwap = $(‘.ui-page’).height()-window.innerHeight/$(‘p’).size() // Essentially the amount one can scroll divided by the number of paragraphs in the chapter. when the user scroll 1/5 of the way down the page it will execute the functions the change focus and image.

This was a pretty cool learning experience; I have seen scrolling impact the page on some portfolios, it was nice to make my own function to do it!

Until next time!
-Joe

From the blog itsJoe's Blog » cs-wsu by itsjoeyoung and used with permission of the author. All other rights reserved by the author.

Page Viewer 0.4

There was a minor issue with animation speed which we attempted to remove, the new page viewer also implements 2 new functions for specific pages.

Attempting to improve performance in only kiosk pro’s browser consisted of removing opacity from the animations. This made a very minor difference with regard to sluggish animation. The animation speed works fine in other browsers on the iPad which leads me to believe this is indicative of an issue with kiosk pro. However removing the opacity will remain in the application even with the negligible performance enhancement.

the two new functions added were from the main page and chapter viewing page:

Main Page:
The primary addition here was the combining of the screensaver function with the main page, it is not sure yet if this will make it to release.

Chapter Viewer:
per request of the Worcester Art Museum we implemented a menu for the chapters. This was done using jQuery Mobile’s built in grouped buttons. These buttons now animate the page viewer to the respective preview. Example: if chapter 2 is clicked the application will animate to the chapter 2 instantly for quick access.
Here is a screenshot:

That wraps up the additions and modifications to the page viewer, until next time!
-Joe

From the blog itsJoe's Blog » cs-wsu by itsjoeyoung and used with permission of the author. All other rights reserved by the author.

Page Viewer 0.3

So the page view has made it into the final production! The goal with the page viewer is to have it function as the main menu for the user to access the content.
With this acceptance into the final product and detailed requests from the art museum we tailored 0.2 to fit the requirements.
First off the project will consist of a main menu and sub-menus:
The main menu will consist of 3 links to sub-menus:

  1. “Story of the Orantes”
  2. Photo Galley
  3. Activities

Story of the Orantes Sub Menu:

1 ARCHAEOLOGY
2 WHAT ARE ORANTES?
3 ORANTES IN THIS EXHIBITION
4 HISTORY OF ORANTES AT THE MUSEUM
5 MATERIALS AND CONSTRUCTION
6 CONSERVATION
7 TECHNICAL AND SCIENTIFIC ANALYSIS OF THE WORCESTER ORANTES
8 WHY IS THE HEAD MISSING?

Photo Gallery is a direct link

Activities sub menu:

1 COLORING
2 PUZZLE

The sub-menu links will go directly to other groups applications.
With the new specifications for the application we removed all dynamic content and buttons for the menus and replaced the with images.

Here is a screenshot of the “main menu”

Until next time!
-Joe

From the blog itsJoe's Blog » cs-wsu by itsjoeyoung and used with permission of the author. All other rights reserved by the author.

article chapter update Week April 29

This week, people from Worcester Art Museum come to the class and gave each of the content group some suggestions to make our app looks nicer and more usable. Her suggestion for our group is follow:

First, make the interface more simpler, so when the readers scrolling the article, the pictures will not fly everywhere;

Second, add the lightbox feature into the chapter. Although I have set up the feature, but we are not yet to combine. 

Third, since they have HD pictures, they want us to make zoom function into the app, which we disable the function at beginning. 

This week, with joe’s help, my lightbox function now is working in the app.

http://cstest.worcester.edu/development/li/zoom/CS401Spring2013-user_interface/articles/archaeology.html

My primary work is working on the zoom function. My goal is to having zoom function, while doesnot effect other chapters. 

By talking with my classmate, Williams, he told me the way  how to disable the zoom function. 

 

Goes in <head> of html

<meta name=”viewport” content=”width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no” />

 
Goes in <javascript>
 
<script type=”text/javascript”>
      $(document).bind(‘touchmove’, function(e) { e.preventDefault(); } );
    </script>
 
And the next thing is to make my lightbox zoom function work. while does not effect my article page. 
 
After I test it, it will work if I close my lightbox in a regular size. However, if I close my lightbox pictures while I zoom in, my article chapter will be effect.
 
For the last week, I will continue working on this problem. And I will say, the article chapter is getting their!

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

What We have Now on ScreenSaver Part

Finally i got the access back to my blog. For some reason i have not been able to receive the password-reset email for my WordPress account.

Now, for the screensaver part, we have the code almost ready. According to the design Tim asked us to make on our app, the screensaver part has 2 parts as i mentioned on my previous post: a screensaver and  a introduction page.

Here is how they look like:

1st: it is a slideshow of the statues and their pieces.

Image

2nd, when any touch is done to the screen, a instruction box will pop up, and after that is the introduction screen.

Image

ImageBy swiping back and forth, we can navigate the slide of the introduction.

3rd, when the “Skip to Home” button is touched, the homepage will pop up.

Image

.

Previously, there was another introduction page we came up with with the design from the website http://www.bttls.com:Image

But due to the incompatibility of this version on the iPad, the jQuery mobile version above was chosen.

From the blog daunguyen10&#039;s Blog » CS-WSU by daunguyen10 and used with permission of the author. All other rights reserved by the author.

Week of 5/6/13: Bug fixing

This past week, I just fixed some bugs in my files

1) screensaver links to the wrong document name (easy fix).

2) IntroPage: left & right navigation buttons are (much) slower than swiping fingers, I’ve tried playing with the values in the jquery-mobile.js file to make the transition faster, which it did make it faster, but the transition was still not seamless like when swipe the fingers. So  I just decided to get rid of the navigation buttons, and replace it with “Help” button to give user info on how to navigate the pages. Now it looks like this,

Image

 

and when you click the Help button, the pop-up dialog looks like this,

Image

 

Now I will work on writing a How-To document to give Tim information on how to change the content of my pages, for future reusability.

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

Week of 5/6/13: Bug fixing

This past week, I just fixed some bugs in my files

1) screensaver links to the wrong document name (easy fix).

2) IntroPage: left & right navigation buttons are (much) slower than swiping fingers, I’ve tried playing with the values in the jquery-mobile.js file to make the transition faster, which it did make it faster, but the transition was still not seamless like when swipe the fingers. So  I just decided to get rid of the navigation buttons, and replace it with “Help” button to give user info on how to navigate the pages. Now it looks like this,

Image

 

and when you click the Help button, the pop-up dialog looks like this,

Image

 

Now I will work on writing a How-To document to give Tim information on how to change the content of my pages, for future reusability.

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

End Results

In the final week of class I find myself going over what I’ve accomplished and learned from this class. I’ve learned how to read HTML 5, not necessarily code in it however. I’ve learned Javascript and how to manage a real life software development project as well as how to interact with others in an environment where there are multiple coders. And I’ve also been able to boost my troubleshooting abilities with programming.

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

This is it…

This semester went by so fast! It is crazy to see how our progress has made over the entire length of the semester from Day 1 to now. I know for my group the puzzle, we have made a lot of progress and learned a lot. Getting a better understanding in HTML5, JavaScript, & CSS has been very helpful. Especially how my job has me doing some work at times with theses languages which make it easier now to understanding the code. The last bit of work left to do is the powerpoint presentation for next’s week final block.

This class has been a fun and a learning experience with new tools that will help us all in our future careers in Computer Science. Working with the Worcester Art Museum was just like working for a company or in my case it felt like I was reporting to my boss. I think the class definitely gave everyone a feel of what the future will be like in our paths and how it will be to meet deadlines for future managers (Tim in our case) to see for approval. Communication is key and this class really got us into that aspect of working as part of a team to complete tasks compared to any other college class.

 

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

This is it…

This semester went by so fast! It is crazy to see how our progress has made over the entire length of the semester from Day 1 to now. I know for my group the puzzle, we have made a lot of progress and learned a lot. Getting a better understanding in HTML5, JavaScript, & CSS has been very helpful. Especially how my job has me doing some work at times with theses languages which make it easier now to understanding the code. The last bit of work left to do is the powerpoint presentation for next’s week final block.

This class has been a fun and a learning experience with new tools that will help us all in our future careers in Computer Science. Working with the Worcester Art Museum was just like working for a company or in my case it felt like I was reporting to my boss. I think the class definitely gave everyone a feel of what the future will be like in our paths and how it will be to meet deadlines for future managers (Tim in our case) to see for approval. Communication is key and this class really got us into that aspect of working as part of a team to complete tasks compared to any other college class.

 

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