Showing posts with label The Newbie Review. Show all posts
Showing posts with label The Newbie Review. Show all posts

Monday, January 21, 2008

Review: Adding Sound to Your Website

JailerJoe avatar
I need to start out this tutorial review by saying I’m not a big fan sound on web pages. In fact, I hate it when I’m innocently surfing along, click on what might be an interesting link and am assaulted by some crummy keyboard generated auto-playing MIDI cover for “Another One Bites the Dust”. You know what I’m talking about, we’ve all been there. Oh and if your site is guilty of this egregious violation to my ears, STOP IT!

Okay, deep breath............

As averse as I am to the above, on-click type sounds on web pages are okay in my opinion as long as they serve a purpose and are used judiciously. I’m not about to define what judicious is but will say that “I know it when I see it”. With that in mind I decided to try adding some sound to one of my websites and it just so happens that Vince (aka wizeman of V2C Studios and rwReview.com) kindly posted an excellent screen cast tutorial of how to do just that using JavaScript snippets that he wrote and SoundManager from schillmania.com.

Vince begins his tutorial by recommending anyone not familiar with JavaScript (me) go to w3school to learn the basics by working through one of their tutorials, but he also states that if you follow his instructions closely you should be able to complete his SoundManager tutorial. That’s what I did and I completed the tutorial with everything working as it should. I am going to check out the w3school JavaScript tutorial when I get a little extra time (says this as if it will ever happen).

The only real problem I encountered was mostly my fault but I’m also going to blame RapidWeaver as well. I’m not going to go into the gory details but if you’re interested in reading about my publishing problems, check out this forum thread. Sufice it to say I wasn’t thinking when I decided to work through the tutorial and I just applied it to the site file that opened when I launched RapidWeaver. This was an as yet unpublished site and was quite large. Like I said I’m not going into details.

The tutorial was very easy to follow and Vince has a pleasant voice and an easy-on-the-ears speaking style. Vince clearly lays out the steps involved and I was able to understand what was going on with very little effort. I have a site in mind that I think I’ll be able to incorporate some sound so this was a fun and useful tutorial indeed. Check out Vince’s SoundManager tutorial and many more at his rwReview.com website.

Thanks Vince!

Saturday, January 12, 2008

Review: RWcss by Larry Pollock

JailerJoe avatar
When Larry Pollock (aka Sundog on the RW forums) released RWcss last September I immediately purchased the book. Since hopping aboard the RapidWeaver train I’ve long wanted to learn some CSS and knowing Larry’s reputation as one of the CSS code gurus on the RapidWeaver forums, I figured I couldn’t go wrong.

Unfortunately, shortly after I bought the book, my non-RapidWeaver life intruded and I only had time to briefly skim the book. With the new year I made sort of a mini New Years resolution to thoroughly read RWcss and work through the tutorial (remember the promise I made to myself in my Videobox tutorial review?). Well I finally did it and here are my impressions of RWcss.

The book comes as a 73 page PDF which Larry has thoughtful laid out in such a manner that you can print and have it bound. I’m too cheap to do that and a PDF is just hunky-dory for me. When you unzip the package you’ll find four items:

  1. The RWcss Book PDF itself

  2. a Basic RapidWeaver Theme

  3. a CSS FIles folder (containing a 23 page PDF of basic CSS code, a Rich Text document of CSS used in the book which is especially good for copy and pasting along with the tutorial, and Rich Text document containing Greybox CSS)

  4. a “Demo & Tutorial Stuff” folder (containing a Rich Text document of the CSS used in the demo, the demo site RapidWeaver file and all the images used in the demo).

The book is divided into three parts: a basic information section, a full theme modification tutorial and a reference section choked full of links to external resources. Larry recommends that the reader read through the first part “several times” and this is good advice. I read through it a couple times and during the tutorial, I went back and reread parts. Surprisingly, it’s a pretty easy read. By that I mean, considering the content (CSS code) and it’s intended audience (CSS newbies like me), it was interesting and not too heavy. Larry has a nice writing style and I was able to follow along and understand what he was saying with very little effort.

In the first part of the book Larry lays the foundation for the tutorial by going over and explaining the basics of CSS. He explains how browsers interpret CSS and how RapidWeaver theme styles affect what is displayed. The rules for how styles “cascade” (CSS stands for "Cascading Style Sheets"), are laid out and Larry explains some of the terminology used when discussing CSS.

In this first section Larry also takes us through modifying a theme using example CSS code entered into the Custom CSS box in RapidWeaver’s Page Inspector. Many of his examples included screen shots graphically showing what the results look like. He also briefly touches on some of the features third party theme developers include with themes, like custom header options, as well as using RWMultitool.

