cvs overview

ser interessant ut...

Codeminer™ CVS Manager
CVS Repository Managing Software

CodeMiner CVSManager is a comprehensive repository monitoring and reporting tool for managing change sets in CVS
....
Search in CVSManager is used to find a particular file in the project, based on the search criteria. The advance search will help to find the file list across all the configured projects. The search criteria can be based on tags, authors, file name, log message etc.

CodeMiner CVS Manager

og litt om søk/ branch:

In the Agile development methodology, development activity on branches is a common scenario. Various features are developed in parallel for easier work environment. Hence different features will be developed on different branches.

• How many files are there in a particular branch?
• How many files intersect with other branches?
• How is my branch development rate?

Blogged with Flock

something for the lunch table...

it's like the microwave you have now, but smaller

Less is More: iwavecube Microwave : TreeHugger

Blogged with Flock

tips: eclipse, plugin, refresh

eit lite tips dersom ein plugin ikkje vil trø i kraft...

Frequently Asked Questions - JUtils ToString Generator Plugin for Eclipse

# I installed the plugin properly but can't see it anywhere:
This can happen sometimes. All you have to do is close the IDE and start it using the -clean option from command line.

# How do I use the -clean option?
-clean is a command line switch for the eclipse.exe executable. To use this, you have to open your command prompt/shell and navigate to the Eclipse installation directory. From there, type either eclipse clean or eclipse -clean. That should start the IDE.

# How will the -clean option help?
Eclipse stores lot of workspace specific data in local file system for better performance. When a new version of some plugin is installed, it's quite possible that the new version is using the plugin specific data such as preference stores created by the older version. To clean this up and aid recreation of preference stores, the -clean option is recommended.

Enkle screenshots i firefox

https://addons.mozilla.org/en-US/firefox/addon/5648

Ser temmelig pen ut. Mye mindre smertefullt å illustrere bugs.

(Inge via epost)

annotation: @SuppressWarnings

Excluding warnings using SuppressWarnings

Help - Eclipse SDK (at the bottom of this page...)

Java 5.0 offers the option to the user to disable compilation warnings relative to a subset of a compilation unit using
the annotation java.lang.SuppressWarning.

 @SuppressWarning("unused") public void foo() {
  String s;
 }

Without the annotation, the compiler would complain that the local variable s is never used. With the annotation, the compiler silently ignores this warning locally to the foo method. This enables to keep the warnings in other locations of the same compilation unit or the same project.

The list of tokens that can be used inside an SuppressWarning annotation is:

• all to suppress all warnings
• boxing to suppress warnings relative to boxing/unboxing operations
• cast to suppress warnings relative to cast operations
• dep-ann to suppress warnings relative to deprecated annotation
• deprecation to suppress warnings relative to deprecation
• fallthrough to suppress warnings relative to missing breaks in switch statements
• finally to suppress warnings relative to finally block that don't return
• hiding to suppress warnings relative to locals that hide variable
• incomplete-switch to suppress warnings relative to missing entries in a switch statement (enum case)
• nls to suppress warnings relative to non-nls string literals
• null to suppress warnings relative to null analysis
• restriction to suppress warnings relative to usage of discouraged or forbidden references
• serial to suppress warnings relative to missing serialVersionUID field for a serializable class
• static-access to suppress warnings relative to incorrect static access
• synthetic-access to suppress warnings relative to unoptimized access from inner classes
• unchecked to suppress warnings relative to unchecked operations
• unqualified-field-access to suppress warnings relative to field access unqualified
• unused to suppress warnings relative to unused code

ms ie 6, headache for developers

6 Reasons Why IE6 Must Die

[my italic]
Internet Explorer 6, released on August 27, 2001, was a package of problems right from the start. Within a year of release, Microsoft silently declared that IE6 would not make enough money for them to support as closely as a browser should supported. The result has been numerous security problems, unfixed browser bugs, and a daily migraine for developers.
....
Lack of PNG Transparency Support
....
CSS Float + Margin / Padding Issues
....
Lack of CSS Pseudo-Class & Pseudo-Element Support
....
No Min-Height CSS Support
....
CSS Anchor Background Image Flicker
....
Crashing With Code