Thanks to Jon Gruber, I learned about Hype.
I’ve been attempting to change my WELLINGTON ROAD Pictures site from a database-driven, somewhat static site to a bit more dynamic, HTML5-based site for sometime. See here, here, here, here and here. Sigh, note the last time I attempted to make changes was almost 9 months ago.
I read about Hype, paid my $29.99 and dove in. The first thing I did was try to create an identical version of my current site. Yeah, that was easy but it was also clear that my database approach to my current layout was far superior. With my current layout, when I create a new film, I upload a poster jpeg, my film and add another line to the database. No coding required. Also somewhat boring from a design perspective.
With Hype, I needed to duplicate a new scene (think web page) for each film. And I would have to embed the Notes and Time text on each page. The management overhead is considerably more using the Hype approach. The extra steps make sense for I am duplicating a static site with a content creator for dynamic sites.
What would be required if I went to a more dynamic design? My mental image of a dynamic WRP site would be to use a film metaphor. I wanted to represent each film by a frame in a film strip. I would have a limited number of films showing and the user would move the film forward or backward to see additional films. Click on a frame would show the film using HTML5 video playback with its most important attribute, play full-screen.
So I started anew with Hype. Using a film strip image, I created 4 scenes, each with a filmstrip of four films and I added very simple text buttons to indicate forward, backward and home. It was quite simple to add transitions to make the filmstrip look like it was going from left to right and right to left for forward and backward, respectively. The crossfade transition also looked nice for showing the film. Hype did advise me that the transitions were only available in Webkit browsers (Safari, Chrome) as Opera and Firefox had yet to implement them. Hype also advised me that only Safari and IE would show the H.264 forms of my films and I would have to use WebM or Theora encoding to have them play in Opera, Firefox or Chrome. [Ed. note: The 1990’s are calling and they want their browser incompatibilities back.] It worked and it took about 2 hours worth of work. Not bad!
My review of Hype:
Ease of Use: Excellent! I did read over the manual quite quickly to gain an overview of how Hype worked. I also watched the first tutorial. So maybe 10 minutes of preparation. I quickly created a basic website than went to creating a dynamic website in 30 minutes. The design guides work well and the inspector mode continues to be an excellent method of managing metadata. With my site design, I had a significant amount of duplication of scenes. Copying elements from one scene across to the other scenes worked well and accelerated my development.Â Speed of Â development and ease of use is where Hype shines.
Hype creates a single webpage that then using dynamic properties to display new content. It works pretty well but it does break the concept of using a specific address for specific content. I thought that my previous design had this fatal flaw as well but one can right click on any movie to obtain the link to showing the specific film. What is also nice is that the specific page does show the film using the HTML5 Video tag, which means it will allow playback in fullscreen. Hype can not provide this level of specificity. Its as bad as Flash. Bummer. While this is a show-stopper for my site, I’ll continue to comment on Hype.
An issue I had with Hype was global changes. I didn’t see a method of making a global change to all selected scenes. I wasn’t able to select more than one scene then applying a change to all. There is a complete lack of contextual changes. Quite often, I would right click to see if there was something I could do to an element. Nope. No response.
Summary: I like Hype. It is easy to use, provides extremely fast prototyping and can be quite powerful using web standards. [Ed. note: I’m not even going to check if it provides validates. I mean technology that is standardized for the web as compared to Flash which is proprietary.] It does break the web so I’m not going to use it for WELLINGTON ROAD Pictures but I will use it to test out concepts. I think it would be fantastic for a class in learning about dynamic websites. I look forward to version 3.