Wikka : GmBowenWikkaAsPIM

• Categories
• PageIndex
• RecentChanges
• RecentlyCommented
• Login/Register
• Search:

Tools To Use Wiki As a Pim

One use of Wikka is as a Personal Information Manager. For some things the free-form writing nature of a wiki is useful (and, dare-I-say, liberating). However, as some of our usage at this site suggests, there are tools that can be developed AS actions in wikka that can make some aspects of information management a bit easier. In the past six months I've modified/developed two tools (with more forthcoming) with this purpose. One tool is a collection of actions so that schedules can be kept and organized on line. Its components include a "rapid entry" tool (scheduler.php, which should be kept on a page called ScheDuler), a monthly schedule view (monthschedule.php which should be kept on a page called MonthSchedule) and a day view (dayview.php which should be kept on a page called DaySchedule). A year-view calendar is also available at GmBowenCalendar. The other available action is a task manager (based on gbtask).

Task Manager

The task manager has two components. One is called mytasks.php which shows the task list of the logged in user. The other is a modified version called usertasks.php which can be used to look at the task list of other users.
http://gmbowen.educ.unb.ca/wikitest/taskmanager.jpg

Note that there is a function code conflict in the task manager that causes problems if two copies are put on one page. This will probably affect your "history" & "revisions" and cause them to "crash" (WSOD). Suggestions for dealing with this are found below...At my site I'm taking care of this by modifying the handlers/pages/history.php file. The history feature "crashes" because it essentially places two versions of the action on the page at the same time. I've taken care of this by having a search & replace done before the version comparison and replacing {{text}} with ||text|| for the sake of differences being shown in the history depiction. This is done by adding the following lines to the history.php file.....

++
++              $bodyB = explode("\n", $pageB["body"]); //add following three lines++
++$brackets = Array ('/{{/i', '/}}/i');++
++$changeto = '||';++
++$bodyB = preg_replace($brackets, $changeto, $bodyB);++
++

and

++
++               $bodyA = explode("\n", $pageA["body"]); //add the following three lines++
++$brackets = Array ('/{{/i', '/}}/i');++
++$changeto = '||';++
++$bodyA = preg_replace($brackets, $changeto, $bodyA);++
++

I'm sure a similar trick will work with revisions.php, but I haven't figured it out yet.

See a more graceful solution than the above as suggested by the combination of Nils & DarTar (which involved putting

before the code (closing it with a } of course) at WikkaForum.

I'll keep working away at trying to figure out why this conflict happens.......it might be the functions defined in the code & a conflict between them....and if it is I'll try and move them to wakka.php. In addition, I'm going to develop a textbox/submit button feature so that the galleries of different users can be seen without having to multiply edit/save the page. Feel free to play with this yourself.

Save the below code as mytasks.php and place in the actions directory

The following code is for usertasks.php which should be placed in the actions directory...it allows you to look at others' schedules

Ultimately, it is intended that a text entry box and a submit button will be added to this code for entering user names so the schedule of any user can be easily obtained without editing the page.

Remember, neither of these can be on the same page at the same time, nor can there be more than one copy of these on any one page....consider yourself warned. As Nils points out below, this is a function code problem....

(see WikkaForum for an example of how to include these functions in wikka.php....wrapping them in a class (as in that example) may offer some advantages. -- GmBowen)

And, of course, you need to create a new table in your database....

---

Scheduler

Scheduler is an action which allows a person to keep a day calendar (or diary for that matter). Although the entry formatting is simple, at the same time it provides flexibility. A user can enter a day schedule.....


or use it to keep a to-do list, or even a diary for the day. The schedule for a day can be viewed with the entry tool, in the monthly view, or in the day view. The day viewer is formatted for printing out usable schedules, & you can designate a specific user with it and see somebody else's schedule (I intend on modifying this so that there will be an easy-to-use text entry box for entering user names).
http://gmbowen.educ.unb.ca/wikitest/scheduler.jpg
Code for table in data base.....

below code added to actions directory as scheduler.php. The action should be placed on a page called "ScheDule".

The following is the action which shows a formatted output for a selected day....the current day (by default) or for any other day (using a link from the scheduler.php & monthview.php actions)....it should be saved into the actions directory as dayschedule.php and for proper functioning with scheduler.php should be placed on a page called DaySchedule.

This is a screenshot of the dayschedule.php output...
http://gmbowen.educ.unb.ca/wikitest/dayschedule.jpg

This final action show a month-view with all of the entries. It should be saved into the actions directory as monthscheduler.php and for proper functioning with scheduler.php the action should be placed on a page called MonthSchedule.

The following is a screen shot of the monthscheduler.
http://gmbowen.educ.unb.ca/wikitest/monthview.jpg

All of the functions on this page user a "bad word function" that is placed in the wakka.php file in the wiki root directory. The following code needs to be placed in the wakka.php file (just after the microtime function which starts "function getmicrotime" and ends with a "}". This code is placed immediately after the "}".

---

CategoryDevelopment