|
Chris Maunder wrote: if only the outlook team would fix their bug.
I do like a man with a sense of humour! 
You looking for sympathy?
You'll find it in the dictionary, between sympathomimetic and sympatric
(Page 1788, if it helps)
|
|
|
|
|
MY fault is that I'm often overly optimistic.
(But the issue's now officially fixed.)
cheers
Chris Maunder
|
|
|
|
|
There is a textbox in the Unsubscribe page between the "Update my subscription" and Orange footer (in the blank white space). It may not be visible, but if you select the whole page (ctrl+A) then the textbox can be seen.
The text box can be very confusing as, people might fill it but it does not do anything.
Thank you.
|
|
|
|
|
I have been writing all my new articles and blog posts in Markdown recently, and I have noticed an error in the way codeproject renders the HTML from markdown.
Any code block in markdown is rendered with a <code> element INSIDE a <pre> element, usually with attributes like <code lang="csharp"> or something. I have tried three different Markdown-to-HTML converters, each with slightly different output, but all of them do this. The problem is that CodeProject renders the <code> tag literally. The opening tag is shown on-screen but the closing tag is hidden. You can see this on my recent blog posts like this one:
Blogging on GitHub[^]
This gets vastly worse if the <pre> tag already contains syntax highlighting. For example see Building a table of contents in Javascript[^] or How to export a blogspot blog to HTML/GitHub with C#[^]
P.S. Ctrl+Z is broken when editing article HTML.
|
|
|
|
|
From the W3C page[^]:
Quote: Preformatted text between the start and end PRE tag is rendered using a fixed with font, in addition whitespace characters are treated literally. The spacing and line breaks are rendered directly, unlike other elements, for which repeated whitespace chararacters are collapsed to a single space character and line breaks introduced automatically.
There are two schools of thought on PRE tags
1. Text inside a PRE tag is pre-formatted. Keep it simple. There's no need to use superfluous decoration.
2. (The semantic argument) PRE says "maintain whitepace formatting" and CPDE says "this is code". The two should go together. Except (in my view) your mixing semantic HTML with formatting HTML which in some minds is a bad thing.
Really, what we should have is <div class="code">
What we're doing isn't "wrong". It's just how we do it in order to keep things simple. the issue we came across with code snippets in PRE tags was that authors often forgot to HTML encode tags in snippets (eg snippets of HTML) and so we instituted a policy of auto-encoding all HTML tags inside PRE blocks, with a few exceptions such as B,I,U and SPAN (to allow emphasis).
cheers
Chris Maunder
|
|
|
|
|
Well, some things to consider:
- Shouldn't the "Expert mode: Don't mess with my HTML formatting" option prevent this behavior (I just checked: it doesn't)?
- A technical blog has already been published in its final HTML form and presumably the author has reviewed the result. Reprocessing the HTML a second time doesn't make sense.
- OTOH, for article editing, the current behavior is confusing because the rich-text HTML editor hides the <code> element and any other elements inside a <pre> element, but the published version shows such elements.
- As I noted, the reprocessing performed by CodeProject evidently doesn't do what it was intended to do: the initial <code> tag is reencoded as <code> but the closing </code> tag is deleted instead.
|
|
|
|
|
Hi,
I would find it excellent if notification where cleared when you navigate to a page via alternate means (Not via notifications) such as via the points screen or through the answers section.
Thoughts?
|
|
|
|
|
The problem is that some things are hard to judge as being read. A forum message, for instance, may not be read even if you visit the page the message is on.
I get your point though, and yes it would be nice to come up with a simple solution.
cheers
Chris Maunder
|
|
|
|
|
Was in lounge. Clicked in search edit. The edit control jumped up an inch or so. This was on Firefox 28. Did the same thing in the latest Chrome and IE 11.
|
|
|
|
|
Oh yeah. Oops!
I fixed that a while back but clearly haven't rolled in the changes. Give me a few minutes and I'll get it sorted.
cheers
Chris Maunder
|
|
|
|
|
I wonder how to pick up "old" subjects best?
Recently I stumbled upon the "Alternatives" feature and searched the discussion board first.
I found a matching thread "Add existing article as an alternative" and posted my addition.
But I assume nobody will ever read it since it is deeply buried in the discussion board, is it?
|
|
|
|
|
There isn't any good way to do this other than voting an item marked as accepted, added to TOD or In Progress up.
The reason is that if we added a simple way to bump items, we'd have a bump war. It's be scary.
In any case, that item you replied to was marked "fixed" but I've changed that to "Added to TODO" because it's not actually been fixed. It's on the list. It'll get done.
In the meantime I'm happy to manually associate articles together if you need.
cheers
Chris Maunder
|
|
|
|
|
How about adding a sort by date feature on each board, to see the latest contributions by message and not by thread?
|
|
|
|
|
That would help for those who choose to sort by date, but the default sort (which most people use) would remain.
How many people would actively sort by date in order to see which threads had the last activity?
I'm just not sure how this would provide a general solution to the issue.
cheers
Chris Maunder
|
|
|
|
|
Well, I assume there is no general solution to the issue.
I have no idea either, how many would use it.
But at least CP staff could use it to find "reopened" issues on the bugs/suggestion board.
Anyway, if it is intended to start a new discussion for additions to "old" issues i'm fine with that.
|
|
|
|
|
Re=opening closed items is a good use case actually.
I will ponder. You raise some good points.
cheers
Chris Maunder
|
|
|
|
|
I think of using the CodeProject Open License on my code on GitHub, but I am a bit confused about section 3b and 3c, hence I ask this question:
Can other people:
- fork my code
- make modifications (improvements, bug fixes, new features ...) and push them
- and pull request them if they want?
The quick red ProgramFOX jumps right over the Lazy<Dog>.
|
|
|
|
|
Yes they can.
This raises (re-raises) an issue that we've been discussing internally for a while now: CPOL v.Next.
The CPOL is designed specifically to protect authors while allowing as wide a usage as possible. It has IP and patent clauses, distinctions between your code and your article, and specifically states jurisdiction. It's the fully packed, ticked-all-the-boxes license.
However, it has clauses (eg 3c) that simply don't suit some people so we're looking to provide an updated, more relaxed, less high-string version. Use the CPOL now and then update to the new license if you wish in the future.
cheers
Chris Maunder
|
|
|
|
|
Ok, thanks for answering!
The quick red ProgramFOX jumps right over the Lazy<Dog>.
|
|
|
|
|
I must say, I like the CPOL, and... altough it is very well explained, some points are still a bit obscure/difficult for a not english native as me.
Would it be feasible to add a "side note for dummies" with a brief plain-english explanation of the difficult points of the licenses?
I think many users would appreciate that and probably have less problems to choose the one that fits best their desires.
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Yes. Definitely.
cheers
Chris Maunder
|
|
|
|
|
Thanks Chris 
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
One more question, is there an exact definition of "prominent notice in each changed file stating how, when and where You changed that file.", or is that up to the author? For me, a Git diff is enough for this, but this might be in contradiction with the license.
The quick red ProgramFOX jumps right over the Lazy<Dog>.
|
|
|
|
|
It's extremely painful to try and provide an exact definition. The overriding principle here would be "what's acceptable to a reasonable person".
cheers
Chris Maunder
|
|
|
|
|
Alright, thanks!
The quick red ProgramFOX jumps right over the Lazy<Dog>.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
