Archived DevDiscussion?.


comments:

Skins kapoot? --DeanGoodmanson, Fri, 07 May 2004 07:21:24 -0700 reply
Noticed on the preference pages that there's no longer an option to choose a different skin. Guess this feature didn't make it past the experimental phase?

Skins kapoot? --simon, Fri, 07 May 2004 09:33:27 -0700 reply
It was just a zwiki.org demo.. in moving from a skinned folder to a btree folder we lost that ability, the other skins were out of date/not working and not used afaik.

spam ? --simon, Sun, 09 May 2004 07:58:53 -0700 reply
Someone keeps adding these to the front page on zwiki.org & zopewiki. I think they are spam - can someone out there tell more ?

http://www.emmss .com http://bbs.qqfans .com

my stability problems --BillSeitz, Mon, 10 May 2004 14:09:31 -0700 reply
see bottom of BillSeitz:ZwikiFreebsdStabilityProblems

there were 53 crashes yesterday: error codes 6, 10, and 11

Ideas? (problem started mid-April - had not made any code changes - maybe hitting a threshhold of size?)

FIT work noted on Daily-URL --DeanGoodmanson, Tue, 11 May 2004 06:42:27 -0700 reply
Congrats! http://www.pythonware.com/daily/

my stability problems --simon, Tue, 11 May 2004 07:47:42 -0700 reply
Hi Bill.. you saw my reply, right ? I just happened to pass by yesterday.

