Community
Participate
Working Groups
Currently http://localhost:8080 redirects to navigate-table.html. We don't know about /file and if we try http://localhost:8080/file we get a cryptic error. The top-level page should welcome you to the Orion server, give the server version number, link to /file and /navigate-table.html, and give info on how to configure the server (eg org.eclipse.e4.webide.server.allowedPathPrefixes). /file should serve the directories under org.eclipse.e4.webide.server.allowedPathPrefixes.
Generalizing this bug for the general problem of what we put on our root landing page.
Once logged in, I could see this page doing things like: - if you have no projects, give you several big buttons to populate projects by: 1) generating content (at sites like initializr or HTML5 boilerplate) 2) importing content from a zip 3) pointing to a github URL 4) linking to your file system - also a list of recent projects I'm starting to wonder how useful a navigator view of "root" really is. We hide the notion of projects, yet there are "special actions" that only apply to root (such as link content) and others that cannot apply to root (link folder). So I could imagine the landing page as a place that organizes your "projects" or lets you easily create and populate new ones, and then when you decide where you want to work, you could have a navigator on that specific project.
Yes, a list of projects would be useful but this doesn't necessarily need to be the navigator. For example a list of projects sorted by most recently used or modified might be interesting.
(In reply to comment #3) > Yes, a list of projects would be useful but this doesn't necessarily need to be > the navigator. For example a list of projects sorted by most recently used or > modified might be interesting. That's exactly what I meant. We show the projects (and give links to create new ones in different ways) on the landing page, and use the navigator once that choice is made.
*** This bug has been marked as a duplicate of bug 343290 ***
