Jon Steelman schrieb:

I'm interested in creating a plugin that might do either of these. The

motivation is that IDEA is so slow over the samba mount but by

corporate decree the projects have to be built and run over that samba

mount, so a system that runs in parallel on a local drive and pushes

the changes out to samba is one performance workaround worth

exploring.

I strongly suggest you look into using a version control system (e.g.

Subversion). Several developers working on one source tree via Samba

isn't exactly the recommendable method of collaboration in a developer

team ...

cu,

   Raffi

--

Come to think of it, there are already a million monkeys on a million

typewriters, and Usenet is nothing like Shakespeare!

herzog@raffael.ch · PGP Key 5D1FF5F4 · http://www.raffael.ch/

Hello Jon,

• A hook so that whenever a file saves (automatically or explicitly)

to its content root that you can also save the file out to another

point outside of the project's content roots?

FileDocumentManagerListener.beforeDocumentSaving()

• A hook that would allow you to find all the changed files and also

save all those outside of the proejct's content roots?

Depending on what you mean by "changed", FileDocumentManager.getUnsavedDocuments()

may be what you need.

--

Dmitry Jemerov

Software Developer

JetBrains, Inc.

http://www.jetbrains.com/

"Develop with Pleasure!"

Hello Jon,

Dmitry - Thanks! I'll give those a try.

Note that not all disk writes go through this path. For example, ipr/iml/iws

saving does not.

Have you considered simply using rsync?

--

Dmitry Jemerov

Software Developer

JetBrains, Inc.

http://www.jetbrains.com/

"Develop with Pleasure!"

Hello Carolina,

Because I want the user to be able to say no to my question, that is

to cancel the saving.

 

This makes sense if you disable Idea autosave... Eclipse does

something similar, I hate Eclipse but I have to recognize that would

be the right behaviour...

Actually IntelliJ IDEA saves files automatically in very many situations

(compiles/Ant builds, VCS operations, refactorings etc.), so giving an option

not to save only on exit will hardly be an adequate solution.

Also, the local history keeps track of old versions of files, so even if

you make some unwanted changes which are then saved, you can restore the

previous version from the local history.

--

Dmitry Jemerov

Development Lead

JetBrains, Inc.

http://www.jetbrains.com/

"Develop with Pleasure!"

Hello Carolina,

Actually we are not using the Java part a lot... we are mainly using

xml editing so refactors, etc, are not a concern for me.

 

I never disable automatic saving.. but I've got a coworker that does,

and he complains that Idea saves his files without asking (like any

other editor would) even when he has disabled automatic saving. I

believe he is right there...

 

I posted a question to support and they said there is an opened issue

about it, but that it is not likely to be fixed...

http://jetbrains.net/jira/browse/IDEABKL-59

 

So I thought that I could do a plugin to make it behave that way,

because I thought it was a reasonable thing to ask...

 

It seemed to me that those to methods I've asked for would serve my

purpose... but I don't know where to define them...

Well, you can try to write such a plugin, but I don't think it would provide

a satisfactory user experience.

You need to define an ApplicationComponent in your plugin, and call FileDocumentManager.getInstance().addFileDocumentSynchronizationVetoer()

with your implementation of FileDocumentSynchronizationVetoListener. Your

implementation should throw VetoDocumentSavingException from the beforeDocumentSaving()

method implementation if you decide to block document saving.

--

Dmitry Jemerov

Development Lead

JetBrains, Inc.

http://www.jetbrains.com/

"Develop with Pleasure!"