OSCOM Kupu News http://kupu.oscom.org:84/news/ News from the OSCOM Kupu editor project en OSCOM Kupu News Midgard Components Framework - de.linkm.newsticker Kupu 1.3 released http://kupu.oscom.org:84/news/kupu13.html http://kupu.oscom.org:84/news/kupu13.html Mon, 5 Sep 2005 13:56:23 +0200 guido_w Highlights are i18n support, a Sarissa upgrade, spell checking and Plone 2.1 support (and a lot of Plone-specific bug fixes!) The Kupu team has just released Kupu 1.3 final. Highlights for 1.3 i18n support Sarissa upgrade spell checking support Plone 2.1 support Changes since 1.3rc3 disabled entity escaping linkbyuid turned off by default fixed linking to folder types What is Kupu? Kupu is a rich-text ('WYSIWYG') editor for browsers, written entirely in JavaScript. It runs on Internet Explorer and Mozilla based browsers, and produces well-formed, clean (X)HTML. It can (optionally) save to a page without reloading, provides generic browser interfaces to the server (so-called 'library drawers') to browse for images and links and has a large set of tools (functions) available, as well as providing an API to easily roll your own. Kupu is distributed under terms of a BSD-style license and is used in a number of commercial and open-source products. There's a friendly, active community and there's quite extensive documentation available. Download Kupu 1.3 can be downloaded here: http://kupu.oscom.org/download/kupu13.html More information about usage and development of the product can be found on: http://kupu.oscom.org

Highlights for 1.3

  • i18n support
  • Sarissa upgrade
  • spell checking support
  • Plone 2.1 support

Changes since 1.3rc3

  • disabled entity escaping
  • linkbyuid turned off by default
  • fixed linking to folder types

What is Kupu?

Kupu is a rich-text ('WYSIWYG') editor for browsers, written entirely in
JavaScript. It runs on Internet Explorer and Mozilla based browsers, and
produces well-formed, clean (X)HTML. It can (optionally) save to a page
without reloading, provides generic browser interfaces to the server
(so-called 'library drawers') to browse for images and links and has a
large set of tools (functions) available, as well as providing an API to
easily roll your own.

Kupu is distributed under terms of a BSD-style license and is used in a
number of commercial and open-source products. There's a friendly,
active community and there's quite extensive documentation available.

Download

Kupu 1.3 can be downloaded here:
http://kupu.oscom.org/download/kupu13.html

More information about usage and development of the product can be found on:
http://kupu.oscom.org
]]> Kupu article on ONLamp http://kupu.oscom.org:84/news/onlamp_article.html http://kupu.oscom.org:84/news/onlamp_article.html Fri, 29 Apr 2005 16:22:11 +0200 guido_w Robert Jones wrote a cool article on ONLamp today which explains how to install and set up the Kupu editor (http://www.onlamp.com/pub/a/onlamp/2005/04/28/kupu.html). http://www.onlamp.com/pub/a/onlamp/2005/04/28/kupu.html http://www.onlamp.com/pub/a/onlamp/2005/04/28/kupu.html]]> Kupu 1.2 released http://kupu.oscom.org:84/news/kupu12released.html http://kupu.oscom.org:84/news/kupu12released.html Wed, 20 Apr 2005 16:05:10 +0200 guido_w After some delay version 1.2 of the Kupu rich-text editor has been released. This release contains a substantial number of new features, as well as numerous bugfixes. Highlights Image upload for the image browser Improved 'out-of-the-box' support for the browsers Added support for CSS' float on images Zoom mode to make Kupu fill the full browser window BeforeUnload handler added which controls all form fields A lot of specific fixes and enhancements for the Silva and Plone platforms What is Kupu? Kupu is a rich-text ('WYSIWYG') editor for browsers, written entirely in JavaScript. It runs on Internet Explorer and Mozilla based browsers, and produces well-formed, clean (X)HTML. It can (optionally) save to a page without reloading, provides generic browser interfaces to the server (so-called 'library drawers') to browse for images and links and has a large set of tools (functions) available, as well as providing an API to easily roll your own. Kupu is distributed under terms of a BSD-style license and is used in a number of commercial and open-source products. There's a friendly, active community and there's quite extensive documentation available. Download Kupu 1.2 can be downloaded here: http://kupu.oscom.org/download/kupu12.html More information about usage and development of the product can be found on: http://kupu.oscom.org Highlights
  • Image upload for the image browser
  • Improved 'out-of-the-box' support for the browsers
  • Added support for CSS' float on images
  • Zoom mode to make Kupu fill the full browser window
  • BeforeUnload handler added which controls all form fields
  • A lot of specific fixes and enhancements for the Silva and Plone platforms

