Re: Package Abstracts

On Thu, 2004-11-18 at 21:07, Paul M Jones wrote: > Helgi Þormar wrote: > > On Thu, 2004-11-18 at 20:43, Martin Jansen wrote: > > > >>On Tue Nov 16, 2004 at 10:5932PM +0000, Helgi Þormar wrote: > >> > >>>On Tue, 2004-11-16 at 22:37, Paul M Jones wrote: > >>> > >>>>I have volunteered in the past, and will continue to do so on a > >>>>standing basis, to set up a YaWiki > >>>><http://yawiki.com> installation for > >>>>pear.php.net. > >>> > >>>We want to integrate this into pearweb thus we can't use yawiki (well > >>>okey we don't want to use it because of the deps outside of pear, > >>>specially because of yawp) > >> > >>Who said that? I for one would be very delighted to set up Paul's wiki > >>on e.g. wiki.pear.php.net - this way the wiki does not need to inherit > >>any code from the website, and at the same time the wiki can use the > >>existing user table for authentication. (Killing two birds with one > >>stone.) > > > > I'd assume if we were going to integrate it it would be kinda funky to > > have 2 frameworks, i.e. Yawp and Damblan, integrate I mean not just by > > placing yaWiki in some folder on the server, but well have it as you > > like. > > Not to nitpick, but Yawp is not a framework (at least I don't think of > it as such). I call it a "foundation" on which you can base apps of any > sort; except for some glue-code to automate authentication and > object-creation, it's really just a bunch of PEAR classes aggregated > behind a static interface class plus a unform configuration file. I > attempted to make it solution-agnostic; you can use it to write up MVC > solutions or standalone monolithic apps. Hmm yeah I know, misused that word, Damblan isn't either a framework in a way. > > > If we get some features to work with yaWiki (not doubt out that we will > > be able to do so) then I'm fine with having it. > > (features I mean by little things as #342 turn into a bug link and etc, > > maybe even a roadmap "module" if I find the time to write such for > > pearweb.) > > The Bug link thing is even easier thank you think. One example is to > treat the word "Bug" as an interwiki keyword. In the Yawp.conf.php > file, you would add: > > [yawiki] > interwiki_site = Bug, http://pear.php.net/bugs/bug.php?id=%s > > Then Text_Wiki will automatically translate the text "Bug:2228" as a > link to http://pear.php.net/bugs/bug.php?id=2228 -- no > programming > involved, just a change to the config file. :-) I see, never was sure what those interwiki things were anyway :) but can it do like something similar to this, #4353, and not changing #foo into a link, i.e. kinda yes just allowing numbers through that config ? - Helgi