My last blog was about a crazy javascript issue on swapping SWF files within a page. I even resorted to emailing the ISYS List (which is a list that ISYS BYU students use to communicate and keep in contact). Well, what was funny was instead of a straight response I got a bunch of criticism for the site I created. Even so, I was still determined to find the solution.
After about a week I resorted to asking my Professor, Dr. Liddle, about what I could do. He then explained that SWFObject (http://code.google.com/p/swfobject/wiki/documentation). Well, by myself I got far. However, I still needed his direction to help me get the results I wanted. It took quite a bit of time, but we finally figured out how to switch out the SWF's. I am really lucky to have a professor who would take the time to help me with Javascript. Now, I am finally able to make some real progress with the site. At any rate you can see my dad's updated site now. I am very pleased with the results (check out the Completed Projects and Current Projects page for what I am talking about).
http://potentialelectricllc.com/
Tuesday, February 24, 2009
Monday, February 16, 2009
A Bit of Frustration
Some of you know I do a bit of websiting on the side. I'll admit, I'm not great. I know very little about site design and I am trying to learn it as a side thing (more of like an addicting hobby when I get the chance). Anyways, for quite some time I have been stumped by the problem of switching out SWF files. After searching for hours (literally) I finally found what I thought to be the code I needed. After another hour of messing around with the code, I got it to work...yet, it only worked on IE. Sad. I then was wondering why the SWF files weren't swapping in Firefox or Chrome (I sort of gave up on Safari as I'm not a Mac fan). Still, I was determined to find out what was the difference.
After reading up on how Javascripts work, I did notice that if I used Alert(), I could "see" what was passing through in the functions. Turns out there were very little differences, but then what was really weird was that I could actually see the SWF file I wanted to appear in the spot it should have. Then when I clicked "Ok" on the Alert the entire SWF disappeared from sight. In both Chrome and Firefox the same thing happened. I was wondering why only IE worked fine.
After a few hours of testing I decided to hit the ISYS list. I usually don't resort to such measure, but I figured I should anyhow. The first response was useful as I was using .innerHTML and learned that I shouldn't be using that. Instead I was told to use the DOM methods. So, I did. Yet, the same results occured. The other responses thus far were sort of humerous as a few were telling me how aweful my site looked (true, it doesn't look great, but that wasn't my question).
Well, now it's day two and I still haven't gotten anywhere. Thus, I am writing this blog about my frustration. The link below is a demo of what I am trying to accomplish (but, again, it only works for IE).
http://potentialelectricllc.com/c.htm
After reading up on how Javascripts work, I did notice that if I used Alert(), I could "see" what was passing through in the functions. Turns out there were very little differences, but then what was really weird was that I could actually see the SWF file I wanted to appear in the spot it should have. Then when I clicked "Ok" on the Alert the entire SWF disappeared from sight. In both Chrome and Firefox the same thing happened. I was wondering why only IE worked fine.
After a few hours of testing I decided to hit the ISYS list. I usually don't resort to such measure, but I figured I should anyhow. The first response was useful as I was using .innerHTML and learned that I shouldn't be using that. Instead I was told to use the DOM methods. So, I did. Yet, the same results occured. The other responses thus far were sort of humerous as a few were telling me how aweful my site looked (true, it doesn't look great, but that wasn't my question).
Well, now it's day two and I still haven't gotten anywhere. Thus, I am writing this blog about my frustration. The link below is a demo of what I am trying to accomplish (but, again, it only works for IE).
http://potentialelectricllc.com/c.htm
Thursday, February 12, 2009
It's Over!
Well, after waiting well over 2 days I finally found out the results to the Omniture Competition. Sad to say, we did not make the semi's. I think what really bothered me was the communication.
First, I receive a have typed email from Omniture and then I get partial responses to my emails. I would think that they would at least make sure that this competition process went as smoothly as possible (considering that this is not the first time they did this competition). Also, since they have done this before, I would think that they would inform the students better about what was going on and why they took so long. It took our class to email the BYU staff about it to email them until we received an email saying they would be delayed.
Still, I think the waiting is what bothered me the most. Taking two days without any updates on how things were was terrible. Then, finding out that I didn't even make the semi's made me feel like I waited for nothing. Yeah, I know I can't expect much considering that it was my first time competing, but I would think the process could have gone a lot better.
I did email them and asked them what I could do to improve, but after what's been going on, I have my doubts that they will reply with anything of use. Yet, it's still early. My faith in their communication might be renewed if they give some useful feedback. Even so, I am not sure if I would ever compete in the Web Analytics competition next time, as my experience has been a lot more negative than positive...
First, I receive a have typed email from Omniture and then I get partial responses to my emails. I would think that they would at least make sure that this competition process went as smoothly as possible (considering that this is not the first time they did this competition). Also, since they have done this before, I would think that they would inform the students better about what was going on and why they took so long. It took our class to email the BYU staff about it to email them until we received an email saying they would be delayed.
Still, I think the waiting is what bothered me the most. Taking two days without any updates on how things were was terrible. Then, finding out that I didn't even make the semi's made me feel like I waited for nothing. Yeah, I know I can't expect much considering that it was my first time competing, but I would think the process could have gone a lot better.
I did email them and asked them what I could do to improve, but after what's been going on, I have my doubts that they will reply with anything of use. Yet, it's still early. My faith in their communication might be renewed if they give some useful feedback. Even so, I am not sure if I would ever compete in the Web Analytics competition next time, as my experience has been a lot more negative than positive...
Monday, February 9, 2009
Omniture Competition - Thoughts for First Part
I had an entire weekend that was free...sort of. The only thing I worked on was the BYU Omniture Competition. I would say my first experience with this project was, overall, not bad. Definetely not great. The bad parts were with how slow SiteCatalyst was. I was really frustrated at times where SiteCatalyst told me that the "Data was not Available" or "You do not have access to this data." Also, the load time after each query took forever.
Contrastingly, the good parts were the extended time. Originally I would not have had the two weekends to work on it. Now, I know I only put in a good 19-20 hours, but they were crammed in to one weekend. Even so, that extra time was much needed, as the week before was quite crazy (tests, work...etc). Anyways, I think Bryan and I did well overall. We made our presentation simple. We split it up into three parts that we thought were key to explaining what's going on with Overstock.com.
Contrastingly, the good parts were the extended time. Originally I would not have had the two weekends to work on it. Now, I know I only put in a good 19-20 hours, but they were crammed in to one weekend. Even so, that extra time was much needed, as the week before was quite crazy (tests, work...etc). Anyways, I think Bryan and I did well overall. We made our presentation simple. We split it up into three parts that we thought were key to explaining what's going on with Overstock.com.
Friday, February 6, 2009
First Experience With SiteCatalyst
This year I have recently gotten into Web Analytics. I have looked at Google Analytics and I like how straight-forward it is. Recently, I have been trying to use Omniture's SiteCatalyst to complete a project for the Web Analytics Competition. All I can say is it's a very powerful tool. However, there are also some downsides to using it.
As for downsides, the thing I noticed most was the speed. When using SiteCatalyst things can take a very long time. Sure they have an option to send the data to you, but then again, there was a lot of times where I got the result "Data Not Found." That becomes a little frustrating when you are trying to complete a project.
The ups to using SiteCatalyst is that you can find all sorts of data. I was impressed with the different types of data you could find and also manipulate the data to be more understandable. The interface is also pretty straightforward. You can basically find what you need (if it allows you). Again, the only downside is you might be waiting a while until you actually "see" the data you are looking for. Waiting really stinks.
As for downsides, the thing I noticed most was the speed. When using SiteCatalyst things can take a very long time. Sure they have an option to send the data to you, but then again, there was a lot of times where I got the result "Data Not Found." That becomes a little frustrating when you are trying to complete a project.
The ups to using SiteCatalyst is that you can find all sorts of data. I was impressed with the different types of data you could find and also manipulate the data to be more understandable. The interface is also pretty straightforward. You can basically find what you need (if it allows you). Again, the only downside is you might be waiting a while until you actually "see" the data you are looking for. Waiting really stinks.
Sunday, February 1, 2009
Thoughts on Bounce Rates
January is now over and February has arrived. I began writing blogs to blogger at the beginning of this year. To me, blogging is sort of another form of a journal for me. At any rate, I suppose my life is rather simple or uninteresting to most of the world, so I guess I can be safe on what I write.
Anyways, as many of you know (if you have been following my blogs), I am in a web analytics class. As such, we were told to track our site traffic using Google Analytics. I must say it's neat. However, one sad thing is my traffic is low. Why? Again, most likely what I said in the beginning paragraph (not interesting). As I looked at my stats, I remembered one of the topics covered in class: Bounce Rates! It's a way to see the quality of visits. If you have a high bounce rate, it means people are coming and then leaving immediately (or not staying long enough to get a good visit). I guess it could be compared to a movie. If the movie is really good, some people will come early to get a good seat. Then they watch the entire film. If it's an even more captivating movie, some people will stay until the end (thus, the length of time spent at the theater is lengthened). The same can be said about a bad movie. If it's terrible most people can't wait to leave. Some might even walk out.
In comparison, my site is, I suppose, a slightly poor movie. My current bounce rate is around the mid-upper 50%. I suppose my blogging is a bit like one of those family videos you take on one of those special occassions and it is pretty much never watched until a family member decides to look at it (or asked to). So, yeah, most of my visits have been family members. So, thanks to you all. I guess it could be worse. I could have no visitors.
Anyways, as many of you know (if you have been following my blogs), I am in a web analytics class. As such, we were told to track our site traffic using Google Analytics. I must say it's neat. However, one sad thing is my traffic is low. Why? Again, most likely what I said in the beginning paragraph (not interesting). As I looked at my stats, I remembered one of the topics covered in class: Bounce Rates! It's a way to see the quality of visits. If you have a high bounce rate, it means people are coming and then leaving immediately (or not staying long enough to get a good visit). I guess it could be compared to a movie. If the movie is really good, some people will come early to get a good seat. Then they watch the entire film. If it's an even more captivating movie, some people will stay until the end (thus, the length of time spent at the theater is lengthened). The same can be said about a bad movie. If it's terrible most people can't wait to leave. Some might even walk out.
In comparison, my site is, I suppose, a slightly poor movie. My current bounce rate is around the mid-upper 50%. I suppose my blogging is a bit like one of those family videos you take on one of those special occassions and it is pretty much never watched until a family member decides to look at it (or asked to). So, yeah, most of my visits have been family members. So, thanks to you all. I guess it could be worse. I could have no visitors.
Subscribe to:
Posts (Atom)