This does not mean that anything beyond having it compile will be done. I just basically want to have the initial extension building working so that work can be done later. Whenever any component enters "stable" status, it would be easier to commit it to the extension. I think that it may take a little bit of debate as to which component is stable and when. It also depends on how difficult it is to (re)write the component in C++ in the first place. I would like a direct PHP to C++ library class translation. This means that the library (definitions) and code will basically match the PHP counterpart (except where hashes won't be efficient). The PHP Extension part will list the classes, the methods and create the C++ library code for PHP and call the methods. So the only thing the PHP Extension code will be is using the C++ library and making it available to the userland.
If this works out well, then it might just be as quick to write the C++ code as it is to write the PHP code (just kidding, but it would be easier). After I have written enough (the skeleton), I plan on committing it to the repository. Granted, I need to have Subversion on my PC for which to commit the ext/qgl to the Quantum Game Library repository. Which is why I'm writing the extension now in the first place, that I can't access the repository, currently.
See how far I can get before I get paid and get the parts to get my new computer. That will be longer than one week, but it should be okay given that there are some components that could be converted during that period.
PHP to C++
For efficiency purposes, really only the methods and properties will be the same. There should be a few times the code for PHP wouldn't be translated to C++. However, the results should be the same regardless.
The road map was to start this project in March. The reasoning being that a large percentage of the library would be stable and wouldn't be at risk of refactoring. It is unpreventable that some parts would later be refactored. That shouldn't stop it from doing so, however the extension shouldn't be too far behind.
There would have to be extension versions that either match the library version or a list which states which extension version matches what library version. Since there currently isn't a version, this won't be a problem until a release. Only then hopefully a better C/C++ developer would join.
How hard can it be? I'm being serious, I don't want to get into it and realized that I suck. Doesn't help that I have to relearn most things about C++.