Thinking about meta-data —!!3!! >Thinking about meta-data —!!4!! —!!5!! Which kind of metadata were you thinking of? Could something like a certain action for a particular page be part of it? Those could be seen as properties of a page: for example one could execute contents in the page if a property meaning there’s dynamic code inside is set. Could it be feasible? Or is it a path towards complexity you wouldn’t like to take? (I’m thinking something along the lines of properties for a !!1!! page.) — Giulio Piancastelli —!!6!! —!!7!! I was thinking about the ability to associate arbitrary data with a page, currently along the lines of a key value hash. The only real need for it at the moment would be to store the number of times the page has been viewed, but I imagine there could be uses for it in terms of authentication and for automatic helper classes to tag particular pages as of interest. !!8!! —!!9!! The dynamic code thing like Fitnesse is allready more or less feasible. You could write a helper class that watches for page revisions, checks whether they contain a test table, and if so modify it to reflect the results of some tests. What is missing is a way for the user to notify a helper class (like the test button in Fitnesse), so currently it would have to run periodically (every minute or hour or whatever, or it could watch a cvs in some fashion). — tamc !!10!! —!!11!! Yes, sorry not to have been more precise. What I found interesting was exactly the idea of having a user deciding if something like a test button must appear in a page using a property. The action behind the button does not need to be linked to an helper class in the Soks package or an external class; could be a simple CGI script also. (See the !!2!! for examples on this.) But what’s important is the presence of some kind of basic infrastructure in the wiki to allow users specify certain actions to be linked to particular (classes of) pages. —!!12!! —!!13!! Ok. That sounds possible. What I’m wondering is whether the same effect would be easier with some form of code word or special markup that the user puts in the page (e.g. [ [insert a test button] ]), rather than using meta-data? !!14!! —!!15!! I’d like an approach leading towards separation of concerns: markup seems to be about content, not actions you can perform on the content itself. Indeed the user must be able to associate one or more actions with a page: I was thinking about a dropdown in the edit view to select a single action, or checkboxes to activate more actions for the page being edited. —!!16!! In order to get going with the meta-data I need to decide on the —!!17!! > —!!18!! File format —!!19!! !!20!! How it links to a page —!!21!! !!22!! Should it have a history / be undoable? !!23!! !!24!! Should it only be programmatically accessible, or should there be a user interface —!!25!! —!!26!!
Edit this page or watch for changes using RSS.