agilesWissen

My slides about my experience with webOS and the development of Sorting Thoughts for webOS:

My last test installation of XWiki was three years ago and after reading the current feature list of XWiki Enterprise I’m really impressed. I think I have a new entry for my task list: “Installing XWiki and test it”.

Links

• click for more details about the sildes
• XWiki

• Eclipse 3.5 – New and Noteworthy
• Ten Tips for Installing Plugins in Eclipse Galileo
• Eclipse RCP – Tutorial with Eclipse 3.5 (Galileo)
• Memory analysis with Eclipse 3.5
• Open Eclipse 3.5 Bugs

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

.

Um den Master Passwortcheck (mit dem sinnigen Feature “Show password” :-) von Eclipse 3.4 wieder loszuwerden, muss man folgendes machen:

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

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/

..a new metaphor for knowledge access and management.

ABSTRACT

Successful knowledge management results in a competitive advantage in today’s information- and knowledge-rich industries. The elaboration and integration of emerging web-based tools and services has proven suitable for collecting and organizing intellectual property. Due to an increasing information overload, information and knowledge visualization have become an effective method for representing complex bodies of knowledge in an alternative fashion by using visual languages. The focus of this research is the development of a “Visual Wiki”, which combines the notion of a textual and a visual representation of knowledge. A Visual Wiki model has been proposed which provides a unified framework to design and discuss different approaches. Three prototypes of Visual Wikis have been implemented and evaluated according to the improvements to knowledge management applications that they facilitate. This is joint work with Christian Hirsch and John Grundy

(Link)

..or the organic software visualization of Eclipse (SDK).

This visualization, called code_swarm, shows the history of commits in a software project. A commit happens when a developer makes changes to the code or documents and transfers them into the central project repository. Both developers and files are represented as moving elements. When a developer commits a file, it lights up and flies towards that developer. Files are colored according to their purpose, such as whether they are source code or a document. If files or developers have not been active for a while, they will fade away. A histogram at the bottom keeps a reminder of what has come before.

see Code Swarm, http://code.google.com/p/codeswarm

code_swarm – Eclipse (short ver.) from Michael Ogawa on Vimeo.

What is the best way to communicate source code changes? Write a mail, send an instant message or hope the next cvs sync will inform all your co-worker? Vincent Massol suggests two solutions: “Diff emails on SCM commit” and “RSS feeds”. This solutions are good ideas for small projects, but with a lots of changes (important and unimportant) this doesn’t work.

I think the best way to communicate important source code changes is a project team Wiki with the ability to create source code links. This links should have two possible targets. When you click on a source code link in a standard browser, you will directed to the source code in a WebCVS view and a click in the Eclipse embedded web browser will open the source code.

If you use SnipSnap as project wiki tool, you can install my IDE Wiki Plugin for Eclipse to use source code links:

Links

• IDE Wiki Plugin – Project Site
• Screencast
• Installation Instruction
• Download (ZIP: plugin + SnipSnap extension)
• Eclipse Update Site (plugin only):
  http://ide-wiki.googlecode.com/svn/trunk/IdeWikiUpdateSite/

Findbugs looks for bugs in Java programs
Update-Site: http://findbugs.cs.umd.edu/eclipse/

PMD scans Java source code and looks for potential problems
Update-Site: http://pmd.sourceforge.net/eclipse

Checkstyle helps you ensure that your Java code adheres to a set of coding standards
Update-Site: http://eclipse-cs.sourceforge.net/update/

Code Analysis Plugin (CAP) checks dependencies between the classes and packages and gives you a hint about the architecture, reusability and maintainability.
Update-Site: http://cap.xore.de/update

moreUnit is a eclipse plugin that should assist you writing more unit test.
Update-Site: http://moreunit.sourceforge.net/org.moreunit.updatesite/

EclEmma is a free Java code coverage tool for Eclipse.
Update-Site: http://update.eclemma.org/

JAutodoc is an Plugin for automatic adding Javadoc and file headers to your source code.
Update-Site: http://jautodoc.sourceforge.net/update/

..in your browser with: http://www.websequencediagrams.com/

“The SD Generator was created by Steve Hanov, who does not like using Microsoft Visio.”

“Projektmanagement von Projity für Linux, Unix, Mac und Windows

Mit “OpenProj” will Projity eine Open-Source-Alternative zu proprietären Projektmanagement-Lösungen wie Microsoft Project bieten. Die Java-Applikation steht in der Version 1.0 ab sofort für Linux, Unix, Mac und Windows bereit.
…
So kann OpenProj z.B. Dateien aus Microsoft Project öffnen und in sein eigenes Format überführen.”

Quelle: Golem.de

Links

• Projekt-Seite von OpenProj
• OpenProj by Projity: The Next Step In The Open Source Solution

Screenshot

jOra ist ein Eclipse-Plugin für Oracle Developer und Oracle Admins. Es macht die Arbeit mit Oracle einfacher, effizienter und erleichtert den täglichen Umgang mit der Datenbank.
jOra integriert sich nahtlos in die Eclipse Workbench und ist damit auch bestens für Java-Entwickler geeignet die für die Datenhaltung eine Oracle Datenbank einsetzen.

Links

• jOra Project Site
• Updatesite: http://jora.luenasoft.de/updatesite

EclEmma is a free Java code coverage tool for Eclipse, available under the Eclipse Public License. Internally it is based on the great EMMA Java code coverage tool, trying to adopt EMMA’s philosophy for the Eclipse workbench:

• Fast develop/test cycle: Launches from within the workbench like JUnit test runs can directly be analyzed for code coverage.
• Rich coverage analysis: Coverage results are immediately summarized and highlighted in the Java source code editors.
• Non-invasive: EclEmma does not require modifying your projects or performing any other setup.

..implemented by Marc R. Hoffmann. It’s simply the best JUnit coverage plugin for Eclipse.

• Project Site
• Update Site: http://update.eclemma.org/