We were shut

No one may wonder why I have hibernated for the last 4 or 5 days without a post. It's just our network center was being moved from the 10th floor to the 1st, so we were literally shut from the internet for a small period of time. Finally, we are back on line and connected again to the pulses of the information world!

The entire instructional building is now refreshed with new colors, illuminations, information facilities, chairs and desks. Various administrative offices and the pivot of networking have been transferred to the 1st floor for the sake of convenience. Good news for us and the poor tiny elevator. The next time to renew my campus network identity, I don't have to climb a height of 10 storeys step by step any more. And it's also more easier to bug the professors in the name of your right to get a pass grade. :D

I'm trying, but it's turning into a nightmare

Baskets and baskets of ideas, but tons and tons of study works - Ohhh, only if I was endowed with the codes written by Jesus that are able to do a Time Squeeze function! Which magnifies my time axis by 2, and thereafter I can have 48 hours a day!!

So, another day passed and nothing evolved with this site. Well, why not talk about some of my greatest insights about Build Easy. - -!

Simplicity is a virtue, indeed, but more importantly, it can be used to cover up my inability to create sophisticated web pages, haha :D . I am a practical person, and I believe the happiest ones in the world should be those who are being paid for what they love to do. Web building is one of my favourite passtimes(the others being WoW, a gorgeous MMORPG made by Blizzard, and classical music, and, part of the things happening from the global economic community), so it's a genius idea to do it well and make some money(passers-by: "Look the ego on you!"). SEO is not what I specialize, though - no, wait, please, don't direct the spotlight at me, cause' I am sweating already, thank you - the fact is I don't specialize in anything, and to the least of all, this blog, is really a bad example of the global bullshitting industry, and should be awarded the Nobel Prize in Poorest Bullshitting of this year. Undoubtedly.

'Kay, the bullshitting is enough. What I mean by nightmare is that my schedule is so tight that I almost got no time to bullshit. And look, that's half my life! My routine class time every day is from 8 o'clock a.m. to 6:30 p.m. with a 2-hour lunch break, let alone those annoying homeworks. Right after this blog entry, I will be nightmaring again tonight with professors smearing guts in my face and on my neck if I don't find myself doing the essay of Summer Toil Camp in 30 seconds. And DO NOT. DO NOT ever underestimate their capabilities and determination to kick your ass. Everything you heard about college professors is true, except when they tell you this: It doesn't matter what I think; write what you believe.

I have written several versions of SSI framework, used mainly to quickly implement static content. The first one is cumbersome, with quite a few fundtionalities realized by less than 10 instructions available with SSI. Page titles, meta description, and keywords are managed automatically, going with the depth of the page in the whole website hierarchy. Each category of content has its own navigation information that is automatically incorporated into the final page request. In this sense, every hierarchical structure of entire building has a common snippet of HTML codes that enable you to make changes to a specific set of pages immediately. For instance, we have

kavoir.com
　｜
　｜=Reference
　｜　｜
　｜　｜=HTML Entities
　｜　｜　｜
　｜　｜　｜=page1.shtml
　｜　｜　｜
　｜　｜　｜=page2.shtml
　｜　｜　｜
　｜　｜　｜=page3.shtml
　｜　｜
　｜　｜=CSS Colors
　｜　　　｜
　｜　　　｜=page1.shtml
　｜　　　｜
　｜　　　｜=page2.shtml
　｜
　｜=Tools
　｜　｜
　｜　｜=Color Scheme from Pics
　｜　｜
　｜　｜=Email Pics Generator
　｜　｜
　｜　｜=Text Pics Generator
　｜
　｜=Bullshit
　　　｜
　　　｜=Devil Dic

and change a common file of codes for all the pages under HTML Entities should be able to have a universal effect on all of them, easing the jobs of adding, deleting, or maintaining a specific gadget to a specific group of pages. The website is more flexible when each category can be moved around freely without the panic of navigation disorder, because the SSI framework is made to deal with such situations wherein the navigation is almost automatically rebuilt for you - of course, one or two alterations to the meta files of each category are unavoidable. Above all, SSI is a good friend if you stay away from the complex and confusing webs of directives when it grows big - like this one. And it is why I abandoned it and decided to write a simpler one.

The second is even more flexible that you can move different categories around without any necessary changes to the meta files. Nevertheless, it is deprived of the capability to generate hierarchical navigation bars accordingly. And you know what, I might have a better plan, that is, to make every category an self-contained unit.....................................BULLSHIT!!!!!Yet again, another weird dream...........upohhhhh

I'm gonna hit on the essay now, bye~~~~~~~~~~love ya~~~~~~~~

First of all, SSI: How easily you can maintain your website

