3 Replies Latest reply on Apr 30, 2007 8:27 AM by maxandersen

    xhtml editor is terribly slow

    mugwump

      I just wonder, if anyone else has made the same experience: I'm using exadel to edit facelet/xhtml-pages mixed with some javascript. And the xhtml-editor is slow up to being completely unusable, even if I use it in the source-only mode.

      I'm not sure, what exactly makes it so slow, as content-assist is almost non-existent (attributes for tags work, but as I am using seam it does not resolve any el-statements). I now switched back to the html-editor from wtp: Functionality is not too different, but at least it doesn't hang up and it is fast.

      So, here are my questions:

      - anyone knows what causes the editor to be so damn slow?
      - are there any new features for the editor planned in the red-hat-release (resolving el's for seam?!)

      cheers
      stefan

        • 1. Re: xhtml editor is terribly slow
          maxandersen

          No i dno't know why it should be slow. How big are your files ?

          and yes, resolving el's for seam is already implemented for @Name'ed components.

          More on the way...look in our RHDS jira for seam feature requests and let us know ;)

          /max

          • 2. Re: xhtml editor is terribly slow
            mugwump

            the files are small most of the time: Between 5 and 10kb. Most of the layout-info is in css and a template, so there is only some simple display-logic left.

            Is mixing java-script and xhtml a problem? I'm currently prototyping, so i have some inline javascript in the files - maybe this causes the editor to choke?!

            /stf

            PS: resolving seam-el's is great news! Are there any betas planned?! "Summer" is a little vague for a release-date, are there any dates for a pre-release?

            • 3. Re: xhtml editor is terribly slow
              maxandersen

              alpha is planned for soon ;)

              if you could please report steps to reproduce this it would be great (put it in rhds jira)