Use Developer Tools to figure out what is wrong with plugins

[P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓]

.HTML with quotes tells JavaScript to render it as html so your table could go in there. The first part $('#id') is where the HTML will be placed

[P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓]

Nov 13, 2017 21:48:53 GMT -8 Alan Vende said:

Nov 13, 2017 21:38:19 GMT -8 P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓ said:

You can write HTML in js components using single or double quotes. You can place them in the footer per se by using document ready. You can place it in the header using append. You can write CSS by appending styles or stylesheets. And you can do evything in the header or footer components too. There's a million. Ways to skin a cat, you just have to write it in a way that your component understands.

Writing HTML in the JS component is what I'm attempting to do with the table since I don't see any other viable way of making it work correctly, but every time I try to do it, the plugin breaks. ...I guess I'm just not a good coder. :/

The only thing that matters is that the component itself understands, it doesn't matter specifically how you write it--like you said: "there's a million ways to skin a cat..."

Nov 13, 2017 21:41:26 GMT -8 P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓ said:

Yeah I'd should NEVER be something like blue. Yes multiple components like that. Yes if you wrote a code that overwrote someone else code or moved something g so that Brian's plugin would no longer work, that would probably be bad coding.

Blue being too common of a word, right? It being a color would probably be referenced within the styles of a theme or within discussions in the boards. I can think of many reasons why that type of word wouldn't be good.

It's never good to stop other's plugins from working anyway. It would be bad, and then it would be up to you to fix it.

Yep exactly. Or figure out a different way to do what you want that won't cause admins to scratch their heads why two plugins don't work together

[P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓]

You can write js in headers and footers and themes using <script> and style for css

[Alan Vende]

Nov 13, 2017 21:53:06 GMT -8 P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓ said:

.HTML with quotes tells JavaScript to render it as html so your table could go in there. The first part $('#id') is where the HTML will be placed

Using your code that you gave me earlier in the thread as an example, it would go here, right: $('#customdialogbox').html('Grrrrr... Brrrrrrrrr...')? I tried that, though, and that's where I ran into problems with the red tags and, when I attempted to open the dialog box by clicking the button, that not working either.

Which is what prompted me to wonder if I should attempt to code it another way, although I don't see any other viable way to make it so the dialog box turns into a tabbed dialog box and still opens onclick of the button.

Like I said, it completely stumps me.

Nov 13, 2017 21:54:47 GMT -8 P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓ said:

Nov 13, 2017 21:48:53 GMT -8 Alan Vende said:

Writing HTML in the JS component is what I'm attempting to do with the table since I don't see any other viable way of making it work correctly, but every time I try to do it, the plugin breaks. ...I guess I'm just not a good coder. :/

The only thing that matters is that the component itself understands, it doesn't matter specifically how you write it--like you said: "there's a million ways to skin a cat..."

Blue being too common of a word, right? It being a color would probably be referenced within the styles of a theme or within discussions in the boards. I can think of many reasons why that type of word wouldn't be good.

It's never good to stop other's plugins from working anyway. It would be bad, and then it would be up to you to fix it.

Yep exactly. Or figure out a different way to do what you want that won't cause admins to scratch their heads why two plugins don't work together

