Results matching “dreamweaver” from Ye Olde Rad Blog III

Have a special treat for you today » my Nuclear Grade Stew recipe (2 pages). I've made this stew at least 50 times over the years .. probably closer to a hundred. Now that autumn is here, and the nights are getting chilly, it's time to break out the crock pot.

For the pages that contain this recipe, I designed a new, single-sidebar layout .. another liquid-elastic hybrid. See what you think.

For previous web pages, I used a design that comprised dual-sidebars, one on each side, cuz I liked the balanced, symmetric look provided by that layout. So this feature took longer to complete than expected, cuz I first had to code the CSS from scratch.

I've made this stew for the Bug many times (cutting the veggies into smaller pieces so they fit easily in his little mouth). So it's made with lots of love. He digs it.

Been lagging on entries lately, as you mighta noticed. Been dabbling in Programming. Kinda got lost. Big subject.

On the personal side, I took the Bug kayaking last week .. out on the Newport Back Bay. (No waves there.) He later confided, "Dad, at first I was a little scared. But now I'm not scared." We stopped at a small island where he got out and searched for buried treasure.

"Hey Rad Man!" began an email I received last week. "I'll pay $100 for a link on your Downloads page." Of course, there's no way of knowing if such offers are legit .. until the cash arrives.

 I've researched Search Engine Optimization (SEO) enough to know I don't much care for it.

Programming I enjoy, but SEO contains a seemingly endless amount of info to digest, some of which conflicts from site to site.

And the suggested techniques are often time-consuming, with dubious results that demand the patience of a saint before you start to see results. Rather focus my energies on generating original content.

Moreover, some of the techniques used to 'optimize' web pages (for higher search engine rankings) seem manipulative, if not downright dishonest. Many of the SEO sites I've visited have a 'slimy' feel to them » detailing how to trick search engines into ranking your pages higher.

I learned that links from 'ranked' pages will (in turn) yield greater 'importance' to the pages that those links aim at (point to). This is (I assume) what this person had in mind when she contacted me.

The email seemed both professional and specific. (Not slimy.) The girl was clear about what she wanted. And best of all, her proposal could be implemented minutes. (Simple.)

The problem was .. that the page they wanted a link on was created back when I knew squat about web standards (XHTML & CSS). The underlying mark-up (code) was a rat's nest of deprecated tags and coding no-no's.

Downright embarrassing .. from a webmaster's point-of-view. Miracle the page would render at all (.. even in 'quirks' mode).

Changed the type of layout I use on the home page .. to » LIQUID-ELASTIC hybrid. If I did this correctly, you shouldn't notice any difference .. unless you change your default text-size (.. by selecting 'Text Size' from the 'View' menu in IE). Lemme know if you notice any display quirks.

There are 4 different 'types' of layout designs:

1. FIXED (column widths remain fixed, no matter what, used » here)
2. ELASTIC (column widths change with changes to your preferred font-size)
3. LIQUID (column widths change with changes to browser-window sizing, used » here)
4. HYBRID (combination of two or more of the above, used »  here)

I've long preferred LIQUID layouts (sometimes called » FLUID), which resize column widths as you resize your browser window (called the "viewport" by those in the biz). It's easier for me to understand the concept behind LIQUID layouts .. than ELASTIC.

