Skip to main content

Home/ Diigo Community/ HTML edition in areas of Diigo: WYSIWYM (WMD), WYSIWYG (FCKeditor, Kupu, TinyMCE)
Graham Perrin

HTML edition in areas of Diigo: WYSIWYM (WMD), WYSIWYG (FCKeditor, Kupu, TinyMCE) - 103 views

WYSYIWYG WYSIWYM HTML links broken bug suggestion gpd4

started by Graham Perrin on 16 Nov 08
Graham Perrin liked it
  • Graham Perrin
    To inform this discussion, some highlights and sticky notes:






    The latter suggests that WebKit developers may be close to resolving or working around a significant issue. However: this is _not_ an issue that I should expect to affect a minimally-configured Kupu in UIs within Diigo.

    = About versions and maintenance of Kupu =

    Don't be misled by the 2006 version 1.3.5 of Kupu at

    Focus instead on, and all of which demonstrate that (as Kupu for Plone is a product that is within 'Plone core') Kupu is highly and regularly maintained. (Many of the references to changesets etc. are to changesets within the Kupu code base, not the Plone code base. Open source done well.)

    = Merits of Kupu, FCKeditor and TinyMCE =

    It's often said that FCKeditor excels at dealing with the monstrosity that is Microsoft HTML. However, re as Diigo is HTML-centric, so we should not expect people to annotate (or paste from) Microsoft Word :)

    All things considered, I should tend towards Kupu …

    Best regards


    * annotated link to the PYPI page includes a sticky note highlighting that the list of supported clients of Kupu (browsers) does include WebKit-based browsers

    * annotated link to the WebKit bugzilla may fail in some browsers, if so then aim directly for
  • Graham Perrin
  • Graham Perrin
 | Public Sticky notes

    This exemplifies the difference between:

    a) rich highlights from an original

    - one of three highlights includes a link that can be clicked


    b) poorer, text/plain Diigo annotation

    - stuck to one of the highlights, text authored by a Diigo user includes two links, _neither_ of which can be clicked.
  • Graham Perrin
    Subject: WYSIWYG edition of rich text in Diigo comments, notes, posts

    I'm certain that for some users, WYSIWYG would encourage greater/richer use of annotations.

    Whilst I still wish for WYSIWYG edition of rich text in these areas, there's a side of me that prefers plain text:

    * partly for aesthetic/visual reasons - it's often easier to read plain text, especially in 'busy' environments;

    * partly for technical reasons - I think vaguely of APIs, and the like.

    In the meantime, it would be neat if we could preview things before posting.
  • Graham Perrin
    > WMD that's used in the Stack Overflow interface


    Reportedly good for Chinese text, too:

To Top

Start a New Topic » « Back to the Diigo Community group