Posted by Gordon P. Hemsley on April 18, 2009
During our last status meeting, I brought up the issue of people not taking tabs (and the fact that they are variable-length characters) into consideration when coding new features that require text manipulation. As a result, I was asked to write a little tutorial on the wiki to help explain the situation to those not familiar with the code.
Take a look at the article. It starts by giving a little background information about the issue. It then makes note of which functions are expecting to be fed
modelPos, rather than
pos. It then goes on to explain how to obtain the proper position value and other things related to the fact that tabs are variable-length, based upon where they are in a line.
This article outlines the tools that one needs in order to properly consider tabs in text. However, it does not necessarily give step-by-step instructions on how to properly use the code; it has no examples. Is it clear enough to use? Or is there still confusion as to what to do?
Please leave me feedback here, and I’ll make any changes that are necessary to clarify things better. (Alternatively, you could make the edits yourself—it is a wiki, after all—but I wouldn’t necessarily recommend that. I mean, I am the one that wrote the original code…. You know, just saying.)
Posted in Mozilla | Tagged: Bespin, characters, coding, comments, conference call, feedback, Mozilla, MozillaWiki, RFC, status meeting, tabs, text, tutorial, wiki | Leave a Comment »
Posted by Gordon P. Hemsley on April 13, 2009
A lot has happened since I last blogged about adding real tab support to Bespin. Since then, my code was merged into the main repository and things have taken off. I later tore apart a huge chunk of Bugzilla by way of sorting through and updating a lot of the old bugs, many of which had been on the books since before Bespin went public, or had been fixed a long time ago. I still have not sorted through all of them, and there are probably still a number of open bugs that fall into that latter category.
Since appointing myself the de facto Issue Manager (hat tip to amotsjonov for the link), I have been watching the incoming bugs like a hawk, and have determined that using the whiteboard to organize bugs has already become too unwieldy. Bespin needs to pop itself out of the Mozilla Labs product so that it can have components of its own. So I’ve filed a bug to that effect. I hope it will get approved and put in place soon, so that I can really attack all of the remaining unloved bugs and narrow down the focus of what there is to do.
Last week was also the first Bespin Status Meeting. After some technical difficulties getting our more foreign correspondents into the call, it went well. We discussed the near and far future of Bespin and what we plan to do. April is dogfood month, so we’re going to have to sort out the most glaring bugs and get the most important features implemented. That way, we’ll be able to use Bespin to edit Bespin. I’m looking forward to it.
Our next meeting is tomorrow. Though the agenda is not quite set yet, I do hope to discuss how things are running, and how to get them running even more smoothly. Perhaps I will chime back in after the meeting with more details.
Posted in Mozilla | Tagged: amotsjonov, April, Bespin, bug, bug triage, bugs, Bugzilla, Carl Fogel, conference call, conference calls, dogfood, issue manager, Mozilla, Producing OSS, status meeting, status meetings, tabs | 2 Comments »