Alternative Tab Content Definition about blaze-tabs HOT 4 CLOSED

1 should be an option, but I wouldn't recommend it. It mostly exists for backwards compatibility.

See the code here:
https://github.com/meteortemplates/tabs/blob/master/templates:tabs.coffee#L75

I'll have to respond to your class concerns a little bit later when I have more time to dig into the code. Let's continue that discussion in your other issue.

from blaze-tabs.

@jonjamz, I don't mind if you want to keep discussion in one issue, but I'd like to clarify that while I'm personally only concerned about adding custom classes at this time, the ability to use a custom definition of #tabContent seems of greater importance since it's not clear if it can be done without forking the entire project (which I have).

from blaze-tabs.

You shouldn't have to fork the project to write your own #tabContent. Just copy the HTML and JS from the package over for that template in your project (you should be able to create as many differently named variations of this as you want) and keep the existing helpers and add your own new stuff. The codebase of the package is really small, like ~140 LOC, and it's all just Blaze.

from blaze-tabs.

Ah, good point. I hadn't realized that the tabContent helper was independent of the rest of the package.

from blaze-tabs.