XHTML Doclet

Well, after a round of massive refactoring and improvements (during the semester break), the time has come to return to the task at hand: finishing my MS in Computer Science. If all goes well, I will be completely finished by August, and off to work ... [More] full-time at Apple. However, I'm still planning to grab time when I can (perhaps weekends and holidays) to work on XHTML Doclet. I'm keenly interested in seeing it succeed and become as useful as it is intended to be. There is still a long way to go to make it as complete as the standard doclet, but I hope it will be worth the wait. Hopefully, the changes I've made most recently will make it easier for interested parties to use and modify the code, perhaps even contribute changes to improve the current state of things. The hard part is rooting through the legacy code to figure out who does what, and how to replicate behaviors cleanly in the new code. Help is welcome, and I hope to respond in a reasonable time frame. This project is not dead, just semi-dormant, a temporary victim of higher education. I look forward to when I can return to more active development, hopefully this fall. [Less]

Well, after a round of massive refactoring and improvements (during the semester break), the time has come to return to the task at hand: finishing my MS in Computer Science. If all goes well, I will be completely finished by August, and off to work ... [More] full-time at Apple.However, I'm still planning to grab time when I can (perhaps weekends and holidays) to work on XHTML Doclet. I'm keenly interested in seeing it succeed and become as useful as it is intended to be. There is still a long way to go to make it as complete as the standard doclet, but I hope it will be worth the wait.Hopefully, the changes I've made most recently will make it easier for interested parties to use and modify the code, perhaps even contribute changes to improve the current state of things. The hard part is rooting through the legacy code to figure out who does what, and how to replicate behaviors cleanly in the new code. Help is welcome, and I hope to respond in a reasonable time frame.This project is not dead, just semi-dormant, a temporary victim of higher education. I look forward to when I can return to more active development, hopefully this fall. (0 comments) [Less]

Well, after a round of massive refactoring and improvements (during the semester break), the time has come to return to the task at hand: finishing my MS in Computer Science. If all goes well, I will be completely finished by August, and off to work ... [More] full-time at Apple.However, I'm still planning to grab time when I can (perhaps weekends and holidays) to work on XHTML Doclet. I'm keenly interested in seeing it succeed and become as useful as it is intended to be. There is still a long way to go to make it as complete as the standard doclet, but I hope it will be worth the wait.Hopefully, the changes I've made most recently will make it easier for interested parties to use and modify the code, perhaps even contribute changes to improve the current state of things. The hard part is rooting through the legacy code to figure out who does what, and how to replicate behaviors cleanly in the new code. Help is welcome, and I hope to respond in a reasonable time frame.This project is not dead, just semi-dormant, a temporary victim of higher education. I look forward to when I can return to more active development, hopefully this fall. (0 comments) [Less]

Well, after a round of massive refactoring and improvements (during the semester break), the time has come to return to the task at hand: finishing my MS in Computer Science. If all goes well, I will be completely finished by August, and off to work ... [More] full-time at Apple. However, I'm still planning to grab time when I can (perhaps weekends and holidays) to work on XHTML Doclet. I'm keenly interested in seeing it succeed and become as useful as it is intended to be. There is still a long way to go to make it as complete as the standard doclet, but I hope it will be worth the wait. Hopefully, the changes I've made most recently will make it easier for interested parties to use and modify the code, perhaps even contribute changes to improve the current state of things. The hard part is rooting through the legacy code to figure out who does what, and how to replicate behaviors cleanly in the new code. Help is welcome, and I hope to respond in a reasonable time frame. This project is not dead, just semi-dormant, a temporary victim of higher education. I look forward to when I can return to more active development, hopefully this fall. [Less]

This is just a heartbeat for those of you checking the pulse of this project. I've been completely occupied with programming for my internship at Apple, including overtime hours and working from home. However, my internship ends in 2 weeks and I hope to return to more regular development for this Fall. Thanks!

This is just a heartbeat for those of you checking the pulse of this project. I've been completely occupied with programming for my internship at Apple, including overtime hours and working from home. However, my internship ends in 2 weeks and I hope to return to more regular development for this Fall. Thanks!

This is just a heartbeat for those of you checking the pulse of this project. I've been completely occupied with programming for my internship at Apple, including overtime hours and working from home. However, my internship ends in 2 weeks and I hope to return to more regular development for this Fall. Thanks! (0 comments)

This is just a heartbeat for those of you checking the pulse of this project. I've been completely occupied with programming for my internship at Apple, including overtime hours and working from home. However, my internship ends in 2 weeks and I hope to return to more regular development for this Fall. Thanks! (0 comments)

Release 0.1 was posted a few weeks ago, and release 0.2 is now online. The release notes describe the changes. Much work still remains to be done, but it's moving forward. Please explore this release to flesh out bugs and weaknesses in the improved ... [More] areas. More frequent builds are available at http://xhtmldoclet.sourceforge.net/download.php as before. [Less]

Release 0.1 was posted a few weeks ago, and release 0.2 is now online. The release notes describe the changes. Much work still remains to be done, but it's moving forward. Please explore this release to flesh out bugs and weaknesses in the improved ... [More] areas.More frequent builds are available at http://xhtmldoclet.sourceforge.net/download.php as before. (0 comments) [Less]