This was a hard-work weekend. On Thursday, it seemed like I had lots of code starting to work. It appeared that the imaginary brackets that surround each work package and sub package were closing themselves off, so that the virtual equation that describes my work might seem a little smaller and more tractable. That’s when I pressed the wrong button. Continue reading
I’m rather enamoured with this little plugin. It’s a regular expression evaluator, great for writing and checking regular expressions and knowing that they’re going to work in the way you think they will. Continue reading
This could be useful; it’s a tool which stops Windows from swapping Eclipse out of memory. Continue reading
The geek in me loves this. It is a java bytecode viewer plugin for eclipse. Continue reading
Good PNG support is an important thing to nail since it has a significant effect on the sheen of the application. The alpha transparency mechanism currently supported by Eclipse already works under certain circumstances, but not all, and until it does, developers are stuck with the clunky transparency offered by GIF. Continue reading
Eclipse 3.0.1 has been released and includes 286 bug fixes. This is generally good news for the stability of the platform.
Looking at the list of fixed bugs, 76 were of major, critical or blocker status, and only 5 were enhancements. This reflects the intended purpose ironing out any v3 teething troubles.
Some good news. I now have an RDFX View linked to the properties view so that both Resources and Literals are showing up.
Still to do however:
1. Stop showing the triple, just show the RDF object value
2. Display resources and Literals in different twisties within the Properties View (and add user preference)
3. You may also notice that the content of the RDFX View tree has been frigged – this is currently a big to do.
4. Also, for twisties, are cases where there are multiple values for a particular property.
5. Add a lookup for the Property Name so that if it has a “plain english” value defined somewhere it can be used – (using schemas notes added on this later).
there is a problem with much eclipse development – when something doesn’t work, you’re left very much in the dark. the purposeful lack of documentation thus far – perhaps to enable the platform to remain agile leaves one relying on examples, which is fine – it suits my learning style – but sometimes, when things don’t work, it can be a time sapping drag.
This book very very good. Read it before you start writing anything in Eclipse. If the last five months of hacking have taught me 30% of what I need to know to really understand the internals of Eclipse as it stands today, then this book just confirmed that 30% and had added another 20% by the end of the “first circle”.
Really; read it before you start to code anything in Eclipse.
