A few interesting gadgets for Google Desktop, including Separator and Indexing Status.
I'm trying out Google Desktop on Windows 7 and comparing to Windows Search.
Saturday, June 19, 2010
eclipse-cs: The Checkstyle Plug-in for Eclipse
eclipse-cs: The Checkstyle Plug-in for Eclipse: "The eclipse-cs Checkstyle plug-in integrates the well-known source code analyzer Checkstyle into today's leading IDE - Eclipse.
Checkstyle is a Open Source development tool written by Oliver Burn, Lars K�hne and others to help you ensure that your Java code adheres to a set of coding standards. Checkstyle does this by inspecting your Java source code and pointing out items that deviate from a defined set of coding rules.
Apart from using the Eclipse Checkstyle plug-in you can also use Checkstyle from the command line or as part of an Ant build.
For more information about using Checkstyle outside of Eclipse see the Checkstyle documentation.
With the Checkstyle Eclipse plug-in your code is constantly inspected for problems. Within the Eclipse workbench you are notified of problems via the Eclipse Problems View and source code annotations just as you would see with compiler errors or warnings.
Visit the screenshots page to get a clue."
Checkstyle is a Open Source development tool written by Oliver Burn, Lars K�hne and others to help you ensure that your Java code adheres to a set of coding standards. Checkstyle does this by inspecting your Java source code and pointing out items that deviate from a defined set of coding rules.
Apart from using the Eclipse Checkstyle plug-in you can also use Checkstyle from the command line or as part of an Ant build.
For more information about using Checkstyle outside of Eclipse see the Checkstyle documentation.
With the Checkstyle Eclipse plug-in your code is constantly inspected for problems. Within the Eclipse workbench you are notified of problems via the Eclipse Problems View and source code annotations just as you would see with compiler errors or warnings.
Visit the screenshots page to get a clue."
Java theory and practice: Where's your point?
Java theory and practice: Where's your point?
Great overview of the non-integral numeric values in Java.
Explains the floating-point types (float and double) and arbitrary-precision decimal (java.math.BigDecimal).
Wednesday, June 16, 2010
Google C Style Guide
A coding style guide (coding standards) from Google: Google C Style Guide.
Some useful recommendations, no matter which language you code in.
Thursday, June 10, 2010
Redmine - RedmineUpgrade - Redmine
Original Redmine Upgrade instructions: Redmine - RedmineUpgrade - Redmine
These instructions explain how to perform a Redmine upgrade. The version I deployed today does not have subtask support so I might need to get the latest one from the source code repository directly.
Edit: My tailored version of the instructions: Redmine Upgrade.
Edit: My tailored version of the instructions: Redmine Upgrade.
RedMine Installation on Windows (issue tracker)
RedMine
The current version of the installation instructions are at my RedMine page.
The instructions below are now obsolete!
------------------------------------------------------------------------------------
Installation
gem install rails -v=2.3.5
# adapter: mysql
# database: redmine
# host: localhost
# username: root
# password:
# encoding: utf8
production:
adapter: sqlite3
dbfile: db/redmine.db
Tuesday, June 08, 2010
US Immigration – A Guide for Employees
US Immigration – A Guide for Employees: "E-3 Visa for Australians
In 2005, the US announced a new visa called the E-3, for Australians only. The E3 visa allows Australian nationals, along with their spouses and children, to come to the US to work in a specialty occupation.
This should be welcome news for Australians interested in working in the US. Until now, Australians have had to battle it out with others around the world for the highly desired H1B Visa. Last year only 900 Australians obtained an H1B - now Australians have 10,500 E3 visas just for themselves. A specialty occupation is one that requires a body of knowledge in a professional field, and at least a bachelor's degree or its equivalent, as a minimum for entry into the occupation in the United States. For Australians interested in the E3 visa, the process is actually quite similar to the H1B visa. You must first find a job with a company who will then sponsor your visa. There are 10,500 E-3 visas available per year.
Spouses of an E-3 visa holder are permitted to come to the US and work also. A spouse's employment may be in a position other than a specialty occupation."
In 2005, the US announced a new visa called the E-3, for Australians only. The E3 visa allows Australian nationals, along with their spouses and children, to come to the US to work in a specialty occupation.
This should be welcome news for Australians interested in working in the US. Until now, Australians have had to battle it out with others around the world for the highly desired H1B Visa. Last year only 900 Australians obtained an H1B - now Australians have 10,500 E3 visas just for themselves. A specialty occupation is one that requires a body of knowledge in a professional field, and at least a bachelor's degree or its equivalent, as a minimum for entry into the occupation in the United States. For Australians interested in the E3 visa, the process is actually quite similar to the H1B visa. You must first find a job with a company who will then sponsor your visa. There are 10,500 E-3 visas available per year.
Spouses of an E-3 visa holder are permitted to come to the US and work also. A spouse's employment may be in a position other than a specialty occupation."
Running a web server (Cassini)
My favorite way of starting the Cassini web server is by creating a batch file in SendTo directory. The content of the file is:
"C:\Program Files\Common Files\Microsoft Shared\DevServer\10.0\WebDev.WebServer40.EXE" /path:"%1"
You can name it "start web server here.cmd". Then, simply right-click a folder in Windows Explorer, select Send To and "start web server here.cmd".
Monday, June 07, 2010
Scott Hanselman - The Weekly Source Code 25 - OpenID Edition
Scott Hanselman - The Weekly Source Code 25 - OpenID Edition
Cool post about implementing OpenID. Adding the following two lines to your blog/site will make it your OpenID:
<link rel="openid.server" href="http://www.myopenid.com/server" />
<link rel="openid.delegate" href=http://YOURUSERNAME.myopenid.com/ />
There is also a part discussing implementation of OpenID authentication in .Net.
Tuesday, June 01, 2010
Upgrading Persisted Workflows (WF 4.0)
When changing workflows, Microsoft does not support direct data migration from the long-running and persisted workflows instances. This means that every change to the workflows necessitates recompilation of the project and redeployment of the code/site. This may pose a problem for workflows that are persisted to the data store. If the changes to the workflow do not result in changes to the serialization of the workflow instance to the persistance store (database), you may be ok with updating the workflows and survive the exercise.
But, if those changes result in different serialization - meaning there are new states, activities, fields, etc. - then upgrading the workflow assembly and trying to resume persisted instances will not go all that well.
One of the ways to mitigate this in a state machine activity is to short-circuit the states. Meaning, apart from the initial trigger, there would be an additional trigger for short-circuiting the flow. The Receive activity, the trigger, could accept just the case identifier if your case data is stored in a database anyway. Then the case would travel directly to the state it was left in, before it was persisted, rather than go through the state machine all over again.
In the destination state activity itself a workaround is required in the Entry activity. There could be a simple If activity that does not perform any particular actions if we are short-circuiting *or* perform all the normal activities if the case came into the state the regular way.
Hopefully things get easier in the future.
But, if those changes result in different serialization - meaning there are new states, activities, fields, etc. - then upgrading the workflow assembly and trying to resume persisted instances will not go all that well.
One of the ways to mitigate this in a state machine activity is to short-circuit the states. Meaning, apart from the initial trigger, there would be an additional trigger for short-circuiting the flow. The Receive activity, the trigger, could accept just the case identifier if your case data is stored in a database anyway. Then the case would travel directly to the state it was left in, before it was persisted, rather than go through the state machine all over again.
In the destination state activity itself a workaround is required in the Entry activity. There could be a simple If activity that does not perform any particular actions if we are short-circuiting *or* perform all the normal activities if the case came into the state the regular way.
Hopefully things get easier in the future.
Subscribe to:
Posts (Atom)
