User:Mardus/sandbox

"Towards the five richest EU countries"

 * There was a sentence involving a 2007 election plank of the Reform Party in the article Economy of Estonia. I'd written some text and text and gathered enough sources, but ultimately decided to remove the original passage, and not to include the following stuff in the article, as the original passage pushed a non-neutral point of view (NNPOV).

In 2006, Andrus Ansip, then the Prime Minister and a member of the Estonian Reform Party, stated before the Riigikogu in an overview about EU politics an optimistic aspiration, that Estonia could set itself a goal of becoming one of the five richest EU members by GDP per capita.

In a 2007 election campaign for Parliament, the Reform Party made this their election plank, setting the target to 2022. To reach such a goal, Estonia's economy would have had to grow at least 8% every year, to which analysts and experts were more cautious (reported in a 2011 E24 article), and did not recommend such growth, as this would precipitate an economic boom and a painful recession.

This became a bone of contention to Reform's political archnemesis, the left-wing and largely pro-Russia Center Party, which quickly rushed for judgement: for years on end, the Centre and its members incessantly belittled both the Reform Party in general and Prime Minister Ansip in particular; resorting to bickering, ad hominem attacks and name-calling ('liars', 'charlatans').

Despite that, then-Prime Minister Ansip has remained optimistic; though in 2012, he adjusted his projection to Estonia reaching the levels of Finland by the target year of 2022.

The longevity of Android versions
Approximations based on this image: File:Android historical version distribution - vector.svg

Referring to liveblog posts

 * How to refer to each individual post in a liveblog, and the pros and cons of liveblogs in news outlets
 * In advanced liveblogs, each section is anchored, and the anchor is openly linked usually where the section timestamp is. Like this.
 * In less advanced liveblogs, an anchor can be looked up from the page source code.
 * In Firefox-based browsers, select the last (body) text of a section and the first (body) text of the next one, and select to view selection source from the context menu.
 * An alternate and more comfortable option is to use the DOM and style inspector in browser developer tools. I'll use Firefox and derivatives as an example. Developer tools can be opened in several ways:
 * with the F12 key, but this can open the most recently-accessed section of developer tools other than the DOM and style inspector, which one would then have to switch to.
 * using the program's menu. If you can't see the menubar in Firefox, press Alt or F10 keys, move to Tools &gt; Developer &gt; click on Inspector. Or press Ctrl+Shift+C on the keyboard. But these options would open the DOM and Style inspector at the top of page code, away from the liveblog.
 * The most comfortable part is to right-click on the section of a liveblog item for the context menu, and to click the "Inspect element" command. This opens the Style and DOM Inspector, and moves focus in the code view to the element that was right-clicked. Each subelement in the code is indented for better legibility. One can move up the code to find the element with an  or  . Hovering over each element in the code highlights said element in the viewport above.


 * Anything in code with an  (numbered or named) or   above a section containing body text of that (next) section can be accessed by using hyperlink fragments. These are marked with a hash # at the end of a URL in the address bar, or can be added by users: add the # sign, paste the contents inside the   or   parameters (without quotes), and press the Enter key. Test it out first.
 * Note, that liveblogs often refer to original articles and sources, so these can instead be referenced. The original sources would still be considered as primary. A liveblog of a reputable news outlet is also useful to confirm a tweet or a Facebook / social media post, because reputable news outlets exercise due diligence in confirming sources, and make a dedicated record of statements published via tweet or post on social media.

Timelines

 * User:Mardus/Timeline of 1990s sci-fi/fantasy television
 * User:Mardus/Free software support of older operating systems

Applying gradients to borders
Example 1. Some box content. Example 2 (simpler colour selections). Border width (length) is set to 300px instead of 100%.     Example 3. Blueish: . 45px left with black &amp; white at 113px; 49px left with black &amp; white at 112px;  above: inherited bgcolor rgba semitransparent; white border ending. Here: inherited bgcolor, transparent border ending.
 * A very basic tutorial

The use is somewhat different. In this example:
 * 1) Set
 * 2) * is the bottom border width (thickness) for Examples 1 and 2;
 * 3) *If bottom border length is in pixels, you might want to match it with box width. Otherwise, the pixel number can be arbitrary (as you like it), but to match box width automatically, set it to 100%; it will then rely on  or   (, if there is more content).
 * 4) *The arbitrary pixel number is interesting, because one can set a lesser length than the actual box length; In this case, the border starts from the left.
 * 5) Example 1:  &mdash; Note that here, the percentage width of each colour gradually increases in increments of 16.
 * 6) *Example 2, simple setting:  as you would when applying   to backgrounds.
 * 7) Example 3 with yellow and green borders makes it more interesting and more usable, as  is used in order to set the border just outside the box, whereas the set box size is 50px. In Examples 1 and 2, the borders would be rendered inside the box, and content positions in that box must be adjusted with paddings. The boxen are set with diagonal gradients , and the right-most box has   in the middle. Tip from here.





Border-bottom

These two examples are not very good, because the right and bottom borders appear to intersect with one another.    

Bluetooth profiles
09.02.2014

These explaining links with tooltips can be used in mobile phone infoboxen to include in a list of supported profiles:
 * A2DP, AVCTP, AVDTP , <abbr title="Audio/Video Remote Control Profile">AVRCP , <abbr title="Generic Audio/Video Distribution Profile">GAVDP , <abbr title="Hands-Free Profile">HFP 1.5, HID, <abbr title="Headset Profile">HSP , OBEX (OPP, <abbr title="Basic Printing Profile">BPP ) <abbr title="Personal Area Networking Profile">PAN , SPP

The list is not exhaustive, and can be added to. Links should be checked for redirects (important) every year or so, given that they don't change all that often. Used in Samsung SGH-i907.

Characters
O - Capital O &#xB0; - Degree &#x02DA; - Ring above

&#x2218; - Ring operator &#x229A; - Circled ring &#x25CB; - White circle &#x25CE; - Bullseye &#x25EF; - Large circle

Malaria
Promising new treatment:

Drugbox
The solution to long chemical notations is to introduce  into each very long field. This ensures that if the notation is longer than the width of the drugbox, its field will have a scrollbar. Another option I've considered is using a forced linebreak, but that might break the notation itself.

Experiments with syntaxhighlight
The problem with  tagging is that there is no programming language notation formatting that would best allow for a more visual representation of chemical notation.

And then I decided to create a more visual representation in step with programming language indentation:
 * SMILES:

1/C43H66N12O12S2/&#8203;c1-5-22(4)35-42(66)49-26(12-13-32(45)57)38(62)51-&#8203;29(17-33(46)58)39(63)53-&#8203;30(20-69-68-19-&#8203;25(44)36(60)50-&#8203;28(40(64)54-35)16-23-8-10-24(56)11-9-23)43(67)55-14-6-7-&#8203;31(55)41(65)52-&#8203;27(15-21(2)3)37(61)48-18-34(47)59/&#8203;h8-11,21-22,25-31,35,56H,5-7,12-20,44H2,1-4H3,(H2,45,57)&#8203;(H2,46,58)&#8203;(H2,47,59)&#8203;(H,48,61)&#8203;(H,49,66)&#8203;(H,50,60)&#8203;(H,51,62)&#8203;(H,52,65)&#8203;(H,53,63)&#8203;(H,54,64)/&#8203;t22-,25-,26-,27-,28-,29-,30-,31-,35-/m0/s1 1S/C43H66N12O12S2/&#8203;c1-5-22(4)35-42(66)49-26(12-13-32(45)57)38(62)51-&#8203;29(17-33(46)58)39(63)53-&#8203;30(20-69-68-19-&#8203;25(44)36(60)50-&#8203;28(40(64)54-35)16-23-8-10-24(56)11-9-23)43(67)55-14-6-7-&#8203;31(55)41(65)52-&#8203;27(15-21(2)3)37(61)48-18-34(47)59/&#8203;h8-11,21-22,25-31,35,56H,5-7,12-20,44H2,1-4H3,(H2,45,57)&#8203;(H2,46,58)&#8203;(H2,47,59)&#8203;(H,48,61)&#8203;(H,49,66)&#8203;(H,50,60)&#8203;(H,51,62)&#8203;(H,52,65)&#8203;(H,53,63)&#8203;(H,54,64)/&#8203;t22-,25-,26-,27-,28-,29-,30-,31-,35-/m0/s1
 * InChI:
 * StdInChI:

Siemens Mobile
Available via Internet Archive:
 * SG68 &mdash; Press release
 * SL75 &mdash; In German, via Internet Archive
 * SFG75 &mdash; In English

Android version history
On 15 September 2009, the Android 1.6 SDK – dubbed Donut – was released, based on Linux kernel 2.6.29. Included in the update were numerous new features: