Skip to main content

Best open source HTML editors, continued

I have played a little with Nvu and I must say that even if I like the way you can edit the pages in WYSIWYG mode, I don't like that you cannot see the source in the same time. I like to see that in an editor. I also didn't find it very intuitive. There should be a way to see all the html pages in a directory through a file system browser. You shouldn't be constrained to make a project in order to have the pages at hand.
Another issue that concerns me is how much updated it gets. It doesn't seem to be maintained. The last version (1.0) is from June last year. It loses so many points for this issue that it really doesn't even worth to talk about it anymore.
Amaya on the other hand lets you see the source while you modify the pages in WYSIWYG mode. This tool is highly maintained; it reached version 9.5 this April. It started in 1996 as a HTML + CSS style sheets editor. But become much powerful over the years. And the main thing is that it's powered by W3C, the web consortium, so it feels good that you are making W3C compliant web pages. It supports CSS, MathML, SVG, RDF and XPointer so that's kind of good. You can use it as a browser, and that's also kind of good. The main problem: it doesn't provide you with a file system browser that you can dock at the left of the screen, and this is pretty important in my case. It also lacks support for the most web programming languages like php, perl, ruby etc. But for plain HTML editing it's very good. The address is http://www.w3.org/Amaya/Overview.html

The good thing for both tools is that they are both open sourced and cross platform. People should play with both to see which is more suitable for their needs.

Comments

Popular posts from this blog

First things first

So, this is kind of my first blog post. It's a start, and I hope a good one, knowing today is Friday 13. Now let's get back to work, it's almost weekend and maybe I will finish what I started in the morning.

Finishing puzzles, reading books, what else ...

Yesterday evening my wife and I finished putting together the 1000 piece puzzle. It is a wonderful feeling to finish something you started. A puzzle, a book, a task. You feel you did something till the end, and that gives you background in order to do it again and again. Getting something done it's a learning habit. After finishing the puzzle I continued reading "Mythical Man Month" and I came across a sentence that I particularly liked: " Thinkers are rare; doers are rarer; and thinker-doers are rarest. " It was about the separation between the "producer" ( the one in charge of assembling the team, dividing work, making the schedule) and the "technical director" ( the one in charge of making the design to be built, and inventing solutions for technical issues). On small teams the thinker (technical director) and the doer (producer) can be one person, but for big teams the pressure it’s too much for it to work. This book is written with m...

My GTD Implementation

For GTD to work, you must find a way to implement your own organizing system that you can trust. You must trust your system for it to work. If you think that your system might not be good enough for capturing all the stuff that gets your attention, it won’t be successful. You must free your mind from the task of remembering everything that you need to do, and focus on actually doing those things. So I have built myself my own PDA, Hipster PDA that is. Even if it sounds like something highly technologic and expensive, it isn’t. It’s just a bunch of index cards and a binder clip to hold them together. Maintaining lists on these index cards it’s all you have to do. You can have an index card for each context. For example I have the following cards: @ Work – list of next action items that revolve around the “work” context @Home – self explanatory @Calls and Emails – list with calls I have to make and emails I have to write @Agenda – actions that depend on other people (meetings, @Some...