Phil Daintree's shameless lies - Part 2

This page is written in response to the lies that +Phil Daintree has written about me, and spread on the internet. Despite years of searching he has been unable to find anything I have written that is untrue, and he has had to resort to vague generalities, faked emails, and badly fabricated screenshots (you can see the joins if you zoom in using any bit mapped image editor). +Phil Daintree is welcome to make any comments to these pages, as he has done in the past. If I agree with what he says I will amend my writings, if I do not agree I have allowed his comments to stand next to mine so that people can make their own judgements. I have every confidence in the intelligence of readers to make a sensible judgement based on the facts. +Phil Daintree will not allow me the right of reply to any of the lies he has told about me. It seems to me significant that he realises that if people see both sides of the argument they will see through his lies.

As with anything I publish, anybody (except the viagara  salesmen) can comment on my blog. I make a public commitment that I will not attempt to forge or censor any posts, as goes on in all the communication channels on webERP. If Phil Daintree wishes to dispute anything in this blog he is free to do so. If I am wrong I will alter my post. I trust in the common sense and intelligence of people to read the facts and to make up their own minds.

We have a lot of lies to get through so it's time I did another of this series in order to get it completed this year.

Lie number 3 - Phil Daintree's claim to have written "most of the code" in webERP

Phil Daintree claims that other people including me, are exaggerating their contribution to webERP and in a recent email he claimed that "most" of the code had been written by him alone, which justified his claim to own the copyright to the whole code base. Let's examine the basis of this claim. Phil Daintree uses a command that assigns the authorship of a line of code on the basis of the last change to that line. After Phil Daintree discovered this command I noticed that he had started to go through the code adding spaces and tabs to the end of lines of code, where they wouldn't be noticed unless the editor being used was set up to show them. Using his command, this gave him authorship of the line, even though the actual code had been written by someone else.

