No, not really. You can output a custom <script type="text/css"> inside a PHP function, hooked into wp_print_scripts. And the custom CSS rules themselves, being non-html text, can easily be sanitized and saved to the database.<div>
<br></div><div>For example, see how Twenty Eleven outputs its custom link color CSS rule (look for the twentyeleven_print_link_color_style() function, hooked into wp_head):</div><div><a href="http://themes.svn.wordpress.org/twentyeleven/1.3/inc/theme-options.php">http://themes.svn.wordpress.org/twentyeleven/1.3/inc/theme-options.php</a></div>
<div><br></div><div>Thanks,</div><div><br></div><div>Chip<br><br><div class="gmail_quote">On Sun, Mar 18, 2012 at 7:55 PM, // ravi <span dir="ltr"><<a href="mailto:ravi-lists@g8o.net">ravi-lists@g8o.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Mar 18, 2012, at 9:10 AM, Chip Bennett wrote:<br>
><br>
</div><div class="im">> Is there any particular reason that your "skins" have to use these sort of files, rather than simply enqueueing CSS files?<br>
><br>
<br>
</div>To clarify my previous post further, I guess I can indeed enqueue the CSS files to serve them to viewers, but writing/creating these CSS files based on blog owner supplied values will still need WP_Filesystem, I think?<br>
<div class="HOEnZb"><div class="h5"><br>
—ravi<br>
<br>
<br>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
</div></div></blockquote></div><br></div>