Community
Participate
Working Groups
Build Identifier: 20100917-0705 Hi, In workspace launcher, the following sentence explains workspace meaning: "Eclipse stores your projects in a folder called a workspace." Although above info this is not wrong, it definitely is not explaining the meaning of eclipse workspace to a new user. Many new eclipse users struggle with workspace in eclipse because it is a directory and not a file. It is very important to provide a good explanation to eclipse workspace concept. It is relevant for all eclipse versions (Indigo, Helios, e4, etc.). Thanks, Yevgeny Reproducible: Always
Hi, Below link has a very good workspace explanation: http://www.dvteclipse.com/vlogdt/html/concepts/workspace_workbench_refresh.html Relevant part: "The workspace is a directory which holds information about the projects you work on, as well as the Eclipse preferences (from layout to behavior). We can say that the workspace "holds" the Integrated Development Environment: the data you work on (organized in projects) and how you work with it (preferences)." Thanks, Yevgeny
Additional useful explanation that could help defining a better text to "workspace launcher": http://www.dvteclipse.com/vlogdt/html/concepts/what_is_a_workspace.html
It could be improved, especially because there is no (F1/?) help.
Hi, Is there a chance to support this for Juno release? It's only a matter for changing a text. Thanks a lot, Yevgeny
This will be post Juno PW
Hi, Any plans supporting this? Thanks, Yevgeny
(In reply to Yevgeny Shifrin from comment #6) > Hi, > > Any plans supporting this? > > Thanks, > Yevgeny Not without a patch from the community.
(In reply to Dani Megert from comment #7) > (In reply to Yevgeny Shifrin from comment #6) > > Hi, > > > > Any plans supporting this? > > > > Thanks, > > Yevgeny > > Not without a patch from the community. I opened this ticket several years ago. I think it is very important, as new users are very confused with "workspace" concept. I even proposed a text that could be added (with some minor modifications). It should take an experienced eclipse developers 5-10 minutes to fix it. Really frustrating that it was not done till now and you need community patch for this :(
New Gerrit change created: https://git.eclipse.org/r/47364
I pushed my proposal for workspace launcher text: The {0} workspace is a folder holding data and metadata of your projects, as well as application's preferences.\n\ Choose a workspace folder to use for this session. The length of the above text has direct influence on the width of the workspace launcher dialog. Please, see the Gerrit Change and give feedback.
(In reply to Patrik Suzzi from comment #10) > I pushed my proposal for workspace launcher text: > > The {0} workspace is a folder holding data and metadata of your projects, as > well as application's preferences.\n\ > Choose a workspace folder to use for this session. > > The length of the above text has direct influence on the width of the > workspace launcher dialog. > > Please, see the Gerrit Change and give feedback. Hi Patrik, Thank you very much for pushing it :-) Best regards, Yevgeny
As pointed by Dani: > The workspace doesn't necessarily contain the data. It can also be outside the workspace. > Also, if we change this we should do it everywhere where the workspace is mentioned. > Maybe the explanation of a workspace is better done in the F1/? help.
(In reply to Patrik Suzzi from comment #12) > As pointed by Dani: > > > The workspace doesn't necessarily contain the data. It can also be outside the workspace. > > Also, if we change this we should do it everywhere where the workspace is mentioned. > > Maybe the explanation of a workspace is better done in the F1/? help. I think that proposed formulation is much better than the existing text ("Eclipse stores your projects in a folder called a workspace.") which is really bad :-( Of course it could be improved and some other adaptations could be made. I would suggest pushing this change as quickly as possible. Maybe additional enhancement request could be opened for additional improvements.
We discuss a solution via Bug 479847. *** This bug has been marked as a duplicate of bug 479847 ***
