I believe that one can already do something like this with commit and checkout event scripts in CVS that. One would just have to write the tool that translate between the two formats.
"Paul Ruane" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]... > > I was thinking of suggesting something along the same lines myself, but I believe this would better form a separate product that sits > between any editors (such as Idea) and whatever VCS is being used. That way you don't even have to stipulate that all developers even > use the same development tools -- another point that's hard to enforce. I'd hate to go back to JBuilder now! Plus it would also other file > types that cannot (or are best not) developed in Idea such as C++ files, HTML etc. that a project may be using. > > It could have a CVS style interface, for example. Any editor could use it believing that it was interacting with CVS directly, > but the program would apply coding styles before delegating the real repository work off to the actual CVS or other VCS? It would > apply a repository coding style when sending to the repository and apply a personal style when reading back. You could > have different preferred coding styles for different file types. > > Most importantly, it would finally banish the tab versus space conflicts! > > If the Idea guys are not interested in providing such a system, then perhaps a few of the people who contribute to this > list (myself included) could consider getting together to discuss the possiblity of creating such a product, open-source? Unless > someone knows of one already? > > Paul. > > > > > > "schmoe" > <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] > Sent by: cc: > [EMAIL PROTECTED] Subject: [Eap-features] code style: different settings for view/edit and persist > tbrains.com > > > 21/06/2002 15:13 > Please respond to > eap-features > > > > > > > Probably the biggest feature I'd like to see in Idea is a controversial > one - a separation between the way the code looks when I'm viewing/editing > it and how it looks on disk. Lots of developers end up having lots of > different coding styles (this is why Idea has so many code-formatting > options), and when working on a multi-developer project, these can conflict. > The easy answer is to impose a coding standard, but I'm not convinced that's > the right answer. I could get the best of both worlds if I could set up 2 > different sets of code-formatting options in Idea, one for view/edit and one > for save. My team could easily agree on an on-disk coding standard, as long > as we could each have our own individual edit/view code-views. It would be > great, because everyone's code would look like to me like it was written in > my style, and to everyone else like it was written in their style. > > I think this would be a cool feature, although it certainly raises some > deeper philosophical questions: If my view could obscure problems with the > on-disk version, the editor would be worthless. Is it really useful/correct > to have an editor that translates between the code you write and the code > that gets dumped to disk? > > Clearly, it would be better to just have the rest of the world adopt my > coding style, but until that happens, this is something I'd like to see. > Any chance the details of this feature could be worked out such that we > could see something like this someday? > > mike > > > _______________________________________________ > Eap-features mailing list > [EMAIL PROTECTED] > http://lists.jetbrains.com/mailman/listinfo/eap-features > > > > > -- > > This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. > > _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features