my stability problems --BillSeitz, Tue, 11 May 2004 09:59:44 -0700 reply
your reply when/where? (imeme has boosted my memory allocation, and we'll see if that changes things after a day...)

Gadzooks, more referrals --DeanGoodmanson, Tue, 11 May 2004 22:34:02 -0700 reply
Todd Ogasawara over at O'Reilly blogs has noted Zwiki a one of his favorite Zope products. link ... and that post was also Daily-URL'd!

Gadzooks, more referrals --Simon Michael, Wed, 12 May 2004 06:41:45 -0700 reply
Hurrah! Thanks Dean.

link banning implemented --simon, Thu, 13 May 2004 23:00:19 -0700 reply
Repeated link spamming is becoming a problem on this and other wikis.. text edits containing banned urls - bbs dot qqfans dot com etc. - will now raise an error. These are regular expressions in a banned_links lines property on the folder.

link banning implemented --DeanG, Mon, 17 May 2004 12:07:35 -0700 reply
Nice

I've seen a number of "erased" and deleted pages lately. I'd like to post these page names as request for status somewhere. Could you direct me to a page? Latest page is AdvancedEditOptions?

Top google hit for dtml-in --DeanGoodmanson, Mon, 17 May 2004 15:48:41 -0700 reply
Nice Zwiki summary of the joys of wiki and journey of dtml by [Paul Hammond]? http://www.paranoidfish.org/notes/2003/12/04/1904

Master Catalog joy --DeanGoodmanson, Mon, 17 May 2004 15:59:33 -0700 reply
I've figured out how to copy a Zwiki catalog to Zope's root server, then re-catalog and find every wiki page within all my SubWikis...and searches work.

Q: How can I get this catalog to automatically find new pages as they are added?

Master Catalog joy --Simon Michael, Mon, 17 May 2004 18:36:45 -0700 reply
If all goes well.. put your master catalog's id in a SITE_CATALOG property on the root folder and all wikis should use that one.

(runs for cover)

Top google hit for dtml-in --Simon Michael, Mon, 17 May 2004 18:43:23 -0700 reply
Yes that is nice, thank you chief scout. We should link it somewhere.. not sure where right now..

link banning implemented --Simon Michael, Mon, 17 May 2004 18:45:51 -0700 reply

I've seen a number of "erased" and deleted pages lately. I'd like to post these page names as request for status somewhere. Could you direct me to a page? Latest page is AdvancedEditOptions?

Sorry, how do you mean ? Not RecycleBin? ?

--befuddled

link banning implemented --DeanGoodmanson, Mon, 17 May 2004 21:37:15 -0700 reply
Primarily pages that show up in the RecentChanges? that when viewed, have no content...and when browsing through the diff screens show no sign of vandalism.

Master Catalog joy --DeanGoodmanson, Mon, 17 May 2004 21:39:28 -0700 reply
That sounds OK..but I'm hesitant to give up the existing wiki-specific Catalogs. I'd like the local and master to be updated.

Rss2 page type --DeanG, Tue, 18 May 2004 10:55:53 -0700 reply
Simon - Would you turn off EPoz? on the RSS2 page? I'd like to add the summary() method within the description element but cant edit it in plain text mode.

Inspired by Ian's comment here

Rss2 page type --Simon Michael, Thu, 20 May 2004 13:37:20 -0700 reply
DeanG wrote:

Simon - Would you turn off EPoz? on the RSS2 page? I'd like to add the summary() method within the description element but cant edit it in plain text mode.

Now I see what you mean. I think that page has to be HTML mode to work. See http://zopewiki.org/ZopeWikiRSS for a different solution using a helper dtml method.. this is the most up-to-date zwiki rss work AFAIK.. I am not clear where it all is at though.

tracker tweak --simon, Sun, 23 May 2004 23:34:33 -0700 reply
I've removed the big OPEN/TOTAL counts that were at top-right of IssueTracker. Better or worse ?

tracker tweak --simon, Thu, 27 May 2004 13:50:23 -0700 reply
Also the tracker defaults to open and pending, rather than recent. Better or worse ?

alt-r shortcut --DeanGoodmanson, Thu, 27 May 2004 14:26:15 -0700 reply
Jut a quick note that the embedded RSS reader in Firefox (and Mozilla?) uses Alt+r to open the side bar. I'm not sure it's a concern, but wanted to mention it.

Re: zwiki i18n/l10n coordination --Simon Michael, Thu, 27 May 2004 14:28:27 -0700 reply
Simon Michael wrote:

How do we reach everyone involved in zwiki i18n/l10 when we need to ? How do we scale as more people get involved ?

Aside from IRC, my suggestion at the moment is that everyone should subscribe to http://zwiki.org/InternationalisationDiscussion or at least check it once in a while, if they're not already subscribed to the whole wiki. That's where I would usually post things of interest.

I'm open to any other ideas, if you have one, please post there so we can all discuss.

I'll cc this to DevDiscussion? for anyone I've missed.

Thanks! -Simon

Re: Subclassing/extending ZWikiPage --Simon Michael, Thu, 27 May 2004 18:30:28 -0700 reply
Edoardo ''Dado'' Marcora wrote:

Wouldn't it be possible by eliminating all the dependencies on self.meta_type in ZWikiPage (a other scripts) such as:

def pageObjects(self): """ Return a list of all pages in this wiki. """ return self.folder().objectValues(spec=self.meta_type)

Maybe ZWiki should consider not only ZWikiPages? but also any product that would implement a ZWikiPage-like interface. Maybe the filtering should be done on a property (defined in the interface) like .isZWikiAware or something like that.

I am not much of a programmer (I am a neurobiologists with little programming experience) but you would knowk for sure if this is at all possible.

Thanx for your interest,

Dado

----- Original Message ----- From: "Simon Michael" <simon@joyful.com> To: "Edoardo ''Dado'' Marcora" <marcora@caltech.edu> Sent: Thursday, 27 May 2004 8:23 Subject: Re: Subclassing/extending ZWikiPage

Hi Edoardo.. if you know how, we are certainly interested. Cheers.

editing errors --Bob McElrath?, Fri, 28 May 2004 12:37:43 -0700 reply
So someone ran /clearCache on one of my pages last night (Simon, was it you)? Which resulted in a latexwiki-generated page error. (I am having difficulty tracking down exactly what in that page generated the error...)

It seems that when a page generates an error, editing that page does not occur properly. After editing I am redirected to a page like http://site/page/ (note trailing slash), which gives the error again. Going to http://site/page (no trailing slash) gives me an old version of the page.

This is all related to pre-rendering, I think. Have others observed this? I will try to track this down this weekend perhaps.

editing errors --simon, Fri, 28 May 2004 12:49:21 -0700 reply
No, not me.. unless I was sleep-surfing again..

I am also being bugged by page rendering errors lately, eg from unquoted dtml. Yours was not a dtml error I take it.

I think it would be best if the page and skin always rendered no matter what, so that it's at least easy to get in and edit. I thought of quoting all dtml or just hiding the entire page content when there is a dtml error. One drawback is this might be less informative when you are editing and trying to get some dtml just right.

editing errors --Bob McElrath?, Fri, 28 May 2004 12:58:44 -0700 reply
simon [zwiki-wiki@zwiki.org]? wrote:

No, not me.. unless I was sleep-surfing again.. =20 I am also being bugged by page rendering errors lately, eg from unquoted dtml. Yours was not a dtml error I take it.

No it was a regex recursion error in my code, triggered by some (as-yet-unknown) text on the page.

I think it would be best if the page and skin always rendered no matter what, so that it's at least easy to get in and edit. I thought of quoting all dtml or just hiding the entire page content when there is a dtml error. One drawback is this might be less informative when you are editing and trying to get some dtml just right.

A more general error mechanism is probably in order. Consider how LatexWiki does it: when there is a latex error, the page is quoted (<pre>) with an error in red at the bottom.

What if we expand the concept of page-rendering errors and treat them all uniformly, whether it's a zwiki/latexwiki code error, dtml error, latex error...catch the exception and display source with an error message, rather than letting zope give its (useless) error page. Zwiki error pages should preserve the zwiki header/footer so that useful links like "edit" and "diff" are still there.

In some cases it may be possible to mark up the source to indicate the position of the error. (This is certainly possible for latex...dtml too? If you catch a dtml exception does it give a line number?)

Furthermore, comments should be treated as seperate documents so that a comment can't hose an entire page. How about edit links for each comment? Would that be cumbersome? Maybe editing the main page would show only the page and not comments?

editing errors --simon, Fri, 28 May 2004 13:04:38 -0700 reply

No it was a regex recursion error in my code, triggered by some (as-yet-unknown) text on the page.

Ah.. freebsd python bites again ? Maybe you can tweak the offending regexp to make it less expensive (or do without it).

A more general error mechanism is probably in order. Consider how LatexWiki does it: when there is a latex error, the page is quoted (< pre>) with an error in red at the bottom.

Agreed, I'll look at how you do it.

So far, storing comments as part of the page text is the simplest thing that could possibly work.. it simplifies searching for example. They do get individually rendered though, so we could just do similar error handling for each comment.

Re: Subclassing/extending ZWikiPage --simon, Fri, 28 May 2004 13:11:51 -0700 reply

Maybe ZWiki should consider not only ZWikiPages?? but also any product that would implement a ZWikiPage-like interface (eg in pageObjects)

Yes that seems like a way to go. What would we mean by the Zwiki interface, though. I think defining that would be the first task. The zope 3 zwiki implementation might be a good starting point. I have no concrete need for this at the moment, and it's hard to envision what it would bring in practice - meanwhile I'll support anyone that wants to work on it.

Re: Subclassing/extending ZWikiPage -- Fri, 28 May 2004 16:48:22 -0700 reply
In my mind I envision ZWiki to become more of a versatile knowledge-base which could contain anything (structured or not) ranging from bibliographic references to information about genes and proteins (I am biologist... therefore I am little biased ;). I envision the ability of subclassing ZWikiPage as a way of supporting structured documents/objects (e.g., bibliographic references) which also supports specialized behavior (e.g., downloading of bibliographic information from online databases). Any type of content that can be described as a Zope product could use the ZWiki-way of linking/organizing resources which I found very clever... the problem is that not everything can be efficiently represented as free-form text. Just my two cents. (p.s. I will think about the interface and get back to you!). Thanx :)