Re: [Phpwiki-talk] Re: Development on phpwiki

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

Dan Frankowski schrieb:
> Reini Urban wrote:
>> Dan Frankowski schrieb:
>>> - Sorting on the PageList widget 
>> sortby=rating? ok.
> 
> Not exactly. Two things here so far:
> 
> 1. We need to sort on things not in the DB (e.g., predicted value). 
> Thus, I am adding sorting of pages in memory based on 
> column::_getValue() (incidentally for any column, which is nice).
> 2. We need multiple columns of the same type (e.g., 'ratingvalue' type 
> for my buddies A, B, C, D, etc. on the same PageList).

Ok. Sorting as generic slow PageList method, to be able to sort on every 
column. Even better.

> I have been delaying my reply until I have posted some code for this on 
> WikiLens, but it's going slower than I'd hoped, so I'm replying without 
> code in order to give you a heads-up. 2 is more challenging-- it 
> requires identifying column by something other than name or type. Right 
> now, I am trying to convert the code so it can still use the name, but 
> immediately translates it into column # (0, 1, 2, 3, etc.) for the 
> purposes of button headings specifying sorting. I'll post this as soon 
> as I can.

>>> - others will arise (e.g., things in PageList, making categories more 
>>>   "natively" supported in Phpwiki, etc.)
>>
>> This is new to me. Can you describe this?
>> Do you mean dynamic categories? We had some kind of patch for this 
>> feature some years ago. page : category relation in the database.
>> Other wiki's tried that also.
>> We didn't like that. We thought that manual fixes (links at the bottom 
>> of each page) and backlinks are easier, just the engine should support 
>> the needed features people are proposing.

> 
> Unfortunately, I cannot be specific yet. I don't think we understand 
> what we want. I'll just say that a category is looking more and more 
> important to me. Random thoughts:
> 
> 1. Imagine recommending movies versus sodas. Each of those 
> recommendation "domains" is so different, you might want the recommender 
> to act different in each.
> 2. If ActionMovie is a subcategory of Movie, you might want traits of 
> Movie (e.g., structured data fields) to 'inherit' from the Movie category.
> 3. You might want to get notification whenever a new item enters or 
> leaves a particular category (which is different from page-level 
> notification).
> 4. Category-level modification time (when's the last time someone 
> changed something in this category?).
> 5. List all category pages (currently: pages with the CategoryPage plugin).
> 
> These are ideas floating around category that make it look pretty 
> important. Only 3 and 4 are concrete. Not sure if the back-links is 
> enough to support  this stuff eventually.

Well, this sounds like wikilens extensions to existing plugins.
I would rename them then.

We currently have subpage and category pagegroups. Maybe seperate 
indexing and queries (also search) for page groups will be useful.
But we haven't spoken about so far.

>>> Thus, I would be interested in hearing more from you about how you 
>>> think of the Phpwiki development process. That is, what should I keep 
>>> in mind to make my work most likely to be accepted by the Phpwiki 
>>> team? How can I best help out the Phpwiki team, given my interests?
>>>
>>> This sort of thing might include just plain knowing more about you or 
>>> other Phpwiki developers. Possible examples:
>>>
>>> - How much time do you devote to it?
>>
>> Currently full time. In the near future about 4 hrs a week. Not as 
>> less time as in the last two years for sure.
> 
> What does this mean? Why currently full time? 

Because I quit working full-time in Oct 2003, and will start soon again 
full-time. Now I do work half-time.

 > Why 4 hours/week later?

Because my new job will give me more free time than the last one, which 
exhausted me.

>>> - What is the team style?
>>> - What development processes do you think work well?
>>> - Where could there be improvement?
>>> - How would you like to grow the Phpwiki development team so that it 
>>>   can make faster progress?
> 
> Er .. okay. I think there are advantages to each, but I respect your 
> preference. So what do you think of the development process (i.e. 4 
> questions above)?

Just send patches for the beginning.

>>> I would be eager to help where I can. I am not entirely useful, 
>>> though. For example, unfortunately, I do not know the code or 
>>> functionality as well as you or other developers, so I cannot take 
>>> over documentation.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/