Blog improvements
Greetings! Keith, the blog seems to suffer some little issues. Eg, sometimes arrow keys don't work, and it doesn't appear to handle straight text very well (< and > don't work, and \ (that's a single \\ in case you missed it) doesn't seem to act sensibly).
Is the blog one you grabbed or wrote yourself? Maybe we could start a project to write our own software if it is one you grabbed. Would this be too insane?
Also, a spell checker would be really cool. Is that possible? Auto spell check as the text is being entered. Maybe that's too extravagant.
All in all the blog is good to get unwanted traffic off the mailing list, and the comments are stored which is even better.
Perhaps we should encourage more members to post news items etc to the website (as in 'slashdot flavour') to reduce traffic on the mailing list for those that might find it a!
nnoying.
As the group ages and expands we need to get some organisation stuff happening. This could be our first group project?
I can find out if (or how) a spell checker is possible within a blog. Can you give us a link to the source code you used?
Speaking of which, when I went on to 'irc.freenode.net' channel #C they directed me to a useful tool to paste in my source code when then gave an html link for others to view the code with.
Check:
http://rafb.net/paste/
This would be useful for us as well (although the link above doesn't appear to store source for very long, two or three days I think). If we could store source in html links that display inline, that is as a pointer to the link that displays the full source within the blog not just the link (php should cope with that), this would be unreal. That way the same source can be posted in one line to the mailing list, etc, by using the html link.
What do you think?
Cheers-
Ian S.
- Login to post comments
Spell checking isn't very eas
Spell checking isn't very easy client side (ie.. as you type). It is possible to do it server side using aspell/ispell and then prompt the visitor etc. All interfaces I've seen that use this.... suck.
If you really wanted to check out client side then the only way I can think of would be either a really massive javascript or an iframe/frame that refreshes constantly and checks spelling server side - ugly either way. The problem then is highlighting the errors. You would need to make an iframe/div/etc editable instead of using a textarea because textarea's don't allow you to set styles for bits of text. Basically. This would be weeks and weeks worth of work... and then it would only work in late mozilla or internet explorer. :-/
Or.. you could write an applet... eegad!
Daniel