OSCommerce Product Manager for Windows
FS#81 - WYSIWYG HTML editor.
Attached to Project:
OSCommerce Product Manager
Opened by Mario A. Valdez-Ramirez (mvaldez) - Tuesday, 24 August 2004, 07:47 GMT
Last edited by Mario A. Valdez-Ramirez (mvaldez) - Saturday, 15 April 2006, 06:23 GMT
Opened by Mario A. Valdez-Ramirez (mvaldez) - Tuesday, 24 August 2004, 07:47 GMT
Last edited by Mario A. Valdez-Ramirez (mvaldez) - Saturday, 15 April 2006, 06:23 GMT
|
DetailsThe 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
We should test the Mozilla component:
http://www.iol.ie/%7Elocka/mozilla/mozilla.htm
http://www.paranoia.clara.net/articles/taming_the_lizard_with_delphi.html
It should work alike.
Testing EmbeddedED Delphi component (LGPL) as interface of the MSHTML engine.
We could use alse SynEdit as source-code editor.
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.
Changed the title of this bug by adding "WYSIWYG"; HTML source is Ok, but WYSIWYG is what most users had been asking.
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.
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.