By Geertjan-Oracle on May 17, 2007
Now that the book is done, and the use of the DocBook modules has proven so effective, a few people within Sun are considering using them within other contexts. In these contexts, one can't really talk about "the DocBook modules" anymore, since that term is only meaningful to NetBeans developers. It makes more sense to talk about the whole product, which is a scaled-down version of NetBeans IDE plus the two DocBook modules, as a product in itself. In that sense, the fact that it provides support for local history is just as relevant as its DocBook-HTML generation facility, because the end user sees the product as one whole, not as a collection of modules. Currently, this is how the end product, tentatively called "DocBeans", looks:
There's also the possibility of us open sourcing this product, possibly on java.net, so that the community at large can benefit from it and so that the product can be supported via that route. Because, after all, that's the main downside to choosing an internal solution over an external vendor... you need to provide support (e.g., bug fixes and feature enhancement requests) yourself! But, aside from this concern, DocBeans seems like an interesting avenue to explore.
In other news. Thanks for all the tips and tricks for setting up TwinView on Ubuntu 7.04! I can't announce the winner yet, because I first need to try the solutions, which means hooking my laptop up to a secondary display, which requires such a display, which means booking a room where all that equipment is found. So it may take some time, but in due course the rightful winner will be proclaimed and rewarded with the promised postcard!