What is Kupu?

Kupu is a rich-text ('WYSIWYG') editor for browsers, written entirely in JavaScript. It runs on Internet Explorer and Mozilla based browsers, and produces well-formed, clean (X)HTML. It can (optionally) save to a page without reloading, provides generic browser interfaces to the server (so-called 'library drawers') to browse for images and links and has a large set of tools (functions) available, as well as providing an API to easily roll your own.

Kupu is distributed under terms of a BSD-style license and is used in a number of commercial and open-source products. There's a friendly, active community and there's quite extensive documentation available.

Download

Kupu 1.2 can be downloaded here: http://kupu.oscom.org/download/kupu12.html

More information about usage and development of the product can be found on: http://kupu.oscom.org

]]> Kupu 1.2b1 released http://kupu.oscom.org:84/news/kupu_1_2b1_released.html http://kupu.oscom.org:84/news/kupu_1_2b1_released.html Wed, 5 Jan 2005 16:30:33 +0100 guido_w The Kupu team has just released version 1.2b1 of their cross-browser JavaScript WYSIWYG editor. This is a beta of the upcoming 1.2 feature release, which will hopefully be releases within a few weeks. The Kupu team has just released version 1.2b1 of their cross-browser JavaScript WYSIWYG editor. This is a beta of the upcoming 1.2 feature release, which will hopefully be releases within a few weeks.Highlights: Added image upload.Improved drawer support and demo content for drawers.Added support for CSS 'float' for images.Zoom mode to make Kupu fill the browser window.BeforeUnload handler added which controls all form fields.A lot of Plone fixes and enhancements. JavaScript WYSIWYG editor. This is a beta of the upcoming 1.2 feature
release, which will hopefully be releases within a few weeks.

