Upstreaming scsolver

Share Button

I’m in the process of upstreaming my solver (a.k.a scsolver – its cvs module name) to the OpenOffice.org repository at the moment. So, with everything else put on hold, all my effort is shifting toward making that happen.

Typically, any new code to the OO.o is upstreamed via a process known as the child work space (CWS), which is basically a front-end to the CVS repository (soon to be SVN’ed, I suppose? ;-) ) designed to ease the management of source control from different parties, including external contributors such as myself.

But CWS can be a bit intimidating and confusing to the un-initiated. For instance, it took me a great deal of trouble to figure out how to add new top-level modules. All sorts of emails went back and forth, and in the end, thanks especially to Petr, I was able to at least add new stub modules directories in cvs HEAD, and filed an issue to have the right person (Jens?) add cvs alias to those modules so that they can be checked out for further work.

Also, because my code has dependency on lp_solve, which itself is an external project, the right steps needed to be taken as outlined in the external project page to make sure that we are complying with the license of that particular software. Not sure how long this process will take, but at least I did my part (or did I?).

Anyway, things are moving along. :-) Michael was kind enough to create a new cws for me, so hopefully once those modules get aliased for checkout I’ll be able to start working on putting my code in that cws.

Oh yeah, also not to forget that patch for lpsolve that maho wants to commit. ;-)

Hacking Calc – The First Step

Share Button

I’m happy to announce that the article I submitted to the OpenOffice.org Developer Article Contest has been selected as June’s winner! You can read my article here. Though this article attempts to cover the hard topic of hacking the core part of OO.o’s code base, I tried to keep it somewhat of an easy read.

I hope this article will help lower the initial barrier to entry, because hacking OO.o, though it admittedly comes with a steep learning curve, is quite fun once you set your foot in the door. So, even if you are a little intimidated by the sheer size of the code base, come and try with your hand a little. You might actually like it. :-)

Interested in writing your own article for the contest? Cool. Go read the guideline and submit your own!

Recent activities

Share Button

So, I have several things going on at the moment:

  • I have just registered for my final exam for the class I’ve been taking since December. This class has certainly been an eye-opener, especially for someone like myself who’d been coding in high-level languages with only a vague understanding of low level architectural stuff.
  • I’ve started looking at lp_solve for possible integration into Calc Solver, and solicited for some interests. This Solver task, admittedly, has become much, much, more than what one person can handle. So, strategic change is necessary to keep things moving. I’ve also updated the wiki page to add more content.
  • Created a new wiki page for Statistical Data Analysis Tool project, to hopefully mobilize the near-death-experienced-yet-still-important project for Calc. There is no content on this page yet as it is still pretty much a skeleton. I wonder if this project will ever gain enough momentum to get it going…

First scsolver binary package after ooo-build integration

Share Button

Since not everybody who wants to use my solver has a version of OO.o derived from ooo-build, I have made available a separate binary package that can be installed on a regular OO.o. There is no functionality change since the last snapshot I uploaded here on my website, so if you are having trouble solving your model with my solver, sorry, this snapshot is not gonna help you.

Because now I work directly off of ooo-build cvs, the new changelog is located here. The old changelog is no longer maintained.