Browse through blog tags below:
Displaying entries tagged: blog page
Blog Entry Title
Date
Tags
Splash 8.42 is now live.
February 24, 2008 - 12:38
- Splash - Photo Album Page - Blog Page - LOST
I dislike my tendency to not document more things that cross my mind and my life, in my blog. Substitute blog with any other method one would use to document/discuss whatever they choose, I think it is beneficial to have a place to do these things. It's interesting to think about the differences between an online blog and a personal diary. Both could serve the same purpose, but hopefully don't. I do not keep a diary. Every time I think the word diary I think of a girly book. Substitute diary with journal. I do not keep a journal, but I used to. Holy crazy, I would never document any of the stuff in those books in an online blog. Maybe I still do keep a journal and it's just been a long time since my last entry. Yes, no reason to close that book just yet, I revise my previous statement.
There is a bunch I would like to talk about, but I just don't know where to begin. Instead, I will do something I haven't done in like 7 months, I'm going to list some pending and outstanding web site features and issues.
-The current version of the splash page is technically 8.41, but I am now deeming it 8.42 to account for minor undocumented changes.
-Photo album page:
This page is to be replaced by my 3rd generation album page, which is currently on it's 10th revision (pic10.php). The page currently linked to via "Picture Album Beta" is pic8.php . The 2nd generation page was only linked to via a blog post, it was never more than a proof of concept page. The most relevant outstanding issues with pic10 include:
-IE not unhidding hidden divs after thumbnails are loaded and resized. This is a difficult issue that I believe will be resolved using proper image loading.
-the inability to honor $_GET[] variables, therefore being unable to jump to specific albums. This functionality will likely not be very difficult to implement.
-the page sometimes not displaying properly on it's initial load. This problem will likely be fixed when I work on handling $_GET variables. For now, a user refresh should do the trick.
-various minor styling and external linking issues. Not a major issue, nothing I am dreading to fix.
-The bottom line is that this page is a disaster, from a coding point of view. I implemented a ton of new techniques I had just learned, and it is painfully obvious. I learned new and better way of doing things on the fly, and implemented them as such. My plan is to implement/fix the above bullets without having to re-code the entire page. I am pleased with how the page works from a user point of view and will be happy if I can wrap it up and not worry about it ever again.
-Blog page:
This page was never intended to be used as long as it has been. It was coded in a weekend and and lacks a ton of features. I am saddened by the fact that it is was people get if the link to me via RSS feeds. The most relevant outstanding features and issues with this page include:
-The inability to view and post comments.
-The fact that all posts are displayed when the page is entered directly.
-The "tag cloud" could use some help.
-I like the look of the page. The images that are used to give it the feel of an actual book are pictures I painstakingly took of a blank page in one of my previously mentioned journal books; getting shots that would seamlessly repeat along the Y axis took some time.
-None of the above issues are difficult to implement. I have been reluctant to do any work on this page because I will likely re-build/code it from the ground up. I'm not sure how high of a priority this is at this time.
-Backend pages:
User control page and user log page:
-I am currently working on a project with a friend that will likely yield much improved backend pages (administrative pages not for users). Our project specifically deals with user logs but will likely prompt me to redo the majority of my backend pages.
-I am happy enough with my current Blog post entry page to not feel the need to work on it at all, at this time. I am currently running version 0.010 of this page.
Running parallel to the website in regards to projects I am dedicated to working on is Discomentary Volume One. I would say that this video project is my number one priority. With that said, I can't just bang it out with a ton of man hours, it's stuff that needs to be thought and re-thought about. I am close to reaching one milestone with Discomentary, once that is reached, I will begin a ton of footage editing and cutting.
I'm kind of tired right now so I'm not going to write much more.
This pic is from the other day. I'm holding the best rubber bouncy ball ever made. I got it at the NBA store in NYC. I went online to see if I could buy more but I couldn't find it listed in the online catalog. I instead bought a box of 50 bouncy balls from a store other than NBA.com . It was a mediocre alternative pick, but it was the best I could find. Yes, those balls join the new LOST Xbox 360 game and a new Bluetooth headset as items I purchased that night drunk.
From the inside, out, good night.
There is a bunch I would like to talk about, but I just don't know where to begin. Instead, I will do something I haven't done in like 7 months, I'm going to list some pending and outstanding web site features and issues.
-The current version of the splash page is technically 8.41, but I am now deeming it 8.42 to account for minor undocumented changes.
-Photo album page:
This page is to be replaced by my 3rd generation album page, which is currently on it's 10th revision (pic10.php). The page currently linked to via "Picture Album Beta" is pic8.php . The 2nd generation page was only linked to via a blog post, it was never more than a proof of concept page. The most relevant outstanding issues with pic10 include:
-IE not unhidding hidden divs after thumbnails are loaded and resized. This is a difficult issue that I believe will be resolved using proper image loading.
-the inability to honor $_GET[] variables, therefore being unable to jump to specific albums. This functionality will likely not be very difficult to implement.
-the page sometimes not displaying properly on it's initial load. This problem will likely be fixed when I work on handling $_GET variables. For now, a user refresh should do the trick.
-various minor styling and external linking issues. Not a major issue, nothing I am dreading to fix.
-The bottom line is that this page is a disaster, from a coding point of view. I implemented a ton of new techniques I had just learned, and it is painfully obvious. I learned new and better way of doing things on the fly, and implemented them as such. My plan is to implement/fix the above bullets without having to re-code the entire page. I am pleased with how the page works from a user point of view and will be happy if I can wrap it up and not worry about it ever again.
-Blog page:
This page was never intended to be used as long as it has been. It was coded in a weekend and and lacks a ton of features. I am saddened by the fact that it is was people get if the link to me via RSS feeds. The most relevant outstanding features and issues with this page include:
-The inability to view and post comments.
-The fact that all posts are displayed when the page is entered directly.
-The "tag cloud" could use some help.
-I like the look of the page. The images that are used to give it the feel of an actual book are pictures I painstakingly took of a blank page in one of my previously mentioned journal books; getting shots that would seamlessly repeat along the Y axis took some time.
-None of the above issues are difficult to implement. I have been reluctant to do any work on this page because I will likely re-build/code it from the ground up. I'm not sure how high of a priority this is at this time.
-Backend pages:
User control page and user log page:
-I am currently working on a project with a friend that will likely yield much improved backend pages (administrative pages not for users). Our project specifically deals with user logs but will likely prompt me to redo the majority of my backend pages.
-I am happy enough with my current Blog post entry page to not feel the need to work on it at all, at this time. I am currently running version 0.010 of this page.
Running parallel to the website in regards to projects I am dedicated to working on is Discomentary Volume One. I would say that this video project is my number one priority. With that said, I can't just bang it out with a ton of man hours, it's stuff that needs to be thought and re-thought about. I am close to reaching one milestone with Discomentary, once that is reached, I will begin a ton of footage editing and cutting.
I'm kind of tired right now so I'm not going to write much more.
This pic is from the other day. I'm holding the best rubber bouncy ball ever made. I got it at the NBA store in NYC. I went online to see if I could buy more but I couldn't find it listed in the online catalog. I instead bought a box of 50 bouncy balls from a store other than NBA.com . It was a mediocre alternative pick, but it was the best I could find. Yes, those balls join the new LOST Xbox 360 game and a new Bluetooth headset as items I purchased that night drunk.
From the inside, out, good night.
lazy Sunday...
June 3, 2007 - 5:1
- blog page - Splash 8 - life tips
I wasn't incredibly upset today when it started pouring, as it gave me a guilt free opportunity to stay inside and work on some different stuff.
To talk "Geek" for a brief second:
I got a good amount of work done on my Blog section. I am not sure how it will look tomorrow on Internet Explorer, but I am happy with the Firefox results. I have thus far incorporated "search by tag" functionality but still need to work on a few additional blog search queries. I haven't done much with formatting the layout of the blog entries, nor is there currently any opportunity for users to add comments. I expect to work on those features in the very near future. Worthy to note, one hassle was the fact that my old DB was using mySQL 4.0 and some of my searching requires sub queries (available in version 4.1+, I eventually learned). Luckily, godaddy.com offers the option to set up new databases using version 4.1 or 5, so all I needed to do was create a DB and import the existing data. This thankfully went off smoothly.
Ok, done with that. I don't have a ton else for ya. I do have one comment for everyone out there: It's usually not a good idea to blind speakerphone a person. I got blind speakerphoned today, and it may or may not have lead to some embarrassment for people in the car. In this case, no harm was caused to myself, and likely none to those involved; but the potential definitely does exist for a scenario to arise where either the caller and/or listeners get a little dose of embarrassment when something is said that wouldn't be appropriate for the audience within listening distance.
Take that tip to the bank and save it with the rest, because I am full of good ideas today :-)
If I don't have a chance to tell you later on, enjoy Sopranos tonight!
To talk "Geek" for a brief second:
I got a good amount of work done on my Blog section. I am not sure how it will look tomorrow on Internet Explorer, but I am happy with the Firefox results. I have thus far incorporated "search by tag" functionality but still need to work on a few additional blog search queries. I haven't done much with formatting the layout of the blog entries, nor is there currently any opportunity for users to add comments. I expect to work on those features in the very near future. Worthy to note, one hassle was the fact that my old DB was using mySQL 4.0 and some of my searching requires sub queries (available in version 4.1+, I eventually learned). Luckily, godaddy.com offers the option to set up new databases using version 4.1 or 5, so all I needed to do was create a DB and import the existing data. This thankfully went off smoothly.
Ok, done with that. I don't have a ton else for ya. I do have one comment for everyone out there: It's usually not a good idea to blind speakerphone a person. I got blind speakerphoned today, and it may or may not have lead to some embarrassment for people in the car. In this case, no harm was caused to myself, and likely none to those involved; but the potential definitely does exist for a scenario to arise where either the caller and/or listeners get a little dose of embarrassment when something is said that wouldn't be appropriate for the audience within listening distance.
Take that tip to the bank and save it with the rest, because I am full of good ideas today :-)
If I don't have a chance to tell you later on, enjoy Sopranos tonight!