Highlights:

  • Added image upload.
  • Improved drawer support and demo content for drawers.
  • Added support for CSS 'float' for images.
  • Zoom mode to make Kupu fill the browser window.
  • BeforeUnload handler added which controls all form fields.
  • A lot of Plone fixes and enhancements.
]]> Kupu 1.1 released! http://kupu.oscom.org:84/news/2004-07-14-000.html http://kupu.oscom.org:84/news/2004-07-14-000.html Wed, 14 Jul 2004 18:31:00 +0200 guido_w The Kupu developer team is proud to announce the 1.1 release of Kupu. This release provides a number of new features as well as a lot of bugfixes. What is Kupu? Kupu is a JavaScript WYSIWYG editor that works on both Mozilla and Internet Explorer based browsers. It allows editing a web-page from the application serving it rather then in a seperate application. Key features are extensibility and clean code, but it tries to also provide a good user experience by using a different approach for certain standard things, for instance it's document-centric rather then data-centric, meaning that (in the default setup) one edits a full page rather than part of a form (note that it can be used as a textarea replacement as well) and it uses PUT request (also optional) whenever possible to give the user the impression he's working in a real application rather then on some web page. Kupu is released under a BSD-style license. What's new? Changes from 1.1b2-1.1: Added a new SourceEdit tool, replacing the old function (thanks to Damian Gajda).Added definition list support to the core distribution (template).Moved the drawers out of the core distribution since they're not bugfree when used from the filesystem. Highlights from 1.0.3-1.1: Added a new Selection object that provides a high-level cross-browser API for working with selections.Added a templating system for the HTML files. This makes producing HTML a bit harder but allows you to change a feature in one place for all the HTML files (so no copy/pasting of HTML is required anymore).Added a unit test suite (ecmaunit, see http://kupu.oscom.org for more details) and some unit tests.A new feature called drawers has landed. Drawers are some form of in-page windows that provide functionality as the toolboxes do (so adding images and links, for instance), they provide an alternative for situations where there's little real-estate. Some special drawers got written (library drawers) that use XSLT to transform XML from the server to content (works on any server that can produce XML).Added support for Silva, Silva 1.0 will ship with Kupu 1.1.Added Plone support.Buttons are now stateful, meaning they look different when the cursor is inside an element they control (so when inside a bold piece of text, the button looks pressed in).There are now access keys defined for all the buttons in the toolbar.A lot of bugfixes... Especially IE 5.5 has had some extra attention. We don't expect all bugs are gone now, but stability has improved a lot since the 1.0.3 release (and a lot more even since 1.0). Where can I find it? You can download the release here: kupu::http://kupu.oscom.org/download/kupu11.html Thanks to: We would like to thank the people from Infrae, ETH and Oscom, and Holger Krekel, Damian Gajda, Jan Smith, Felicia Wong for the logo, Eric Casteleijn for the name and Torvald de Boskat for ethical support. We hope you enjoy Kupu For questions, remarks or information, check the homepage for a list of possible channels to get in touch. We have an IRC channel on irc.freenode.net (#kupu), a mailinglist and an issue tracker, and we're very prepared to help you out. Additional developers are always welcome. Cheers, Guido Wesdorp, the Kupu team

What is Kupu?

Kupu is a JavaScript WYSIWYG editor that works on both Mozilla and Internet Explorer based browsers. It allows editing a web-page from the application serving it rather then in a seperate application.

Key features are extensibility and clean code, but it tries to also provide a good user experience by using a different approach for certain standard things, for instance it's document-centric rather then data-centric, meaning that (in the default setup) one edits a full page rather than part of a form (note that it can be used as a textarea replacement as well) and it uses PUT request (also optional) whenever possible to give the user the impression he's working in a real application rather then on some web page.

Kupu is released under a BSD-style license.

What's new?

Changes from 1.1b2-1.1:

  • Added a new SourceEdit tool, replacing the old function (thanks to Damian Gajda).
  • Added definition list support to the core distribution (template).
  • Moved the drawers out of the core distribution since they're not bugfree when used from the filesystem.