One of the best things you can do with SSI(Server Side Include), is to slice a normal HTML page into several common parts such as header and footer, so that you can more easily update a website of hundreds of thousands of pages for just a slight alteration of a single file. And this is accomplished by the following directives:


<html>
<!--#include virtual="path/to/the/header.txt" -->
...primary content goes here...
<!--#include virtual="path/to/the/footer.txt" -->
</html>

(I used HTML entities to represent tags in this example. Chances are you will encounter some cases where the use of an HTML entity is necessary, such as when you are writing copyright notice. So why not have a look at the HTML entities page I have made? It's here!)


As you have guessed, codes between the HTML tags are those that we want to display in the client's browser, while header.txt and footer.txt contain the HTML snippets that are used throughout the whole website. Instead of putting them directly in all the HTML files, we have abstracted them into separate files and linked them from the files that need them. In this way, once we feel like deleting a link in the navigation bar, for example, we just remove the corresponding codes in the header.txt, and effects are immediately seen throughout the website. Maintenance made much easier, huh?

However, merely inserting a directive like <!--# include virtual="..." --> into a normal HTML file with an extension of .html or .htm doesn't give you the advantages described to you. You have to name it with .shtml, or it won't work. Remember, as long as there are SSI directives you want the web server to parse, you should name the file containing them with an extension of .shtml. And what if you write a directive like this:


<!--#include virtual="path/to/the/header.shtml" -->


In this case, the server first read the directive, locate the header.shtml, parse it, and then replace the above directive with the parsing results of header.shtml, which in turn, contains some directives to follow. In the first example, however, the header.txt is not parsed for SSI directives, because it has no .shtml extension. The web server simply read the content in a verbatim manner and put them in the place of the directive including header.txt.

In addition to the SSI pages of kavoir.com, more complete and authoritative resources can be found at apache.org.

Before I can concentrate

econguru.com is almost on its own stand now, I am beginning to check for literal mistakes(mispellings, gramatical errors and so forth), broken links and minor accessibility issues before the search engine submission. After that, I would only add a resource or two every other day to make it up to date, and check links once upon a month or so. Websites need supply and refreshments to be alive. You should provide content to them on a regular basis.

After all the construction and inspection jobs' finished, the maintenance should be easy in that I have used SSI for the skeleton of all the pages; and I will have my focus on the blog of Build Easy. Up to this point, I notice my English is still not good enough for a fluent or streaming writing style, I can't fully concentrate on my thought when my improficiency with English hinders me. Hope it would turning better with more upcoming entries.

Let's get back to Build Easy. I love this name, so I decide to work hard to make it as excellent as possible. Despite this blog you have seen, more things like handy reference pages, small tools, simple and pleasant tutorials of web building technologies and techniques are to be added on kavoir.com. It takes time, surely. I don't have much time to spare and I want this website to be useful and at the same time, graceful. One of the most popular advice for all crafts, is to think your way, and establish a unique style of your own. It also takes time, but I am trying, and you should, too. :)

Things to make Blogger sexier

I've been with Blogger a little while, okay, one month. Overall, it's a very outstanding blog publishing platform. I love them for they let me do blogging with their system without being branded with their name, if you know what I mean. (Wow, what an expression with with ... without ... with, have you ever seen that before?) On the other hand, it would have been perfect if they had considered something I imagine of to provide to the users.

1. Data backup and export.
   Backing up is a fundamental function that Blogger should not have missed. Perhaps they think that, okay, now that we are publishing content to HTMLs on another host, why bothering to code a button that backs things up. They are actually copied to another place upon publication, aren't they, only in a different format. Hmmm, sounds reasonable, right, I give in. (I'm such a jerk.) However, while -
   Backup is good, export is better, I believe. This enables the users to export their whole blog or selection of entries to such cute popular serious formats other than HTML as TEXT, XML(not to mention DocBook as well as various other solid XML destinations), PDF, and even more. You name it. But wait, will Blogger continue to be free when it offers us this? The answer is clear. That it is. Impossible. And negative. Daydreams do no harm, do they.
2. Template customization layer.
   The DocBook guys took applicable customization into account from very early versions of DocBook when it still depends on DTD for schemes. And a customization layer is the snippet a user put in the beginning that redefine one or more parts of the official DocBook scheme. Very intuitive and easy to maintain, also less error-prone. Unlike Blogger, it doesn't force your eyes to painstakingly locate the codes dispersed all around everytime before committing any modifications; DocBook customization layer is all at the top of the entire official scheme, so add or modify your own layer, and that's all. More importantly, this layer is preserved when you update the official scheme. You just put your customization layer on top of the new DocBook, and everything's done. On the contrary, all the information including previous styling and marking-up must be provided to Blogger again when you want to use another template. It's no easy task, let alone the errors you may incur.
