Bug 102910 - [Share] Unknown file type handling in Share Project wizard needs to be improved
Summary: [Share] Unknown file type handling in Share Project wizard needs to be improved
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2005-07-06 14:39 EDT by John Whitley CLA
Modified: 2019-09-06 16:10 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Whitley CLA 2005-07-06 14:39:53 EDT
It should be possible to create new CVS file types (e.g. bindings to
Binary/ASCII for extensions or names) within the Share Project wizard. 
Currently, the user has to:
1) Realize that they're about to commit their files as binary, not ASCII.
   (thankfully, the UI makes this fairly plain..)
2) Cancel out of the wizard
3) Web search around for the problem
4) Go to Window -> Preferences -> Team -> CVS -> File Content to add any
   new file types.
5) Start the wizard all over again.

The wizard works well for "on the beaten path" projects, but this aspect of the
workflow needs improvement for projects with unusual file types.  In my case,
these were Myghty templates (http://www.myghty.org/, extension *.myt) and SCons
(http://www.scons.org/) build spec files ('SConstruct' and 'SConscript').
Comment 1 Michael Valenta CLA 2005-07-06 15:37:12 EDT
Actually, all you need to do is click finish in the sharing wizard and it will 
bring up the commit wizard. The commit wizard allows the user to configure 
unknown types. However, I admit that this is not obvious from the sharing 
wizard and that the workflow needs improvement.
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:10:10 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.