|
Same for me. If CP is staying on that decision, I will not post anymore 3rd party controls article here from now. Also assuming that, those previous articles will not delete from here.
One more query to Chris, what if anyone feed a blog post which says about 3rd party controls? Will that case be taken care too?
|
|
|
|
|
Blog articles must also follow the submission guidelines.
I know this is difficult and frustrating so thanks for being supportive and understanding. We wish the world worked differently some days.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
It's a bad day for me that some of my articles have been removed because of that issue. I obey the rules of CP and can't do anything more for that. I will ensure that, I will not post any article on 3rd party controls from now. Have no other choice than that.
Will request my readers to follow my blog in such case.
|
|
|
|
|
Sorry for waking up the sleeping dog But at least CP is fair to the community...
Christian Kleinheinz
From Visions to Solutions
MasterSoft
|
|
|
|
|
|
Waking up the dog again?
Anyway, anyone who is interested in the RadMessageBox article can find the article here[^].
I will publish articles about 3rd party libs there.
@Chris: Is it ok when I do add the link to my personal CP blog?
Christian Kleinheinz
From Visions to Solutions
MasterSoft
|
|
|
|
|
Hi Kunal,
I have gone through and removed the articles on the list that require third party components.
Unfortunately until we can think of a system that considers and effectively deals with every possibility no article that directly requires third party components can remain. If you or other members find any more, please let us know.
The ideal is to allow and reward authors like yourself who only seek to help other developers with coding problems, but as previously discussed it is a tricky proposition that we do not have a solution for 'yet.'
Thanks,
Sean Ewington
The Code Project
|
|
|
|
|
|
I reckon I can fix that
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Thx for the fast response and the articles re-activation
cy
Christian Kleinheinz
From Visions to Solutions
MasterSoft
|
|
|
|
|
I just posted a comment with some HTML, and it actually treated it as HTML rather than encoding it. I'm guessing this behavior is intentional, although it was not expected. I had no way of knowing that the HTML would not be encoded as it used to be. Perhaps it's time comments got previews? Or maybe not... it was easy enough to edit my comment after I posted it to correct it.
|
|
|
|
|
And comments need to be very serious, only Asian smiles are allowed.
(o.o)
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
|
|
|
|
|
Luc Pattyn wrote: (o.o)
Woah!
|
|
|
|
|
I'm afraid you misread...
(@_@)
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
|
|
|
|
|
First you guys don't want HTML, then you do, then it's all bad. Sheesh!
How about a "Encode HTML tags" checkbox?
Or better still: A check box with whatever wording you feel is best.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Chris Maunder wrote: A check box with whatever wording you feel is best. My choice: [] Do what I want, dammit!
|
|
|
|
|
The System.MindReading namespace is still in beta and heard the GetUserWishes(DateTime.Now) is unstable due to constant and unpredictable changes in sampling data. I think the biggest problem they are having is getting consistent, non-conflicting and repeatable data.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Sir, we don't need The System.MindReading namespace nor the GetUserWishes(DateTime.Now) we just want to stop using < and her sister >.
is this a dreem, sir.
Help people,so poeple can help you.
|
|
|
|
|
So then what about those who asked to be allowed to include links? Or bold?
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
don't listen to them.
Help people,so poeple can help you.
|
|
|
|
|
As a consequence of another thread (two down from here) I decided to update my TT on PRE tags. only to (re)discover a bunch of issues which I will list shortly:
1. title length checks, just silly.
2. vertical spacing seems arbitrary; how can I get the first paragraph closer to its title, and consistently so?
3. HTML tags inside PRE: bold "works" and is hardly noticeable, italics does nothing, underline shows its tags. This has been better before.
4. without lang="text" even the HTML-escape snippet would show odd coloring for no apparent reason.
5. forums show some icon next to the author, Q&A lists total rep points, however articles and TT don't do any such thing, just a plain author name. why?
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
|
|
|
|
|
Luc Pattyn wrote: underline shows its tags
I see you beat me to this.
|
|
|
|
|
Yeah, I've been called Greased Lightning earlier today.
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
|
|
|
|
|
Luc Pattyn wrote: 1. title length checks, just silly.
Allowing single word or pointlessly short questions: automatically avoidable. You've put me on notice enough times saying I should do more automated checks and balances of input and I think this falls squarely into that realm. I am, however, open to adjusting the limits, but I stand by the opinion that yes, it's simple to craft a very small title or question, but that it is just as easy and usually more valuable to be more descriptive.
In your "Using PRE tags" tip the title suggests to me a tip about using PRE tags in HTML. It's actually a tip about using PRE tags in CodeProject content so I would call it "Using PRE tags in questions and articles". It would certainly satisfy those who continually push for the wording on the site to be more accurate and descriptive.
Luc Pattyn wrote: vertical spacing seems arbitrary; how can I get the first paragraph closer to its title, and consistently so?
The first paragraph is separated from the title by the abstract line and then the list of attrbiutes. You've added what looks like most of the main attributes to your "Using PRE Tags" tip which means when you shrink/expand your browser that line of attributes may wrap and drop the first paragraph down even more.
How about trimming the list of attributes to something reasonable? Or even just having the tags "CodeProject" and "Formatting" for example.
Luc Pattyn wrote: HTML tags inside PRE: bold "works" and is hardly noticeable, italics does nothing, underline shows its tags. This has been better before.
Bold hasn't changed in years and italics are certainly working for me (and again, haven't changed). It's the nature of the courier font that we've used since day one. I can't remember a time we supported underline. We have always reserved the underline decoration for hyperlinks.
[Edit: I've added in support for underlines. I can see bold really well on all my monitors, but if you're having problems maybe so are others so this will give you another option]
Luc Pattyn wrote: without lang="text" even the HTML-escape snippet would show odd coloring for no apparent reason.
You mean the block starting with <pre lang='cs'...?
Think what you're asking the colouriser to do: Do you want it to colourise the C# code, or the HTML tags? It can't do both because there's no syntax in practice that would ask for this. My best suggestion is to set the lang='html' and do something like
<pre lang='cs'> <!--
private static int multiply(int arg1, int arg2) {
return arg1*arg2;
}
</pre> <!--
Although I am guessing this isn't what you're after. Alternatively I could add the option to use a <span class='no-colour'>...</span> to give you the ability to uncolour parts of the PRE text.
[Edit: adding "no-color" and "no-colour" now.]
Luc Pattyn wrote: forums show some icon next to the author, Q&A lists total rep points, however articles and TT don't do any such thing, just a plain author name. why?
That's just the way the lists of those items evolved independently. I do have a task in the list to make these consistent.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
1.
yes I will lengthen that title next time, not for the reasons you envision though. If "CP Vanity" had to change it would loose part of its appeal IMO. The silly things are (1) your checks are inconsistent (new stuff versus edited stuff) and (2) your checks can be fooled as I have proven again today. Anyway I feel confined by whatever minimum length you impose.
2.
I have complained about vertical layout aspects over the years, just take a look at any article, TT, whatever and look for the rhythm of the white space, it ain't right. What I am referring to today is the amount of white space between every title (mostly h2 tags in this instance) and the first paragraph that follows as well as the last paragraph that precedes it. It should be something like 2.5 (before) and 1.5 (after) times the normal line distance, so the new header goes with the text that follows, not the text that precedes it, without wasting too much. As it is it is more the opposite, and not constant. I also have the impression preview and final view are different here.
Side note: I just discovered different heading levels in articles create different colors now (orange and blue); and TT header colors (blackish) differ from article colors. It is all getting pretty ugly.
3.
Look at my TT on PRE tags, where I explain italics and underline, italics doesn't work, and underline shows its tags. Tried FF 3.6.15, IE7 and Chrome 10. Do you see anything italicized or underlined where I explain them? My examples are failing.
4.
The snippet explaining how to escape <>& now has lang="text"; if you remove that it becomes a mixture of black, red and blue without any logic I can imagine. Like so:
< <
> >
& &
I wish the default had been lang="text" everywhere unless the context indicates otherwise (as in C# forum, or reliably sniffed). I know you can't just change the default, unless you also change all existing database content! Maybe a new command that allows to set the default would be nice, <prelang="xyz"> which would set lang="xyz" for all PRE blocks that follow. Then I could fix all PRE blocks in one step.
BTW: You will have noticed I am limiting the number (and length) of my posts in S&B as I'm not impressed by their effectiveness; CP is running in circles too much to my liking.
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
|
|
|
|