Today however, I'm demo'ing a » HYBRID layout .. that combines elements of both LIQUID & ELASTIC. [ If you've read my SCSI guide, you know I'm a fan of hybrid config's. ]

The center section/column remains » LIQUID, while the two sidebars (blue-green colums) are now » ELASTIC. This means they will resize with changes made to your preferred font-size (e.g. » small, medium, large, gigantic, etc.). The center section will continue to change proportionally, as you resize your browser window - just like before.

Resizing your browser window will no longer affect the width of the blue-green sidebars (which are already skinny), while changing your default font-size will not affect the width of the center column/section.

The design itself of the home page has remained unchanged. Only the 'type' of layout has been modified (.. from LIQUID to » LIQUID-ELASTIC hybrid). This new type of page layout is considered more 'accessible' ..

.. especially for those who might have difficulty reading smaller text, and need to bump up their default font-size.

Been working on the Rad guide to Drive Imaging & Disk Cloning. Helps to be up-to-speed on Web Page Templates. Makes that part of it go more smoothly.

I endeavor to work on it a little every day, tho it never works like that. Yet when I focus, I'm able to put my head down & plow.

The guide seems to have a mind of its own .. like it knows how it wants to turn out. So I go with the flow, prepared to lay aside preconceived notions.

I would hope all Rad regulars are already onboard with a backup program .. since creating backup images with a Cloning program is what we do here.

One of the concepts that keeps popping up in my study of Programming languages is » expressiveness. Loosely defined, expressiveness is » the ability to say a lot with a little (my own definition).

Where Programming languages are concerned, expressiveness might be the ability to DO a lot with a little.

Related terms » Meaningful. Concise. Simplicity (as it applies to the elimination of unnecessary complexity). Elegance. Efficiency.

No doubt, you know an 'expressive' person or two. But sheer volume of words does not an expressive person make.

Some people can talk for hours without really saying anything (.. at least not anything meaningful). While others can speak volumes with a simple glance.

In programming, the notion of expressiveness is often touted as a plus, associated with "higher level" languages. I could be wrong, but the idea I get is » the more expressive (a language is) the better. Notice the statement that begins the second paragraph here:

"My contention is that expressive power is the absolutely most important property to focus on right now."

This from a developer with an admitted "unhealthy interest in programming languages," who's currently developing his own. Since the learning process often involves relating new information to things we already know, that's what I've been doing.

As chance would have it, I was watching Hamlet last night (the Kenneth Branagh version). Didn't take long to realize much of what was being said wasn't getting thru. ( "Say what?" )

So I enabled English subtitles and started vigorously working the pause button .. in order to read & digest the Elizabethan chatter. Much better.

Saying Much with Little

Note how the phrase » 'To be or not to be' is exceedingly simple. Yet it carries much meaning beneath the surface (.. especially that 'not-to-be' part).

The ability to "say much with few words" is a primary reason cited when discussing Shakespeare's literary prowess. In other words, it's not just what he says, but the way in which he says it .. that makes his writing so .. descriptive, enchanting.

Last month I mentioned a quest to learn the Unix shell .. specifically » bash (the Bourne Again SHell). Almost done. Currently ~80% complete .. enough to feel reasonably confident at a terminal.

The 'shell' is simply a program that lets you interact with the operating system (actually the kernel, to be more precise) ..

.. by taking your (text-based) commands and passing them on to the kernel. In my case, this kernel happens to be » Linux (which is but one variant of Unix).

The term 'shell' comes from the notion that this software acts like a 'layer' that sits between you and the operating system .. similar to the way an egg-shell sits between you and your hard-boiled breakfast.

The shell can be intimidating, cuz it uses a (text-based) command-line interface (CLI). No intuitive GUI to help you along. You either know the commands or you don't.

Didn't take me long to realize the CLI was where Linux's true power resides. When we upgraded the site, for example, to a Virtual Private Server, the support-techs who helped me with the move all used the command-line to work their mojo.

Most Linux distros do indeed come with an excellent GUI (usually either KDE or Gnome). But (but!) the Rad VPS does not. Which is why it became necessary to learn the Unix shell. (Something I tried to avoid.)

The Rad VPS is based on CentOS (Community ENTerprise Operating System), an off-shoot of Red Hat, which is probably the most popular of all enterprise Linux distros (.. and now a new member of the S&P 500, a development you may find telling).

GUIs (such as KDE or Gnome) require lots of memory/RAM. My laptop, for example, has 2-gigs, but the Rad VPS comes with an allotment of only 512-MB (.. upgraded from 384 just today).

With that limited amount, I need to run not only all the standard web applications .. such as Apache (web server), MySQL (database), Perl (scripting language), etc. but also cPanel/WHM.

So there's not much RAM left to run a GUI. [ Don't think I didn't inquire about installing a GUI. =) ]

Bottom line » if you wanna administer your own VPS, you need to learn the Shell. So that's what I'm doing. (Of course, there have been distractions, making progress uneven.)

Back when I investigated how to create a webpage template, a couple weeks ago, I really had in mind the notion of using a template as the basis for a new Rad guide .. not one on Dreamweaver Templates however, but rather one for » Drive Imaging & Disk Cloning. Today I created that template, and began a new Rad guide.

Definitely takes longer to get up-n-running when using a template, cuz you first must determine exactly how the guide will be structured .. and what items to include in the template, and what parts need to be editable.

Can't just start cranking out pages of text and entertaining new ideas (.. like I used to) .. leaving the details of page structure to deal with later.

Templates force you to pre-think everything up front, before you begin generating content-one. They even force you to anticipate changes .. which is new for me .. especially since I've grown accustomed to the ready-fire-aim approach, which leaves the details of page structure for later .. but by then it's difficult to make changes .. cuz each page must be edited individually (.. hence the need for templates).

I was so eager to get started on the guide that I actually had to start over (several times) .. due to major template modifications. (Arrgh!) Kept getting new ideas .. things I wanted to add/tweak.

You can always modify a template, as that's what they are designed for. But when a template requires many edits, it seems easier to just start over and create a new one. (Something I'm getting good at .. from all the practice.)

