Okay, it's too early -- or too late -- to actually release this
tonight, but I wanted to give people a chance to play with a Ruwiki
0.9.0 instance on RubyForge. One of the first things that you'll
notice is that the edit buttons are *not* present on your initial
visit, unless you have signed into RubyForge for the day.
Yes, I'm authenticating against the RubyForge user/session database.
Cool.
I'll make a full release and proper announcement of everything
tomorrow, complete with .tar.gz and RubyGems release, and Batsman has
promised an RPA release very quickly after that.
This is a big change, folks -- and there's bigger changes to come in
the new year.
Okay, it's too early -- or too late -- to actually release this
tonight, but I wanted to give people a chance to play with a Ruwiki
0.9.0 instance on RubyForge. One of the first things that you'll
notice is that the edit buttons are *not* present on your initial
visit, unless you have signed into RubyForge for the day.
nice, thanks
Yes, I'm authenticating against the RubyForge user/session database.
Cool.
indeed
Anyway, I don't think that editing a locked page should give this error:
Austin just fixed this, It wasn't a Ruwiki bug but a permissions
error with his installation on RubyForge.
···
On Sun, 28 Nov 2004 20:57:52 +0900, gabriele renzi <rff_rff@remove-yahoo.it> wrote:
Austin Ziegler ha scritto:
> Okay, it's too early -- or too late -- to actually release this
> tonight, but I wanted to give people a chance to play with a Ruwiki
> 0.9.0 instance on RubyForge. One of the first things that you'll
> notice is that the edit buttons are *not* present on your initial
> visit, unless you have signed into RubyForge for the day.
nice, thanks
> Yes, I'm authenticating against the RubyForge user/session database.
>
> Cool.
indeed
Anyway, I don't think that editing a locked page should give this error:
Well, it is giving an error right now -- I may change that because in
the last days of editing Ruwiki 0.9.0 I added a non-error message
mechanism. I may change this before the final release today.
However, the lock error was a directory permission problem on
RubyForge and this has been fixed. A couple of other problems have
been fixed as well.
-austin
···
On Sun, 28 Nov 2004 20:57:52 +0900, gabriele renzi <rff_rff@remove-yahoo.it> wrote:
Austin Ziegler ha scritto:
> Okay, it's too early -- or too late -- to actually release this
> tonight, but I wanted to give people a chance to play with a Ruwiki
> 0.9.0 instance on RubyForge. One of the first things that you'll
> notice is that the edit buttons are *not* present on your initial
> visit, unless you have signed into RubyForge for the day.
nice, thanks
> Yes, I'm authenticating against the RubyForge user/session database.
> Cool.
indeed
Anyway, I don't think that editing a locked page should give this error:
Well, it is giving an error right now -- I may change that because in
the last days of editing Ruwiki 0.9.0 I added a non-error message
mechanism. I may change this before the final release today.
However, the lock error was a directory permission problem on
RubyForge and this has been fixed. A couple of other problems have
been fixed as well.
wonderful seems to work now.
Now, maybe there is a tiny problem /but maybe it is not) with wikiwords.
It seem that while non ascii characters are allowed in [[wikipedia style]] links they break when used with WikiWords. See Tutorial::SandBox for an example.
I guess it is hard/impossible to fix, due to how regexen works in ruby, but maybe it should be pointed out on the WikiMarkup page.
Also, since there is support for ruby-talk/core/dev specialized markup, maybe an RCR:<num> tag could be useful too.
