Re: TK LABEL WIDTH TO FIT IN TEXT AREA [id://1199162]
by Anonymous Monk on Sep 12, 2017 at 14:35 AEST
Re: TK LABEL WIDTH TO FIT IN TEXT AREA [id://1199161]
by Anonymous Monk on Sep 12, 2017 at 14:35 AEST
Just putting this out there to see if anyone else has experienced this.
I apologize for not putting more effort or detail in this. (In my defense, I was pretty ill and not thinking very clearly... yes, that is my poor excuse) I was using my Windows laptop which I seldom do,
and did not bother to fire up the Linux laptop that I normally use on a daily basis.
Wrong!This turns out to be a browser issue on the Windows laptop. I am still not clear what the issue is and need to explore a bit more. Following is as far as my foggy head has let me get:
(To be clear: This is not a huge issue, just an observation, and I am still foggy from the meds, so I hope I got this edit formatted fairly decently) Thank you to those who bothered to respond!
YourMother is correct. A/some .css and .js file(s) are no longer available from buzzfeed.org.uk, it seems the site is down...
Appears that buzzword.org.uk is back on line.... for anyone that cares...
...the majority is always wrong, and always the last to know about it...
A solution is nothing more than a clearly stated problem...
I'm not for certain, but it seems to me that some Monks magically appear on a thread if a specific topic is mentioned, or perhaps their uid is mentioned.
Can someone explain how this is accomplished (or at least tell me that it isn't happening, and I'm just imagining things)?
I mean, mention threads, and without fail, a major resident expert magically appears. Could be coincidence, but I'm not sure.
Question is, is there a way, without having to continuously re-roll the Perlmonks website scraping, to see if a username or phrase or something is published, to recognize this? I'm definitely no web expert, but I can work my way with JS/jQuery/CSS to a degree, but searching is usually required.
I am getting this message on one of my posts: "Some notes below your chosen depth have not been shown here". I go to the link and do not see anything about depth. It is probably there somewhere, but I don't see it. How do I set my chosen depth?
A couple of suggested changes. I propose that if a node not under considereation hits the same level of downvotes required to trigger auto reaping, the node content should be automatically hidden, a message displayed warning readers that it's quality/relevance is in question, a link would allow reading the original. Something along the lines of:
This node was taken out by the NodeReaper on Jul 16, 2017 at 09:42 BST
Reason: [NodeReaper] - Post contents hidden due to sufficiently negati
You may view the original node and the consideration vote tally.
I was a happy user of the #cbstream IRC ↔ PM client that makes the ChatterBox feel and behave like the IRC. But then sometimes broke (as it happened time to time), but ambrus hasn't been around for the last three weeks to fix it. So I wrote a simple ChatterBox reader myself. At the moment, it only reads, and I'm still not sure I want to add the ability to write to it. It uses the new CB XML ticker (as I skimmed over the other CB clients, they all seem to use the old one). If you want to use it, or just check the code, you can find it on GitHub.
<tr class="post-body post_body">
<ul><p>Fellow monks, could you try going to <a href="?node_id=1040">Pe
+rl Monks Discussion</a> and seeing if the following renders as actual
+ input boxes?</p>
<p>Because that is what is happening ...</p></input></input></ul>
The current link from SSCCE points to node # 1177743, which is a page containing only one thing: a link to node # 1177642 -- the page that actually describes what an SSCCE is. The handy syntax link is great, but could it be updated to point directly to the page? I don't really see the point of the intermediary page, and I fear that some newbs who click to it won't manage to click through to the real doc. Studies about page depth and retention show ... , etc. and the link doesn't exactly stand out.
Can we do away with the intermediary page and update the link?
The way forward always starts with a minimal test.
Since I made some mistakes in formatting, I then immediately went to change the formatting to what's below. When I hit the update button, nothing happens. It doesn't update and doesn't reload the page, but it does show the button was pressed. I'm using Firefox on Android.
I'll try again on a desktop computer, then report back.
The details of Modern Perl can be found in other reviews on PerlMonks. As it is freely available and anyone can look at the chapter descriptions, I won't review those here.
What I want to point out is the usefulness of this book for teaching best practices. The basic Perl part of the book isn't strictly necessary as this is covered in perlintro. However, many of the best practices cannot be found in perldoc or can't be found easily.
Such chapters as 2 and 7-12 are gold mines for best practices, many of which are difficult to find elsewhere unless searching specifically for them. Such things as the best community websites, Moose, style, exceptions, testing, warnings, reliability, security, idioms, things to avoid, and other tips are all considered in an uncluttered format, simple to understand and free to read (although you may want to donate on onyxneon.com).
Enjoy this modern, free, effective best practice guide.
The added text also appears at the end of the Cabalists’, Find Nodes, Settings, and Leftovers Nodelets.
The rendering problem is common to all the nodes in the thread, so presumably the arrow in the node title is the trigger? I see the problem on both Chrome and Firefox1, whether I’m logged in or viewing anonymously.