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

* Your Email Address
* Spam protection	Enter the letters below: .___..__ .___.. ..__. \| [ __ _/ \|__\|\| \| \| [_././__.\| \|\|__\|
Comment	> 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?
Attachment
Watch this ticket

Saved Queries