Bui4Ever v15…coming soon!!!

Greetings folks! It may seem to many that I haven’t done any updates in awhile, but there is a reason for that…I’ve been busy spending time with Andrea, studying for school, and many projects at work. Along the way I’ve been working on some other sites and found a new, better way to do sites which led me to Bui4Ever v15…the xhtml strict incarnation of Bui4Ever. Keep checking back for the offical launch!

Bui4ever v15 coming along nicely

Bui4Ever v15 is coming along very nicely! Using WordPress to handle all my content has taken a huge load off my chest. I’m now able to redistribute a considerable amount of time and effort from architectual layout semantics and focus on design. I’m about done with template modification and will be transfering all my data from v14 to v15 shortly. I should be able to officially launch v15 by the end of this week fully functioning (*crosses fingers*).

The biggest foreseeable difficult is Gallery. I’m not entirely sure how Gallery will completely interact with WordPress. Recoding the design shouldn’t be too difficult, it’s fixing the 100 validation errors (on xhtml transitional, no less) will be the tricky part. Gallery 2.0, “out of the box”, was originally xhtml strict, but in order to validate on v14, I had to switch the doctype to xhtml transitional. Now I got to go back and change some transitional markups to strict. Fun.

Got my new work laptop…MacBook Pro!

After being on order since Apple’s announcement of Intel dual core processors in their 15inch laptops, it arrive this morning into shipping. I’m currently in the process of transferring all my data from my current PowerBook G4 to the MacBook Pro. So far my observations on the new MacBook:

  1. It’s a tad bit thinner than the PowerBook (1 inch versus 1.18).
  2. It’s a bit wider, 15.4 inch as opposed to the 15.2 on the PowerBook.
  3. The display is brighter and seems more clearer.
  4. The MacBook’s screen requires a bit more force to open and close compared to the PowerBook. Not entirely sure why that is.
  5. On installation of software such as Adobe CS 2, Apple Remote Desktop, Microsoft Office 2004, etc. doesn’t seem much faster, but that could be because I’m transfering 12gb of document data while installing the software.
  6. The MacBook seems to run a bit warmer than the PowerBook, but that seems to be related reason #5. Once I start doing the same things I did on the PowerBook on the MacBook, we’ll see if it’s still warmer. After using it a bit more (i.e. more file transfering), it turns out that the MacBook is about as warm as the PowerBook. When you try to multitask too much, it gets warmer since more load is placed on the dual processors.
  7. The illuminating keyboard is much brighter. With the lights on the office, I can definitely tell the illuminated keyboard is on.
  8. The built on iSight webcam is very nice. Seems to be as good as the iSight on the new iMacs despite the size difference.
  9. The remote control is cool.
  10. The magnetic quick detach power supply is very cool.
  11. The fact that the new power supply is double the size of the previous power supply plus it’s now 85 wattage is not so cool.
  12. The keyboard doesn’t have the same nice soft, quiet feel that the PowerBook has. It’s starting to feel like a Dell’s keyboard.
  13. There is no modem jack. You have to buy a usb modem if you want/need to dialup.
  14. Instead of having a PCMCIA slot, it has an Express Port.
  15. The RAM is easier to get to.
  16. Apple Remote Desktop (ARD) does not work with the MacBook at this time, even with Rosetta. Refer to Apple’s notes on ARD and the Intel Based Processors. But supposedly ARD 3.0 is supposed to be released anytime according to Apple Insider.
  17. Apparently the optical drive on the MacBook is 4x SuperDrive with no dual-layer burning capabilities as compared to the 8x SuperDrive with dual-layer burning…although the MacBook’s drive is smaller…small comfort. Read more about it here, along with a pretty good in-depth review by MacWorld on the MacBook, .
  18. According to Dane Riley, the MacBook Pro is supposed to have a Windows-like hibernation mode in which if the battery is near critical depletion, it will dump all the RAM data to the hard drive so the next start up will bring power back to existing last state. Interesting.
  19. Apple TechTool Deluxe does not work on the MacBook Pro, not yet anyways.
  20. Any other copies of the Mac OS that does not specifically say MacBook Pro on it will not boot by holding the “C” button down.
  21. Non-Intel processor Macs cannot access, see, etc. an Intel processor Mac placed in target disk mode.
  22. WinXP can be installed on Intel based processors with the use of Apple’s Boot Camp.

The MacBook Pro that I got is configured as such: 1.83GHZ Dual Core Intel Processors, 80GB hard drive, 1GB of RAM, and 128mb video card.

Daunting Task

In all respects, this redesign is so drastic and requires so much changes to the core that I don’t believe this will be Bui4Ever v14b, but rather Bui4Ever v15. And following in line with the proposed v13-15 plan (v13 = first CSS layout site, v14 = first xhtml transitional compliant site, and v15 = first xhtml strict compliant site), this will be my first personal site that is xhtml strict. I had already made the strict leap while working on a redesign for Alan’s existing design at http://www.alanliudds.com for his dental practice.

Originally I was planning to just update Bui4Ever (i.e. Bui4Ever v14b) from xhtml transitional to strict, but after trying to rework the code, every step in creating strict compliance triggered an error in another part of the code that would fail xhtml strict. After much frustration, I said screw it, I’ll go strict on Bui4Ever v15. Which I guess is essentially here. It’s funny how I’ve actually never finished my personal site completely. I’ll start out very strong, get a new design going that I will like for awhile, and then learn something new and wonderful and ready to throw the old design out the window before the site is even completely up. V14 was supposed to be a design that I was going to stay with quite some time, but after all the issues with the blog/news programs, I was ready for change.

The daunting task is not only bringing over all the other pages from v14 to v15, but also bringing stuff I hadn’t had time to bring to v14 from v13. The majority of the content in v14 is easily transposable to v15, with some changes, but unfortunately, v13 content is going to be painful as it is really behind.

Switch to WordPress

After working on various new and current web projects, I’ve finally come to the conclusion that it is probably better to use WordPress as my site news/blog. Previously I’ve looked into alternatives (scratchlog, snews, easynews, and then finally SimpleNews) for various reasons. These reasons were:

  1. The Theme system seemed daunting to learn and I mistakenly thought, despite the theme system and the use of CSS, that the design would be too limiting for my taste.
  2. I tried various times to integrate WP into Bui4Ever with no avail.
  3. How could I showcase my web skills if WP did all the work?

After using four different types of news/blogs, I think I will listen to the thousands of people who use WP and integrate it successfully into their custom designed sites. And I’ve also come to the conclusion regarding #3, WP won’t do all the work for me, it will handle a big part that is complex and difficult to handle in itself, which is: the site’s news. So let’s see how this goes.

Current Projects

I’ve been working on two new web projects. The first one is for my friend Alan, for his new dental practice, Sweet Home Dental. I’ve hit a bit of a wall on that one because of the tabbed menus are not working the way they should.

The second web project is for a comic store I frequent, Funny Monkey Comics. Its given me the opportunity to try some new things that I’ve been wanting to try and hadn’t had the opportunity to yet. Partly from that did I discover SimpleNews.

I want to do more updates to Bui4Ever.com hopefully soon. There are some validation errors because of SimpleNews that I definitely need to address. Basically I’m going have to dig through the code and correct some areas to ensure they follow xhtml 1.0 transitional.