Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: Prism for html preview in write tab
Offline
Re: Prism for html preview in write tab
sacripant wrote #298070:
See prism-core
Ooooh, we can also use lang-* as shorthand. Neat, thanks for the hint.
And as for language-markup, I’ll give it another go sometime when I’m not not distracted.
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Hire Txp Builders – finely-crafted code, design and Txp
Offline
Re: Prism for html preview in write tab
Might this simple prism-based syntax-highlighted textarea be a good match for syntax highlighting textile / markdown fields in the Write panel?
Micro Code Editor codepen sample
Related project by the same author: Codeflask
The advantages:- Would make use of the existing prism resources
- Minimal, no line numbering etc.
- Very lightweight compared with other full-blown solutions
- Potentially stylable via prism
TXP Builders – finely-crafted code, design and txp
Offline
Re: Prism for html preview in write tab
Meanwhile, it’s a good idea to make your first plugin for txp 4.6 :)
Offline
Re: Prism for html preview in write tab
Still think Txp should adopt Markdown as core and make Textile the alternate filter. Especially as it seems Textile development is on it’s last leg.
Offline
Re: Prism for html preview in write tab
Destry wrote #298228:
Still think Txp should adopt Markdown as core and make Textile the alternate filter. Especially as it seems Textile development is on it’s last leg.
If it’s feature complete and bug free, there really isn’t a need for further development.
Offline
Re: Prism for html preview in write tab
Well, feature complete and bug-free are debatable sooner or later.
I’d like to see definition lists changed to something more Textile obvious, similar in idea to how tables can be notated. For example:
dl(class).
; Title
: DataAnd I’d like to see hard rules added:
hr(class).So wether Textile is bug-free as is, what does that say about making it better?
But the real point I was making is that Textile isn’t as popular as Markdown, not even fractionally close. It just doesn’t make sense to cling to it as a default filter anymore, sentimental reasons aside. Make it an alternate filter instead of the core default and you still get the best of both worlds (plus active Markdown development).
Offline
Re: Prism for html preview in write tab
But the real point I was making is that Textile isn’t as popular as Markdown, not even fractionally close. It just doesn’t make sense to cling to it as a default filter anymore, sentimental reasons aside.
I disagree with this reasoning.
War of PHP CMS is over! Textpattern is an alternative. He continues to exist because he is different. And theses differences allowed him to retain users.
Textpattern must cultivate its difference. this is not a story of sentimental reasons
Do as global thinking may, however, be fatal to Txp.
Yes, markdown must be an option, Textile must be an option, Wysiwyg must be an option. But want to make the same choice as the other is not necessarily a good idea.
Offline
Re: Prism for html preview in write tab
sacripant,
Switching the default role of Markdown and Textile has nothing to do with any “CMS war”, whatever that is, nor does it influence anything about the functional integrity of core Txp.
What it does enable, however, is the likelihood that more people in the world will try Textpattern, and especially as it would more easily accommodate the content produced in other editing tools that typically support Markdown but not Textile (iA Writer, Ulysses, Draft, GitHub Pages, GatherContent, etc, etc, etc). That’s a very practical and sensible reason to make the reversal.
As an editor that routinely works with contributing authors, I can tell you that many are beginning to know Markdown though use of their other writing tools, while none have ever heard of Textile.
Stubbornly refusing to accommodate other leading tools on the market because of favoritism for an abandoned language is very much an expression of sentimentalism, and more likely to be the demise, you suggest, of a CMS.
Don’t get me wrong, I prefer Textile too, for personal use, and I can keep using it either way. But I’m not so sentimental as to be blind to the practical value otherwise — for the project itself.
Last edited by Destry (2016-03-14 12:07:38)
Offline
Re: Prism for html preview in write tab
Destry wrote #298228:
it seems Textile development is on it’s last leg.
As Ruud says, what more do you add when it has syntax for just about everything you need in 90% of cases? Aside from making it feel more like other markup languages or tackling the niche features.
The best killer feature, imo, would be to finish off the textplugs branch and/or add some kind of extensible callback system. Because then you could make it feel like any damn system you liked: extend it, alter it, add tags, make your own shortcuts, whatever you fancied.
There’d be no more grounds to claim it didn’t support the HTML 8 <megadoohicky> tag, or that it should use the Redcloth syntax, or use a different shortcut for dl, because you could make a plugin for it.
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Hire Txp Builders – finely-crafted code, design and Txp
Offline
Re: Prism for html preview in write tab
Bloke wrote #298252:
what more do you add when it has syntax for just about everything you need in 90% of cases?
I think my “last leg” remark got misconstrued. All I meant was that when you look at Markdown — or, as it seems to be headed these days, CommonMark — there’s a big difference between active interest and development there versus Textile.
As developers, you guys can interpret that any way you want to, I guess, but as a user, I’m inclined to favor, for the sake of collaboration (most important in my world), where there’s a more obvious future. But, hey, if you devs can invent megadoohickeys, don’t let me interfere. ;)
Offline
#27 2016-03-14 13:56:15
- candyman
- Member
- From: Italy
- Registered: 2006-08-08
- Posts: 684
Re: Prism for html preview in write tab
Many years ago I preferred TXP over WP because of textile.
Actually I would choose Markdown because all my other Mac utilities and word processors and forums softwares use markdown as default.
Today I have to remind myself to use textile only when I have to write some blog articles or into a thread of this forum.
So, if you create a website for a client that will be managed only by a person (better if a TXP enthusiast) textile is still OK (rather, we all agree it’s better),but if you are going to create a site that will be used by many people (for comments and so on) keep to insist on textile isn’t a good idea.
So it would be great if TXP 4.6 could give us the option to choose our favorite markup language.
Last edited by candyman (2016-03-14 13:56:53)
Offline
Re: Prism for html preview in write tab
candyman wrote #298255:
So it would be great if TXP 4.6 could give us the option to choose our favorite markup language.
Textpattern 4.6 is feature complete now, just some minor bugs to mop up and then it is beta ready. So this will need to be discussed as part of 4.7 or later – hopefully 4.7 will also be put this year though.
In the meantime, Robert has created a Markdown filter if you want it sooner.
Offline
Re: Prism for html preview in write tab
candyman wrote #298255:
it would be great if TXP 4.6 could give us the option to choose our favorite markup language.
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Hire Txp Builders – finely-crafted code, design and Txp
Offline
Re: Prism for html preview in write tab
candyman,
Yeah, the filter option is now there. And it’s wonderful!
My notes were about which one serves as the default, and I was proposing that to be Markdown.
For everyone in this community working on personal websites, it’s a trivial (and subjective) issue. But the second you start thinking outside of the box and into the future (collaboration, markup language support in other popular applications, etc), it’s not so trivial (or subjective) anymore. The decision about a default becomes one that is more practical to the majority of user interests.
One thing is for sure. It’s not Textpattern’s role to sell the world on Textile. It seems the only support of it at this point is because a niche CMS forced it on us and made us all junkies. ;)
Offline