WestNIC provides reliable web hosting services
Fastwebhost offers cheap web hosting & reseller hosting services
This page is part of a searchable archive of the Code Style site log. Technical implementation notes that shed light on when, why and how the site has evolved since 2000.
Follow the latest entries to the site log.
Wrote an SQL query to count the total number of subscribers to the font survey email newsletters, and to list the addresses, each a union of 3 tables.
SELECT count(email) FROM submission
WHERE submission.notify = true
UNION
SELECT count(email) FROM archive_submission
WHERE archive_submission.notify = true
UNION
SELECT count(email) FROM notify
WHERE notify.notify = true;
SELECT email FROM submission
WHERE submission.notify = true
UNION
SELECT email from archive_submission
WHERE archive_submission.notify = true
UNION
SELECT email FROM notify
WHERE notify.notify = true;
Actions: Ask a question about this post, seek clarification or offer a correction.
Completed the One percent better manifesto article with bounty offer to reward suggestions for substantial improvements to the site. Added links to all relevant pages including the site map, section table of contents, Code Style subject index and home page.
Created a new CSS rule for h3 headings in bullet list items for the one percent better manifesto article, and added paragraphs in list items to the grouped selector for font-size: 100% to prevent compounding a smaller font size.
#Content ol li h3 {
font-size: 1.34em;
}
#Content ol li p
{
font-size: 100%;
}
Reverted the premium content service purchase scheme to a single one-off payment rather than an automated subscription. A significant number of subscribers had not understood the automated subscription scheme, which caused unnecessary alarm when the second annual payment was drawn. Despite efforts to highlight the subscription arrangement during the sign-up process and to forewarn subscribers of the renewal payment, the scheme was evidently unclear.
Doubled the price of a single year's premium content subscription to $40 to maintain an equivalent revenue level and increased the single FAQ by email option to $2.99. Added an ellipsis, …, and "premium content omitted" to premium content stub answers and updated all relevant calls to action and subscription forms. Also updated 401 error page that intercepts login failures with new prices.
Changed dashed line above premium content answer links to a solid 1 pixel grey line.
.Premium {
border-top: solid #ccc 1px;
}
Updated site log for 17 to 22 October.
Actions: Ask a question about this post, seek clarification or offer a correction.
Published 13 new FAQ answers covering Javascript and DOM, Java and JSP, HTML and CSS web fonts. The site now carries over 700 FAQs, of which 281 are only available to premium content service subscribers.
String and StringBuffer?
+ operator is not overloaded in Java!
Added a new Lighttpd friendly redirect for the FAQ announcement page, FAQs published on 22 October 2009 , and issued a Twitter feed update.
Actions: Ask a question about this post, seek clarification or offer a correction.
Created a Twitter feed landing page to introduce followers to one-to-one help sessions by instant messenger. Follow the feed and check direct messages for details.
Actions: Ask a question about this post, seek clarification or offer a correction.
Installed and ran the GUI version of the Java FindBugs tool on the Code Style code base and made an initial classification of the issues for priority action. No significant problems with core production code, most issues are to do with site management utilities and work in progress.
Actions: Ask a question about this post, seek clarification or offer a correction.
Latest: Build a better CSS font stack with our font survey results:
Archived survey submissions before 10 October 2006 to maintain rolling 3 year span.
Merged development current live site content into the development site path with exception of the Lighttpd configuration. Includes all changes to do with the reset grid redesign.
Archived site log July 2009 and site log August 2009.
Actions: Ask a question about this post, seek clarification or offer a correction.
Find technical implementation notes on all aspects of the Code Style site.
For a summary overview, see the final site log contents.