aura, ash, chromeos

[Thiago Farina]

Hi,

Can someone help clarify what aura, ash, chromeos means in UI terms?

For aura we have:

src/ui/aura/ - aura::Window/RootWindow
src/chrome/browser/ui/aura - ?

For ash we have:

src/ash/ - Aura Shell, ok, that
means, at least on linux, that I get a normal gtk/X11 window, but
inside that I have *windows* for my *web* apps, a launcher, a system
tray, and a desktop background (customizable).
src/chrome/browser/ui/ash/ - What does that means? Is ash an UI?
src/chrome/browser/ui/views/ash - What does that means? Is ash under
views UI? No seriously, this is very confusing :/

For chromeos we have:

src/ash/system/chromeos/
src/base/chromeos/
src/chrome/browser/chromeos/ - This used to be linux_chromeos, the
fullscreen Window Manager on Linux, the OS was entirely inside the
browser. Not anymore the case.
src/chrome/browser/ui/webui/chromeos/
src/chrome/browser/ui/webui/options/chromeos/
src/chromeos/
src/webkit/chromeos/

If we could get an overview of what each directory is and what it can
contain and even possibly an README file describing those things that
would be awesome!

Yes, what I can't get yet is the difference between Ash and ChromeOS.
And this is becoming more and more confusing with the Views toolkit,
because of Aura, it means we can use views on Windows, Linux and
*where* ChromeOS or should I say Ash? If there is something we can do
to improve this confusion I would be happy to know.

Thanks!

--
Thiago

[Mike Frysinger]

https://groups.google.com/a/chromium.org/d/topic/chromium-dev/hjCJUQyJrvs/discussion

-mike

--
Thiago

--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
    http://groups.google.com/a/chromium.org/group/chromium-dev

[Thiago Farina]

On Sat, Nov 17, 2012 at 7:23 PM, Mike Frysinger <vap...@chromium.org> wrote:
> https://groups.google.com/a/chromium.org/d/topic/chromium-dev/hjCJUQyJrvs/discussion

This diagram (http://dev.chromium.org/developers/design-documents/aura/aura-and-shell-dependencies)
is great to explain the relationship between src/ui/aura,
src/ui/views, src/ash/, src/c/b/ui/views

But misses src/chromeos, src/c/b/chromeos, src/c/b/ui/ash,
src/c/b/ui/aura, src/c/b/ui/views/ash/

--
Thiago

[oshima]

chromeos/ is for chromeos specific stuff, such as communicating chromeos

services, or detecting and configuring displays. This component shouldn't and

doesn't depend on ui nor chromeos.

c/b/chromeos is similiar, chromeos specific stuff, but needs to be chrome/browser due to

dependency (such as profile or BrowserThread). There is an effort to reduce the dependency,

and this is expected to shrink as they move to either ash/ or chromeos/

Other directories can be interpreted in the same way. c/b/ui/ash is there because it has dependency

to chrome, but they doesn't have dependency to views, and so forth. That's being said, not all

files meet this criteria. It could be regit (be in the same dir as related files that have dependency),

,refactoring removed the dependency from the file, or could be simply misplaced from the beginning.

If you find such files, please feel free to fix it, but make sure you consult with owners first.

- oshima