Just a friendly reminder that the Eclipse October BugDay is coming up this Friday. We already have a few awesome participants, but it would be nice to have some more. If you’re interested in helping PDE out this time around, we recently enhanced the error log view by partitioning out log statements by session:
Cool huh? It would even be cooler if the current session was highlighted.
If bolding text isn’t your thing, here are some other bugs from PDE:
I’ve been wrapping things up today before I head to Cancun by going through some small bugs and came across a new addition to PlanetEclipse. Daniel Ford talks about going “First Shooter” on Eclipse in a way that makes the geek inside of me jealous 😉
In other news, Apache Felix is lighting up to PDE.
So, given that I’ve seen two instances today where people have wanted to know how to use the log view within their applications, I figure a blog entry is in order. The log view currently lives within the PDE feature and specifically the org.eclipse.pde.runtime plug-in (or org.eclipse.ui.views.log in Eclipse 3.4 and beyond). To add the view to your application you need to do two things:
org.eclipse.pde.runtime.LogView (this is the same still in 3.4)That’s it! Don’t believe me? Here’s the famous RCP Browser example with the log view (patch to help people out in 3.4, if in 3.3, simply replace org.eclipse.ui.views.log with org.eclipse.pde.runtime as a dependency in the MANIFEST.MF).:
So what happened this week in PDE?
Last month’s Eclipse bugday ended with 22 bugs fixed and improved project participation!
The next bugday is scheduled for October 26th with rumors of EMF and GEF participating this time around. If you’re looking for interesting PDE bugs, check these out:
Good luck!
I had a bit of time to reflect on the Equinox Summit and here are my take aways:
On the whole, the trip was very enjoyable. It was a pleasure to meet new people and see some faces I haven’t see in awhile. Thanks to the Eclipse Foundation and Jeff for putting this event together. Maybe it’s time for a PDE Summit in Austin :)?
My first day in Ottawa and all I can think about is the Marlboro Man. I guess since arrived late into Ottawa this evening for the Equinox Summit, I was blessed with a hotel room that was probably occupied by the Marlboro Man before I arrived. Since the hotel is full, I have to endure the smoky smell until tomorrow 😀
On the Eclipse-side of things, I released changes for 3.4M3 that will upgrade Bundle-RequiredExecutionEnvironment (BREE for short) from coach to first class (thank you Gary Duprex for your patches and patience). Why are BREE’s good? Read PaScaL’s blog post.
In the new plug-in project wizard, you’ll see an option to set your target environment:
Also, we now flag missing BREE’s in honor of Remy Suen who may suffer from a heart attack if people don’t set BREEs in their bundles.
Note: I know you can have multiple BREE’s per bundle, but we currently don’t support this scenario in the new plug-in project wizard due to the rarity. If additional BREE’s need to be added, PDE offers a fantastic forms-based editor and a source editor with code completion.
On my way to the Equinox Summit with a 160 minute layover in Chicago, I was hacking a bug to add execution environment selection and validation to PDE (thanks Gary) when I noticed this in a recent build of Mylyn:
Thanks Mylyn! I was waiting for the ability to edit those Bugzilla keywords. Now we just need to figure out how to work with bugzilla flags without me opening a web browser.
By the way, if you haven’t tried out Mylyn, I’d recommend it. It has some nifty features that I can’t live without these days:
Just a reminder for people that the next Eclipse BugDay is coming up. There’s a bit more projects participating this time around. If you really want to help out a project in need, check out the Visual Editor’s (VE) list of bugs (VE Contributing Guide). They really need help with general triage to get the project moving again.
If you want to take a stab at one from the PDE camp, here’s one:
Thanks!