Auto creation of complex folder structures

I regularly use very complex folder structures that return for different projects, different years, etc. very time consuming if done by hand. Is there a way in Dopus to automate the proces? There is a nice freeware utility that basically does this http://www.iansharpe.com/help_makenewfolder.php but it doesn't work under Dopus, and I have to start ugly explorer every time I want to use it, hence my question.
Thx.

Opus lets you create multiple folders and/or nested folders out-of-the-box.

Just use \ characters in the path to create nested folders (e.g. A\B\C\D) and use , characters to create multiple folders (or nested folders) at the top level (e.g. X,Y,Z).

You can combine the two (e.g. Cow\Moo,Dog,Cat\Meow).

(Make sure the "Create moultiple folders (comma-separated)" option is turned on in the Create Folder dialog. Of course, that will cause problems if you need to create a folder with a , in its name.)

Also, if you find that you're always creating the same complex structure below each folder then you could create a button which automates that entirely.

Thx Leo, could you show me an example of doing this with a button? I have been trying but it doesn't always work as expected...

What's the folder structure you need the button to create?

for instance (I am using spaces in the folder names):

1 aaa
sub one
2 bbb
sub two
subsub A
3 ccc

maybe this is more clear

1 aaa
---sub one
2 bbb
---sub two
------subsub A
3 ccc

This will create that:

CreateFolder NAME="aaa\sub one" READAUTO=no CreateFolder NAME="bbb\sub two\subsub A" READAUTO=no CreateFolder NAME="ccc" READAUTO=no

works perfectely! thx Leo, just a little thing I can't get to work: your earlier remark about combining / and , ??
what if in the above example I want to have :
2 bbb
---sub two
------subsub A
------subsub B
how do I button that?

In the create folder dialog, you could enter this:

2 bbb\sub two\subsub A,2 bbb\sub two\subsub B

In a button it's easier to do it like this:

CreateFolder NAME="2 bbb\sub two\subsub A" READAUTO=no CreateFolder NAME="2 bbb\sub two\subsub B" READAUTO=no

@Leo

I also have to create involved folder structures from time to time. Using the create folder dialog in Dopus to create something like this:

A
--a1
----aa1
----aa2
------aaa1
------aaa2
----aa3
------aaa1
--------aaaa1
B
--b1
----bb1
----bb2
----bb3
------bbb1
--------bbbb1
--------bbbb2

it almost easier to do it one folder at a time. When facced with this i'm still starting up Explorer so that I can use MakeNewFolder (as LukeQ mentioned) The MNF syntax is simple, intuitive and the above example can be done on one line.

The MNF syntax is siblings are seperated by a | and children are enclosed in <>. Here's a full explaination:

http://www.iansharpe.com/help_makenewfolder.php

Be nice if the powers the be could make to Dopus syntax as simple.

laffin_boy

If you want to request a feature, tell GPSoftware not the forum. :slight_smile:

Although, I have to ask...

Would you really be typing in the syntax for such a complex folder structure directly into the create folder window?

If not, and you're creating buttons which will create specific hierarchies, I don't see how the syntax makes it easier than explicitly listing the folders that need to be created (taking advantage of the fact that Opus will already create multiple levels of folder).

One very long and complex line, though. I can't imagine many people typing the line required to create the folders in your example and not making a mistake along the way. (Did you mean for all the B-level folders to have completely different names to the A-level ones? If they were all the same then I can see the syntax being a bit more useful.)

Edit: Actually, looking at your example more, I don't see how the syntax would help much as there's very little commonality between any of the subdirectories being created. Perhaps I need to read more about the syntax.

Can you show us the string you'd type to create those folders?

Hi Leo,

The difference is that using Dopus you have to keep re-entering the top level folder in order to call out all the sub-folders. I MNF the child folders are enclosed in angle brakets so you never repeat anything. Here's the complete "A" folder example in MNF syntax:

A<a1<aa1 | aa2<aaa1 | aaa2>> | aa3<aaa1>>

MNF also enters <>'s in pairs for you so that you're less likely to make a mistake.

lance

And you'd actually type that in on-the-fly as a one-off operation, with confidence that it'd do what you expected and you hadn't made a mistake?

What about the B level?

I can see the syntax has its uses, I'm just not yet convinced that many people would use it versus what's already possible in typical situations. (Not that I'm the person who needs convincing!)

Hi Leo,

It's just as easy using MNF as the A structure was. And using Dopus....well i'll let you diagram that one. I don't have time tonight.

(At the risk of accusing you of a serious geek crime) Leo, you're not being logical here. Dopus has already gone to the trouble of providing a way to do this - regardless of how often it's users might actually exercise it. I'm simply pointing out that Dopus's method is much more work than the MNF method for the equivalent task.

Your objectivity is beyond question.

lance

This is where my doubts come in. If it's a hassle to work out the string you'd type for the example you chose, how many people are really going to use this syntax for anything complex? (For simple stuff, the existing system works fine.)

It's not that the new syntax makes things worse -- people would obviously not be forced to use it -- but a question of whether implementing it is a good use of time.

If it's easy to add to Opus then I'm for it (or at least not against it) but if it's a pain to add then it might not be worth it.

I guess you guys wouldn't be asking for it if it wasn't something you used in real life.

If it was added I think I'd want changes to the Create Folder window so that it was bigger and maybe even could display a tree that shows you which folders it's going to create so you can spot any mistakes (i.e. a < > | in the wrong place, or missing).