3. Account settings export or sharing a common setting XML among selected blogs.
   Sometimes it's necessary to make changes to the settings of various blogs at the same time, or you just want to synchronize them so that they are in the same pace. Blogger could well maintain XML sockets for every single blog, and let the users to upload their XML to the server and choose to plug one or more of them into the sockets of each of their blogs. In this way, blogs plugged with the same XML will have some of the settings in common. (Hey you geek, is this necessary? The tweaking job takes days to accomplish for you, does it.) Hmmm, that's a thinker. So see this. Why not trying to integrate this settings XML into the custimizatino layer we just talked about, every blog has only one template at a given time, right?
4. There's a text color button in the WYSIWYG editor, so why don't you treat me with a background color button?!
   Cause' I love it.
5. Enable the users to integrate some of the customized styles into the WYSIWYG editor as buttons.
   For instance, I frequently site code snippets in my work, so I make up a div idded myCode and the corresponding CSS styles. Without the button for it, it would be necessary for me to dive into the mess of HTML, scroll, and find the exact place of the target content to add this markup manually everytime I want to site a snippet. With the button, I just select the tract and push. It's much easier.
6. Display HTML tags in colors when editing HTML.
   Like some local HTML editors do. A general well aware of where his soldiers are is more likely to triumph over one who doesn't.

Maybe I can write my own blog publishing scripts with PHP? No I can't. So Blogger, would you please do me the favor? Noooo you won't.

The machining window

Since this is getting more and more interesting, I cannot help but writing the idea down. It may not be original - coming up with something totally original is much too difficult at an era of information and knowledge explosion such as this for anyone - but what does it matter.

A machining window is actually an ongoing or ever changing agenda or tasklist placed on the side of your working blog that keeps track of your future plans, current projects, and accomplished jobs, be them blogs, articles, programs, compositions, drawings, audios, videos or any other sorts of weird stuff. Visitors see it, so they know what's upon you recently, or what to expect from you in a near future. Beyond the visible window, backwardly they can also explore your past undertakings, achievements and experiences. And forwardly, you may write some long-term goals or plans in a big advance and alter them from time to time. As you come near of those that you planned years ago, isn't it exciting to know that you have made these plans and goals and actually carried them out along the way!

To plan or not to will do quite differently for you. Think about it! (Thumb high)

A test entry posted with Writely

KBE Mission Statement

Testing with Writely

Header 1

Header 2

Header 3

Kavoir Build Easy, or KBE, is the ultimate blog based website that boosts novice web development.

Access the website: KBE

Here you will find resources needed to learn web developing quickly and effectively. We offer information and tools just right for you. As simple as possible. As neat as possible. And as intuitive as possible. No more nor less. Professionally, we are out of the track. But we are able to work things out pretty admirably in an easier way. Learn it, love it. We are not geeks. We are here to create, to enjoy, and to share. We enjoy our lives with our family and friends. We come on-line for a reason, with a goal. So not until we succeed, we will not give up what we believe in the first place.

2¹⁰=1024,

A₁, A₂, A₃

This is absolutely bullshit!!! Yet more nonsense!!!

Poeple love lists, don't they.

O'er all the hilltops,

Is quiet now.

In all the treetops,

Hearest thou

Hardly a breath.

The birds are asleep in the trees.

Wait: soon like these,

Thou too shalt rest.

(Style => Block quote isn't working.)

1. Arial: Potato
2. Arial Black: Tomato
   1. Arial Narrow: Apple
   2. Book Antiqua: Lotus
   3. Century Gothic: Big Leaf
3. Comic Sans MS: Banana
4. Courier New: Watermelon
5. Fixedsys: Max Leaf

• Garamond: Harvard
  • Georgia: Law
  • Impact: Management
  • Lucida Console: Dentistry
• Palatino Linotype: Stanford
  • Symbol: Math(Symbol) - abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ
  • System: Economics
  • Tahoma: CS
• Times New Roman: MIT
• Trebuchet MS: UCLA
• Verdana: Columbia
• Wingdings: Cornell(Wingdings)abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ

11	12	13	14	15
21	22	23	24	25
31	32	33	34	35
41	42	43	44	45

O'er all the hilltops,

Is quiet now.

In all the treetops,

Hearest thou

Hardly a breath.

The birds are asleep in the trees.

Wait: soon like these,

Thou too shalt rest.

Excerpt from Wanderer's Nightsong by Goethe

Steinway & Sons

So, this is a new page??

---

Special characters you can insert from the menu: ¶ ŋ and more....

Okay, I think that's all.