This is a test of Bluefish 1.07.which looks like a web document development tool. This is on Ubuntu 8.10 on a Compaq Presario with 64-bit Athlon and 3 GB of RAM. After playing with this for an hour, I must say that I am overall quite positively impressed, because I find myself settling into a fast itterative rhythm, which is a good sign, since you don't want the editor to get into the way.
There is a template for beginning a web document that sets many things
in meta tags. I am less sure about how settings that affect
standards allow for things like style. But, as it turns out, you insert style
wherever you want, and then get to debug it. Mozilla complains about the URL every time
this file is reloaded. I figured this out, there is a meta tag that
the editor created in its default template that supplied a URL stub that is
wrong. It looks in that url whenever the browser does a refresh of what is
loaded. When I set that to a valid file off the DOCUMENTROOT for
the web server it causes the browser to branch there after only a few seconds.
The message from the browser goes away, so does this page. So, I commented
out the reference.
Bluefish refuses to open the file in a browser even though there is a button for that. The CSS hooks are OK, if prone to causing errors because the editor is stupid about the syntax. It just inserts style snippits anywhere the coursor happens to be. Not good. That appears to be the standard for most of the other IDEs, since these do code completions, and are not general purpose text editors. Emacs looks like a good alernative, still, because it can act as either a very power ordinary text editor, or an IDE for things like code completion, but it doesn't have the GUI hooks that are most important in tasks like setting style color. It is pretty time consuming to set RGB hex values by hand.
This ia just a way to play with style within a division, by centering the lines of text within a paragraph on the page and coloring the text red.
This took two separate attributes to the div tag. the attributes
are align and style.
I hope that no one does grep code [this file] and sees the
number of tags. But I hope they enjoy the pretty blue color of the
geekisms.
I took the style I made for the first code tag and made is global to
the file by putting it up in the style for the head.I thought
it was connoical to do that in the body instead.
I have also discovered that I go and put line feeds around the tags
even though the editor makes tight formatting. In my taste, this
mkes it easier to read the HTML file as text.
The Wiki phenomonon is that one can write blog-like or twitter-like, which is to say, stream of conscious, into a text editor of text blocks and titles and then sent that through a style sheet driven by something like python and produce a pretty web-document. This is no more advanced that generaling HTML from perl-www, which I did four or five years ago, but neither is it more conveinient that doing that here within something that like this that manages the nasties of HTML and allows you to control the style. Some of these other Wiki tools have a default style sheet that you may or not control. One of these is kjots, which made a particularly bad choice of style in my opinion. I may just take the flat text file it created and plunk it down into one of my HTML templates and mark it up. It may even be best to preprocess it with emacs before using it here to mark it with style.