I didn't consider that, but I will. I think moinmoin has the advantage
of more examples to refer to. I'm still quite new this and using
pydiddy is an atttractive idea, but I'm not sure I'm up to it.
The integration with webware is really cool but there are some features
I'm going to need. Already mentioned the searching. I need to be able
to select all or some pages and print them. I think the way to do this
is to return the pages all sequentially, on a single page and then use
the browser print command. There is a zope solution like that for
zwiki. I also need to easily import images viewed inline. And produce
pdf output as well. Is there support for tables? reStructuredText?.
I'm really going to look hard at pydiddy and see if I may be biting off
more than I can chew. Thanks for the idea.
>On 10/11/02, from the brain of Frank Barknecht tumbled:
> Michael Montagne hat gesagt: // Michael Montagne wrote:
> > The application is an office manual. About half the pages are free form
> > text I'd like to be served by moinmoin to be easily updateable and
> > easy to add more pages. But the other half will be served from a
> > database using MiddleKit(things like checklists and layer lists).
> > The whole thing needs to be able to be printed or selected chapters
> > printed. And searched.
> Did you consider developing all your needs inside Webware? There
> already are two Wikis for WW available, Ian's Wiki and my PyDiddy.
> Ian's code is much more modular than mine, which could be a blessing
> or a curse, depending on what you want to do. I think, mine is easier
> to grok, but, well, I'm biased... PyDiddy is easier to set up though...
> > I'm really not sure if this is the right approach cause it's not clear to
> > me that the db served pages will be searched by moinmoin like I need
> > (full text search).
> I think, moinmoin just 'greps' through the Page files, so you'd need
> to add SQL/MiddleKit-code to your search function anyways. This also
> might be easier, if the search function would be inside one of your