The searching is almost done (it searches and highlights the results), but while I was polishing things, I introduced a bug I've not been able to repair yet. I'm getting a NullPointerException from a line of code that is almost the same as before. It is one of those bugs you end up thinking if your computer is pulling your leg.
For improving the contributions-experienceTM I've added to the home page a text that says if you have made any contributions (which are not uploaded yet) or explains a little bit how to make a contribution. The point is that I wanted a list with links to all the contributions, but that was more difficult to obtain than I thought. The information being saved with every change was not enough to get those links, so I've added a nice URL to every change being saved in chageset.xml.
The problem is that the Urls in monodoc are a little weird. In the case of ecma documentation, if you click on the TreeView, you get something like ecma:10#Array/ while through the links you get T:System.Array. Depending on the place you are working you use one or another (although they point to the same doc), adding some confusion to the internals of the program. To get my desired list I've written a new method that figures out the nice url T:System.Array when it is not available. The results here:
The thing is that, in my opinion, we should revise the internals of monodoc at some point, because the design is sometimes limited or confusing. I don't mean a rewrite of the program, but a reorganization, localizing the points where we are doing almost the same thing (two different urls pointing the same doc for example) in slightly different ways and looking for a design that facilitates more the manipulation of documents.
Tomorrow, the contributions-experienceTM patch will land the mailing lists. Stand by. Now is time to sleep.
No comments:
Post a Comment