Enable folders in Editor (+3)

[DartBot]

This issue was originally filed by grob...@gmail.com

---

The Dart Editor does not show subfolders of a project.

This is requirement for more advanced project layouts, like for example mavens recommendation of a standard directory layout:

/src/main/dart
/src/test/dart

[danrubel]

Removed Type-Defect label.
Added Type-Enhancement, Area-Editor, Triaged labels.

[keertip]

Changed the title to: "Enable folders in Editor (+1)".

[danrubel]

[user feedback]
looks nice, what I really miss is that my libraries (ie "applications") are a bunch of files although they are organized in folders.
Which is already known by the editor (or only compiler? atm) that those files are in subfolders (#import("someFolder/someFile.dart")

---

Changed the title to: "Enable folders in Editor (+2)".

[DartBot]

This comment was originally written by JayYoun...@gmail.com

---

The usefulness of the library drill-down navigation in the Dart Editor completely escapes me. I do understand the utility of being able to quickly find and open the files that declare the APIs that you're using, but from the standpoint of navigating around a project, it seems completely inadequate. For example, I've been working through the code samples of a recent book, but writing them in Dart rather than Java (the language the book uses). I set up a directory structure similar to how you would using Java packages - this is just a very natural way to organize code for many, many developers.

The attached "directory_structure.png" screenshot shows the project's directory structure. I'm only a few chapters in, so you can imagine how it would look when complete. The "dart_editor.png" attachment shows how this looks in the dart editor. Many of the libraries are repeated in the project window, including "dart:core". Having this enumerated under every library is seriously just silly. Contrast this to the "komodo-ide.png" screenshot. Komodo doesn't recognize Dart syntax, has no highlighting or code completion, damnit, you know what the project structure is!

A simple directory-structure navigation and a sane library system for code organization (the current one is baffling and really needs to be documented, even if it's going to change) would go a long, long way for anything but the smallest projects. Of course, you might easily be tempted to go too far the other way. Eclipse barfs on anything but the most rigidly predictable, standard project set-up. As such, every single time I've tried to start using it (that is, several times), I wage war against it for an hour and then quit. Please don't go that far.

---

Attachments:
directory_structure.png (139.58 KB)
dart_editor.png (272.33 KB)
komodo-ide.png (277.90 KB)

[jwren]

Since Dart applications can pull in content from directories outside of a single directory (i.e. #source(''../../X.dart)) using Eclipse's project structure isn't an option since Eclipse projects consider only the contents of a single directory on disk part of a program.

The intention of the Libraries view was to show the logical structure of the program. Given this feedback, the Libraries view/ File navigation story is being re-visited and reimplemented.

I will update this ticket again when there is progress on this work.

---

Set owner to @jwren.

[jwren]

Added Usability label.

[danrubel]

Can you enable addition a directory in project?

Thank yiu
////////////////////////////////////////////////////////////////////////////////////
Editor Version: 4166

---

Changed the title to: "Enable folders in Editor (+3)".

[pq]

Set owner to @pq.

[pq]

Files and folders are now first class players in the editor (with the arrival of the new files view). Folders (that correspond to folders on disk) can now be created, removed and renamed as expected.

---

Added Fixed label.