Larry then goes on to briefly explain some common CSS terminology and corresponding “parts”. This is where it gets a bit deep and it was very helpful, as Larry suggested, to reread this part. He also touches on page specific CSS in this section as well as including a developer “tips” section. This last part was a particularly interesting read.

The next main section of the book is the tutorial. Larry lays it out in a fairly straight forward fashion that is quite easily to follow. For the most part you’re copying and pasting code from either the book itself or from the included CSS rtf to RapidWeaver’s Custom CSS panel. I’d suggest not bothering with copying from the book and just using the CSS rtf. The reason being that when you copy from the book, you’ll sometimes inadvertently (and unavoidably) copy some of the tutorial text.

For the most part, the tutorial went as intended. I did encounter a couple minor problems but nothing that prevented me from completing it. The first popped up (literally) when I went to load the RW tutorial file. I got an RW error pop up message that said “Could not find theme. Could not locate the theme...” I immediately emailed Larry and he responded within an hour. The fix was as easy as applying the Blog Pop duplicate theme that I’d created in the previous step to the blank RW demo site file.

The next minor problem I encountered was when I modified the QuickTime page. This step came late in the tutorial and Larry doesn’t go into a lot of detail on these later steps. Larry doesn't include a movie file for this page (I’m assuming for size reasons) so I just added my own in Edit view. I’ve never used a QuickTime page so was unprepared for the result: the movie completely took over the page, overlapping most of the navigation menu.

Lastly, because I was copying from the CSS rtf file, the instructions and accompanying screenshots in the book didn’t exactly follow the results I was getting. For example, in the book, Larry tells us to past this code into the Custom CSS panel:


#pageHeader {
background: #005400 url(assets/redrock_golf.jpg) no-repeat top
left;
}


Next he states to add this code to the #pageheader CSS:


height: 244px;


In the CSS rtf file, however, the height attribute was already included in the code. This really is no big deal and I immediately knew what was going on.

All in all it was a fun exercise. My tutorial site turned out pretty much how Larry illustrated. There were a couple minor bumps in the road but nothing that I couldn’t figure out by myself. Larry was quick to reply to my one support question and had I thought about it a little bit, I probably would’ve been able to find the solution on my own.

If I were to make one suggestion, it’d be for a more in depth discussion of CSS terminology and the corresponding mechanics. For example, I’m still not entirely sure what Selectors are and what they do, and Larry mentions divs but never really explained what they are and how they fit into this whole CSS thing. This, of course, might be beyond the scope of this book. I’m sure there’s a “CSS for Dummies” that I could pick up that delves more deeply into this sort of thing.

I highly recommend RWcss, especially if your a relative newbie to RW and are itching to modify themes a bit. You’re not going to completely learn CSS from this book and I’m sure this is not what Larry intends. What you are going to learn are some fundamentals and you’ll walk away with a good basic understanding of how to use CSS in the Custom CSS panel. If you’re like me, you’ll also probably walk away with a desire to learn more. I can’t wait for RWcss II (hint, hint Larry)! At $14.95 (USD) RWcss is a steal and you can get at Larry’s InsideRapidweaver.com website.
Editors note: A CSS selector is the html element that you are applying style to. In the case of:

#pageHeader {
background: #005400;
}
"#pageHeader" is the selector as it is the item in the html that you want to change the look of.

A "div" or <div> tag defines a division in the in the document that is a block level html element, meaning that by default, it exists on it's own in the document, occupying the full page width (unless we style it otherwise). It is a common element in RapidWeaver theme development used mainly for layout.

Tuesday, December 18, 2007

Working through VideoBox

JailerJoe avatar

Que the Mission Impossible music...

Dah dah dahn nah, dah dah dahn nah
Dah dah dahn nah, dah dah dahn nah, etc.
My mission this week, and I chose to accept it, was to work through and then review a user contributed tutorial from the forum. Judging by all the forum questions inquiring about Lightbox, LightWindow, Slimbox, graybox, thisbox and thatbox, I thought a tutorial involving one of them might be a good one to work through. On my sites I use either the built in Lighbox triggers of Loghound's excellent PlusKit or one of the templates included with Scott Mackie's wonderful RapidAlbum but there are many folks who don’t use those so I thought this would be a good area to work in. Plus, I’d previously not tried to integrate any kind of “box” effect with video.