Highlights from 1.0.3-1.1:

  • Added a new Selection object that provides a high-level cross-browser API for working with selections.
  • Added a templating system for the HTML files. This makes producing HTML a bit harder but allows you to change a feature in one place for all the HTML files (so no copy/pasting of HTML is required anymore).
  • Added a unit test suite (ecmaunit, see http://kupu.oscom.org for more details) and some unit tests.
  • A new feature called drawers has landed. Drawers are some form of in-page windows that provide functionality as the toolboxes do (so adding images and links, for instance), they provide an alternative for situations where there's little real-estate. Some special drawers got written (library drawers) that use XSLT to transform XML from the server to content (works on any server that can produce XML).
  • Added support for Silva, Silva 1.0 will ship with Kupu 1.1.
  • Added Plone support.
  • Buttons are now stateful, meaning they look different when the cursor is inside an element they control (so when inside a bold piece of text, the button looks pressed in).
  • There are now access keys defined for all the buttons in the toolbar.
  • A lot of bugfixes... Especially IE 5.5 has had some extra attention. We don't expect all bugs are gone now, but stability has improved a lot since the 1.0.3 release (and a lot more even since 1.0).

Where can I find it?

You can download the release here: kupu::http://kupu.oscom.org/download/kupu11.html

Thanks to:

We would like to thank the people from Infrae, ETH and Oscom, and Holger Krekel, Damian Gajda, Jan Smith, Felicia Wong for the logo, Eric Casteleijn for the name and Torvald de Boskat for ethical support.

We hope you enjoy Kupu

For questions, remarks or information, check the homepage for a list of possible channels to get in touch. We have an IRC channel on irc.freenode.net (#kupu), a mailinglist and an issue tracker, and we're very prepared to help you out. Additional developers are always welcome.

Cheers,

Guido Wesdorp, the Kupu team

]]> Kupu 1.1 Beta 1 released http://kupu.oscom.org:84/news/2004-05-22-000.html http://kupu.oscom.org:84/news/2004-05-22-000.html Sat, 22 May 2004 13:43:38 +0200 philikon The Kupu Team is pround to announce the first beta release of Kupu 1.1. After the 1.0.3 release, which was the first one to carry the new name and license, the new version brings new, long-awaited features. What is Kupu?Kupu is a client-side JavaScript What You See Is What You Get (WYSIWYG) editor. It works in both Mozilla and Internet Explorer based browsers (including Netscape 7) and produces well-formed XHTML. Kupu is object oriented and designed to be customizable and extensible.Where to downloadYou can find the release tarball at http://kupu.oscom.org/download/.What is new in Kupu 1.1?Templates for different systems are now generated using an XML/XSLT-based templating system. The system is completely extendable and customizable, thus allowing third-party developers to integrate Kupu in their application even easier.Configuration of the editor instance is now done using embedded XML, instead of non-standard attributes on the iframe element. This makes it not-only standard-compliant, it is also much easier to extend the set of configuration directives.Some core functionality is now covered by unit tests, based on the JavaScript testing framework ECMAUnit. This has helped to improve the code quality in JavaScript environments tremendously.A new way of inserting images and linking to documents were implemented: library drawers. Drawers are windows that open up inside the browser without invoking a browser popup. Library drawers load information about linkable/insertable objects from the server via standardized XML. That makes them indepentend of any target platform.Stateful buttons now indicate when the cursor is inside text that is bold, underlined, etc.Apart from ordered and unordered lists, Kupu also now supports adding HTML definition lists.A cross-browser selection API was implemented to allow manipulationof a document's arbitrary elements using selections and cursors.Access key functionality was added.The Silva integration has been improved a lot. This is the first release with complete Silva support.Integration into Plone has been completely rewritten. It now features a complete server-side implementation of the drawers while providing basic support for the WYSIWYG editor API.What to expect from Kupu in the future?For the final 1.1 release, we hope to mainly improve some of the UI aspects. For the more distant future, we hope to make our editor compliant with ATAG, the W3C's standard for editor accessability. On the technical side of things, we are working on completing editor configuration and initialization through XML as well as the cross-browser selection API. We hope to make more and more components available as separate packages, such as ECMAUnit by Guido Wesdorp or the great Sarissa cross-browser library by Manos Batsis.Special thanks toFelicia Wong for the new shiny Kupu logoHolger Krekel and Codespeak for the invaluable supportManos Batsis for SarissaJan Smith for testing and finding bugsETH for support and inspirationOSCOM for support and resources Infrae for supportOn behalf of the Kupu Team,Philipp von Weitershausen What is Kupu?
Kupu is a client-side JavaScript What You See Is What You Get (WYSIWYG) editor. It works in both Mozilla and Internet Explorer based browsers (including Netscape 7) and produces well-formed XHTML. Kupu is object oriented and designed to be customizable and extensible.

Where to download


You can find the release tarball at http://kupu.oscom.org/download/.

