Creating new module

When creating a new module, I find it annoying that the Module Content root follows the Module name, and the Module file folder follows the Module Content root.

So, if you type in the Module name field, the Module content root field (and the Module file folder) will pick up changes.
And if you type in the Module content root field, the Module file folder will pick up changes.

I don't find this particular convenient. Typically, I want to store my module files in a single folder, and my content roots will be somewhere else.
There is no direct correspondence at all between the module names, the module file locations, and the module content roots.

So I find it annoying that IDEA by default makes this correspondence. Do others find this useful, or annoying?

11 comments

If you change either name or path, they are not synchronized anymore. So if
you change module content root first and then module name and module
location, you'll get the desired result. As for defaults, quite a few people
find them convenient and logical, that's why we have chosen them.

--
Best regards,
Eugene Zhuravlev
Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"


0

If you change either name or path, they are not
synchronized anymore. So if
you change module content root first and then module
name and module
location, you'll get the desired result.


Yes - I recognise that.

As for
defaults, quite a few people
find them convenient and logical, that's why we have
chosen them.


"Quite a few people" - I'm one of those who doesn't find it convenient - indeed I find it inconvenient. So part of my question was as to how many people find it convenient or inconvenient.
If it's only "convenient and logical" for a small proportion of people, and inconvenient for others, then it's maybe not so good to have it as a default behaviour.
Or at least make it configurable :)

0

I'm part of "Quite a few people" - I find it very convenient.

0

I'm also among the "convenient" group, sorry Calum.
r.

Calum MacLean wrote:

"Quite a few people" - I'm one of those who doesn't find it convenient - indeed I find it inconvenient. So part of my question was as to how many people find it convenient or inconvenient.
If it's only "convenient and logical" for a small proportion of people, and inconvenient for others, then it's maybe not so good to have it as a default behaviour.
Or at least make it configurable :)

0

I don't find it convenient. I have to change it every time I create a
project.

--
Norris Shelton
Sun Certified Java Programmer


"Calum MacLean" <no_mail@jetbrains.com> wrote in message
news:7956480.1076499969769.JavaMail.itn@is.intellij.net...

If you change either name or path, they are not
synchronized anymore. So if
you change module content root first and then module
name and module
location, you'll get the desired result.

>

Yes - I recognise that.

>

As for
defaults, quite a few people
find them convenient and logical, that's why we have
chosen them.

>

"Quite a few people" - I'm one of those who doesn't find it

convenient - indeed I find it inconvenient. So part of my question
was as to how many people find it convenient or inconvenient.

If it's only "convenient and logical" for a small proportion of people,

and inconvenient for others, then it's maybe not so good to have it as a
default behaviour.

Or at least make it configurable :)



0

I'm part of "Quite a few people" - I find it very convenient.

0

convenient

"Calum MacLean" <no_mail@jetbrains.com> wrote in message
news:7956480.1076499969769.JavaMail.itn@is.intellij.net...

If you change either name or path, they are not
synchronized anymore. So if
you change module content root first and then module
name and module
location, you'll get the desired result.

>

Yes - I recognise that.

>

As for
defaults, quite a few people
find them convenient and logical, that's why we have
chosen them.

>

"Quite a few people" - I'm one of those who doesn't find it

convenient - indeed I find it inconvenient. So part of my question
was as to how many people find it convenient or inconvenient.

If it's only "convenient and logical" for a small proportion of people,

and inconvenient for others, then it's maybe not so good to have it as a
default behaviour.

Or at least make it configurable :)



0

I find it inconvenient. I keep both my project files and my module files
outside of the content root.
And what's even more annoying, is that the default path (along with the
project file) is the one I want to keep, but it gets changed every time I
change the content root (which is, evidently, somewhere else).

And since we're at that dialog, what's with the two directory location entry
modes? Why isn't the module file location an edit box, as the content root
one? That way I could, at least, copy its value before changing the content
root and put it back afterwards.

Anyways, having two ways of entering directory paths (on the same page,
even) seems less than optimal to me (and not even that creative). Stick with
the edit boxes, so many people know their directory structure and are
quicker at typing than at expanding trees.

Andrei

"Calum MacLean" <no_mail@jetbrains.com> wrote in message
news:7956480.1076499969769.JavaMail.itn@is.intellij.net...

If you change either name or path, they are not
synchronized anymore. So if
you change module content root first and then module
name and module
location, you'll get the desired result.

>

Yes - I recognise that.

>

As for
defaults, quite a few people
find them convenient and logical, that's why we have
chosen them.

>

"Quite a few people" - I'm one of those who doesn't find it

convenient - indeed I find it inconvenient. So part of my question
was as to how many people find it convenient or inconvenient.

If it's only "convenient and logical" for a small proportion of people,

and inconvenient for others, then it's maybe not so good to have it as a
default behaviour.

Or at least make it configurable :)



0

That way I could, at least, copy its value before changing the content
root and put it back afterwards


With the current UI you can copy the value module location value

--
Best regards,
Eugene Zhuravlev
Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"



0

That way I could, at least, copy its value before changing the content
root and put it back afterwards

>

With the current UI you can copy the value module location value

>

Yeah, but it will change when I change the content root and I will have no
option but to expand trees to get the old location back. It kind of sucks, I
really think it should be an edit box, like the one for content root.

Andrei


0

Please sign in to leave a comment.