Add "New Child Folder" or "New Subfolder" option

[GoogleCodeExporter]

There is a "New child page" option, why not a "New child folder"? It it kind of 
annoying to have to constantly drag and drop new folders into parent folders to 
keep an outline structure. 

Original issue reported on code.google.com by sprocke...@gmail.com on 2 Mar 2011 at 5:51

[GoogleCodeExporter]

Not an answer to your question, but merely a question related to it: can 
someone explain the conceptual advantage or disadvantage of pages over folders?

I know that one cannot modify/add the text page of a folder, as it shows as a 
solid gray page (which somehow 'scares' me each time I see one :) but apart 
from that?

Personally I prefer the use of a page as the container, allowing me to put some 
general description of its contents (as a pseudo folder)

Original comment by epposan@gmail.com on 2 Mar 2011 at 9:00

[GoogleCodeExporter]

I added folders a long time ago when pages couldn't have children.  Now page 
can have children, so I myself only use pages (and I sometimes use the 
folder-like icon just to visually breakup the treeview).  I will someday remove 
folders because they cause this confusion.  That is why I am not fully 
developing them with their own set of menu options (like "add child folder").

Original comment by matt.rasmus@gmail.com on 2 Mar 2011 at 11:13

• Added labels: Priority-Low, Type-Enhancement, ui
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

Understood. I can see both sides of the argument. In my opinion, folders are 
good to keep around for a few reasons: 

(1) 99% of the outliner apps out there use this - and even if you're not trying 
to emulate other apps, it is clear that many users will expect them as part of 
the outliner structure. 
(2) As you said, it breaks up the treeview visually
(3) It imitates the true directory structure of the OS. It seems a little 
counterintuitive (to me) to have the true directory structure be folder > 
subfolder > page and then the structure in your app be page > child page > 
child page. Perhaps this is because one of my favorite things about keepnote is 
that it keeps a true file structure instead of a single DB file -- I use this 
in conjunction with dropbox to browse my notes on my mobile device, which I 
wouldn't be able to do well without the folder structure.

Anyway, I guess I'm rambling now, but it just seems to me like folder structure 
is an expected function of an outliner like this. That said, I'd readily give 
it up if/when you pull the plug on folders because I like the app so much, and 
it wouldn't be *that* hard to get used to. Maybe just unsettling for new users 
in the future.

Original comment by sprocke...@gmail.com on 2 Mar 2011 at 4:35

[GoogleCodeExporter]

I think you could close this issue (and keep the menu simpler) if issue 186 
were closed - right now keepnote doesn't mimic industry and OS standards, which 
is what is causing the confusion.

I'd also be sad to see Folders removed, but that's off topic here.  If there is 
a better place to discuss the roadmap, please let us know.

Original comment by clouserw on 6 Mar 2011 at 8:56

[GoogleCodeExporter]

Issue 547 has been merged into this issue.

Original comment by matt.rasmus@gmail.com on 27 Oct 2011 at 12:59