The tutorial I worked through was done on VideoBox and posted by kbbrux. On the main tutorial page kbbrux posted a basic introduction including a link to where you can download the necessary VideoBox files as well as a bit javascript code that needs to be copied and pasted into your project. kbbrux’s post then links to the actual tutorial, a screen cast he has hosted on his own site.

He starts out stating that he’s using RW’s Alpha theme and that he’s been able to get this to work with Silk as well. Well of course using a stock RW theme just isn't good enough for me. I have to muddy the water and use the theme I’m currently playing around with, Henk Vrieselaar’s gorgeous Vertical Image 1 theme. I generally have a test site already made up that I switch themes around on, install and play with new plug-ins, snippets, etc. It so happens that I’d just bought Vertical Image so that was the theme loaded on my test site.

I watched the screen cast all the way through once and then went back and started it over, following along on my own test site. To get VideoBox to work with RapidWeaver is very simple (or so it seemed). First, I download the VideoBox file kbbrux had linked to in tutorial post on the forum. The file came zipped and when decompressed contained a single video folder. This folder and all it’s contents needed to be placed into the themes Css folder so I right-clicked on the theme in the theme drawer, made a duplicate and then right-clicked on the duplicate theme to “Show Contents.” Once the folder contents window opened I dropped the video folder into the Css folder.

Out of curiosity I opened up Vertical Image's Css folder just to see what all was in there. In kbbrux’s video tutorial he was using Alpha and there where three other subfolders in the Css folder. Not so with Vertical Image which had no less than 24 folders. Hmmm..... What are the odds of this working without a hitch and not conflicting with any of those other files?

The next step was to copy the javascript code kbbrux had posted in the tutorial and then to paste that in the Custom Header box in the Page Inspector. Why it goes in there and not in the custom Javascript or CSS box I have no idea. Bear in mind I know little html and absolutely NO Css, Javascript or any other kind script for that matter. One of these days I WILL work all the way through Sundog's RWcss book... One of these days...

Next it was time to actually add the video file to my page. First, you have to add the video to the page as an asset, which I did. Once again, however, I veered off course from the tutorial and attached the video to text I had entered into a Text Block. kbbrux used a Styled Text page. In the Add Link dialog box, I named the link, pointed it at the video file asset and in the rel box typed in vidbox 640 480 as the tutorial instructed.

This is where things went bad. When I previewed the page VideoBox opened up but my video didn’t play. I published the site anyway hoping that might fix things but it didn’t. I figured for sure that my straying from the tutorial by using a different theme and a block page was the cause of my troubles so I started again from scratch using Alpha and a plain old styled text page. Same result! What the heck?

In the tutorial, kbbrux used a .mov file and the file I was trying to use was a .mp4 file. Could that be the problem? My dog knows more about JavaScript, Css and html than I do so I wasn’t about to open up the page in an editor to troubleshoot. Its all greek to me and I wouldn’t know what I was looking at anyway. Instead I recorded a new screen capture movie but made sure to save it as a .mov file. To keep things tidy, I placed the video in the same folder as the one I’d stored the original .mp4 file and proceeded to repeat the tutorial. Still no joy!

What had I done? I’d run (quickly) out of troubleshooting ideas. Out of sheer desperation and unwilling to admit defeat I dragged the video file to my desktop. I don’t know why I did that, I just did. I guess I figured it couldn’t make anything worse. I re-added the file via the Assets window and previewed one last time. It worked! I then tried it in Vertical Image and it worked there too although the VideoBox window opened up kind of behind the sidebar nav menu.

I have no idea why it worked but I will tell you the folder I kept the .mp4 in originally is four levels down in my Documents folder. My theme test file is in a different folder altogether so it’s not that the video file has to be in the same folder as the RW file. I still have no idea why this makes a difference but I’m happy I finally got it to work.

All in all it was a fun and quick tutorial to work through (at least it’d be quick for most people). The only thing I’d change is that when kbbrux is typing in the Add Link drop-down sheet, it’s very hard to see what he’s actually typing. The screen cast seemed to be sized approximately 640 X 350 which would be okay if the camera was zoomed in a little more on the action. As it is the whole RapidWeaver screen is shown. A slightly larger movie or more zooming would make this screen cast easier to watch.

Other than that, the tutorial is short, concise and easy to follow and it adds a really nice effect to videos you might post on your own site. After having failed in my first couple attempts, things went smoothly and as planned as soon as I moved my movie file to the desktop. Not sure why I had to do this and it certainly wasn’t kbbrux's fault.

Speaking of kbbrux, he’s posted eight other screencast tutorials on his site. They’re all equally informative and well done. You can check them out on his RapidWeaver screen-casts page. Thanks kbbrux!