OSCommerce Product Manager

OSCommerce Product Manager for Windows
Tasklist

FS#81 - WYSIWYG HTML editor.

Attached to Project: OSCommerce Product Manager
Opened by Mario A. Valdez-Ramirez (mvaldez) - Tuesday, 24 August 2004, 02:47 GMT-6
Last edited by Mario A. Valdez-Ramirez (mvaldez) - Saturday, 15 April 2006, 01:23 GMT-6
Task Type New feature
Category Backend / Core
Status Assigned
Assigned To Mario A. Valdez-Ramirez (mvaldez)
Operating System All
Severity Medium
Priority Immediate
Reported Version any
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

The product editing window doesn't support HTML highlighting or WYSIWYG edition.

Any or both would be fine.

Currently we are testing the Open source project MSHTML Editor OSPv3r00, by Kurt Senfer (http://groups.yahoo.com/group/delphi-dhtmledit/files/DHTMLEdit/), released under the LGPL license.

It relies on the MSHTML engine provided by IE 5.5.

Also, for hightlighting we were considering SynEdit (http://synedit.sourceforge.net/).

Pending to finish testing of the first one and start testing on the second one.
This task depends upon

Comment by Mario A. Valdez-Ramirez (mvaldez) - Sunday, 10 April 2005, 02:11 GMT-6 Comment by Mario A. Valdez-Ramirez (mvaldez) - Wednesday, 28 September 2005, 13:37 GMT-6

Testing EmbeddedED Delphi component (LGPL) as interface of the MSHTML engine.
We could use alse SynEdit as source-code editor.

Comment by Mario A. Valdez-Ramirez (mvaldez) - Tuesday, 11 October 2005, 00:32 GMT-6
Increasing to High Priority.
Comment by Mario A. Valdez-Ramirez (mvaldez) - Tuesday, 11 October 2005, 00:38 GMT-6

We do not want to discriminate users based on the version of Internet Explorer they have in their computer. Using the MSHTML engine requires IE 5.5. Just adding the HTML editor would left those users without IE (or with older versions) in the dark.

What we can do is to provide an external HTML editor. For example, a button next to the description field in the product editing window named "HTML editor". It would launch a small HTML editor with the current content in the description field. On closing, it would pass the HTML code to the product editing window.

If the user does not have IE 5.5 or higher, no problem, the button will not appear.

The option is to compile two different versions, one with the dependency and other without. Messy. The MSHTML is not that good.
Comment by Mario A. Valdez-Ramirez (mvaldez) - Saturday, 15 April 2006, 01:16 GMT-6

Changed the title of this bug by adding "WYSIWYG"; HTML source is Ok, but WYSIWYG is what most users had been asking.


Comment by Mario A. Valdez-Ramirez (mvaldez) - Saturday, 15 April 2006, 01:18 GMT-6

We have discarded the embedding of MSHTML and Firefox. We will go for the external HTML editor.

Again, we can build our own embedded version (with MSHTML [easy] or Mozilla [harder]) or go and get NVU.
Comment by Mario A. Valdez-Ramirez (mvaldez) - Saturday, 15 April 2006, 01:23 GMT-6

If we choose to use NVU, we cannot distribute it along with OSCPMWin because NVU is released under a MPL license without GPL clause. We would distribute it in a separate package.

If we choose to use our own minieditor (with embedded component), we can release it GPL. However, I am not sure if it worths the pain of building it.

I am font to NVU because it is very powerful and easy to use, but it would look bloated fo this simple application. We can, however, not distribute it, but only support it (leaving the users the task of installing it in their system).

I will try to build NVU from sources, in a kind of NVU lite.


Loading...