New kid on the blog: A look at Serendipity 1.0
|
|
Comments (14)
I love s9y.
Finally registered after lurking for a while. :) *waves*
I agree with devnet. I searched around when I was planning to integrate a blog into my site. (p.s. how do I add links in here?) and settled on s9y because it seemed much easier to setup and customize than the others I looked at. I've been glad I did. Sure, it has it's glitches here and there, but overall it's a nice, easy to use, and very customizable blog package.
Finally registered after lurking for a while. :) *waves*
I agree with devnet. I searched around when I was planning to integrate a blog into my site. (p.s. how do I add links in here?) and settled on s9y because it seemed much easier to setup and customize than the others I looked at. I've been glad I did. Sure, it has it's glitches here and there, but overall it's a nice, easy to use, and very customizable blog package.
> Ask someone who doesn't know HTML and they'll hands down use serendipity.
I always find that I always code in HTML attitude strange. I 'can' write pretty good HTML if I have to, but if given the choice, I'll always use a WSWG like NVU. There might be a case for making minor changes in code, but overall, coding for visuals is just counter intuitive, and no way as quick or consistent. Experienced users should know this best.
I always find that I always code in HTML attitude strange. I 'can' write pretty good HTML if I have to, but if given the choice, I'll always use a WSWG like NVU. There might be a case for making minor changes in code, but overall, coding for visuals is just counter intuitive, and no way as quick or consistent. Experienced users should know this best.
Oddly enough, I go exactly the opposite way.
I can't stand WYSIWYG editors.
Maybe it's my programming background or something, but I feel more comfortable when I can see the code and know that it's exactly as I wrote it, not how some editor thought I meant to write it.
Now maybe if I was doing some serious CSS work I might use an editor, since I don't know the language real well yet, but overall I just plain prefer to work in pure code. :)
> when I can see the code and know that it's exactly as I wrote it
Well I could see that if the final product was not a visual image. To me, that's the only real proof.
Well I could see that if the final product was not a visual image. To me, that's the only real proof.
I can't stand WYSIWYG HTML editors, either. Most of them insert tons of pure garbage. I don't blog, though, so my preference for just editing the HTML probably has no bearing on CMS.
>I can't stand WYSIWYG HTML editors
I think it's all marketing. No less an authority than Richard Stallman believes that what you call something is very important.
Henceforth, I propose that we refer to bluefish and its text-oriented friends and compatriots as WYSIWYC editors -- What You See Is What You Code.
Failing that, WYCISWG, or What You Code Is What You Get.
I think it's all marketing. No less an authority than Richard Stallman believes that what you call something is very important.
Henceforth, I propose that we refer to bluefish and its text-oriented friends and compatriots as WYSIWYC editors -- What You See Is What You Code.
Failing that, WYCISWG, or What You Code Is What You Get.
haha.
I like that.
My personal favorite "web editor" is mcedit. I use nano if I'm doing a quick tweak or working across the net and mc is too laggy on the connection to work with efficiently.
My personal favorite "web editor" is mcedit. I use nano if I'm doing a quick tweak or working across the net and mc is too laggy on the connection to work with efficiently.
Joe or mcedit, with proper syntax highlighting. (The evil vi[m] also does syntax highlighting, but I lack the necessary collection of small, furry mammals to sacrifice to attain an exit from vi[m]).
dinotrac: You're getting close to lyx's motto of what you get is what you meant. :)
dinotrac: You're getting close to lyx's motto of what you get is what you meant. :)
> You're getting close to lyx's motto of what you get is what you meant. :)
More like 'thought you meant' :D.
More like 'thought you meant' :D.
Quoting:Henceforth, I propose that we refer to bluefish and its text-oriented friends and compatriots as WYSIWYC editors
I'd settle for a mandate that people stop pronouncing WYSIWYG.
SFN:
My pet peeve is that made-up thing some folks use in place of SQL. Jeez, there are only 3 letters to say.
My pet peeve is that made-up thing some folks use in place of SQL. Jeez, there are only 3 letters to say.
Is that what they mean?
I always thought they were referring to the next installment...
I always thought they were referring to the next installment...
Yes. Totally unnecessary.
And if they must pronounce it, they should say "squeal". Possibly "squall".
And if they must pronounce it, they should say "squeal". Possibly "squall".
Post a comment
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help
Sign up and post (it is free) or Log in and post

So far, out of all blogging software currently available (wordpress included) I have not found an equal to serendipity. It is the most outstanding blogging software available for free today. Period.
Now to address the review:
It's 2 clicks away from being installed. It's available through Spartacus http://spartacus.s9y.org/ and it is the same service that bad behavior is. Stops everything in its tracks and then if you use askimet, you never get spam anymore (as I haven't for months now) Odd, they've worked flawlessly for me for 3 versions now. One might conclude that the problem lies elsewhere. You're using the wrong image inserter on your htmlarea toolbar. Don't use the Insert Images button, use the Manage Images Button right beside it. Works far better and allows you to position the image into the HTMLArea. This is just inexperience with the software for this one. No fault of the reviewer.