Find a calendar you want to add to your own WebCalendar at iCalShare.
Download the U.S. Holidays from iCalShare or personalize your calendar by incorporating other calendars from iCalShare. You can find important dates in history, birthdays, concert tour dates, and even your favorite sports team schedules.
Sign in to the admin area for your WebCalendar, usually at the bottom of the calendar screen. Once you are signed in, click on the Import link.
WebCalendar import link.
On the import page, choose iCal from the drop-down box, select “No” for the Overwrite Prior Import selection, browse to the
.ics file you downloaded, choose your public or personal calendar, then click on Import.
Import function for WebCalendar.
The next page indicates how many events were successfully imported into your calendar. Just now, I imported 169 astronomy events with the click of a button!
WebCalendar is an open source calendar script that is very flexible and quite useful for sharing your busy life. Here are directions for installing WebCalendar on your site. You can use it on your local machine, too.
Sign in to CPanel, click on Fantastico, and near the bottom of the script list, select WebCalendar under Other Scripts.
Installation screen for WebCalendar.
Click on New Installation to bring up the next installation screen.
Installation details for WebCalendar.
Fill in the directory in which to install the calendar script, enter the admin username and password combination as well as the admin contact information, then click on Install WebCalendar.
Database and MySQL user details for WebCalendar installation.
Make a note of the database and MySQL user that are created for your installation before clicking on Finish Installation.
User details for WebCalendar install.
Enter your email address so that details of the script installation will be sent to you once you click the Send E-mail button.
Now that your calendar script is installed, it’s time to get some help for customizing it. Check out WebCalendar’s developers’ site and a few other helpful links:
The title of this post says everything.
JPGs Can’t Handle Transparency, So Use A PNG Instead
Earlier today I got lost in the details while using The GIMP to create a couple icons for a new WordPress theme. I kept seeing this colored background for an icon that I knew just wasn’t there. I could see that the image had only one layer and no background layer in the layers dialog of The GIMP, but every time I saved the image and viewed the result in my browser I saw the colored background.
This drove me mad until I spotted the obvious mistake. I had been saving the file that I wanted to have a transparent background as a jpg file. Since jpg files can’t handle transparency The GIMP tries to accommodate by exporting the file as a .jpg. Unfortunately, the current background color is used to fill in the transparent parts of the image, so you end up with a non-transparent image.
To make a transparent image or an image with a transparent background, save the file as a png file. PNG files can handle transparency, so once I saved my image as a .png the colored background went away.
One caveat here is that image files with the extension .png are not recognized by older browsers so the colored background will show through and the image won’t be transparent.
Commented code is worth its weight in gold when it comes time to decipher it. Unfortunately, the codes for commenting in xhtml, css and php are not all the same. So, for reference sake here are the comment codes you’ll need and where to use them.
Where xxx is your comment, for
- xhtml (html) and php (outside php code) use
<!-- xxx -->
- css use
/* xxx */
- php (inside php code or between <?php and ?>) use // xxx
- multi-line comments inside php use /* xxx */
Comments are very helpful in troubleshooting style changes. When creating your designs take a few seconds to jot down a comment here and there.
Great uses of comments include labeling the starting and ending location of id- or class-identified divs, putting temporary holds on features that may or may not be needed in the final design — often called commenting out code, sectioning long stylesheets into more easily readable forms, and specifying the author or location of the code.