You are not logged in.
#21 2009-09-22 17:35:55
- jeremywood
- Member
- beta
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
#22 2009-09-22 17:54:40
- fpradignac
- Plugin Author
- iota
- Real name: françois pradignac
- From: France near Cognac
- Known languages: fr - en
- Website
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
#23 2009-09-22 18:42:32
- johnstephens
- Plugin Author
- lambda
- Real name: John Stephens
- From: Harrisonburg, VA
- Website
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
#25 2009-09-22 19:28:53
Re: Remove CSS Editor
+1
Graeme
gbp_permanent_links | Multi-Lingual Publishing Pack | GitHub | Twitter
Offline
#26 2009-09-22 20:26:11
Re: Remove CSS Editor
jeremywood wrote:
Okay, this begs the question to me: What’s the benefit to using any of the “internal” CSS instead of an external CSS file?
For me, it’s not useful for regular site styles. However, for admin-plugins, it’s more convenient for the user to be able to edit a plugin’s CSS via Presentation>Style than having to muck around with the plugin’s source code.
Offline
#27 2009-09-23 05:49:27
Re: Remove CSS Editor
jeremywood wrote:
Okay, this begs the question to me: What’s the benefit to using any of the “internal” CSS instead of an external CSS file?
For me it is because I can edit the css anywhere any time using just the browser without needing any ftp and/or other programs.
When moving an install, the internal css also helps as it is one less thing to worry about.
In fact I would vote for javascripts to be included in the db (can be done with a plugin at the moment) and rvm_css to be modified for them too:)
In fact txp is one of the few programs I know that you can maintain a site without the need of any other software.
Last edited by colak (2009-09-23 05:51:28)
neme.org | hblack.net | neme-imca.org | code4.net | LABS
Offline
#28 2009-09-23 06:29:22
- masa
- Member
- pi
- Real name: Martin Sammtleben
- From: Reykjavik, Iceland
- Known languages: is, en, de
Re: Remove CSS Editor
colak wrote:
In fact txp is one of the few programs I know that you can maintain a site without the need of any other software.
Exactly, and I would like to see that continued.
Offline
#29 2009-09-23 16:56:35
- kostas45
- Member
- delta
- Real name: Kostas
- From: Greece
- Known languages: el, en
Re: Remove CSS Editor
+1 to remove CSS (for dummies) Editor application from core.
+1 to continue to maintain a site without the need of any other software.
Offline
#30 2009-09-23 17:04:39
- saccade
- Plugin Author
- lambda
- Real name: Michael Schlierbach
- From: Raubling, Germany
- Known languages: de, en
Re: Remove CSS Editor
+1 to remove the CSS-Editor application – I never used it and really only viewed it once.
+1 for keeping internal CSS maintainment
Offline