[Tickets #6767] Re: Make (optionally) all multi-line text entry blocks as wiki pages with links to other horde modules

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/6767
------------------------------------------------------------------------------
  Ticket             | 6767
  Updated By         | Chuck Hagenbuch <chuck at horde.org>
  Summary            | Make (optionally) all multi-line text entry blocks as
                     | wiki pages with links to other horde modules
  Queue              | Horde Framework Packages
  Version            | HEAD
  Type               | Enhancement
-State              | Accepted
+State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Chuck Hagenbuch <chuck at horde.org> (2008-07-17 23:09) wrote:

This code will give you all apps that implement show methods:

         foreach ($GLOBALS['registry']->listAPIs() as $api) {
             if ($GLOBALS['registry']->hasMethod($api . '/show')) {
                 ...
             }
         }

(well, it will get you the 'provides' name for those apps). I think we  
need to do some work for this feature to be really useful. The show  
api method isn't really appropriate for this because it requires named  
parameters, which would be awkward:

task:id=2
task:id:2

etc.

I think what we really want is something like path-based browsing,  
with slugs, and to have slugs auto-generated where reasonable for the  
groupware apps. Calendars tend to have the same thing a lot, so that's  
tricky, but we could replace spaces with - in task and note names to  
get a reasonable guess. Combined with named shares... but you can see  
this is a bunch of changes.

For bugs it's simple:

ticket:id

now that we have queue slugs:
ticket:queue_name could probably be recognized also, though we'd be  
unable to distinguish ticket ids from queues with all-numeric slugs  
(my not-so-unreasonable example for this was a photo gallery named  
"007").

for wiki pages too, since they by nature have full slugs:

wiki:SoAndSo

could be easy for photo galleries since we have slugs there now:

photos:Baby-Pictures

etc. Any of those look good/right? Better ideas?