The integration of the widget is very simple and it’s supports some interface reps. abstract classes which helps by the customizing. See AbstractSettings and AbstractLanguageManager. My only problem was to set a new min zoom level because the limit constant in ISettings is not overwriteable. But as workaround it is possible to use the IGanttEventListener. zoomedIn(…) to stop zooming in a not useful zoom level.
“Sorting Thoughts” is a personal information and knowledge management software. It is designed to manage your thoughts such as moments of sudden inspirations, tasks, events, projects and anything else you may think of.
My Eclipse RCP application Sorting Thoughts (for Mac OS X and MS Windows, Sync with HP Palm webOS devices) is now ready for beta test. If you looking for a personal information and knowledge management software try a look at:
“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.”
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.”
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
..a new metaphor for knowledge access and management.
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
..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.
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.