If you view this home page in Firefox (or a browser other than IE or Opera), you'll notice I added some rounded corners.

Been reluctant to spend much time focusing on site styling, preferring rather to concentrate on generating » content.

In the world of cars, for example, I've always preferred the spartan cockpit of a Porsche to the bells & whistles you find sitting in a corvette. Tho admittedly, that's just my druthers.

My point » function should never take a back seat to form.

I've considered adding rounded corners many times before. Countless techniques exist. But they always seemed a kludge. (Andy agrees.) So I never felt it worth adding the extra markup necessary.

Techniques that use graphics to achieve their effect involve inserting additional HTML elements that are otherwise unnecessary, because current CSS standards (v2.1) allow only 1 background image per element (while each box has 4 corners). Future versions of CSS (v3.0) will support 8 images per element (for this very reason).

This approach has 2 main problems. First, adding (otherwise) unnecessary markup goes against all that is holy to the Web Standards movement, which touts the tenent of 'Semantic Markup' as one of its pillars.

If I knew then what I know now. Ever uttered those words? Looking back on my progression of web skills, one omission stands out » incorporating the use of templates to help develop & maintain the pages of my web site.

Templates are both powerful & flexible for two reasons:

1. They speed up site development, by allowing the rapid creation of web pages based on a preformed (uniform) structure .. so all your pages have the same look & feel.
   
   
2. They facilitate site maintenance, by enabling structural changes site-wide via the editing of a single-file .. similar to how CSS works. This aspect of templates is considerably more significant than item #1.

If your web site grows bigger than expected (as they usually do), and you want to make structural changes (non CSS-based changes) to your web pages, you'll have to edit each page individually (.. which suks giant goose eggs). Tedious maximus.

When CSS came along, website designers could transfer all style controls into a single file, so that the look of an entire site could be modified by editing a single file (provided, of course, the entire site was based off of the same style sheet). Very cool development.

But what about structural changes? That's where templates come in. To be honest, I'm not sure if web design programs (such as Dreamweaver and Expression) had the ability to generate templates back when I launched the site. But they do now.

Redesigned the site's » Archive index page (from scratch). It contains links to all monthly archives posted since the site's launch (summer of 2000). Gateway to Memory Lane.

Been meaning to do that for some time now (years, actually). That page was the single-most mucked-up page on the entire site. The code was a rat's nest of deprecated standards, poor design choices and mark-up errors. I'm surprised it would render.

Began that page back when I knew very little about HTML and before I'd even heard of CSS. Over the years, the muck seemed to multiply as the page grew. It's not a highly trafficked page, so I didn't worry about it.

Tho at sundry times, I'd go in and try to manually clean up the code. That always proved an exercise in futility. Seemed like the more I tried, the worse things got. The only real solution was a complete makeover (a move which could be viewed as symbolic of the site's growth and development).

Now the page contains a third the mark-up it did before (10-KB vs 30) and the styling looks 3X cleaner, by making use of advanced techniques such as colgroup styling for better readability. Leaner, meaner and faster-loading.

While recovering from the crud this weekend, I took the opportunity to work thru a video-tutorial for Dreamweaver CS4 .. consisting of ~10 hours worth of instruction and 18 chapters.

So I've gotten up-to-speed on DW.CS4 .. the world's finest web design software. (This page you're reading now was created with Dreamweaver.)

Excellent tutorial. Last year, I worked thru the same title (» Essential Training) for Dreamweaver CS3, which was also good. But this one (done by different guy) was noticeably better.

I especially liked how the guy who narrates this video tutorial (for DW.CS4) spent significant time focusing on the intracacies of working with CSS.

"Computer Science is not a science," proclaims a professor at MIT, drawing an X over the word. He's introducing an introductory course on Programming called » 'Structure & Interpretation of Computer Programs' .. aka SICP. (Watch the video yourself » HERE.)

Less than a minute into the lecture and already I'm curious. "If it's not a science," I wonder, "then...??"

"It might be engineering," he continues, as if reading my mind, "Or it might be art. We'll actually see that computer so-called 'science' actually has a lot in common with magic."

I smile at this point, having gained insight into the graphic displayed on the book's cover, understanding why some refer to it as » The Wizard Book.

Then he draws an X over the word 'Computer' and says, "It's not really about computers either." (Okay, now I'm really interested.)

"The reason we think Computer Science is about computers," he continues, "is for the same reason the ancient Egyptians thought geometry was about surveying instruments ..

.. » because, when a particular field is just getting started, and you don't really understand it very well, it's easy to confuse what you're doing with the tools you use."

So-called Computer Science (he explains) is really about formalizing intuitions & knowledge about » Process (a word he writes on the board .. he's a lefty, btw). He then clarifies himself by saying, "How to *do* things."