Comparison Chart

5 posts, 0 answers
  1. Julian Voelcker
    Julian Voelcker avatar
    156 posts
    Member since:
    Jan 2006

    Posted 25 Sep 2007 Link to this post

    Hi,

    It would be really handy to see a chart comparing the functionality of the 'normal' RadEditor to this Prometheus build so we can see what isn't implemented yet and then providing details of when the features are likely to be implemented.

    Cheers,

    Julian
  2. Shaun Peet
    Shaun Peet avatar
    571 posts
    Member since:
    Aug 2004

    Posted 25 Sep 2007 Link to this post

    Agreed.  I had already requested that Todd make this available on telerikwatch.com - I'm a little surprised it isn't there yet.
  3. UI for ASP.NET Ajax is Ready for VS 2017
  4. Julian Voelcker
    Julian Voelcker avatar
    156 posts
    Member since:
    Jan 2006

    Posted 26 Sep 2007 Link to this post

    Hi Shaun,

    Not come across telerikwatch.com - also doesn't seem to be anything there - is that the right address?

    Cheers,

    Julian
  5. Shaun Peet
    Shaun Peet avatar
    571 posts
    Member since:
    Aug 2004

    Posted 26 Sep 2007 Link to this post

    Yeah that's the right site.  I think Todd may have mentioned something about going to Bulgaria this week so I'm not sure if he's had time to update it.  Hopefully somebody can provide this list for us asap.
  6. Tervel
    Admin
    Tervel avatar
    1337 posts

    Posted 28 Sep 2007 Link to this post

    Hi Everyone,

    The Prometheus editor was written from scratch to address all major problems of the non-Prometheus version.
    The original codebase was obviously used as a reference to make sure the Prometheus editor is stable and its editing features working properly right from the start. The major advantages are of the new editor are:

    1. Greatly reduced loading time (in fact the new editor loads about 3 times faster, and initializes on the client 6 times faster)
    2. Reduced HTML footprint due to semantic rendering
    3. Ability to have editors with different skins on the same page
    4. Full integration with AJAX, as well as when the editor is in HTML mode
    5. Much greater design-time support, including inline declarations of tools and all editor collections directly into the page.
    6. Fast, optimized dialog loading using the new RadWindow for Prometheus
    7. Completely redesigned content filters architecture to ensure XHTML output, as well as correct functioning when the editor is used to edit full HTML pages
    8. New Localization implementation using resource (resx) files, rather than XML - building upon the extensive support for editing resources in VS 2005
    9. Single-dll deployment (all editor resources, including the dialogs reside in the same dll) - which makes deployment as simple as dropping the Prometheus dll and registering an HTTP handler in the web.config.
    10. A new ToolStrip for organizing tools with similar functionality in a dropdown (e.g. the InsertFormElement, PasteStrip and FormatStripper built-in tools) - available to developers as well.

    We chose to implement the new editor in "stages", and we focused on implementing a task completely before moving to the next. Here is a list of functional modules from non-Prometheus editor that are yet to be ported:

    1. AJAX Spellchecking
    2. Editor modules
    3. Docking of toolbars
    4. Several dialogs
    5. More skins

    Currently we are working hard porting the remaining functionality for the Q2 SP1 coming around Oct 10th, and the two editors should end up having essentially the same functional modules.
    In addition to this, after the service pack we plan on porting some of the Prometheus editor design changes to the non-Prometheus editor to increase its performance and usability. To be more specific, we plan to port the following:

    1. Port HTML mode to address problems with using AJAX when editor is in HTML mode
    2. Implement tool rendering using CSS sprites
    3. Implement the Prometheus "link and image path keeper" mechanism that guarantees URLs are preserved as entered
    4. Port the Content Filters implementation to address problems with working with full html pages

    Doing those will result in the "non-Prometheus" editor loading much faster, producing correct XHTML content when using filters, keep links reliably in all scenarios and integrate well with AJAX.

    Greetings,
    Tervel Peykov
    the Telerik team


    Instantly find answers to your questions at the new Telerik Support Center
Back to Top
UI for ASP.NET Ajax is Ready for VS 2017