What is new in Kupu 1.1?

  • Templates for different systems are now generated using an XML/XSLT-based templating system. The system is completely extendable and customizable, thus allowing third-party developers to integrate Kupu in their application even easier.
  • Configuration of the editor instance is now done using embedded XML, instead of non-standard attributes on the iframe element. This makes it not-only standard-compliant, it is also much easier to extend the set of configuration directives.
  • Some core functionality is now covered by unit tests, based on the JavaScript testing framework ECMAUnit. This has helped to improve the code quality in JavaScript environments tremendously.
  • A new way of inserting images and linking to documents were implemented: library drawers. Drawers are windows that open up inside the browser without invoking a browser popup. Library drawers load information about linkable/insertable objects from the server via standardized XML. That makes them indepentend of any target platform.
  • Stateful buttons now indicate when the cursor is inside text that is bold, underlined, etc.
  • Apart from ordered and unordered lists, Kupu also now supports adding HTML definition lists.
  • A cross-browser selection API was implemented to allow manipulationof a document's arbitrary elements using selections and cursors.
  • Access key functionality was added.
  • The Silva integration has been improved a lot. This is the first release with complete Silva support.
  • Integration into Plone has been completely rewritten. It now features a complete server-side implementation of the drawers while providing basic support for the WYSIWYG editor API.

What to expect from Kupu in the future?

For the final 1.1 release, we hope to mainly improve some of the UI aspects. For the more distant future, we hope to make our editor compliant with ATAG, the W3C's standard for editor accessability. On the technical side of things, we are working on completing editor configuration and initialization through XML as well as the cross-browser selection API. We hope to make more and more components available as separate packages, such as ECMAUnit by Guido Wesdorp or the great Sarissa cross-browser library by Manos Batsis.

Special thanks to

  • Felicia Wong for the new shiny Kupu logo
  • Holger Krekel and Codespeak for the invaluable support
  • Manos Batsis for Sarissa
  • Jan Smith for testing and finding bugs
  • ETH for support and inspiration
  • OSCOM for support and resources
  • Infrae for support
On behalf of the Kupu Team,

Philipp von Weitershausen

]]> Kupu Logo official now! http://kupu.oscom.org:84/news/2004-05-17-000.html http://kupu.oscom.org:84/news/2004-05-17-000.html Mon, 17 May 2004 18:17:51 +0200 philikon The kupu team proudly presents: The official kupu logo! Shortly after the name kupu was born, the kupu team was striving to find a logo that would match the new name. We were looking for something that would provide a shape simple enough to allow abstraction, yet unique to Kupu. Surprisingly, our choice for the new name turned out to feature a great coincidence: Kupu kupu means butterfly in Indonesian.Thus, the butterfly is not only kupu's mascot, the blue-winged animal also fancies the logo. Many thanks go to Felicia Wong who drew it for us and Kit Blake who assembled it and the kupu letters into a logo.For all kupu fans out there, we hope to provide little "produced by kupu" logos as well as t-shirts soon. Stay tuned for more...On behalf of the kupu team,Philipp v.W.

Shortly after the name kupu was born, the kupu team was striving to find a logo that would match the new name. We were looking for something that would provide a shape simple enough to allow abstraction, yet unique to Kupu. Surprisingly, our choice for the new name turned out to feature a great coincidence: Kupu kupu means butterfly in Indonesian.

Thus, the butterfly is not only kupu's mascot, the blue-winged animal also fancies the logo. Many thanks go to Felicia Wong who drew it for us and Kit Blake who assembled it and the kupu letters into a logo.

For all kupu fans out there, we hope to provide little "produced by kupu" logos as well as t-shirts soon. Stay tuned for more...

On behalf of the kupu team,

