Michael Bøgballe (2,395 views)

[centrifuge]

One pressing issue, I don't know how to effectively replace the old version with somebody else's new version without messing up the code. For example, the image disappeared, so I had to reupload it. It became small again. Another thing is the vocal summary outright disappearing, and questionable notes no longer listed as such, just being considered a spoiler.

I'm no good at the coding, so I don't know how to fix these things.

[Anacrusis]

Feb 12, 2022 21:02:32 GMT centrifuge said:

One pressing issue, I don't know how to effectively replace the old version with somebody else's new version without messing up the code. For example, the image disappeared, so I had to reupload it. It became small again. Another thing is the vocal summary outright disappearing, and questionable notes no longer listed as such, just being considered a spoiler.

I'm no good at the coding, so I don't know how to fix these things.

First, I wanna say your thread's looking pretty good so far! It's coming together very nicely. Keep up the good work!

Also, I'm not sure how much I could help, but hopefully, I could offer a few pointers that might clear up some of the questions you have with code:

- First, in the code editor, if you haven't already done so, try switching over to the "BBCode" window, whose button is next to the "Preview" window's button near the bottom. This is where I make all of my edits in my threads since it facilitates certain changes (like resizing images and text) and since moving between "Preview" and "BBCode" is known to cause a rendering bug, whereby certain features (eg. spoiler labels and note links/URL's) become chopped up or misplaced sometimes.

- For resizing your OP image, in the "BBCode" window, locate the "img" HTML tag near the top of the code (this is your OP image) and try inserting the attribute style="width:____;" inside the tag ... I've highlighted an example in the code screenshot at the bottom of my comment. This style=width attribute allows you to resize an image pretty easily. In my example, I've shrunk the original image by putting 30% between the colon and the semi-colon, but you could also insert a percentage above 100 in order to enlarge the image. Height, though not mentioned in the code itself, will follow automatically.

- For the Vocal Summary, make sure your HTML/BBCode there follows the format of...

'opening spoiler tag' {Vocal Summary} body of text 'ending spoiler tag' , in which opening spoiler tag is "spoiler" in braces and the ending tag is the same thing but with a forward slash / right before the word "spoiler". I'd type it out here, but that might put an actual spoiler in my comment, lol. I've also included an example for this in that first screenshot below, and I highlighted the HTML tags I'm referring to, with the body of the example spoiler placed in between the tags.

- For your Questionable Notes section, I think the same thing pretty much applies. It's just a matter of making sure all the spoilered text goes in between the right tags and that the tags themselves are done just right. Although, this section is naturally trickier than the Vocal Summary since there's more stuff going on between the tags. If it helps, I've included another screenshot below with an example Questionable Notes section.

- One last general suggestion I have has to do with re-configuring the editor itself. I'm not sure what the general consensus is on TRP, but personally, I've found that coding goes much, much smoother for me if the editor is set to open on the "BBCode" window by default. And then, I never flip over to "Preview" at all. As I mentioned before, flipping between the two causes bugs, and it's quite confusing. If you're interested, in order to make the BBCode section your default, go into the Profile tab (it's one of the tabs in the blue toolbar below the website header). And then locate "Edit Profile" next to the gear icon on the right side of the page. And from there, go to "Settings" and under "Posting Default," toggle "Preview" over to "BBCode." Again, this is just my personal suggestion; it's not mandatory. Although, from experience, I can attest that after your first completed thread (this thread's looking pretty solid so far!), coding all subsequent threads is pretty much copy/paste work, and the remaining HTML edits outside of that are very repetitive and easy to get used to.

- Other than that, again, I'm really enjoying your thread. My only suggestion - although you probably already know about this, whether or not you want to include it; it's all up to you - would be to embed clickable links in both the bold notes and in the highest and lowest notes listed right after the "Vocal Range:" snippet at the top of your thread. This way, if they're curious, users can click on your OP's highest and lowest notes as well as the bold notes and they could be taken to a YouTube timestamp or an uploaded file-sharing clip (eg. SndUp.net) to check out that note. The only thing about this is...like with a lot of random things (lol), the ProBoards editor can get rather fussy about the enconding for links. There's a very particular way you have to encode it in the HTML so that the text can hold both the clickable link as well as the color and boldface. If you want to include these links on your thread, but you're having trouble, I'd suggest checking out this example that Baronessa wrote in the notewatching tutorial. I've also included a screenshot of this below.

- Also, if you have any questions about the code in general, you can always message me and I'll try my best to help out.