Today I`ve finished laying the engine foundation for jQuery Updater for WordPress 3.0
The release of jQuery 3.0.0 alpha 1 triggered me to swap from 2.1.4-beta to 3.0.0-alpha but I`m happy with it. The plugin`s engine got completely rewritten and includes some code that I used to maintain seperatly as a plugin; jQuery Mobile, but also includes jQuery UI and QUnit.
The source can be found at github.com/Ramoonus/jQuery-Updater
The final release, will be done after several public alpha`s and beta`s which include an administration panel.
Roughly a year ago I`ve set the planning for jQuery Updater for WordPress in the post Development Progress of jQuery Updater for WordPress and made a note on the 3.0 release jQuery Updater for WordPress 3.0
This morning I`ve finally got Unit Testing (PHPUnit) and Code Quality up and running. This is powered by Travis CI and Scrutnizer. The development chat is hosted on Slack whereas the source code is still on GitHub. Most functions now also feature a PHPDoc block.
The development release is in the master branch and the latest production in stable.
Today I`ve redrawn the following WordPress plugins from WordPress.org;
- Opera Speed Dial
- jQuery Mobile (Updater)
This plugin will be included in a future version of jQuery Updater
This means that they are no longer available or supported
I will post the source code on GitHub later this week.
With an announcement for the plans of jQuery (Compat) 3.0 I decided to bump the development version of jQuery Updater for WordPress to 3.0 aswel.
The current development is known as 3-dev. This version also included jQuery Mobile and jQuery UI. This version also contains an administration screen, as created in 2-dev.
The latest stable release is the master
The next-gen 2.0 branch is known as 2-dev. This version contains an administration screen.
Today I`ve started working on my jQuery Updater for WordPress plugin.
Step 1: moving to GitHub
First step was linking Subversion and Git, which was a hell
Step 2: decide workflow
The second step is deciding the workflow: tools and rules. I decided to skip Grunt and Vagrant for now, since the code isn`t going to be rocket science.
I use phpDoc for documenting the PHP code and GitHub as project management (issues, milestones).
This setup will do fine for now!
Step 3: project management
Making a roadmap, with issues, features and prioritising all that I want before I start working and losing grip on the project.
Step 4: work
Starting with cleaning up code followed by creating space for new features. Leaving the hardest bits for the last. Although this isn`t ideal it makes future development a whole lot easier.
Want to help?
The project is located on GitHub at github.com/Ramoonus/jQuery-Updater