Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-7308

VPE Part should not show exceptions but readable explanation why it cannot be loaded

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 3.2.1.CR1, 3.3.0.M2
    • 3.2.0.Final
    • All other platforms except supported ones:
      macosx-carbon-x86
      macosx-cocoa-x86
      win32-win32-x86
      linux-gtk-x86
      linux-gtk-x86_64

      Exceptions related to loading xulrunner should be handled right way. Human friendly messages would be good here for usecases we know. VPE should check for current platform and if it is not supported do not scary users with exceptions. It should try to load XL just in case path to XL injected outside through System property, but show explanation instead of just exception. Something like:
      "Current platform ${os}${ws}${arch} is not supported. To find list of supported platforms and possible workarounds. please read this article on JBoss Tools Community Portal". If someone is trying to inject XULRunner implementation using system property it can say, That "Visual Editor tried to load XL from provided loaction ${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log View".
      We could also have check box to remove VE related parts from editor:
      "[x] Open only source part of Visual Editor".

        1. XL-x86_64-1.png
          80 kB
          Denis Golovin
        2. XL-x86_64-2.png
          101 kB
          Denis Golovin
        3. resolved-screenshot-1.png
          43 kB
          Yahor Radtsevich
        4. JBIDE-7308-2.patch
          2 kB
          Yahor Radtsevich
        5. screenshot19.png
          6 kB
          Denis Golovin

          There are no Sub-Tasks for this issue.

              dmaliarevich_jira Denis Maliarevich (Inactive)
              nivologd@gmail.com Denis Golovin (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: