fixed width of text editor fields

muffinmaker · 2012-11-12 14:59:56

Hi there, I’m new to Textpattern and tried out the live demo on http://demo.opensourcecms.com/ prior to setting up xampp and a local Textpattern 4.5.2 installation.

While in the live demo, editor fields can be resized in two directions, my local installation of Textpattern allows resizing editor fields only in vertical direction. Is there anything I can do to change this? Since HTML code lines can get quite long and reading code without syntax highlighting is hard enough I want at least avoid line breaks. In order to get syntax highlighting I’ve tried out the “spf_codemirror” plugin, but as soon as it’s active, it prevents the editor fields from being resized at all.

Highly appreciate any hints!
Tobias

Last edited by muffinmaker (2012-11-12 15:05:54)

Gocom · 2012-11-12 16:33:00

Muffins mmm… Um, wait what? Sorry about. Right, welcome to muf — er, to Textpattern.

The demo hosted at opensourcecms.com is of bit old, it still uses version 4.4.1. In 4.5.2 it’s true that fields are fixed size as it comes to ‘Remora’ and ‘Classic’ themes and resizing is restricted to vertical direction. For those two themes you would have to edit their CSS and remove or alter ‘resize’ properties set for textareas.

Textpattern ships with a third theme named Hive. Unlike those two ‘classics’, Hive is newer and responsive. Hive neither offers a way to manually resize fields in horizontal direction, but the theme is fluid and responsive. In other words, all multi-line fields are as width as they can be.

Last edited by Gocom (2012-11-12 16:36:30)

muffinmaker · 2012-11-12 17:27:28

Wow, that was fast!
Thank you for your help.
“Hive” works fine. Although at higher resolutions it does waste a great deal of space

I think I’ll better go for this solution:

For those two themes you would have to edit their CSS and remove or alter ‘resize’ properties set for textareas.

Edit:
Much better. Still a few pixels wasted, but I guess I can live with that ;)
If there were a possibility to use spf_codemirror and still being able to resize, I’d be a lucky guy…

Thanks again!

Last edited by muffinmaker (2012-11-12 18:38:01)

Bloke · 2012-11-12 18:01:28

muffinmaker wrote:

it does waste a great deal of space

Hi and welcome aboard. Yeah, that’s largely down to the ancient table-based layout of the underlying markup on the admin side. It’s being addressed in the next version as the tables for layout are gradually being removed (although there’s a max-width:116em rule on the body container, even on the new table-less pages, that’s probably for backwards compatibility as we transition things and I guess Phil will revisit that when all the tables are gone).

If you’re curious how things are shaping up for the next version, btw, feel free to grab a nightly.

muffinmaker · 2012-11-12 18:36:28

Thanks for the explanation, Stef.

feel free to grab a nightly.

I’ll give it a shot!

philwareham · 2012-11-12 19:08:48

I don’t have any intention of removing the max-width rule. Even after the move to grid based layout.

However, we are looking at ways to hide the tag builder column on forms/pages, maybe by using a slide out drawer or modal or something I haven’t thought of yet. That’ll give you the same amount of room for the textarea as what’s currently on the styles page.

Last edited by philwareham (2012-11-12 19:09:08)

muffinmaker · 2012-11-12 21:31:47

I don’t have any intention of removing the max-width rule […] That’ll give you the same amount of room for the textarea as what’s currently on the styles page.

As long as anyone can change it back to prior 4.5 behaviour (as in the live demo) I don’t really care, but why not give it a more ergonomic design in the first place? Or did I get you wrong?

Bloke · 2012-11-12 22:29:14

philwareham wrote:

I don’t have any intention of removing the max-width rule. Even after the move to grid based layout.

Ha, well that told me!

Note to self again : keep out of things in which I have limited or no knowledge :-)

philwareham · 2012-11-12 23:44:09

The grids work on inline-blocks and fixed percentages (based on Griddle grid system) so anything the forcibly spills out of those container (such as user resizable textareas) on the horizontal plane will affect the overall page layout. Hence the desire to move/hide the tag builder column to allow for ample textareas in future.

Also, in 4.6 branch the max-width has been increased by a small amount, which will benefit those on larger monitors.

Cheers! Sorry, I think my previous message was a bit blunt!

Last edited by philwareham (2012-11-12 23:44:50)

philwareham · 2012-11-13 09:45:30

Oh, I forgot to mention – if you are using the Hive theme in Textpattern 4.5 then you can completely hide the tag builder column on pages/forms pages by adding this into your config.php file before the closing ?> tag:

define('hive_theme_hide_tag_builder_column', true);

Textpattern CMS

Textpattern CMS support forum

#1 2012-11-12 14:59:56

fixed width of text editor fields

#2 2012-11-12 16:33:00

Re: fixed width of text editor fields

#3 2012-11-12 17:27:28

Re: fixed width of text editor fields

#4 2012-11-12 18:01:28

Re: fixed width of text editor fields

#5 2012-11-12 18:36:28

Re: fixed width of text editor fields

#6 2012-11-12 19:08:48

Re: fixed width of text editor fields

#7 2012-11-12 21:31:47

Re: fixed width of text editor fields

#8 2012-11-12 22:29:14

Re: fixed width of text editor fields

#9 2012-11-12 23:44:09

Re: fixed width of text editor fields

#10 2012-11-13 09:45:30

Re: fixed width of text editor fields

Board footer