Not a very productive week as compared to some of the other students. I’m going to have to ratify that for this second week.
What I’ve done so far:
- Do a Subversion Checkout of the repository I’ll be working in for the Summer.
- Start writing the full Project Roadmap (halfway finished).
- Figure out project deliverables for July 7.
Plans for Week 2
Have base plugin code finished:
- This includes the installer, uninstaller, and plugin administration panels.
- Configuring the location of XDebug performance folder and trying to automatically find that folder for the user.
- Listing the available cachegrind files and allowing the user to choose which ones to extract.
- Parsing the cachegrind files into the database (this will allow for easier comparsions between two or more runs, hopefully).
The base code should be finished, because the majority of the work leading up to July 7, will be porting the code in webgrind over and extending that code. I’ll need to keep two separate branches, because I’ll want to send my enhancements over to the guys working on webgrind at the end of the project.
Cachegrind Database
The plugin cachegrind database is needed, I think for extracting just the parts that deal with different functions. I want to show just the performance for a plugin code base and do so fairly quickly. I also want to extract out parts of the WordPress code base, which is taking the most time to figure out if improvements can be made. If that means using different methods, then it will probably go into some of the experiments.
Looking at Webgrind
Webgrind appears to have the base for, which I can extend and implement graphs for. I’m going to have to look over the code base to see, which parts I can use.
PHP4 and PHP5 Support
The plugin code should (must?) work on PHP4, since PHP4 is supported with the current version of WordPress.
Possibly Related Posts:
- Paying Off Debt Revisited
- Thou Art God
- Saying Good Bye to Dollhouse
- Where the Wild Things Are Movie Review
- Why Choose 1st Financial Bank?