Community
Participate
Working Groups
As Eclipse gains new ground and followers non-programmers are also using Eclipse e.g. CVS. I find that non-programmers(hardware engineers, technical support personnel, web HTML/CSS developers, etc.) and programmers new to software version control struggle with various concepts: - Refresh. At best non-programmers can be trained to *always* perform a refresh before Team->Foo. - Team->Synchronize. This wording is scary. Synchronize is an "active" verb. What does it change? Something locally? Something on the disk? The novice user is *NOT* going to understand that the elipsis means that there are further requests. Although it is late in the game, I claim that Eclipse's current user base is only a small fraction of what it is going to be in a couple of years. Best address this now. ;-) - Binary vs. text files. Øyvind
Here are the responses to your three issues: Refresh: This is covered in bug 73260. Please make relevant comments on this topic there. Team>Synchronize: I agree that this term may be scary to some but it is now well know to Eclipse users. Changing it would confuse an already large user base. Plus, if a novice user is scared by a term, perhaps they should read the doc;-) Plus, I can't think of any reasonable replacements. ASCII vs. Binary: Not sure what specific problem you mean. It is generally the reponsibility of domain specific tooling to provide file types/content types that are meaningful for their domain files. We are doing work in 3.2 which will allow model tooling to handle the merging of their file types which will improve things. If there is a specific problem you know of, feel free to reopen or log a separate bug report. *** This bug has been marked as a duplicate of 73260 ***
(In reply to comment #1) > Here are the responses to your three issues: > > Refresh: This is covered in bug 73260. Please make relevant comments on this > topic there. > > Team>Synchronize: I agree that this term may be scary to some but it is now well > know to Eclipse users. Changing it would confuse an already large user base. > Plus, if a novice user is scared by a term, perhaps they should read the doc;-) The current Eclipse user base is a small fraction of what it will be in the future! :-) Something really must be done about this. How about adding a synonym? "Team->View differences..." > Plus, I can't think of any reasonable replacements. > > ASCII vs. Binary: Not sure what specific problem you mean. It is generally the > reponsibility of domain specific tooling to provide file types/content types > that are meaningful for their domain files. We are doing work in 3.2 which will > allow model tooling to handle the merging of their file types which will improve > things. If there is a specific problem you know of, feel free to reopen or log a > separate bug report. The novice used is asked whether to treat a file as ASCII or binary. The safe choice is binary.
> Team>Synchronize: I agree that this term may be scary to some but it is now well > know to Eclipse users. Changing it would confuse an already large user base. > Plus, if a novice user is scared by a term, perhaps they should read the doc;-) > Plus, I can't think of any reasonable replacements. When trying to introduce version control to a mixed team there is the additional problem of trying to make a team pull in the same direction. There will be team members who are trying to proove that CVS(Version control in general) is not worth the effort or somehow makes this more difficult or error prone. Giving these team members any sort of traction based upon issues in the GUI causes lots of extra work. They most certainly won't be spending their time reading the manual ;-)