Philipp v.W.
]]> Nightly builds available http://kupu.oscom.org:84/news/2004-04-19-000.html http://kupu.oscom.org:84/news/2004-04-19-000.html Mon, 19 Apr 2004 20:08:16 +0200 philikon By introducing the XML/XSLT-based templating system, we have not only made it a lot easier for us and other developers to maintain and customize templates. We've unfortunately also raised the bar for 3rd party developers that simply want to integrate Kupu into their application. To make it a little easier for them, I am now offering nightly builds that come with pre-generated templates for Silva, Plone and Zope2. See http://kupu.oscom.org/download/nightly.html for a download link.The nightly tarball contains a checkout from the subversion repository's trunk as well as the pre-generated templates. They are generated using xsltproc and beautified using xmllint, both from GNOME's libxml/libxslt packages. These are currently the recommended tools to develop with. I recommend Windows developers and contributors, for whom the bar admittedly has been raised (unfortunately), to use the before mentioned tools as well (binaries available for example at http://www.zlatkovic.com/pub/libxml/).With best regards,Philipp v.W. http://kupu.oscom.org/download/nightly.html for a download link.

The nightly tarball contains a checkout from the subversion repository's trunk as well as the pre-generated templates. They are generated using xsltproc and beautified using xmllint, both from GNOME's libxml/libxslt packages. These are currently the recommended tools to develop with. I recommend Windows developers and contributors, for whom the bar admittedly has been raised (unfortunately), to use the before mentioned tools as well (binaries available for example at http://www.zlatkovic.com/pub/libxml/).

With best regards,

Philipp v.W.
]]> Kupu renaming complete http://kupu.oscom.org:84/news/2004-04-09-000.html http://kupu.oscom.org:84/news/2004-04-09-000.html Fri, 9 Apr 2004 12:36:58 +0200 philikon After we settled with Kupu for a new name for the epoz successor a month ago, renamed the codebase two weeks ago and announced the first release under the new name (kupu 1.0.3) a week ago, the renaming is complete now. The subversion repository, mailinglists, and issue tracker were renamed yesterday. Thanks to Holger Krekel for his invaluable support! Subversion repository:http://codespeak.net/svn/kupu/If you have a subversion checkout of Kupu, you will need to switch your working copy to the new path, e.g. if you have a trunk checkout:svn switch http://codespeak.net/svn/kupu/trunk/kupu Issue tracker:http://codespeak.net/issues/kupu/Mailinglists:kupu-dev@codespeak.net (development of Kupu)http://codespeak.net/mailman/listinfo/kupu-devkupu-checkins@codespeak.net (repository checkins)http://codespeak.net/mailman/listinfo/kupu-checkinsPlease use the kupu-dev@codespeak.net list in favour of epoz's list at sourceforge now.In case you encounter problems, the kupu team will be at your assistance on the mailinglist and the #kupu IRC channel at irc.freenode.net.With best regards,Philipp v.W. Subversion repository:
http://codespeak.net/svn/kupu/

If you have a subversion checkout of Kupu, you will need to switch your working copy to the new path, e.g. if you have a trunk checkout:

svn switch http://codespeak.net/svn/kupu/trunk/kupu

Issue tracker:

http://codespeak.net/issues/kupu/

Mailinglists:

kupu-dev@codespeak.net (development of Kupu)
http://codespeak.net/mailman/listinfo/kupu-dev

kupu-checkins@codespeak.net (repository checkins)
http://codespeak.net/mailman/listinfo/kupu-checkins

Please use the kupu-dev@codespeak.net list in favour of epoz's list at sourceforge now.

In case you encounter problems, the kupu team will be at your assistance on the mailinglist and the #kupu IRC channel at irc.freenode.net.

With best regards,

