phpwiki-talk

[Phpwiki-talk] new member pmeignen

[Reini U. <ru...@x-...>]

I gave Pierrick Meignen (pmeignen) cvs access to maintain his files.

locale/fr
locale/po/fr.po
lib/plugin/TeX2png.php
pgsrc/TeX2pngPlugin

He completely rewrote the french locale, all french pages and a new 
simplified TeX2png plugin (using its own cache technique, not via 
getimg.php).

French is now together with german  - and english of course - the only 
language which is 100% feature complete.

Welcome on board!


PS:
I'm considering this for DanFr as well, but at first I have to decouple 
the wikilens specific stuff more from our core.
This will affect lib/wikilens, lib/plugin/RateIt, and themes/wikilens.
And I don't have that much time yet to integrate their huge changes 
right now. Still 2 remaining fatals to catch.
-- 
Reini Urban
http://phpwiki.sf.net/

Re: [Phpwiki-talk] new member pmeignen

[Dan F. <dfr...@cs...>]

Reini Urban wrote:

> PS:
> I'm considering this for DanFr as well, but at first I have to 
> decouple the wikilens specific stuff more from our core.
> This will affect lib/wikilens, lib/plugin/RateIt, and themes/wikilens.


Reini,

We'd also like very much to be decoupled, it's just not been highest on 
our list. Hearing your thoughts would be appreciated.

We will probably not keep everything in lib/plugin/RateIt.php, because 
we will want separate files for organizing code. (Imagine stuffing all 
of lib into one file!). However, we'd be happy to keep our stuff in a 
separate place, perhaps all in lib/wikilens, or lib/plugin/wikilens. Let 
us know any opinions.

Also, eventually we will pull our stuff out of WikiDB into separate 
files. I agree with you that a RatingsDB can be completely separate from 
the page DB (although maybe defaulted the same).

Also, a question about themes/wikilens. Mike is currently working on 
making it work for us and removing duplicate code from other places. 
However, does that mean that our users (who will want ratings widgets 
for example) can't choose other themes? That seems too bad. Maybe it 
would be cool to have a hook into a 'default'-theme-like place that 
could show up in lots of different themes. This is not a high priority, tho.

Much higher priority is getting the user login, account creation, and 
password management really smooth.

Also, for us, we are interested in versioned "structured data" (fields 
like author and title for a book, location and cost for a restaurant, 
etc.). I will send out a proposal for that soon. For those who are 
worried I am trying to turn Phpwiki into some generic groupware, I say: 
no, versioned (wiki-able!) structured data could be generically useful 
in MANY different domains, plenty of which have nothing to do with 
WikiLens, and it is still very wiki-flavored.

> And I don't have that much time yet to integrate their huge changes 
> right now. Still 2 remaining fatals to catch.


I think it's fine that you postpone integration for more important, core 
things. Making the user stuff really smooth, easy, and reliable would be 
great.

Dan

[Phpwiki-talk] wikilens integration

[Reini U. <ru...@x-...>]

Dan Frankowski schrieb:
> Reini Urban wrote:
>> PS:
>> I'm considering this for DanFr as well, but at first I have to 
>> decouple the wikilens specific stuff more from our core.
>> This will affect lib/wikilens, lib/plugin/RateIt, and themes/wikilens.

Dan, I added now your lib/PageList.php to CVS,
and will soon cvs add lib/wikilens, where you should put your extensions.

I fixed a couple of things, please have a look.

I'm also attaching my versions of your wikilens libs,
but these are not tested yet.

> We'd also like very much to be decoupled, it's just not been highest on 
> our list. Hearing your thoughts would be appreciated.
> 
> We will probably not keep everything in lib/plugin/RateIt.php, because 
> we will want separate files for organizing code. (Imagine stuffing all 
> of lib into one file!). However, we'd be happy to keep our stuff in a 
> separate place, perhaps all in lib/wikilens, or lib/plugin/wikilens. Let 
> us know any opinions.
> 
> Also, eventually we will pull our stuff out of WikiDB into separate 
> files. I agree with you that a RatingsDB can be completely separate from 
> the page DB (although maybe defaulted the same).

I seperated a RatingsUser file.

> Also, a question about themes/wikilens. Mike is currently working on 
> making it work for us and removing duplicate code from other places. 
> However, does that mean that our users (who will want ratings widgets 
> for example) can't choose other themes? That seems too bad. Maybe it 
> would be cool to have a hook into a 'default'-theme-like place that 
> could show up in lots of different themes. This is not a high priority, 
> tho.

They can use other themes, but they have to customize them.
As the whole wikilens theme is just a customization of the default 
theme. Just add some hooks.

More on this later.

> Much higher priority is getting the user login, account creation, and 
> password management really smooth.
> 
> Also, for us, we are interested in versioned "structured data" (fields 
> like author and title for a book, location and cost for a restaurant, 
> etc.). I will send out a proposal for that soon. For those who are 
> worried I am trying to turn Phpwiki into some generic groupware, I say: 
> no, versioned (wiki-able!) structured data could be generically useful 
> in MANY different domains, plenty of which have nothing to do with 
> WikiLens, and it is still very wiki-flavored.
> 
>> And I don't have that much time yet to integrate their huge changes 
>> right now. Still 2 remaining fatals to catch.
> 
> I think it's fine that you postpone integration for more important, core 
> things. Making the user stuff really smooth, easy, and reliable would be 
> great.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/