About 3 weeks ago I wrote a post showing some new features for WordPress 2.7. Since then there has been a bit more developing going on and this post touches on a few more features.
As I mentioned back then, things can and very likely will change by the time this release is completed so don’t come back complaining to me when things don’t look the way the do here.
A excellent post on the Weblog Tools Collection has also appeared between these posts and this goes into some more detail about the major additional features. The comments on this post were an interesting read with many people split over yet another admin design change. Whilst I can understand where they’re coming from, 2.7 does make a few good changes that I know I’ll certainly find useful. My advice to critics therefore would be to give it a try and see what they think. If Subversion isn’t something you’re familiar with then feel free to ask for a bit of help.
Read more…
WordPress development, on a whole, is pretty simple. As someone who has come from a background working with IPB and a little bit of phpBB I was quite amazed at how unusual it is to edit the “core” WordPress files – those which are outside the wp-content folder and are distributed each release.
Instead WordPress relies on hooks that are either filters (which change something) or actions (which do something). These are quite simply littered throughout the code and any plugin can jump on these to do whatever is needed by the developer. However, the problem I’ve found is a lack of trying to find the right hook for the job. PHPXref, which is excellent for finding functions and variables doesn’t have the ability to find a hook which is usually in the format of:
do_action('name', $vars); or apply_filters('loginout', $output);
Read more…
If anything sets the internet community buzzing it’s rumours about new programs and services, especially from the big players such as Apple, Google or (heh) Microsoft. With Apple we usually have a few months of leaked information to speculate about. However Google’s Chrome browser, expected out in the next hour, was only leaked around a day or so in advance.
That’s not really stopped the gossip though. Fueled by a 38 page web comic Twitter and the Blogosphere have been going all day long as the release of the browser aproaches.
Judging by the content of the comic this browser could stir the browser wars back into full assault. I particularly like the focus on performance that Google seems to have worked hard on. If I have any gripes about Firefox then speed is certainly it. Version 3 has certainly improved things slightly but it’s still no match to Opera or Safari in both starting the application and loading pages.
Read more…
So I’ve been working on this for most of today and I’m pretty happy with how it’s turned out. I’ve considerably edited a free theme which was designed for a magazine site to something acceptable for personal use.
Comments welcome, I’m particularly interested in whether anyone feels it needs improvement. If anyone can find any bugs then let me know.
So yesterday I noticed a big commit on the WordPress SVN where selected files from the “crazyhorse” branch were merged with trunk. This has resulted in a pretty different look to some of the admin sections. Because I know at least a few interested people read this, I’ve took a quick screencast of what it looks like at the moment.
As a disclaimer, I have no idea if this is technically “allowed”. However all of it is freely downloadable to those who care so I can’t really see any problem with it. I should also add that this is a highly developmental version and the entire thing could spout pink frilly things before it makes it to a release. You may notice a fair few bugs even in this video (which were not intentional but I’m not going to hide the fact it’s buggy). This is also located on my localhost which hasn’t been setup to allow the script to download and has no ftp which is why I stopped at those screens.
Screencast of WordPress Trunk
The crazyhorse branch has a few different widgets on the dashboard, including the ability to post directly from the dashboard.
If I see any more changes of note, I’ll make a similar post.
Looks good to me though.
Read more…
So WordPress 2.6.1 was released today. This marks the first release where I have contributed any code. Nothing big, just 3 bug fixes (#7366, #7336 and #7316) but I have to start somewhere. I’ve also done a bit of inline documenting for some of the functions (which is ironic because most of my own projects have chronically lacked documentation) and with any luck these will be included in the 2.7 release.
I’m quite looking forward to that release based on what I’ve seen being worked on including some very helpful features. I never really appreciated just how much goes into the development of WordPress before and I’m quite enjoying contributing on such an active project. Whether I’ll be able to keep it up when I go back to Uni or not I’m not sure, but here’s hoping.
Popped into the Apple store on Sunday with my MacBook and presented my problem. They didn’t even question the warranty period. Instead I left the shop about 10 minutes later with a free replacement battery.
Considering I was thinking I might have to pay around £50 for a new one, I’m quite chuffed.
Now I just need my TV licence refund and old flat deposit and I should be a little safer in the money camp.
I knew it wouldn’t be impossible, just quite difficult.
However, it seems I’ve broke the battery at least. Technically the die hard mactards would probably claim the computer itself is fine (a fair point, something I’d probably say).
The problem? The battery doesn’t appear to be recognised. Apple knows about it but unfortunately none of those work to solve it.
Honestly, I think i’ll be needing a new battery (£99 from Apple!) but I plan on taking it into the Apple store tomorrow and see if there are any other options.
Apart from that, I now have grown a hatred for the MagSafe power adapter.
On the plus side, I did manage to fix our DVD recorder after my mum decided it would be a good idea to put two DVDs in at the same time…
As my involvement in the dev side of WordPress grows, I’ve been working on increasing the PHPDoc comments through the major parts of the code. A particular challenge I stumbled across today was trying to talk about certain HTML tags in the comments in a way that they wouldn’t then be turned into the actual tag when phpDocumentor ran.
So basically I wanted to say something like
This function returns a properly formatted <pre>…</pre> block
However I found that doing that caused the <pre> tag to be used as part of the page when the docs were transferred to the HTML format.
The solution I discovered was to reference the tags as <<pre>> or <<br />>. This seems to preserve the tag in the finished documentation as a comment and not part of the page.
I struggled to find this in google, so though a little blog post might just help someone.
This should hopefully go to twitter?
——
Indeed it did. The plugins that finally got my setup here are Twitter Updater and Twitter Widget Pro. Took a while to find plugins that were 2.5.1 compatible but these do the trick.
——
Also, I’d highly recommend Fluency Admin which makes the wordpress admin screen a whole lot neater.
——
This also means the next post wasn’t result related. Oh well.
Recent Comments