Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: Dev news
phiw13 wrote #320429:
OK – here is a first pass mock up.
I like it, but would move Preview link to New/Duplicate/View area.
Is this layout ok for everybody? I would then start by transferring HTML/Preview controls to the preview dialog.
Offline
Re: Dev news
etc wrote #320440:
I like it, but would move
Previewlink toNew/Duplicate/Viewarea.Is this layout ok for everybody? I would then start by transferring
HTML/Previewcontrols to the preview dialog.
Yes and no, I would keep the preview link in the write column but near the heading instead of by the main text area.
- It’s a preview of what you are writing, not of what the final published page will look like (if moved to the publish button area its going to get confused with the view link that is already there).
- It’s a preview of all contents of the write column, not just the main text area.
Offline
Re: Dev news
Agree with philwareham – putting that Preview link in the New/Duplicate/View area will ber very confusing.
@philwareham You would put the Preview link before the meta data block, yes?
Where is that emoji for a solar powered submarine when you need it ?
Sand space – admin theme for Textpattern
phiw13 on Codeberg
Offline
Re: Dev news
phiw13 wrote #320442:
@philwareham You would put the Preview link before the meta data block, yes?
Basically where the (now removed) #view-modes div was, yes. Since it governs the whole of that region (title, main, excerpt, potentially custom fields one day, etc.).
Offline
Re: Dev news
philwareham wrote #320441:
Yes and no
As you say :-) Currently the ‘previewable’ set is fixed (Title/Body/Excerpt), but this will surely change in cf branch. Which makes me think we should have a Preview link for every Textilable input rather than a common one, but it is future.
Offline
Re: Dev news
etc wrote #320444:
As you say :-) Currently the ‘previewable’ set is fixed (Title/Body/Excerpt), but this will surely change in cf branch. Which makes me think we should have a
Previewlink for every Textilable input rather than a common one, but it is future.
I guess we could prepare by putting preview links on both the main text area and excerpt text area. That would work. Obviously only previewing them individually. The title preview is of no real value anyway.
Offline
Re: Dev news
etc wrote #320444:
we should have a
Previewlink for every Textilable input rather than a common one, but it is future.
If we’re going that route, I’d rather investigate ProseMirror again and have togglable inputs on each textarea in conjunction with the Textfilter selector somehow. But, as you say, future.
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: Dev news
philwareham wrote #320445:
The title preview is of no real value anyway.
Agreed. If we had individual previews for Body and Excerpt, that’s fine by me if you can squeeze them into the UI.
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: Dev news
Just for educational purposes,
How WordPress would handle this in the Classic Editor. Users toggle back and forth between Visual and Text in the upper-right corner.
And their new Gutenberg Editor – adds a lot more features but kind of buries where you make the switch.
Offline
Re: Dev news
Bloke wrote #320446:
If we’re going that route, I’d rather investigate ProseMirror again and have togglable inputs on each textarea in conjunction with the Textfilter selector somehow. But, as you say, future.
Maybe the ProseMirror guy could do it, but not me. Spent two weeks trying to integrate txp tags – no way. And implementing the whole set of php-textile features is completely out of reach.
Morgen, morgen…
Offline
Re: Dev news
Man, that Gutenberg crap looks ridiculous. The toggles on the Classic editor is more how I was envisioning things here.
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: Dev news
etc wrote #320449:
Spent two weeks trying to integrate txp tags – no way. And implementing the whole set of
php-textilefeatures is completely out of reach.
Yeah, I struggled too. There’ll be a way (somehow) to do enough of it to make a rudimentary formatting toolbar, but not the entire Textile feature set. I need to sit down and grok the builder toolset… when I have a spare few weeks to dedicate to understanding 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: Dev news
michaelkpate wrote #320448:
How WordPress would handle this in the Classic Editor. Users toggle back and forth between Visual and Text in the upper-right corner.
And their new Gutenberg Editor – adds a lot more feature but kind of buries where you make the switch.
We has them here and there, but they suit only for basic text (no txp tags or advanced Textile).
Offline
Re: Dev news
Bloke wrote #320451:
Yeah, I struggled too. There’ll be a way (somehow) to do enough of it to make a rudimentary formatting toolbar, but not the entire Textile feature set. I need to sit down and grok the builder toolset… when I have a spare few weeks to dedicate to understanding it!
The main difficulty I had is ‘txp is not xml’. The standard DOM parser used by ProseMirror is confused by things like
<txp::shortform attr='<txp:tag />' />I have partly succeeded in ‘hiding’ them on parse and then injecting back, but only one way, iirc.
Offline
Re: Dev news
philwareham wrote #320443:
Basically where the (now removed)
#view-modes divwas, yes. Since it governs the whole of that region (title, main, excerpt, potentially custom fields one day, etc.).
[[ Putting the “Preview” link at the very top of the column, before the title input field ]]
Hmm. I’m not so sure it is a good idea (it is currently in core). The link looks and feels like completely disconnected from the rest of the column.
On the other hand, what is discussed further in the thread (preview for each textarea / CF – with preview link connected to each) does seem quite interesting.
Where is that emoji for a solar powered submarine when you need it ?
Sand space – admin theme for Textpattern
phiw13 on Codeberg
Offline