Hi emilyTK,
I appreciate your suggestion. I’m having a bit hard time fully understanding your idea though.
The built-in Plain template does not use JavaScript to apply styles to the output. The intent buttons like Reply, Retweet, Favorite has some JavaScript scripts attached.
Nonetheless, I kind of understand the need of another template that does not use the !important notations. The name Plain is already taken so what would you suggest?
Uh-oh, sorry I was jumping to conclusions.
Anyways, styles are stored inside the HTML style attribute, as seen in the picture I linked to below. Element styles are just a pain to override through CSS. That’s what I’m asking to get rid of.
http://i.imgur.com/ufLzo38.png
The question how to name that template is a very good one. 🙂 Howwww about “unstyled”, or “markup only”, or “bare”?
Since “bare” is a short, and well-known term in programming, and it also speaks for itself, it might be the best I’m coming up with here. 8)
Okay. So it does not have to have a setting page, does it?
That’s right. Safe if you’d like giving code kittehs like me the option of removing or including bits from the markup output.
That is to say, it could have “visibility” settings for images, button labels, etc., but they could work differently: If a plugin user were to choose not to show the twitter profile image, or the retweet icon, it could be completely excluded from the markup output.
The user could then even make their own functionality icons; for instance by using an icon font for fetch-tweet-intent-button list items.
So it would be easier to do stuff like this (and much more!):
http://i.imgur.com/TFYZzxP.png
My understanding of backend programming is really very basic. Sorry if I’m asking for too much!
I suppose it’s coming down to filtering the API in the bare template settings?
That is to say, it could have “visibility” settings for images, button labels, etc., but they could work differently: If a plugin user were to choose not to show the twitter profile image, or the retweet icon, it could be completely excluded from the markup output.
The user could then even make their own functionality icons; for instance by using an icon font for fetch-tweet-intent-button list items.
I suppose it’s coming down to filtering the API in the bare template settings?
It seems I’m having hard time understanding what you are envisioning.
Have you created a custom template (of Fetch Tweets)? If not, I’d encourage you to do so. The instruction is available in the How to Create Own Template section in the Other Notes page.
You should be able to customize the style whatever you want with it. Let me know if that does not satisfy your needs.
