Node perspective doesn't support working sets #25

Open
paulvi opened this Issue Apr 28, 2013 · 14 comments

Comments

Projects
None yet
2 participants
@paulvi
Member

paulvi commented Apr 28, 2013

Node perspective doesn't support working sets.

When selecting Top Level Elements -> Working sets, nothing happens.

Switching-to-Working-Sets

In other perspectives it is OK

@tomotaro1065

This comment has been minimized.

Show comment
Hide comment
@tomotaro1065

tomotaro1065 Apr 28, 2013

Member

You should lean how to user Working Sets on Eclipse.

image

See http://mcuoneclipse.com/2012/05/17/eclipse-working-sets-explained/

Member

tomotaro1065 commented Apr 28, 2013

You should lean how to user Working Sets on Eclipse.

image

See http://mcuoneclipse.com/2012/05/17/eclipse-working-sets-explained/

@tomotaro1065

This comment has been minimized.

Show comment
Hide comment
@tomotaro1065

tomotaro1065 Apr 28, 2013

Member

But bugs exists in Node project wizard and Express project wizard.
Working sets do not appear in [Select Working Sets] dialog. (#25/4)

image

Member

tomotaro1065 commented Apr 28, 2013

But bugs exists in Node project wizard and Express project wizard.
Working sets do not appear in [Select Working Sets] dialog. (#25/4)

image

@paulvi

This comment has been minimized.

Show comment
Hide comment
@paulvi

paulvi Apr 28, 2013

Member

What I have is:
I have 3 working sets: JAVA, NODEJS, NODECLIPSE
When I switch from Java perspective to Node perspective, Project Explorer's project list becomes flat (no working sets). (#25/2)

But I want that my tree stays the same, it is just tools (set of views) that should change, not views content.

Member

paulvi commented Apr 28, 2013

What I have is:
I have 3 working sets: JAVA, NODEJS, NODECLIPSE
When I switch from Java perspective to Node perspective, Project Explorer's project list becomes flat (no working sets). (#25/2)

But I want that my tree stays the same, it is just tools (set of views) that should change, not views content.

@paulvi

This comment has been minimized.

Show comment
Hide comment
@paulvi

paulvi Apr 28, 2013

Member

By the way, can user run a set or selection of Node.js projects? (#25/3) It would have sense sometimes...

Impossible, because of #4

Member

paulvi commented Apr 28, 2013

By the way, can user run a set or selection of Node.js projects? (#25/3) It would have sense sometimes...

Impossible, because of #4

@tomotaro1065

This comment has been minimized.

Show comment
Hide comment
@tomotaro1065

tomotaro1065 Apr 28, 2013

Member

It didn't reproduce.
image
image

Member

tomotaro1065 commented Apr 28, 2013

It didn't reproduce.
image
image

@paulvi

This comment has been minimized.

Show comment
Hide comment
@paulvi

paulvi Apr 29, 2013

Member

Now we have issue inside issue (#25/2), that is closed.

Member

paulvi commented Apr 29, 2013

Now we have issue inside issue (#25/2), that is closed.

@tomotaro1065

This comment has been minimized.

Show comment
Hide comment
@tomotaro1065

tomotaro1065 Apr 30, 2013

Member

(#25/3) No, Multiple boot of Node.js in Nodeclipse is not supported.
(#25/4) This will be fixed in the next version 0.4 .

Member

tomotaro1065 commented Apr 30, 2013

(#25/3) No, Multiple boot of Node.js in Nodeclipse is not supported.
(#25/4) This will be fixed in the next version 0.4 .

@paulvi

This comment has been minimized.

Show comment
Hide comment
@paulvi

paulvi Apr 30, 2013

Member

(#25/1) is likely closed.
(#25/2) is closed.
yes, #25/3 depends on #4 (reading package.json)
(#25/4) will be closed.

Member

paulvi commented Apr 30, 2013

(#25/1) is likely closed.
(#25/2) is closed.
yes, #25/3 depends on #4 (reading package.json)
(#25/4) will be closed.

@ghost ghost assigned tomotaro1065 Apr 30, 2013

@tomotaro1065

This comment has been minimized.

Show comment
Hide comment
@tomotaro1065

tomotaro1065 Apr 30, 2013

Member

#25/3 depends on not only #4 but also its debugging port.
Currently using 5858 port fixedly. If we are going to support for this issue, dynamic management of the port is required. It's not so easy.
I do not know whether there is worth the it. It would be low priority.

Member

tomotaro1065 commented Apr 30, 2013

#25/3 depends on not only #4 but also its debugging port.
Currently using 5858 port fixedly. If we are going to support for this issue, dynamic management of the port is required. It's not so easy.
I do not know whether there is worth the it. It would be low priority.

@tomotaro1065

This comment has been minimized.

Show comment
Hide comment
@tomotaro1065

tomotaro1065 Apr 30, 2013

Member

To Paul,

I'm going to close this issue when I release 0.4 .
If you think there is worth on #25/3, please open another issue.

Member

tomotaro1065 commented Apr 30, 2013

To Paul,

I'm going to close this issue when I release 0.4 .
If you think there is worth on #25/3, please open another issue.

@paulvi

This comment has been minimized.

Show comment
Hide comment
@paulvi

paulvi Apr 30, 2013

Member

I just extended #4.

Member

paulvi commented Apr 30, 2013

I just extended #4.

@paulvi

This comment has been minimized.

Show comment
Hide comment
@paulvi

paulvi Apr 30, 2013

Member

Currently using 5858 port fixedly. If we are going to support for this issue, dynamic management of the port is required. It's not so easy.

There is no sense of debugging several application in the same time. But running them may be helpful. However I agree it is low priority, not so many people would think in this way (running several projects)

Member

paulvi commented Apr 30, 2013

Currently using 5858 port fixedly. If we are going to support for this issue, dynamic management of the port is required. It's not so easy.

There is no sense of debugging several application in the same time. But running them may be helpful. However I agree it is low priority, not so many people would think in this way (running several projects)

@tomotaro1065

This comment has been minimized.

Show comment
Hide comment
@tomotaro1065

tomotaro1065 May 19, 2013

Member

Version 0.4 has been released.

Member

tomotaro1065 commented May 19, 2013

Version 0.4 has been released.

@paulvi

This comment has been minimized.

Show comment
Hide comment
@paulvi

paulvi Jul 10, 2013

Member

Exactly the same bug:

Node perspective doesn't support working sets.
When selecting Top Level Elements -> Working sets, nothing happens.

Nodeclipse NTS 0.4.10 (Nodeclipse 0.4 on Eclipse 4.3 Kepler IDE for JEE developers)
running on Windows 7 (Chinese locale)

Member

paulvi commented Jul 10, 2013

Exactly the same bug:

Node perspective doesn't support working sets.
When selecting Top Level Elements -> Working sets, nothing happens.

Nodeclipse NTS 0.4.10 (Nodeclipse 0.4 on Eclipse 4.3 Kepler IDE for JEE developers)
running on Windows 7 (Chinese locale)

@paulvi paulvi reopened this Jul 10, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment