I'm about to shut down the wiki to switch over to a newer version of
MoinMoin. If you've made any changes in the last hour or so then they will
be lost (but it doesn't look like there have been any changes.) I'll send
another message when it's been switched over.
If you have pages in the wiki that have images on them then you will need to
make a change and upload the images again. (I had hacked in the attached
image support before, now it is a feature of MoinMoin.) I've put a copy of
the images that had been uploaded to the old wiki at http://wiki.wxpython.org/oldimages/ in case you don't have a local copy any
longer. To add an image to a wiki page just use this syntax:
inline:filename.ext
and save the page. If the image hasn't been uploaded yet then you will get
a link to a page that will let you upload it. If you want to reference an
image that is on a different wiki page then just do it like this:
inline:WikiPageName/filename.ext
This version has some cool new features too. If you put "#!python" at the
begining of your {{{ blocks then the code will be colorized as python code.
Also you can get email notifications of changes to pages.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
Any way to make the wiki default to _not_ sending messages on every update? Now that I've noticed that it's doing it, I suppose I can try to remember to un-check for the 99 times when I'm just testing to see if the update took, and to edit one last time to set it true.
It would convenient to just have it queue up a message saying "page X (and Y and Z) was/were updated" and send that at most once/day or so.
Anyway, for now will try to remember to un-check. Have fun,
Mike
Robin Dunn wrote:
...
This version has some cool new features too. If you put "#!python" at the
begining of your {{{ blocks then the code will be colorized as python code.
Also you can get email notifications of changes to pages.
Any way to make the wiki default to _not_ sending messages on every
update?
Use the "Preview" button, then there will be less backup copies of the page
too.
Now that I've noticed that it's doing it, I suppose I can try
to remember to un-check for the 99 times when I'm just testing to see if
the update took, and to edit one last time to set it true.
But then the diff's wont be shown in the email.
It would convenient to just have it queue up a message saying "page X
(and Y and Z) was/were updated" and send that at most once/day or so.
This version has some cool new features too. If you put "#!python" at the
begining of your {{{ blocks then the code will be colorized as
python code.
Also you can get email notifications of changes to pages.
There is a big problem with using the #!python formatting in that each line
is preceded by a line number. The line numbers become part of the selection
if you try and copy the code to use it in a script. If there was some kind
of "Script as text" link it would probably be okay. There might also be some
clever HTML that would allow the numbers to show, but not have the numbers
as part of the selectable text. I know IE does that for ordered and
unordered lists, but I don't know whether it can be made to happen
generically and work in other less popular browsers.
Patrick and I forwarded a note about the line numbers to the MoinMoin author
a month or two ago, but I don't think there has been any action yet. An
option to simply turn off the line numbers in MoinMoin would be best.
In the short term, the relevant lines can simply be commented out of the
MoinMoin sources. The relevant module is MoinMoin/parser/python.py and the
method that does the work is line_no(). So, by commenting out the calls to
line_no in the write method, the line numbers go away, but you still get the
source code coloring. In the 1.0 release of MoinMoin the relevant lines
where line_no is called are 69 and 77.
In the short term, the relevant lines can simply be commented out of the
MoinMoin sources. The relevant module is MoinMoin/parser/python.py and the
method that does the work is line_no(). So, by commenting out the calls to
line_no in the write method, the line numbers go away, but you still get
the
source code coloring. In the 1.0 release of MoinMoin the relevant lines
where line_no is called are 69 and 77.
I thought I might hack in an alternate parser that would do the same thing
without the line numbers and then you could choose if you wanted them or not
on each page... But since I couldn't do it in 20 minutes I gave up and just
commented out the lines. <wink>
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
From: Robin Dunn
>
> In the short term, the relevant lines can simply be commented out of the
> MoinMoin sources. The relevant module is
MoinMoin/parser/python.py and the
> method that does the work is line_no(). So, by commenting out
the calls to
> line_no in the write method, the line numbers go away, but you still get
the
> source code coloring. In the 1.0 release of MoinMoin the relevant lines
> where line_no is called are 69 and 77.
I thought I might hack in an alternate parser that would do the same thing
without the line numbers and then you could choose if you wanted
them or not
on each page... But since I couldn't do it in 20 minutes I gave
up and just
commented out the lines. <wink>
Just an FYI that I forwarded my note about the line numbers to the MoinMoin
list and Juergen has already updated MoinMoin in cvs with a version that
uses a table, so that the source is in its own cell and the text can be
selected without the line numbers. You can't just drop the new python.py
file into a 1.0 install since there have been other changes to MoinMoin
since the 1.0 release, but you can take advantage of the change if you
checkout from cvs.