Philipp v.W.

]]> Kupu 1.0.3 released http://kupu.oscom.org:84/news/2004-04-01-000.html http://kupu.oscom.org:84/news/2004-04-01-000.html Thu, 1 Apr 2004 15:16:23 +0200 philikon It is our pleasure to announce the release of Kupu 1.0.3. As of now, the in-browser WYSIWYG editor formerly known as epozNG has a new name: Kupu! Even though it was never the intention, the Epoz WYSIWYG editor development had split in 2 branches, confusing both developers and users. Hopefully the new name settles this confusion. The pastLast year, a small team of developers started working on a full rewrite of the Epoz product written by Maik Jablonski, with the objective to provide a WYSIWYG editor for Infrae's document management system Silva [http://www.infrae.com/products/silva]. Maik wasn't interested in continuing development of his version and didn't join the team in the rewrite, but he was fine with the team using the name. However, consequent bugfixes and enhancements, mostly coming from Plone [http://plone.org], still went into the old Epoz, leaving us with two actively developed versions. This led to much confusion. In January 2004, Michael Wechner, president of OSCOM (Open Source Content Management) [http://oscom.org] proposed to make epozNG an official OSCOM project. This proposal was welcomed by the development team. As part of the move to OSCOM, it was agreed to change epozNG's name to end the confusion, and to change the license from ZPL to something less Zope-specific, BSD. After two months of brainstorming and endless name suggestions, the team finally decided. Thanks to Eric Casteleijn for "Kupu". Kupu is Maori and means "word, statement, remark". The Present A new name, a new license, a new website [http://kupu.oscom.org], and it's time for a new release. Since epozNG left off at 1.0.2, the first Kupu release is 1.0.3. It's not a major release, mainly containing small bugfixes, but it's a milestone.The Future The future of Kupu seems bright. Currently it provides a host of features for a WYSIWYG editor, and works in both IE and Mozilla based browsers. We intend to continue in that direction. The Kupu developers focus on standards and high quality code as well as new technologies. We plan to steadily improve Kupu, and bring it to maturity without losing its clean design and comprehensible codebase. Thanks to Michael Wechner and OSCOM for providing a new home Holger Krekel and Codespeak for the invaluable support Infrae for support The guys at ETH Zürich for inspiration Eric for "Kupu" Manos Batsis for Sarissa and for letting us distribute it under the Kupu LicenseHenri Bergie for setting us up with http://kupu.oscom.orgJan Smith for testing and finding bugs On behalf of the Kupu Contributors Guido Wesdorp, Philipp von Weitershausen, Paul Everitt The past
Last year, a small team of developers started working on a full rewrite of the Epoz product written by Maik Jablonski, with the objective to provide a WYSIWYG editor for Infrae's document management system Silva [http://www.infrae.com/products/silva]. Maik wasn't interested in continuing development of his version and didn't join the team in the rewrite, but he was fine with the team using the name. However, consequent bugfixes and enhancements, mostly coming from Plone [http://plone.org], still went into the old Epoz, leaving us with two actively developed versions. This led to much confusion.

In January 2004, Michael Wechner, president of OSCOM (Open Source Content Management) [http://oscom.org] proposed to make epozNG an official OSCOM project. This proposal was welcomed by the development team. As part of the move to OSCOM, it was agreed to change epozNG's name to end the confusion, and to change the license from ZPL to something less Zope-specific, BSD.

After two months of brainstorming and endless name suggestions, the team finally decided. Thanks to Eric Casteleijn for "Kupu". Kupu is Maori and means "word, statement, remark".

The Present

A new name, a new license, a new website [http://kupu.oscom.org], and it's time for a new release. Since epozNG left off at 1.0.2, the first Kupu release is 1.0.3. It's not a major release, mainly containing small bugfixes, but it's a milestone.

The Future

The future of Kupu seems bright. Currently it provides a host of features for a WYSIWYG editor, and works in both IE and Mozilla based browsers. We intend to continue in that direction.

The Kupu developers focus on standards and high quality code as well as new technologies. We plan to steadily improve Kupu, and bring it to maturity without losing its clean design and comprehensible codebase.

Thanks to

  • Michael Wechner and OSCOM for providing a new home
  • Holger Krekel and Codespeak for the invaluable support
  • Infrae for support
  • The guys at ETH Zürich for inspiration
  • Eric for "Kupu"
  • Manos Batsis for Sarissa and for letting us distribute it under the Kupu License
  • Henri Bergie for setting us up with http://kupu.oscom.org
  • Jan Smith for testing and finding bugs
On behalf of the Kupu Contributors
Guido Wesdorp, Philipp von Weitershausen, Paul Everitt

]]>