Category Archives: TOS

New Screensaver

Now, our screensaver part seems to be done.  Tim wanted the introPage’s response to the wipe actions to be quicker. We could decrease the time delay for transition effect to have an improvement, but it isn’t a really significant improvement. We believe the reaction speed to the swipe actions depends on the realization of jQuery to the swipe actions/touches.

With the sense of improving, i also made another screensaver as a second choice since i also like a continuous motion pattern (beside fading or popping) for our screensaver. To me, this design makes a sense of showing a collection of all the images related to the Orantes at the first glance with the continuous movement. Here is how it looks like (these images were captured at different moments of the movement).

Screen Shot 2013-05-10 at 11.34.12 PMScreen Shot 2013-05-10 at 11.28.16 PM Screen Shot 2013-05-10 at 11.34.31 PM

The background color can be changed flexibly for an attractive look.

I let Tim know and Im waiting for his response on this new pattern.

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

Week ending 5/11/13: Fix more things & How-To doc

For this week, there wasn’t much left for me to do.

After I showed Tim the recent version of the Introduction Page, he tested it and told me that the transition between pages is a bit sluggish. So I’ve read up on possible solution to fix this, and it is to change the transition value of the .in, .out in the jquery-mobile css file (default to 350ms). So after I did that, I found that the “transition effect” is faster, but the transition is still “slow.” I think this is due to jquery mobile recognizing the “swipe” motion, so there is really nothing else I can do with my little knowledge of javascript.

And Tim said that if this cannot be fixed then it would be ok if I put the button back and choose the transition effect with the least delay. So I put the left & right navigation button back, with the default transition effect of “fade” for those buttons. However, the “Help” button is still there, and we can still navigate the pages by swiping.

I also wrote up a short document on how to change the contents of the Screensaver and the Introduction Page, and it is very simple so I think Tim should not have a problem understanding it.

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

Week ending 5/11/13: Fix more things & How-To doc

For this week, there wasn’t much left for me to do.

After I showed Tim the recent version of the Introduction Page, he tested it and told me that the transition between pages is a bit sluggish. So I’ve read up on possible solution to fix this, and it is to change the transition value of the .in, .out in the jquery-mobile css file (default to 350ms). So after I did that, I found that the “transition effect” is faster, but the transition is still “slow.” I think this is due to jquery mobile recognizing the “swipe” motion, so there is really nothing else I can do with my little knowledge of javascript.

And Tim said that if this cannot be fixed then it would be ok if I put the button back and choose the transition effect with the least delay. So I put the left & right navigation button back, with the default transition effect of “fade” for those buttons. However, the “Help” button is still there, and we can still navigate the pages by swiping.

I also wrote up a short document on how to change the contents of the Screensaver and the Introduction Page, and it is very simple so I think Tim should not have a problem understanding it.

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

Article Viewer 0.3

This version has had the following changes done:
Images now take up the entire image viewing portion of the page.
The image no long scroll they just appear, in addition to now having a position for captions.
The scroll triggers have been removed, the focus change is now all touch.
Added links in the footer to acknowledgements and back to the chapter page viewer.
Font size has also been increase.

The images now have a different function to change:

function swapImage(){
$(‘#image-display’).css(“background-image”, “url(images/”+article+”/p_”+currentRow+”_thumb.jpg)”);
}
This function called on the article variable which is defined in the <body chapter=”X”> declaration in the html folder. This allows for dynamic images based on a common naming convention “/X/p_#_thumb.jpg”.

I removed all scroll functions and just utilize the p.on(‘vclick’) function. The font size was a simple CSS change of p{ font-size: 2em;}

Here is a screenshot of the current version – note the images have no been submitted to fit the div:

Until next time!
-Joe

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

Article Viewer 0.2

One of the clients tested the article viewing concept and had a few suggestions:

The first suggestion was only having a fixed footer and removing the header as well as the previous and next buttons above the article. This was implemented with relative ease, the only issue was the footer which would disappear whenever a function was called that did animation. I learned that this is a default setting for jQuery mobile when you make the footer fixed.
Here is the code for the footer div so that it didn’t move when an animation or click was executed:

<div data-role=”footer” data-position=”fixed” data-mini=”false” data-tap-toggle=”false” class=”ui-footer ui-bar-a ui-footer-fixed slideup” id=”footer” role=”contentinfo”>
</div>

Then i just added the home button, the previous button and the next button. In place of the old buttons I placed the title of the current chapter in a header tag.

The second suggestion which was a solution to a problem in the design of the scroll to switch focus concepts. If there is no where to scroll the user can’t change focus and therefor can’t view the other images. This suggestion was a touch the paragraph to execute the animation and focus changes. This was a very simple and elegant solution; all I added was an if statement that was essentially if the page is not scrolling implement a click function on the p tag to execute the same focus change functions. However in the else statement I also added a function that would allow the clicking on the p tag but it was implemented by scrolling the page, not directly changing the focus. 
In essence: If(no scolling){ p.click -> execute focus change functions} else{ keep scroll functions p.click -> scroll to the proper section}

This worked without any issues and I was a relaly big fan of the touch to change focus solution!
Here is a screen shot of the new setup!

Until next time!
-Joe

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

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&#039;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&#039;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&#039;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.

Last Class!

Today we had our last class! Everything seems to be mostly done just putting everything together and making sure it runs correctly. The only thing that had to be done today was put licensing in the all the code files. Next week we will meet and each group will give a presentation on how the entire semester went and what exactly it is that we did and how we got to our finished product. It has been a long semester and a lot of hard work but it was an interesting class to take. We finally got to take what we have been learning and use it in a real world project. We got to learn how to deal with a company and take what they imagine there application to look like and actually bring it to life. I think we did a good job with grasping all the pieces they wanted in the puzzle app! I can’t wait to be able to visit the Worcester Art museum and actually use the app that we have been working on all semester and be able to say my classmates and I built this!

From the blog klentblog » cswsu by klent22 and used with permission of the author. All other rights reserved by the author.