"serendipity" everywhere!

[digx]

I really like s9y. I think it's a great blogging utility and it's done very well. My biggest complaint, however, is how the name "serendipity" appears everywhere in the code, the filenames, the output html, the css. It's not that I don't want people to know that serendipity is my blogging system but it makes the XHTML extremely ugly and a bigger pain to CSS with. I also don't understand the need for the serendipity_ prefix for all the plugins. Since serendipity is the parent framework for the system anyways, why do you have to include serendipity? It's not like it would cause conflicts with anything else.

[wesley]

Well, I think you could just make a plugin without the prefix, but then not a
lot of plugins come with a readme file, so I think everyone just went onto
stick the prefix as an easy marker of sorts. Also, having the plugin labeled
_event or _plugin doesn't automatically make the plugin act like event or
sidebar plugin, but it's just an agreed naming convention to keep things
organized. Since the plugins are just PHP files, it could easily be taken out
of context, but the naming convention should make it easy to identify where
it was from and what it was intended for.

I do, however, think the whole name of 'serendipity' is tad long. Perhaps it
could've been shortened to 's9y' instead of 'serendipity'. Still, I'm not a big
fan of lifting the moniker off completely.

[garvinhicking]

The prefix allows to use Serendipity in other frameworks. As Serendipity is not completely OO-based, we would pollute the namespace otherwise.

The "serendipity_" CSS references can be changed in your own template. We also keep that to allow easy embedding of serendipity into other frameworks.

Changing it to "s9y" would amount to quite some work in the sourcecode, as serarch+replace would not always work

Regards,Garvin