Differences between revisions 9 and 10
Revision 9 as of 2011-02-12 05:13:23
Size: 3829
Editor: GaganSekhon
Revision 10 as of 2011-02-12 05:13:54
Size: 1096
Editor: GaganSekhon
Deletions are marked like this. Additions are marked like this.
Line 16: Line 16:
= Moin2 CSS Style Guide =
Line 18: Line 17:
/!\ None of this is implemented yet, so it is easy to add your ideas now.

== Major changes in CSS from Moin 1.x. ==
 * use a browser reset (maybe: http://html5doctor.com/html-5-reset-stylesheet/ based on Eric Meyer's html4)
 * --(common.css, screen.css, print.css, and projection.css are combined into one file named moin2.css.)--
   * maybe later, maybe not at all
 * support for obsolete browsers will be removed from moin2.css; if we feel bad about this later we can add it back by continued use of a separate CSS file (msie.css) or use jQuery [[http://github.com/chrispatterson/jquery-super-selectors|super selector]] plugin.
   * IE 6, 7 and earlier
     * as of Aug 2010, IE6 has 16% market share and IE7 11% per http://marketshare.hitslink.com/browser-market-share.aspx?qprid=2
   * Firefox 1, 2
   * Opera 8 and earlier
   * Safari 3 and earlier
 * support for RTL languages will be removed from moin2.css; [[http://code.google.com/p/cssjanus/|cssjanus]] may be used to create a separate CSS file named moin2rtl.css.
 * most contributed themes and other distributed themes will load the unmodified base css files and a theme specific screen.css file.
   * not many themes will be interested in modifying print.css, projection.css, slideshow.css, or msie.css
   * loading base common.css will reduce theme maintenance due to changes in base and html
 * inclusion of jQuery plugins will sometimes add additional CSS files.
   * this creates the possibility of having naming collisions on classes and IDs
   * while we hope all plugin authors have the foresight to carefully name classes and IDs to avoid collisions, we have the same responsibility
   * the solution is to rename all classes and IDs to include a unique prefix, "moin-"

== Format of CSS rules ==

Use a dense, one-line style with comments or blank lines to separate unrelated items and create visual white space. Break long lists of attributes into multiple lines and indent the second line with four spaces. Lists of selectors with common attributes should be broken with new lines so selectors are always on the left margin.

Minimize the length of selectors to increase speed and simplify code:
 * https://developer.mozilla.org/en/Writing_Efficient_CSS (old, but well written)
 * http://code.google.com/speed/page-speed/docs/rendering.html

Use color names and 3 or 6 digit hex notation. Use shorthand notations as described here:
 * http://www.456bereastreet.com/archive/200502/efficient_css_with_shorthand_properties/
 * http://www.dustindiaz.com/css-shorthand/

Alphabetize lists of attributes. Use spaces to separate attributes and attribute names and values (e.g. spaces after : and ;``)

I used a Heuristic approach to narrow down the list of elliptic curves for which \rho_{2,E} is surjective mod 2 but not mod 4 or \rho_{2,E} is surjective mod 4 but not mod. 2not4or4not8v3.sage

The results of the above program for 2not4 curves is li4.sobj 2not4 output.txt

I have verified the results of 2not4 list, using a Galois approach, which involves compute the order of the Gal(Q(E[4])/Q). The program I used is 2not4galoisapproachv2.sage

The results of the above program for 4not8 curves is li8.sobj

I am working on verifying this result using the Galois approach.

.rcpagelink {width: 33%; }
.rceditor {font-size: 0.88em; white-space: nowrap; }

/* admonition start */
div.warning {background-color: #F9F9FF; border: 1pt solid #E5E5E5; color: black; 
    margin: 10pt 30pt; min-height: 64px; padding-right: 64px; }

GaganSekhon (last edited 2011-02-12 05:15:41 by GaganSekhon)