WYSIWYG HTML Editor Ext2.0? ODF

January 5th, 2009
  • Extjs development team,

    I'd like to know your thoughts on the WYSIWYG HTML Editor that is being integrated into Ext2.0. The biggest short comming of the editors available are that they cannot export the content to standard formats such as OpenXML or PDF directly. I would think that an enterprise level application would see this feature as a huge bonus. I've been using TinyMCE which I'm sure you will agree is an outstanding WYSIWYG editor. With the ASP (Application Service Provider) model of years ago now coming to fruition I would think this would be a direction any WYSIWYG would want to go in. Your thoughts?


  • We have no plans to offer anything like this. The HTML Editor is intended to be exactly what it currently is -- a lightweight, simple editor, not an "enterprise" editor. This sort of functionality would have to be plugged in by someone else.


  • The advantage to exporting to one of these formats is that you'll be able to save and open them within applications which support those formats.I'm no MS jock, but can't you edit these formats in Word today?
    No, it's not Word's preferred fmt, but it will do it.

    On the other hand, I see wisdom in the translate-after-export approach.
    It could be done under the hood, after all, which would seem to meet the OP's idea.

    --dan


  • Not on the dev team, but you did post in general discussion so I figured I'd throw in my two cents.

    First off, you have to realize that you are using a WYSIWYG editor inside of a browser. It isn't a fully-functional word processor. It doesn't really make sense, at least to me, how you would plan on editing ODF or OpenXML formats when the browser doesn't render them. You wouldn't be able to switch between html/code view and the WYSIWYG view.

    On top of that, there would be no way for a javascript application to generate a PDF, being that PDF encorperate these three things: PostScript, Embedded Fonts, and data compression. To generate PDF, you need a server-side technology.

    I'm curious to see what the ExtJS devs think about this though.

    Side Note: As for OpenXML, it should be abandoned, like most of Microsoft's technologies, its inherently flawed and bloated. Not to mention, this format requires zip compress capability, meaning you'll have to use a server-side tech.


  • I dont really see the point here? Why not just do an ajax call to the server. It shouln't be that hard to convert xhtml to pdf or whatever using php/asp/etc...

    I'd say this really isn't a javascript task.


  • What i could see as the solution is the WYSIWYG editor having a plug-in type system where those could be added by an end-user much the way the User Extension (http://extjs.com/learn/Ext_Extensions) are being done.

    Just a though...


  • Thank you for the response. Regarding the comment:


    It doesn't really make sense, at least to me, how you would plan on editing ODF or OpenXML formats when the browser doesn't render them


    To clarify, I asked if it could be 'exported' and not necessarily 'edited' as one of the soon to be standardized document formats. The advantage to exporting to one of these formats is that you'll be able to save and open them within applications which support those formats.


  • "Save as ODF"... that's the point. I'm confused why others don't see the value in it?







    • #If you have any other info about this subject , Please add it free.#
    Your name:
    E-mail:
    Telphone:

    Your comments:


    If you have any other info about WYSIWYG HTML Editor Ext2.0? ODF , Please add it free.

    Posted in linkdatax.com | edit

    Intel Officially Releases i845 Chipset
    Thomson's CCBN Buy Ends Corporate Spy Case