Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: Remove CSS Editor
To clarify: this is not about removing the raw CSS editor that uses a single textarea. The proposal is to remove the rarely used “CSS for dummies” editor that tries (!) to split the CSS into a truckload of input fields.
Offline
Re: Remove CSS Editor
+1 for removing it.
But the raw css editor is very usefull for me !
françois
Offline
Re: Remove CSS Editor
mrdale wrote:
+1 as long as you replace it with a pony.
+1
I’ll never use it. Haven’t met anyone who has. I like the raw input field to stay too.
Last edited by whaleen (2009-09-22 10:28:44)
txtstrap (Textpattern + Twitter Bootstrap + etc…)
Offline
#16 2009-09-22 11:07:09
- masa
- Member
- From: Asturias, Spain
- Registered: 2005-11-25
- Posts: 1,091
Re: Remove CSS Editor
+1
whaleen wrote:
I like the raw input field to stay too.
Yes, it’s very handy to have, but the editor can go.
Last edited by masa (2009-09-22 11:08:15)
Offline
Re: Remove CSS Editor
+1 from me too. I had to open up a site to remind myself what it looked like.
Incidentally, I got this error:
Notice: Undefined offset: 1 in /path/to/www.mysite.com/web/content/textpattern/include/txp_css.php on line 253
Offline
Re: Remove CSS Editor
+1 for me too, never used the CSS editor.
I only work with raw CSS.
Offline
Offline
Re: Remove CSS Editor
iblastoff wrote: +50!
Jeez, there’s one in every crowd. And I’m starting to be convinced that they’re all Canadian. Sorry but you can only have one.
Last edited by mrdale (2009-09-22 15:15:11)
Offline
#21 2009-09-22 17:35:55
- jeremywood
- Member
- Registered: 2007-12-12
- Posts: 26
Re: Remove CSS Editor
Okay, this begs the question to me: What’s the benefit to using any of the “internal” CSS instead of an external CSS file?
I’ve never understood why you’d want to use CSS from the DB. You can’t use tools like CSSEdit (http://macrabbit.com/cssedit/) to easily manage your CSS if it’s buried in the DB somewhere.
Offline
Re: Remove CSS Editor
jeremywood a écrit:
Okay, this begs the question to me: What’s the benefit to using any of the “internal” CSS instead of an external CSS file?
I’ve never understood why you’d want to use CSS from the DB. You can’t use tools like CSSEdit (http://macrabbit.com/cssedit/) to easily manage your CSS if it’s buried in the DB somewhere.
Perhaps there are only a few people who need to code with a “machine” like CSSEdit ?
Last edited by fpradignac (2009-09-22 17:55:01)
françois
Offline
Re: Remove CSS Editor
+1 to remove CSS Editor application from core.
+1 to remove base64 encoding of CSS, which Stef said would reduce Textpattern’s footprint to the size of a postage stamp.
Offline
Re: Remove CSS Editor
^^ yes, +1 on removing the unnecessary base64 encoding as well, provided upgrades are handled properly (shouldn’t be too hard).
Offline