Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    1. COYes, the article you linked to seems to cover everything about creating, contributing, and opening a perspective, but it doesn't mention how to only open a perspective on the first launch. I'm looking for similar behavior that the Welcome Screen of Eclipse uses, in the way that it only shows up on the first launch of Eclipse, and on the first launch after a new feature is installed (if that feature contributes to the Universal Welcome Screen). I could probably hack a way around to do this pretty easily, but I'm looking for the "Eclipse Way" to do it if it actually exists.
      singulars
    2. COYou programmatically open perspective and then save a flag that perspective has been opened once in your plugin preferences. Next time you check that flag on startup and skip this step if flag is already set.
      singulars
    3. COI've thought of that, but wanted to try to stay away from reading and writing 'flags' in preferences, since preferences are workspace related. I finally found this jewel...`PlatformUI.getWorkbench().getIntroManager().isNewContentAvailable()`This tells me when new content is installed, but it doesn't tell me what that new content is, so I'm afraid that if some other feature gets installed, then this code will return true again, and trigger my code that shows my perspective to run again. I've seen some Eclipse plugins do this, so I'm going to track down that code and see how they are doing it.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload