|
These are the modifications I wanted to make:
<style>
body, p, h1, h2, h3, h4, h5, h6, li, tr, td, th, dd, dt {font-size: 14px;}
h1, h2, h3, h4, h5, h6 {color: #f90;}
h1 {font-size: 200%;font-weight: 600;}
h2 {font-size: 180%;font-weight: 400;}
h3 {font-size: 160%;font-weight: 400;}
h4 {font-size: 140%;font-weight: 200;}
h5 {font-size: 120%;font-weight: 200;}
h6 {font-size: 100%;font-weight: 200;}
img {border: 1px solid black;max-width: 640px;}
a {font-weight: 600;}
span.this_article {color: #f90;font-style: italic;font-weight: 600;}
</style>
My reasoning - it would be more appropriate to set the pixel height of the font in the first style element (or the body element), and in subsequent elements (for header text), set the height as a percentage of that height. It worked out really well when I was writing my articles.
I also wanted all of the headers to be the same color.
I like a 1-pixel border around my images.
If you go back and look at my recent SQLXAgent article, you'll see the intended results of the this_article class. I think the use of the Segoi font face kinda washes out the hyper links color, especially since you have underscore decoration turned off for links.
Mind you, these are just opinions, and like I said, I understand why you don't allow us to add styles like I showed above.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
modified 3-Oct-17 8:40am.
|
|
|
|
|
Relative font sizing isn't a tweak - it's something we just need to do.
Font-weights will probably get a tweak in the near future. Segoe UI lightweight is kinda 2013.. However, I'm not at all keen on making links different font-weight.
this_Article: The whole linked-article thing needs proper infrastructure (similar to multi-page articles we discussed)
Image borders? Lots of images are best left unbordered. If you want borders then add the border class to the image tag.
cheers
Chris Maunder
|
|
|
|
|
Chris Maunder wrote:
Image borders? Lots of images are best left unbordered. If you want borders then add the border class to the image tag.
Or have a border as part of the image. I think I've done that in the past.
|
|
|
|
|
You'll get scaling artefacts doing that.
cheers
Chris Maunder
|
|
|
|
|
Chris Maunder wrote: Image borders? Lots of images are best left unbordered. If you want borders then add the border class to the image tag.
That was the whole point of me trying to define a style tag.
Maybe let high-rep users do it with a minimum number of articles posted?
".45 ACP - because shooting twice is just silly" - JSOP, 2010
- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Did you forget this[^] ?
Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning
|
|
|
|
|
Wow. That's rude. I'm kinda surprised they haven't removed the offending markup.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
John Simmons / outlaw programmer wrote: That's rude
I'd rather consider it an advertisement.
Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning
|
|
|
|
|
It's mostly harmless though.
|
|
|
|
|
Harmless or not...
More or less, I only want to tidy up the headers. He stepped way outside the box...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
|
|
I've gone in and removed your report.
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|
Thank you Sean!
|
|
|
|
|
I stumbled across this facebook page. It contains links to at least the 20 most recent CodeProject articles (even posted as recently as this morning).
FuseTeam PS
Is this kosher?
".45 ACP - because shooting twice is just silly" - JSOP, 2010
- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
They are possibly consuming an RSS feed and auto posting to Facebook. I can't see anything bad about people linking to this site - it's not as if they ripped the contents and re-hosted elsewhere.
|
|
|
|
|
John Simmons / outlaw programmer wrote: Is this kosher?
Absolutely. The more the merrier!
cheers
Chris Maunder
|
|
|
|
|
I posted an "alternative article" about a half hour ago, and it's not yet shown up in my rep points. I don't know if there's a problem, or if the system is just taking its sweet time in processing it.
This is the article Custom exceptions without constructor tedium (an alternative)
".45 ACP - because shooting twice is just silly" - JSOP, 2010
- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
modified 1-Oct-17 11:19am.
|
|
|
|
|
Looks like a bug. Points still aren't showing up.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
It's a bug. We're going to start working on a solid solution to this issue this week.
cheers
Chris Maunder
|
|
|
|
|
I was sent a message for sign-in email address confirmation containing this line:
Click here: https://www.codeprojectcom/script/Membership/ConfirmEmail.aspx?tg=[removed by Ed]
to confirm that this is your email address.
There is no dot between the domain name and com, so the link didn't work.
|
|
|
|
|
It would be nice if we could sort our articles on the criteria we select (without regard for what section they are in), such as:
- Alphabetically
- Date published (low to high, or high to low)
- Popularity (low to high, or high to low)
- Score (low to high, or high to low)
etc...
Of course, this would also be carried over to Tips...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
|
The one way I can clearly reproduce is posting and article with TOC in the form:
<p>
<div class="toc">
<ul>
<li>...</li>
<!--
</ul>
</div>
</p>
Is it wrong? In this case, submission process adds empty paragraphs before and after this fragment:
<p> </p>
These empty paragraphs are, unfortunately, well visible, because the content of these paragraphs is a non-breakable space. (Implementing of formatting side effects via using of such special characters is usually described as discouraged technique.)
Thank you.
—SASergey A Kryukov
|
|
|
|
|
Before you click the Publish button, try checking the box "I'm an expert - don't mess with my HTML" (or something to that effect).
".45 ACP - because shooting twice is just silly" - JSOP, 2010
- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|