when searching via Google, after entering your search text and running the search, if you modify the resulting HTTP query string and add in the parameter “tbs” and value “tl:1” , which looks like:  ”&tbs=tl:1” and rerun that query (different depending on your browser but in most, if you just press the “Enter” key on your keyboard it will run it), you will then see a timeline like:

Google Timeline view

I will be speaking about rNews, the new standard from the IPTC for embedding metadata in on-line news content, at the upcoming SemTech conference in San Francisco. The session is Wednesday, June 8, 2011
09:45 AM – 10:35 PM. Here is the abstract for the talk:

rNews: Embedding Metadata in On-line News

The IPTC, a consortium of the world’s major news agencies, news publishers and news industry vendors, recently released rNews, a semantic standard for on-line news. rNews uses RDFa to annotate HTML documents with news-specific metadata, to help with search, ad placement, aggregation and the sharing of on-line news. Jayson Lorenzen, a software engineer with Business Wire and one of the IPTC Member organization delegates working on rNews, will give an overview of the IPTC, the rNews standard, why rNews is needed and how the standard was eventually created. The talk will include use cases and live demonstrations of rNews and will end with a call to action for you to participate; rNews is currently at version 0.5 and the IPTC is looking for feedback on how to improve the standard.

Let’s not forget Japan by jays0n With all the other terrible news these days, information regarding Japan’s recovery efforts could be taking a back seat. Did you see stories about the BP Oil Spill on the anniversary, and were you surprised to hear of the struggles still raging for the people there? Lets not let that happen so fast for Japan.

… umm actually, yeah, please do view “Let’s not forget Japan” on Storify, it looks terrible paste into a post here.

I saw some post about passing resources, but having issues with threading. Just a note to myself to not try this again.

This is a service to get HTTP codes for testing how your. stuff handles various HTTP codes.

The service is real simple to use; add a call like:

http://httpstat.us/404

to see how your app handles a 404

There is a good list of codes here too

This is silly but not super obvious and not easy to find on the interweb thingie searches come up with Oracle’s solution about linking the libjavaplugin_oji lib in the Mozilla plugins dir:

<Java installation directory>/plugin/i386/ns7/libjavaplugin_oji.so

which does not work for me. The way to get this going is to create a link to the libnpjp2 library in the Mozilla plugin directory as follows:

ln -s /<Java installation directory>/jre/lib/i386/libnpjp2.so /usr/lib/mozilla/plugins/

sudo fsck.hfsplus /dev/sdb2

This check did indeed find some errors and report it had correct them and afterwards I could once again write to the drive.

I hope this helps the next person searching for this issue. I tried to get all the terms I was searching for, unsuccessfully, into title of this post to help folks locate it. Searching for this issue seems to turn up 99.9% responses about “You have to turn off journaling before mounting with Linux” which I knew already and was not part of the problem at all.

-http-proxy http://user:pass@proxy.example.com:1234

but it did not seem to take. A little searching in some forums solved this however. I am adding it here with a title that matches what I was searching for via Google so that the next person can find it without reading a lot of forum threads.

The trick is that you need to add this info on for the project you are going to be running it from, and there is a convenient place to do so in Eclipse. With the project selected,  choose “Run” from the menu bar at the top, then “Run Configurations” This will show all the run configurations, and have the current project selected. You can also choose the Run/Configurations items from any project and select the correct one once inside. Once a configuration is chosen, choose the “Target” tab from the tabs on the right side of the Run Configurations dialog and look for the Text field labeled “Additional Emulator Command Line Options”. I had to resize the Dialog window to get this box to appear as there are no scrollpanes used there (I am using Linux version 3.5.2. of Eclipse). Below are a couple screen shots of these dialogs.



Add properties to your properties file:

[my.properties]

button.icon.search=”com/example/resorces/search.gif”
button.text.search=”Search”

Load the properties file inside the context file:

<bean
class=”org.springframework.beans.factory.config.PropertyPlaceholderConfigurer”>
<property name=”locations”>
<value>classpath:path/in/cp/my.properties</value>
</property>
</bean>

Access properties from the properties file when setting properties of a bean:

<bean id=”searchButtonBean” init-method=”init” class=”javax.swing.JButton”>
<property name=”text”>
<value>${button.text.search}</value>
</property>
<property name=”buttonIcon” value=”${button.icon.search}”/>
</bean>

Below the explanation, the example referred to in the post will be made available. Now lets get started.

First Create a target that should do some bit of work based on a condition. Make the target depend on two other targets (here these are “setup” and “fail”), and only allow it to execute if a boolean variable has the right value, using the “if” attribute of the “target” element.

<target name=”go” depends=”setup, fail” if=”allIsWellBool”>
<!– SOME WORK HAPPENS HERE –>
</target>

Next, have one of the dependencies create a boolean property based on the condition. The process is a little convoluted, in that you need to use a <condition> construct that has an <equals> test against text to create a boolean property. For instance, in the example for this post, this dependency target, “setup”, asks for some user input, then checks to see if an empty string was entered. A new boolean property is added based on the test.

<target name=”setup”>
<input message=”Please enter something:” addproperty=”somethingProp”/>

<condition property=”allIsWellBool”>
<not>
<equals arg1=”${somethingProp}” arg2=”" trim=”true”/>
</not>
</condition>
</target>

After this target either there is a new boolean property called “allIsWellBool” or there is not. Subsequent test for this property will pass if the property is there, and true, or fail if it is not.

Finally, create a target to execute if the test fails, the else condition basically. This is done by only allowing it to execute if a boolean variable has the right value again, but this time using the “unless” attribute of the “target” element. In the case of the example for this post, this target will execute unless the “allIsWellBool” exists and is true.

<target name=”fail” depends=”setup” unless=”allIsWellBool”>
<fail message=”You must enter something”/>
</target>

See also that we are adding the dependency for the “setup” target here as well. This is because this target depends on a property that is set in the “setup” target, and “setup” should therefore happen first.

The full source of the example mentioned in this post is below.

<?xml version="1.0" encoding="UTF-8"?>
<!--
    Simple example of how to do an If/Else condition in
    your build file without using the ANT-Contrib libs

    This source code is provided free of charge and placed in the
    public domain. It is not supported by anyone.

    Use this at your own risk.
-->
<project name="Test If Else Condition without ANT-Contrib" default="go">

    <!-- ======================= -->
    <!-- THE START OF THE SCRIPT -->
    <target name="go" depends="setup, fail" if="allIsWellBool">

        <echo message="Great, passed the test, lets do something!"/>
        <!-- SHOULD DO SOMETHING -->

    </target>

    <!-- =================================================== -->
    <!-- SETUP, GETS SOME INPUT THAT WE WILL TEST WITH LATER -->
    <target name="setup">

        <input message="Please enter something: " addproperty="somethingProp"/>

        <!-- SET A BOOLEAN PROPERTY IF WE GOT SOME INPUT  -->
        <condition property="allIsWellBool">
            <not>
                <equals arg1="${somethingProp}" arg2="" trim="true"/>
            </not>
        </condition>
    </target>

    <!-- ============================================ -->
    <!-- FAIL, WE DID NOT GET ANY INPUT FROM THE USER
         THIS DEPENDSON THE SETUP TASK AND WILL
         EXECUTE ONLY IF THE PROPERTY allIsWellBool
         IS FALSE
    -->
    <target name="fail" depends="setup" unless="allIsWellBool">
        <fail message="You must enter something"/>
    </target>

</project>