A little while ago I used a script to remove what is called "trailing white space" and is normally considered a bad thing to have in code. When Phil Daintree realised that this would radically reduce his supposed contribution to the project he accused me of trying to sabotage the project (http://weberp-accounting.1478800.n4.nabble.com/Fwd-Web-erp-svn-SF-net-SVN-web-erp-5765-trunk-td4656055.html#a4656056) due to some unspecified "outside interest". Strangely he reversed out my commit and the posted the identical commit himself, but claiming it as his own work. What was worse about his allegation was that he had by then banned me from posting to the mailing list, and so there was no way to refute this and despite numerous people asking him to, he has never apologised for it.

The other flaw in his argument is that it takes no account of the quality of the code. In other words adding a space onto the end of a line is given the same weight as code that actually does something. One of the most important contributions while I have been involved in the project was Mark Yeager's MRP contribution. But was it actually Mark's? Using Phil Daintree's command, Mark's contribution to the files starting MRP*.* is only 3.1% with the bulk belonging to Phil Daintree. So there you are Phil Daintree is claiming to have written most of the MRP system with the original and true author only being credited with 3.1%!! This claiming other people's work as his own is a familiar theme through all his lies. In the first post of this series I proved how he had taken my purchasing ordering report, copied it and committed it himself as his own work the following day!!

Lie number 4 - Phil Daintree's claim about the sourceforge logo

Phil Daintree claims that my only contribution to making webERP popular was to add the sourceforge logo into the footer of each page of webERP.

This is somewhat extraordinary as it was Phil Daintree himself who added the sourceforge logo to the footer in 2005, nearly two years before I joined the project. I actually took it out for a while!!

Anybody who looks at mailing lists for the period I was the administrator of the project (summer 2007 through to January 2011 when I ceased to be admin because Phil Daintree's ego was put out by the argument over retaining Purchase order history) will see that I spent countless hours helping people with their webERP issues. In fact both before I was admin, and afterwards, until Phil Daintree banned me from helping people on the mailing lists, I spent thousands of hours of my own time helping people. I spent thousands of pounds of my own money traveling, speaking at seminars and conferences helping to promote webERP. This I happily did, without seeking any recompense, or even gratitude from those like Phil Daintree who gained financially from the fact the project had a higher profile. I do however find it sad that Phil Daintree should lie like this in an attempt to denigrate the very hard work I did

Anyway, enough for now, watch out for part 3!

Programming the KwaMoja API - A simple client part1

The Client:

For this tutorial we will build a small PHP application that will first interrogate KwaMoja for a full list of available stock locations, build them into an HTML drop down list and then allow a user to input a stock item code and return the quantity of stock of that item at the selected location. We will use PHP for simplicity but any language that has an xmlrpc library (just about every language) can be used to write a client. It is a lengthy post, so I am splitting it into two parts. This is part 1.

Firstly we need the xmlrpc library, so we copy the xmlrpc sub-directory from KwaMoja to this new project.

The basic code will look like this, and be saved into a file called index.php:

<html>
    <head>
        <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
            "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
    </head>
    <body>
        <form action="index.html" method="post">
            Stock Code:<input type="text" name="StockID" /><br />
            Location:<select name="location">
            <?php // Here will go the available stock locations from KwaMoja?>
            </select><br />
            <input type="submit" name="submit" value="Submit" />
        </form>
    </body>
</html>


As it’s name suggests, the xmlrpc function calls are made by sending an XML file with the function name and the parameters to the server, and receive an XML file back from the server.

To assist with this, the phpxmlrpc library that KwaMoja uses (and we will use as well for our client) contains methods to encode our function call as XML, and to decode the XML that we receive back.

First off we need to include the xmlrpc library in our file, so immediately above the HTML, we need the following:

<?php
    include 'xmlrpc/lib/xmlrpc.inc';
    $xmlrpc_internalencoding='UTF-8';
    include 'xmlrpc/lib/xmlrpcs.inc';
?>

Running this page in our browser looks like this:
Not very pretty but you can see the idea.

Now the next thing we need is the code to populate the drop down box with the stock locations in it. Looking at the API function reference in the manual we see a function called kwamoja.xmlrpc_GetLocationList(). Obviously this is the function we require. Looking at the reference, the function takes two parameters, a valid userid for the KwaMoja instance, and the password for that user. In my case that is admin/kwamoja as in the standard demo setup, you must change yours to be whatever the name of the database is on your target KwaMoja installation.

We require a PHP function to return a list of locations to populate the drop down list. The function will look like this, and be at the bottom of the file, within a PHP code section (ie <?php ?>).

   function GetLocations() {

        //Encode the user/password combination
        $UserID = php_xmlrpc_encode("admin");
        $Password = php_xmlrpc_encode("kwamoja");

        //Create a client object to use for xmlrpc call
        $Client = new xmlrpc_client("http://localhost/KwaMoja/api/api_xml-rpc.php");

        //Create a message object, containing the parameters and the function name
        $Message = new xmlrpcmsg('kwamoja.xmlrpc_GetLocationList', array($UserID, $Password));
<

Programming the KwaMoja API - An introduction

 Introduction

This is a series of blog posts that will attempt to teach the programming and debugging of client applications for KwaMoja, using the API that comes bundled with it.

This can seem daunting at first, but as I hope to show you when you look behind the magic, it is really very easy for anyone who knows a programming language.

KwaMoja comes with a simple to use and flexible API that allows client programs to access KwaMoja in a safe and secure manner. If you wish to write an application that accesses KwaMoja, either to post transactions, or to extract information, then you should use the API, rather than try to access the KwaMoja database directly, as the API makes sure that the integrity of the data is maintained.

In this series I intend to show how to create a simple PHP client application, how to debug that application, then I hope to move on to writing a client in a different programming language, and finally how to extend the API.

The Protocol

The API uses the XML-RPC protocol to communicate between the client and the server. This was chosen because it is lightweight, simple, and easy to use. The API uses the XML-RPC for PHP external library, rather than the XML-RPC extension for PHP as it is small lightweight, and the extension is often not installed by default, so would add another dependency to KwaMoja. 

However the API was structured in a manner that allows other protocols to be used very easily. All that would need to be done to use the SOAP protocol for instance would be to create an api_soap.php file with the same functions as the api_xmlrpc.php file.

Setting up the server:

Before we start on the client there is one thing needed to be changed on the server side. This is to set the database to be used inside the api/api_php.php file. Mine is simply called kwamoja, so line 6 of api_php.php should read as:

$api_DatabaseName='kwamoja';

That is it for this introductory blog. Next time we will get down to some serious programming by starting work on our client application.

Phil Daintree's shameless lies - Part 1

An introduction

This page is written in response to the lies that +Phil Daintree has written about me, and spread on the internet. Despite years of searching he has been unable to find anything I have written that is untrue, and he has had to resort to vague generalities, faked emails, and badly fabricated screenshots (you can see the joins if you zoom in using any bit mapped image editor). +Phil Daintree is welcome to make any comments to these pages, as he has done in the past. If I agree with what he says I will amend my writings, if I do not agree I have allowed his comments to stand next to mine so that people can make their own judgements. I have every confidence in the intelligence of readers to make a sensible judgement based on the facts. +Phil Daintree will not allow me the right of reply to any of the lies he has told about me. It seems to me significant that he realises that if people see both sides of the argument they will see through his lies.

As with anything I publish, anybody (except the Viagra  salesmen) can comment on my blog. I make a public commitment that I will not attempt to forge or censor any posts, as goes on in all the communication channels on webERP. If Phil Daintree wishes to dispute anything in this blog he is free to do so. If I am wrong I will alter my post. I trust in the common sense and intelligence of people to read the facts and to make up their own minds.

I thought I would do a series of posts on the libels that Phil Daintree has been putting around the web. I also believe he has been mailing them to anybody who he thinks will listen. There are too many to do in one post so I thought I would make a regular feature of it.

Phil Daintree has admitted to a number of people that he made the whole lot up as an attempt to discredit me, but it seems he is still desperately seeking to find someone to believe him.

Phil Daintree regularly states that I am a liar, but has never managed to find anything I have said that is untrue. A number of people have asked him for an example but he never replies. try it and see....

It's been a bit spooky being the subject of his hate campaign. Sometimes I have felt like I was playing Michael Douglas to his Sharon Stone. He has even been snooping around in the online lives my friends and colleagues, in his desperate attempts to find an example of where I have said something untrue.

The fact that he cannot find an example, despite the closeness of our working relationship over such a long time is a source of great pride to me.

I will state nothing here without backing it up with relevant links to the facts.

Lie number 1 - The reason and timing of his taking away my admin rights

Phil Daintree apparently claims that he withdrew my admin privileges because he didn't like my work on fixed assets (incidentally still in use at one of East Africa's major companies - they don't like his version it doesn't do what they require). This is just untrue.

The truth is Phil Daintree had his ego bruised when somebody agreed with me in a dispute over Purchase Order history being kept, in December 2010 as can be seen here: http://weberp-accounting.1478800.n4.nabble.com/Re-webERP-users-Bug-in-Planning-and-MRP-td3085185.html#a3085235.

I had been administering webERP right up until this date when Phil Daintree suddenly stated that he was withdrawing my admin access. This was the first time either publicly or privately he had mentioned my admin access. Only the day before I had been using my admin rights so the claim that he removed them in November is obviously one of his lies.

Lie number 2 - The purchase ordering system

Phil Daintree apparently then goes on to say that I didn't like his idea of keeping the purchasing conversion factor inside the order class. Phil Daintree has obviously forgotten that revision control systems have a long memory. As can be seen here I actually wrote the code and committed it here http://bazaar.launchpad.net/~tim-weberpafrica/web-erp/trunk/revision/4188 at 2011-01-09 12:27:33 UTC and then Phil Daintree copied my code and committed it here: https://sourceforge.net/p/web-erp/code/4463/#diff-5 on the following day.

So Phil Daintree "claims" I was against his idea and says: "Tim refused to accept my decision, rather than gracefully accepting it was a simple mistake and it was much more elegant to hold the units in the businesses unit of measure. A tirade of angry emails to the list ensued much more than a simple technical disagreement.". Now it turns out that he actually copied my work and claimed it as his own!! This theme of copying other peoples work and claiming it as his own carries on through much of the life of webERP.

The initial purchase ordering system that Phil Daintree initially claimed was "......really good - sorry it has taken me a while to recognise the large improvements you have effected in this area. I can't believe there has not been more excitement around this work. Although perhaps it is only crazy accountants that get excited about such things." (http://weberp-accounting.1478800.n4.nabble.com/Major-upgrade-to-purchasing-td1487909.html#a1487912) wasn't even written by me but by Rob Virgin, so why Phil Daintree thinks I would have behaved like he claims is yet another mystery!!

As Fahad points out here https://sourceforge.net/p/kwamoja/blog/2013/02/lies-damn-lies-and-phil-daintree/ little if anything Phil Daintree says turns out to be true, which is why he needs to so extensively use censorship in the webERP project.

Anyway, that is enough until Part 2  

KwaMoja/webERP and me, the facts!

As with anything I publish, anybody (except the viagara  salesmen) can comment on my blog. I make a public commitment that I will not attempt to forge or censor any posts, as goes on in all the communication channels on webERP. If Phil Daintree wishes to dispute anything in this blog he is free to do so. If I am wrong I will alter my post. I trust in the common sense and intelligence of people to read the facts and to make up their own minds.

This is a post that I didn't really want to have to spend time writing. It is unfair that attention should be taken away from the hard work the guys on KwaMoja have put in, and this is why I have tried to remain silent on the matter. Also I want to concentrate on the code which is far more fun, and far more productive. However it has been brought to my attention that there is much misinformation on this subject that is being propagated on the web by people with their own agendas to push. So, for those reasons I feel I have to put right the facts regarding me, KwaMoja, and webERP.

KwaMoja grew from a series of lectures I gave at a community college in Kenya last year. As part of the course work I set the students to work on some modifications for webERP. Two of the students expressed an interest in continuing this work and doing their own version for Kenya. I had also about that time had an email from an Indian gentleman wanting to know if I wanted to do a fork. I put him in touch with my two students and that is how KwaMoja began. One of my reasons for setting up my company in Africa was always to help African programmers, so I was pleased to help them, and I have donated some code to them. I also leant them some money to purchase the domain name (after their .org domain name was taken by somebody trying to make mischief) and for hosting, which has since been repaid. However this doesn't diminish my commitment to webERP which is a project to which I have given thousands of hours and spent thousands of pounds in promoting over the years. Indeed a look at the recent commits here https://sourceforge.net/p/web-erp/code/commit_browser shows I am still a very active committer to webERP.

One of the things I love most about open source is being able to discuss interesting ideas with like minded people. Technical discussions are a very interesting way of reinforcing your views on a subject. It is a shame that these have been virtually banned on webERP and a pleasure to work with people on KwaMoja who are interested in discussions.

The short answer for those who don't want to read all the stuff above is that I am very committed to both KwaMoja and webERP and intend to keep donating my time and my code to both projects.

2011-02-03

• Played around with more of the translations code.
• Did some more work on the manual
• Looked at a couple of the outstanding bugs for 4.0.2

2011-02-01

• Loaded up new Turkish translation as part of experiment with getting the Turkish locale to work properly.
• More work on moving the manual to the wiki  http://wiki.web-erp.org/index.php?title=UserManual.