public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Humphrey <peter@humphrey.ukfsn.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Kompozer: undefined reference to `SEC_ASN1Encode_Util'
Date: Tue, 3 May 2011 09:12:04 +0100	[thread overview]
Message-ID: <201105030912.04292.peter@humphrey.ukfsn.org> (raw)
In-Reply-To: <201105022118.11798.michaelkintzios@gmail.com>

On Monday 02 May 2011 21:18:00 Mick wrote:

> A bit O/T to the original post, but how does kompozer compares to
> Komodo-edit?

I was too terse a moment ago. I haven't seen Komodo-edit, but from the list of 
features on Softpedia's site it seems to omit the one thing I use Kompozer for: 
WYSIWYG style editing.

It's extremely useful to be able to see the effect on a web page of a small 
change in a style definition - the instant the change goes in. No before-and-
after comparisons, no unnoticed effects on other style elements.

For content editing I prefer BlueFish, but when I approached a site redesign 
idea the other day I realised I'd be lost without Kompozer. It really is that 
good.

It does have bugs, but most of those can be evaded by following Greg Tutor's 
tutorials on the web. It also needs a lot more development effort.

HTH.

-- 
Rgds
Peter



  parent reply	other threads:[~2011-05-03  8:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-27 17:08 [gentoo-user] Kompozer: undefined reference to `SEC_ASN1Encode_Util' Peter Humphrey
2011-04-28 19:28 ` Paul Hartman
2011-04-29  9:03   ` Peter Humphrey
2011-05-01 16:29     ` Peter Humphrey
2011-05-02 16:54     ` Paul Hartman
2011-05-02 19:12       ` Peter Humphrey
2011-05-02 20:18         ` Mick
2011-05-03  8:00           ` Peter Humphrey
2011-05-03  8:12           ` Peter Humphrey [this message]
2011-05-03 18:18             ` Mick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201105030912.04292.peter@humphrey.ukfsn.org \
    --to=peter@humphrey.ukfsn.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox