On 23/11/2011, at 6:02 AM, Luke Daley wrote: > > On 22/11/2011, at 6:50 PM, Adam Murdoch wrote: > >> Can we default to dsl? This should be the most common case. > > We need some kind of prefix. We were matching too much, e.g. FQCNs in pasted > in logs.
ok. > >> One problem with coding the type is that it doesn't pick up changes to >> either the code or the documentation (ie something that used to have only >> javadoc gets added to the dsl reference). The doc generation stuff k nows >> which type of link to use for the <apilink> tags. I wonder if we could >> publish this meta-data somewhere for the forums to use? > > Potentially. It needs to be fast, which means JSON. > > Given the potential size, we may also need to do use html5 client side > databases to avoid having to have the client load the whole data structure > across the wire *every page*. > > The other alternative is to create a smart “jump off” page, that redirects to > the appropriate place. This would move the heavy lifting to the server side. > This is probably a better idea. A much better idea. Then we can have permalinks to the documentation for a given type. Which means we could (relatively) safely include them in error messages and generated reports and so on. And probably some other nice stuff, too. This something that might be good to bake into the plugin portal. -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
