[Webkit-unassigned] [Bug 32773] [check-webkit-style] Create a "styles" folder in Scripts/modules

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=32773





--- Comment #11 from Chris Jerdonek <chris.jerdonek at gmail.com>  2009-12-19 13:56:38 PST ---
(In reply to comment #1)
> We could also consider just making [the style folder] a peer of 
> modules instead of inside modules.

(And comment #5)
> Adam and I as recently as last night we discussing breaking some 
> of the modules in modules/ out into separate or sub-modules.

After thinking about this, it seems like it might be better to keep all of the
"library" python code under a single folder (but grouped into subfolders and
packages) -- as opposed to having some of it be in siblings of the modules
folder.

This would make it easier to locate and reference other python modules.  It
also keeps the top level Scripts folder cleaner and easier to navigate.  Since
the Scripts folder contains the scripts executed by the end-user, people might
be browsing its contents:

http://webkit.org/coding/scripts.html

Are there any reasons we might want to have multiple folders of python code in
the top level of the Scripts folder?

(In reply to comment #1)
> modules probably needs a better name.

What are some of the names you were considering?  I'm starting to think maybe
we can call it pywebkit, or simply webkit.  Then from a top-level script, you
could write, for example--

import webkit.style.checker
import webkit.scm....

Finally, a couple questions just to clarify:

In terms of restructuring, I assume it's safe to say we want to continue
storing all of the end-user scripts in a single folder?

Are any of the scripts currently in the top level Scripts folder not meant to
be executed by a human being (i.e. meant more to be called from other scripts)?

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.