Don't most coders have to figure out different ways of coding what they want when their original attempt doesn't work, or can most get it on the first try? (Like with this, for example, if you were coding this, would it work for you on the first try? If so, I'm jealous. )

[P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓]

With js syntax is everything. By using the js component, if the code breaks your plugin won't work. But say you have a script that breaks in the header, it will most likely prevent all other JavaScript on the page from working (other than other js components)

[Alan Vende]

Nov 13, 2017 21:57:00 GMT -8 P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓ said:

You can write js in headers and footers and themes using <script> and style for css

Right <script></script> and <style></style>[/tt]. But that doesn't apply to plugins, right? From what I understand when writing a plugin, you do not include the tags.

Nov 13, 2017 22:00:16 GMT -8 P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓ said:

With js syntax is everything. By using the js component, if the code breaks your plugin won't work. But say you have a script that breaks in the header, it will most likely prevent all other JavaScript on the page from working (other than other js components)

With what you just said, then why does the <marquee></marquee> still work in the plugin? Even though the button doesn't work sometimes with what I do to it in trial and error, the marquee always seems to scroll.

[P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓]

Nov 13, 2017 22:00:10 GMT -8 Alan Vende said:

Nov 13, 2017 21:53:06 GMT -8 P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓ said:

.HTML with quotes tells JavaScript to render it as html so your table could go in there. The first part $('#id') is where the HTML will be placed

Using your code that you gave me earlier in the thread as an example, it would go here, right: $('#customdialogbox').html('Grrrrr... Brrrrrrrrr...')? I tried that, though, and that's where I ran into problems with the red tags and, when I attempted to open the dialog box by clicking the button, that not working either.

Which is what prompted me to wonder if I should attempt to code it another way, although I don't see any other viable way to make it so the dialog box turns into a tabbed dialog box and still opens onclick of the button.

Like I said, it completely stumps me.

Nov 13, 2017 21:54:47 GMT -8 P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓ said:

Yep exactly. Or figure out a different way to do what you want that won't cause admins to scratch their heads why two plugins don't work together

Don't most coders have to figure out different ways of coding what they want when their original attempt doesn't work, or can most get it on the first try? (Like with this, for example, if you were coding this, would it work for you on the first try? If so, I'm jealous. )

Rarely do my codes work on first or even third try.

[Alan Vende]

Really? Rarely? Yours works great for me. I just wish I could have it listen to me to give it tabs.

[P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓]

Nov 13, 2017 22:04:32 GMT -8 Alan Vende said:

Nov 13, 2017 21:57:00 GMT -8 P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓ said:

You can write js in headers and footers and themes using <script> and style for css

Right <script></script> and <style></style>

[/tt]. But that doesn't apply to plugins, right? From what I understand when writing a plugin, you do not include the tags.

Nov 13, 2017 22:00:16 GMT -8 P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓ said:

With js syntax is everything. By using the js component, if the code breaks your plugin won't work. But say you have a script that breaks in the header, it will most likely prevent all other JavaScript on the page from working (other than other js components)

With what you just said, then why does the <marquee></marquee> still work in the plugin? Even though the button doesn't work sometimes with what I do to it in trial and error, the marquee always seems to scroll.[/quote]
Marquee is HTML. It will scroll through HTML. There are also CSS animations too.

[Alan Vende]

Nov 13, 2017 22:10:23 GMT -8 P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓ said:

Nov 13, 2017 22:04:32 GMT -8 Alan Vende said:

Right <script></script> and <style></style>

[/tt]. But that doesn't apply to plugins, right? From what I understand when writing a plugin, you do not include the tags.

Nov 13, 2017 22:00:16 GMT -8 P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓ said:

With js syntax is everything. By using the js component, if the code breaks your plugin won't work. But say you have a script that breaks in the header, it will most likely prevent all other JavaScript on the page from working (other than other js components)

With what you just said, then why does the <marquee></marquee> still work in the plugin? Even though the button doesn't work sometimes with what I do to it in trial and error, the marquee always seems to scroll.[/quote]
Marquee is HTML. It will scroll through HTML. There are also CSS animations too.[/quote]

---

Duh. My bad! I feel like more of an idiot now.

[P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓]

I use script and style tags in plugins sometimes instead of using the components

[P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓]

Nov 13, 2017 22:10:22 GMT -8 Alan Vende said:

Really? Rarely? Yours works great for me. I just wish I could have it listen to me to give it tabs.

I believe my notes is a plugin that is editable that has comments on what each line does. It might teach you something

[P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓]

I thought myself JavaScript through examining plugins and google

[P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓]

We could voice chat in a couple hours if you want to talk about coding

[P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓]

Peter's ebook is excellent, I read it myself. support.proboards.com/thread/614269/free-ebook-creating-proboards-plugins
And that my notes plugin editable in build mode: My Notes 2-1 Editable.pbp (3.23 KB) with comments on what everything does. I assume you fixed the red color thing since I didn't see anything red.