> I've heard other platforms (not windows) were trying avoid depending
> on views
ah, scratch that.
--~--~-~--~~~---~--~~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.googl
> Sadly, chrome/common sounds generic enough that it's become a place to
> stash files. I'm not blameless - for some reason I put Animation
> there, when it clearly belongs in views/.
I've heard other platforms (not windows) were trying avoid depending
on views, but they definitely need animation
On Fri, Apr 24, 2009 at 10:19 PM, Brett Wilson wrote:
> On Fri, Apr 24, 2009 at 10:10 PM, Aaron Boodman wrote:
>> Is it possible to enforce these rules with code rather than capital letters?
>>
>> I don't think I've made this particular error, but it's something I
>> could see myself doing. From
Sadly, chrome/common sounds generic enough that it's become a place to
stash files. I'm not blameless - for some reason I put Animation
there, when it clearly belongs in views/.
Common's purpose is for files shared between two or more subdirs of
chrome where those subdirs are peers on the depende
On Fri, Apr 24, 2009 at 10:10 PM, Aaron Boodman wrote:
>
> Is it possible to enforce these rules with code rather than capital letters?
>
> I don't think I've made this particular error, but it's something I
> could see myself doing. From their names, "chrome/common" seems like a
> reasonable thi
Is it possible to enforce these rules with code rather than capital letters?
I don't think I've made this particular error, but it's something I
could see myself doing. From their names, "chrome/common" seems like a
reasonable thing to include from "chrome/views".
Just a thought. Don't we have s
