If you search for a backlog tool, take a look on http://www.userstories.com/products.
For example, a simple and good backlog tool is eXPlainPMT
.
Presentation about “Clean Code”
Here are my slides about Robert C. Martins great book “Clean Code: A Handbook of Agile Software Craftsmanship“:
Clean Code
View more presentations from hebel.
How-to: Eclipse Commands
If you searching for good eclipse commads instructions, see here…
Six good articles by Prakash G.R.:
- Commands Part 1: Actions Vs Commands
- Commands Part 2: Selection and Enablement of IHandlers
- Commands Part 3: Parameters for Commands
- Commands Part 4: Misc items …
- Commands Part 5: Authentication in RCP applications
- Commands Part 6: Toggle & Radio menu contributions.
Other articles:
- Using advanced features in Eclipse popup menus
- Advanced features in Eclipse popup menus – Take 2: The new API
- Commands in die Toolbar einfügen
and the standard set of references:
Pony Meeting
This refers to a story Lopp told earlier in the session, in which he described the process of a senior manager outlining what they wanted from any new application: “I want WYSIWYG… I want it to support major browsers… I want it to reflect the spirit of the company.” Or, as Lopp put it: “I want a pony!” He added: “Who doesn’t? A pony is gorgeous!” The problem, he said, is that these people are describing what they think they want. And even if they’re misguided, they, as the ones signing the checks, really cannot be ignored.
Lösungen für einen SWT Rich Text Editor [Update]
Wenn man, wie ich, vor der Aufgabe steht einen WYSIWYG Rich Text Editor in eine Eclipse RCP Anwendung zu integrieren, stellt man leider schnell fest, das es keine Standardlösung gibt. Vielmehr hat man folgende Optionen mit ganz speziellen Vor- und Nachteilen, für die man sich entscheiden muss:
“Privacy and the Future of the Cloud”
..interesting slides from Nat Torkington
via O’Reilly Radar
Aza Raskin – Humanes Interface-Design
Golem führte ein wirklich sehenswertes Interview mit Aza Raskin zum Thema Humanes Interface-Design und Firefox:
Links:
GuiceBerry: JUnit with dependency injection
GuiceBerry brings the joys of dependency injection to your test cases and test infrastructure. It leverages Guice to accomplish this. It allows you to use a composition model for the services your test needs, rather than the traditional extends MyTestCase approach.
GuiceBerry does not supplant your JUnit testing framework — it builds on top of it (and works around it, when necessary), so you can run your tests normally, from your favorite command line or IDE environment.
Links
- Presentation Video: Clean Code Talks – “GuiceBerry” and Slides
- GuiceBerry Project Page
- GuiceBerry Tutorial
- Guice
80:20 rules! – Building software smarter
Google Tech Talks
October 8, 2008ABSTRACT
Ever notice that you seem to spend 80% of your time on 20% of your tasks? Or that 80% of the decisions in a meeting seem to occur in 20% of the meeting time? Welcome to the world of the 80:20 rule. When we design, build and test software, we have to determine where to start and what we should do next. The 80:20 rule helps provide an answer to these questions, while helping to increase our productivity and effectiveness. As well as being an agile principle, it’s a common thread in other disciplines, and there’s a special variation that applies to software defects. We’ll explore the different ways testers and developers are using the 80:20 rule. This rule could be a secret ingredient to help you build software smarter!
Speaker: Erik Petersen
Eclipse secure storage provider deaktivieren
Um den Master Passwortcheck (mit dem sinnigen Feature “Show password” :-) von Eclipse 3.4 wieder loszuwerden, muss man folgendes machen:
- in den Eclipse Preferences unter Genral > Security > Secure Storage die checkbox bei “Master Password Provider” deaktivieren
- Eclipse schließen
- unter C:\Documents and Settings\[username]\.eclipse\org.eclipse.equinox.security die Datei secure_storage löschen
- Eclipse starten und sich mit dem CVS synchronisieren, bei der erneuten Passwortabfrage die “password speichern” checkbox aktivieren
Google Chrome und die eindeutige Anwendungsnummer
Warum hat Google so was eigentlich nötig?
“Ihre Kopie von Google Chrome enthält mindestens eine eindeutige Anwendungsnummer. Diese Nummern und Informationen zur Installation des Browsers (z. B. Versionsnummer, Sprache) werden bei der erstmaligen Installation und Verwendung der Anwendung und bei der automatischen Update-Prüfung von Google Chrome an Google gesendet. Falls Sie Nutzungsstatistiken und Ausfallberichte an Google senden, werden uns diese Informationen sowie eine eindeutige Anwendungsnummer vom Browser übermittelt. Ausfallberichte enthalten Informationen aus Dateien, Anwendungen und Diensten, die zum Zeitpunkt eines Problems ausgeführt wurden. Mithilfe von Ausfallberichten können Browserprobleme diagnostiziert und behoben werden.”
http://gears.google.com/chrome/intl/de/privacy.html
Mozilla Firefox ist übriges nicht viel besser, aber zumindest kann man den Automated Update Service abschalten…
“Automated Update Service. Firefox’s automatic update feature periodically checks to see if an updated version of Firefox is available from Mozilla. This feature sends Non-Personal Information to Mozilla, including the version of Firefox you are using, a list of the add-ons you have installed, and your language preference. This feature also sends Potentially Personal Information to Mozilla in the form of a cookie named “aus” that contains a unique numeric value to distinguish individual Firefox installs. Mozilla uses this information to provide you with updated versions of Firefox and to understand the usage patterns of Firefox users.”
http://www.mozilla.com/en-US/legal/privacy/firefox-en.html
10 Features of Google Chrome
Berkeley DB JE: DPL Assistant for Eclipse
The Berkeley DB Java Edition Team announced the DPL (Direct Persistence Layer) Assistant Eclipse Plugin:
This first version of the plug-in performs validation of DPL
annotations in Java source code. Each time you save changes from the
Java source code editor, the validator analyzes annotations (@Entity,
@Persistent, etc.) and reports any errors or warnings that it can
detect, in a similar way to how the IDE reports Java compilation
errors.
- Usage and Installation infos: Berkeley DB Java Edition Forum
- Update-Site: http://download.oracle.com/berkeley-db/eclipse/
