Bugs and Suggestions

Coral module on docker needs curl

5-Nov-23 10:15

Yes, I saw that the other day and was about to dig in but it looks like a caching issue that's resolved.

Thanks for letting me know.

cheers
Chris Maunder

VavoVavo1-Nov-23 12:01

VavoVavo

1-Nov-23 12:01

Please add curl in the docker container as it is needed by the install script for the coral module

Re: Coral module on docker needs curl

Richard Deeming1-Nov-23 23:36

Has the articles’ layout been modified?

1-Nov-23 23:36

You have posted this in the forum for reporting bugs and suggestions for the CodeProject website. As such, your message makes no sense.

If your message relates to a specific article, then post it in the comments section at the bottom of that article.

If it relates to the CodeProject API, then post it in the CodeProject API forum[^].

"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer

FredAu29-Oct-23 0:41

FredAu

29-Oct-23 0:41

In the past few weeks the articles’ layout looks slightly different; before there were additional information and quick access links on the Articles left-hand side pane, now there are only three links.
No comments have been posted in this regard except a reference about “articles rating graph not working properly” about the same time I noticed this discrepancy.

Below there is a a image of ‘Before’ i.e. how the articles were laid out (borrowed from one of the forum answers) and an ‘After’ image of the same article i.e. current layout. Red arrows pointing to the pane in question.

All articles show the same behavior.

Current environs: Win10 - tried with both Edge and Google as well as a portable Firefox browser - identical results.

BEFORE

AFTER

Chris Maunder30-Oct-23 4:30

30-Oct-23 4:30

Yes, the layout has changed

cheers
Chris Maunder

Jo_vb.net30-Oct-23 7:21

Jo_vb.net

30-Oct-23 7:21

If this is by design then I think it was a bad decision to remove the link for jumping to the comments Thumbs Down | :thumbsdown:

Chris Maunder30-Nov-23 6:20

30-Nov-23 6:20

It's still there

cheers
Chris Maunder

Richard Deeming30-Nov-23 22:47

30-Nov-23 22:47

Ah, the good old design trick of replacing text labels that users don't read with tiny icons that users don't understand. Laugh | :laugh:

"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer

Chris Maunder1-Dec-23 4:54

A question for 'Technical Blog' publishing

1-Dec-23 4:54

Exactly!

cheers
Chris Maunder

0x01AA28-Oct-23 8:32

0x01AA

28-Oct-23 8:32

A lot of time when somebody tries to publish a 'Technical Blog' I see a lot of times members who vote 'Format / Layout issues'.

My experience is, that the blogger has little/no influence how blogs will be published finally on CP. Therefore 'Format / Layout issues' makes no sense in that case?

Is this correct or not?

Example: Enable syntax highlighting in Nano for Java Server Pages (JSP)[^]

RedDk28-Oct-23 8:56

RedDk

28-Oct-23 8:56

"Format/Layout issues" is directed at voting members. Seeing what has happened to a post as a cpian arrives at it, without reading the entire text of the thing, recreates the bias with which an opinionated editor last edited a post and in that recollection, he is better able to adjust his old attitude towards the usual detritus, ignoring it, and form a new perspective. In effect continuing his reading and therefore his objectivity.

Example:

I see a bunch of lowercase "i" peppering the question. And I categorically downvote the post without leaving any explanation at all as to why it deserved downvoting. If this guy doesn't care enough to appeal to my general sense of what's good in this world, neither do I.

As for reading the peppered post in it's entirety? Fagettaboutit!

modified 30-Oct-23 10:01am.

0x01AA28-Oct-23 10:10

0x01AA

28-Oct-23 10:10

What? Sorry I'm not native English. Please keep it simple for me Wink | ;)

modified 28-Oct-23 15:20pm.

RedDk28-Oct-23 10:26

RedDk

28-Oct-23 10:26

... nothing Thumbs Up | :thumbsup:

I suppose I was just venting my frustrations while pouring over evaluation software as the deadline to purchase quickly approaches. Smile | :)

Richard Deeming30-Oct-23 0:11

30-Oct-23 0:11

I think it's reasonable - it's a flag to notify the editors that the post requires some help, not a "go away, we don't want your sort here" kick to close the post. Smile | :)

"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer

Sean Ewington30-Oct-23 6:18

Sean Ewington

30-Oct-23 6:18

Reporting Format / Layout issues is A-OK, because it sends a clear message to the CodeProject editors what needs to fixed.

Thanks,
Sean Ewington
CodeProject

Code block line numbers

Richard Deeming27-Oct-23 5:42

Re: Code block line numbers

27-Oct-23 5:42

It is currently possible to add line numbers to a code block by adding the linecount="on" attribute to the <pre> element.

  1  Line 1
  2  Line 2
  3  Line 3

These line numbers are inserted directly into the rendered HTML:

HTML

<span class="code-linenumber">  1  </span>Line 1
<span class="code-linenumber">  2  </span>Line 2
<span class="code-linenumber">  3  </span>Line 3

As a result, if you try to select part of the code block to copy, you end up including the line numbers:

The only option is to use the "copy" icon at the top of the script block to copy the entire block without line numbers, then use a text editor to trim it down to just the part you wanted to copy.

If instead you added the line numbers using the ::before pseudo-element[^], they would not be selectable. You would be able to select and copy any part of the code block without including the line numbers. And the "copy" script wouldn't need to strip the line numbers out.

You could even use CSS counters[^] to automatically generate the line numbers. Smile | :)

For example:

HTML

<pre data-linecount="True" style="--line-start:10;--line-increment:10;"><span class="code-linenumber"></span>Line 1
<span class="code-linenumber"></span>Line 2
<span class="code-linenumber"></span>Line 3
</pre>

CSS

pre[data-linecount="True"]{
    --line-initial: calc(var(--line-start, 1) - var(--line-increment, 1));
    counter-reset: line-number var(--line-initial, 0);
    
    /*
     Throw in some gratuitous CSS Nesting, now that it's widely supported:
     https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_nesting/Using_CSS_nesting
    */
    & .code-linenumber::before {
        counter-increment: line-number var(--line-increment, 1);
        content: counter(line-number);
        display: inline-block;
        text-align: right;
        width: 2em;
        margin-right: .5em;
        opacity: 0.5;
    }
}

Demo[^]

The only potential issue would be determining an appropriate width for the line number element, so that it doesn't push short blocks over too far, but leaves enough room for the occasional massive wall-o-text code dump.

"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer

Chris Maunder27-Oct-23 5:50

Minor niggle: message column alignment issues

27-Oct-23 5:50

Oh, that's nice!

cheers
Chris Maunder

Richard Deeming27-Oct-23 4:42

Re: Minor niggle: message column alignment issues

27-Oct-23 4:42

Am I the only one who's noticed this? Smile | :)

Because each message is its own nested <table>, and they don't use table-layout:fixed, the "columns" don't quite line up properly.

It seems to be related to the ~~message subject~~ message timestamp rather than the user; you can see in that screenshot two threads started by Griff which don't line up with each other.

Firefox v119
Fluid layout
Document width 1849
Display 3840×2160 scaled to 175%

"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer

modified 27-Oct-23 10:14am.

Chris Maunder27-Oct-23 5:51