Workspaces 0.8

Workspaces 0.8 is available at:

http://www.intellij.org/twiki/bin/view/Main/WorkspacesPlugin

Changes since version 0.7:

  • Global preferences panel (in IDE Settings)

  • Option to not close files belonging to other open workspaces (configurable

in preferences panel)

  • Workspaces now accessible via tool window and/or menu (configurable in

preferences panel)

  • "Close All Workspaces" action (currently only available in Workspaces

menu)

  • "Close All Non-Workspace Files" action (currently only available in

Workspaces menu)

  • When creating a workspace containing only one file, the workspace name

defaults to the name of the file (instead of "Untitled").

I'd really appreciate any feedbackespecially from Swing guruson better
ways to do things and to help solve the several known issues (see Known
Issues list at above URL). (I can spell Swing, and that's about it, so
there are probably a ton of things that I'm doing in a really stupid way.)




3 comments
Comment actions Permalink

Chris, you are about to create one of the most influential plugins.
The latest 0.8 version is amazing.

However there is one logical issue:

  • Option to not close files belonging to other open workspaces

(configurable

in preferences panel)


This feature is (I believe) quite important but let's assume this:
- a workspace is considered open implicitly (based on open files)
- have a workspace W1 with one file A
- have a workspace W2 with files A and B and C and D
- have no files open
- open and then close W2 - you will left with file A open
- open W2, close it and then try to close W1 - no luck, A is still open.

I believe the problem is in the implicit 'open workspace' definition.
If the status 'open' would be explicit (someone opened it) this problem
would be gone.
I will try to look at the plugin sources and maybe I'll come with an
alternative
implementation to try and see.

r.


0
Comment actions Permalink


"Richard Nemec" <rndzank@attbi.com> wrote in message
news:aoi08t$8l3$1@is.intellij.net...

Chris, you are about to create one of the most influential plugins.
The latest 0.8 version is amazing.


Hey, thanks! :D

However there is one logical issue:

>

  • Option to not close files belonging to other open workspaces

(configurable

in preferences panel)

>

This feature is (I believe) quite important but let's assume this:
- a workspace is considered open implicitly (based on open files)
- have a workspace W1 with one file A
- have a workspace W2 with files A and B and C and D
- have no files open
- open and then close W2 - you will left with file A open
- open W2, close it and then try to close W1 - no luck, A is still open.


Yeah, this is one of my major beefs with this feature (this is the "it'll
look like the close button doesn't work" problem i talk about in one of my
posts at the URL below). But, I can only reproduce the case you describe
when the settings are:

When closing a workspace, don't close files that belong to other...
( ) Fully-open workspaces
(*) Partially-open or fully-open workspaces

Changing it to be stricter by selecting "Fully-open workspaces" makes the
problem go away, no?

I debated whether or not to even provide the looser "Partially-open or
fully-open workspaces" option, but i figured that if i didn't, someone would
ask for it :D

I believe the problem is in the implicit 'open workspace' definition.
If the status 'open' would be explicit (someone opened it) this problem
would be gone. I will try to look at the plugin sources and maybe I'll
come with an alternative implementation to try and see.


Cool, thanks. I'm not convinced explicit opening/closing is the way to go
yet, but if you wanna give it a shot, i'd love to see it (apologies in
advance for the nearly complete lack of javadocs :) For more thoughts on
explicit vs implicit opening/closing, see my first reply (to Jon) at:

http://www.intellij.net/forums/thread.jsp?forum=18&thread=12754

I'm still kinda on the fence about the whole "don't close files belonging to
other open workspaces" feature, or at least the current implementation of it
(mainly due to situations like you describe above and the "it'll look like
the close button doesn't work" problem).

What're your thoughts about my suggestion (last paragraph in that same post
at the above URL) for a locking scheme? I imagine the global prefs panel
might have locking options that would cause workspaces to become
automatically "locked" once they're fully opened (explicitly/implicitly),
maybe auto-unlocked when closed (explicitly/implicitly), etc.

Thanks,

chris


0
Comment actions Permalink

- open and then close W2 - you will left with file A open
- open W2, close it and then try to close W1 - no luck, A is still open.

>

posts at the URL below). But, I can only reproduce the case you describe
when the settings are:

>

(*) Partially-open or fully-open workspaces

>

Changing it to be stricter by selecting "Fully-open workspaces" makes the
problem go away, no?


Sory I was not exact. These were two problems:
- first (open and close W2 doesn't close everything) happens always
- second (cannot close subworkspace) happens with the partial setting.

Of course, all these happen when
"not-closing-files-if -belong-to-another-workspace"
option is turned on.

I will continue later with the rest of your message :)

r.


0

Please sign in to leave a comment.