From: <pau...@us...>
<pau...@us...> - 2008-07-27 20:32:26
|
Greetings! Brian Aker wrote: > Hi! > > On Jul 26, 2008, at 6:34 AM, Paul wrote: > >> Rather than all this mucking around with XML, it might be far better to >> have all nodeballs, or at least ecore, as an sqlite database. On > > I cannot decide on first read if this is brilliant, or just another tool > I cannot edit with a plain text file. > Well, actually that reason and also the fact you can't diff it easily is why it might not happen. My main aim for suggesting that ecore be stored as an sqlite file is that, we need to get more people interested in Everything and whilst coding in perl is really cool and stuff, there are far more people who can knock up a bit of css than they can hack some perl. So, I'm thinking it is away to make installation easier, so that people can start making funky themes as they do with wordpress. To help this process I was considering putting a bare Everything up somewhere and leaving it open so that the public could hack it. Of course, you'd often get idiots who'd delete the whole site, and worse, but with frequent enough DB dumps it might have been OK. Then I remembered that Everything has pure code all over ecore and the aforementioned idiots might have even more fun with system('rm -rf /') and similar. And whilst the apache user might not have that many priveleges it's still enough to cause havoc. But perhaps I could just leave the CSS file open or something.... Speaking of CSS one of the things that bugs me about it, and indeed, one of the things I find annoying about CMS's like wordpress, is that you end up with these huge CSS files in which it is impossible to find the bit you're looking for. I hear that sensible people split up their CSS files into manageable and bite-sized chunks. The question is how to do that with Everything. > I am not a fan of XML because of all of the escaping required. Me neither, but I don't dislike it as much as I dislike the DOM :) Cheers Paul |