|
I would have expected something along the lines of code submission with article submission but caught unawares, I now have an article with no source code.
"'Do what thou wilt...' is to bid Stars to shine, Vines to bear grapes, Water to seek its level; man is the only being in Nature that has striven to set himself at odds with himself."
—Aleister Crowley
|
|
|
|
|
Pack your code into a zip file (or two)...
Upload it just like you upload images...
Use the ' Add selected zip files to article' button, together with the checkbox next to your file to insert into your article a link to the code (probably at the top)...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
|
I'd like to be able to override the styles of various elements in my articles without having to do it in each one individually, via a <style>...</style> block. I really don't care for the way CP styles them.
".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
|
|
|
|
|
Sorry mate but a basic principle of CodeProject is we work hard to try and keep the styles across articles consistent. If we made it easy for authors to change styles then we'd have situations like this[^] and this[^]
Further, we need the flexibility to change the design occasionally and so we prefer that there actually be no styling (or the bare minimum) applied in to allow layout changes (eg responsive design).
If there are specific things you wish to have changed then let me know. Previously we've wrapped new elements into the overall design so everyone gets them.
cheers
Chris Maunder
|
|
|
|
|
Chris Maunder wrote: If we made it easy for authors to change styles then we'd have situations like this[^] and this[^]
LOL. Surely those two examples cannot be intentional? 
|
|
|
|
|
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
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
