Alternative to 'Only when no "..\" is required'

Could we perhaps use the collective wisdom in this forum to
think of a better alternative for the radio button 'Only
when no "..\" is required' on the Paths page?
The current text contains one restriction, one negation and
one requirement. That's at least two things too many for a
slow guy like me.

How about: 'Only for subfolders'
or: 'Only for children of module file folder'

12 comments

That would be cool if someone invent a better text! We spent many hours here
discussing it :)).

--
Valentin Kipiatkov
Chief Scientist, Vice President of Product Development
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

"Mikael Karlsson" <no_mail@jetbrains.com> wrote in message
news:29175827.1075471773040.JavaMail.itn@is.intellij.net...

Could we perhaps use the collective wisdom in this forum to
think of a better alternative for the radio button 'Only
when no "..\" is required' on the Paths page?
The current text contains one restriction, one negation and
one requirement. That's at least two things too many for a
slow guy like me.

>

How about: 'Only for subfolders'
or: 'Only for children of module file folder'

>


0

Problem is, "only when no .. is required" it's not only for subfolders of the module since IDEA can substitute path variables. So, thin radio button means: "Save paths relative to the module, if the path is under the module root OR under any path defined in 'Path Variables'". Since this is kinda long I think jetbrainers tried to shorten it _

My shot would be transform this into a simple checkbox (as opposed to a radio) labeled "Always use relative paths", which is off by default. Then, it's behaviour should be well documented in the help file. Like the old days :)

0

Leave it as is. It's better to have to think a couple of seconds about it than to be absolutly clueless because the description is to vague. (I almost never get as far as opening the help documentation.)

0

Please let me ensure you that the check box variant has been also discussed,
but leaving it as "Always use relative paths" may produce a confusion:
If unchecked, how would the paths be stored? People may think that even
paths under the module file folder would be stored as absolute which is not
true.

What do you think if we just present you several variants that we had before
we ended up with this one.
Your feedback will definitely help us close this thread before IDEA 4.0 is
released ;)))

So, here are the variants:

1.----


Paths that root from directories above the module file location:

- Store absolute

- Store relative to module file



2.----


Store relative to module file:

- All paths

- Only paths that root from the module file directory or lower

-



Thank you in advance for your help.

--
Ann Oreshnikova
Customer Support Manager
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

"Marcus Brito" <pazu@animegaiden.com.br> wrote in message
news:25186334.1075477638341.JavaMail.itn@is.intellij.net...

Problem is, "only when no .. is required" it's not only for subfolders of

the module since IDEA can substitute path variables. So, thin radio button
means: "Save paths relative to the module, if the path is under the module
root OR under any path defined in 'Path Variables'". Since this is kinda
long I think jetbrainers tried to shorten it _
>

My shot would be transform this into a simple checkbox (as opposed to a

radio) labeled "Always use relative paths", which is off by default. Then,
it's behaviour should be well documented in the help file. Like the old days
:)


0

Ann Oreshnikova wrote:

> 2.----


> Store relative to module file:
>
> - All paths
>
> - Only paths that root from the module file directory or lower

A variation of this would be to explicitly include the module file
directory. Something like this:

Store paths relative to the module file directory for:

- Files within /home/whatever/projects/FooModule

- All files, including files outside /home/whatever/projects/FooModule

This would perhaps be easier to understand because people won't have to
start thinking about what the module file directory is. Or perhaps it
would be more difficult to understand why
/home/whatever/projects/FooModule is chosen if you don't realize it is
because this is the location of the module file. I don't know.


A slightly different alternative:

Store paths relative to /home/whatever/projects/FooModule:

- For files within /home/whatever/projects/FooModule

- For all files

0

Here's another one:

For files outside module directory:
o Use absolute path
o Use relative path

It (more or less) clearly identifies what is affected and
it also clearly presents the two choices.

0

I agree that this is a silly piece of text. Not only is it confusing,
it means nothing on my platform (Linux). For me, that would be "../" so
this definitely has to change one way or another.

I vote for "Only for subfolder of module" or something like that.

Thanks,

Nick.

Mikael Karlsson wrote:

Could we perhaps use the collective wisdom in this forum to
think of a better alternative for the radio button 'Only
when no "..\" is required' on the Paths page?
The current text contains one restriction, one negation and
one requirement. That's at least two things too many for a
slow guy like me.

How about: 'Only for subfolders'
or: 'Only for children of module file folder'

0

This is how it was previously (except that we used "external" instead of "outside" ). I agree this describes the behaviour clearly
but only if the term "external" and "outside" is unambiguously defined.

--

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


"Mikael Karlsson" <no_mail@jetbrains.com> wrote in message news:30586062.1075499803250.JavaMail.itn@is.intellij.net...

Here's another one:

>

For files outside module directory:
o Use absolute path
o Use relative path

>

It (more or less) clearly identifies what is affected and
it also clearly presents the two choices.

>


0

It may look confusing, but the text is 100% correct. As for the slash, this is already fixed, will be available in the next build.

--

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


0

Mikael Karlsson wrote:

Here's another one:

For files outside module directory:
o Use absolute path
o Use relative path

It (more or less) clearly identifies what is affected and
it also clearly presents the two choices.


+10 this makes total sense.

R

0

Mikael Karlsson wrote:

Here's another one:

For files outside module directory:
o Use absolute path
o Use relative path

It (more or less) clearly identifies what is affected and
it also clearly presents the two choices.


Good solution, as long as you also include the name of the module
directory. If not, I think there's a risk that people think "module
directory" refers to the content root, and if the module file is stored
somewhere else, the option might not do what they think it does.

(I know you can have multiple content roots but many people may never
use this feature.)

0

After some discussions we have found this to be the best suggestion.
Thanks, Mikael!

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


0

Please sign in to leave a comment.