Ryuichi Okumura

iYQL 0.3.0, supported HTTPS endpoint

2013-04-30T00:00:00-07:00

I have been updated Node.js version iYQL which I made last year. It added "--ssl" option to command line in the update of this time.

$ iyql -h
Usage: iyql [options]

Options:
  -p, --endpoint set YQL endpoint URL
                 default: http://query.yahooapis.com/v1/public/yql
  -e, --env      set YQL env URL
  -h, --help     print help
  -s, --ssl      use HTTPS endpoint
  -v, --version  print version

This was formerly the default the HTTP YQL endpoint, but you can change it to use at the time of the request the HTTPS YQL endpoint by specifying this option.

Because YQL tables can usually be used via HTTP, but some tables have become mandatory request via HTTPS, that would be a good place to use this option when such.

You can be installed via npm command.

$ npm install -g iyql

Because I think the ability add more, please check the GitHub repository if desired or bug.

node-iyql on GitHub

Promises/A+ at YUI

2013-03-29T00:00:00-07:00

Added a module that compatible with the Promises/A+ in YUI 3.9.0, which was released recently. Promises/A+ is a specification that further improve the specification of Promises/A of CommonJS. Such as specifications and test cases that have been published on GitHub. Today, I would like to introduce the sample code for that module.

Load promise module

First, you need to load promise module, and you can use Y.Promise within YUI sandbox.

YUI().use('promise', function (Y) {

    // You can use Y.Promise

});

"Y.Promise" and "then" function

Basic usage is something similar to the following.

var promise = new Y.Promise(function (fulfill) {
    fulfill(10);
});

promise.then(function (value) {
    Y.log(value); // value: 10
});

The callback function of Y.Promise accept a second function for rejected.

var promise = new Y.Promise(function (fulfill, reject) {
    reject(20);
});

promise.then(function (value) {
    Y.log(value);
}, function (value) {
    Y.log(value); // value: 20
});

A instance of Y.Promise is chainable.

var promise = new Y.Promise(function (fulfill, reject) {
    Y.log('OK 1');
    fulfill(10);
});

promise.then(function (value) {
    Y.log('OK 2');
    return Y.Promise(function (fulfill) {
        fulfill(10);
    });
}).then(function (value) {
    Y.log('OK 3');
});

This result just below.

OK 1
OK 2
OK 3

"Y.when" function and "Y.batch" function

The promise module provide 2 advance functions for YUI instance.

Y.when function is abstraction API allowing you to interact with promises or raw values as if they were promises.

Y.when(new Y.Promise(function(fulfill) {
    fulfill(10);
}), function (value) {
    Y.log(value); // value: 10
});

Y.batch function returns a new promise that will be resolved when all operations have completed.

function fn(value) {
    return new Y.Promise(function (fulfill, reject) {
        fulfill(value);
    });
}

Y.batch(fn(10), fn(20), fn(30)).then(function (result) {
    Y.log(result); // [10, 20, 30]
});

So please try using it now.

Using YConnect with Node.js and YQL

2013-02-13T00:00:00-08:00

Last November, Yahoo! JAPAN released a product called YConnect. This is a new authorization system that is compatible with OAuth 2.0 and OpenID Connect. In OAuth 2.0, the flow is simplified compared to OAuth 1.0, so it is easy for developers to implement. Furthermore, YConnect anticipates client-side applications such as native applications and can support many cases of use. This time, I would like to introduce examples that uses UserInfo API, supplied by YConnect, from Node.js and YQL.

YConnect with Node.js

First, with Node.js, I have created a npm package for YConnect. You can install the package via npm command.

$ npm install yconnect

By passing the access token to access the API, you can retrieve the data.

var YConnect = require('yconnect').YConnect;
var yc = new YConnect({
    access_token: '<access token>'
});

yc.getUserInfo({schema: 'openid'}, function (error, data) {
    if (!error) {
        console.log(JSON.parse(data));
    } else {
        console.log(error);
    }
});

The result just below.

{ user_id: '43M63NAGMHBAYMXRMY3WODOWS4',
  name: 'OkumuraRyuichi',
  given_name: 'Ryuichi',
  'given_name#ja-Kana-JP': '',
  'given_name#ja-Hani-JP': 'Ryuichi',
  family_name: 'Okumura',
  'family_name#ja-Kana-JP': '',
  'family_name#ja-Hani-JP': 'Okumura',
  locale: 'ja-JP',
  email: 'okuryu@gmail.com',
  email_verified: true,
  address:
   { country: 'jp',
     postal_code: '1060032',
     region: 'Tokyo',
     locality: 'Minato-ku' },
  birthday: '1984',
  gender: 'male' }

YConnect with YQL

Next is YQL. In the same way, I have created a table for YConnect. YQL can be tested easily from the YQL Console too, but this time I will show an example of executing with the iyql command that I made last time.

$ npm install iyql

The result just below.

$ iyql
iyql> select * from yahoojp.yconnect.userinfo where access_token="<access token>" and schema="openid"
{
    "user_id": "43M63NAGMHBAYMXRMY3WODOWS4",
    "name": "OkumuraRyuichi",
    "given_name": "Ryuichi",
    "given_name_ja-Kana-JP": "",
    "given_name_ja-Hani-JP": "Ryuichi",
    "family_name": "Okumura",
    "family_name_ja-Kana-JP": "",
    "family_name_ja-Hani-JP": "Okumura",
    "locale": "ja-JP",
    "email": "okuryu@gmail.com",
    "email_verified": "true",
    "address": {
     "country": "jp",
     "postal_code": "1060032",
     "region": "Tokyo",
     "locality": "Minato-ku"
    },
    "birthday": "1984",
    "gender": "male"
}

YConnect can be used immediately once an application ID is issued, so please try using it.

Faster function that happen async with YUI

2013-01-31T00:00:00-08:00

From next version of YUI, timers module will add into YUI core module. You can use Y.soon function by this module.

This function is similar to Y.later, used when there is something that you want to process asynchronously. Recently, we have come out that can be used to implement a function called setImmediate in IE10 and Node.js 0.9. Y.soon can also consider such implementation, asynchronous processing is performed faster than Y.later.

Just show you an example.

<script src="http://yui.yahooapis.com/3.9.0pr2/build/yui/yui-min.js"></script>
<script>
YUI().use('timers', function (Y) {
  Y.log('hello timers');
  var asyncTask = Y.soon(myTask);
  Y.log('end timers');
  function myTask() {
    Y.log('called myTask()');
  }
});
</script>

It results in the following.

hello timers
end timers
called myTask()

YUI also supports Node.js, so that the same logic also works on the browser, even on Node.js.

In addition, there is a function called to cancel in object that Y.soon returns. You can then call this function to cancel the action to be performed.

<script src="http://yui.yahooapis.com/3.9.0pr2/build/yui/yui-min.js"></script>
<script>
YUI().use('timers', function (Y) {
  Y.log('hello timers');
  var asyncTask = Y.soon(myTask);
  Y.log('end timers');
  asyncTask.cancel();
  function myTask() {
    Y.log('called myTask()');
  }
});
</script>

If you call cancel and you will not be executed.

hello timers
end timers

This feature is available from YUI 3.9.0, its Preview Release 2 is currently. The GA is planned in the near future. There is a possibility that Y.later is obsolete in the future, it would be good to remember that the Y.soon.

Looking back on 2012

2012-12-31T00:00:00-08:00

As the my goal of the year, I have listed three things. They haven't decided the concrete contents in advance. Determine goals and only roughly, more I have to be any good thing to be associated with that goal.

Contribute to the internet

I sent a total of 50 patches near several OSS. I think most of them are small, but, whether it is the contribution for each community was able to more than a little than nothing. Then, I had to write a blog in English this year. As write once a month, I was somehow continued one year. If I feel tired that I have every week, as my pace is so good about this. I began to increase little by little opportunity to use English on Twitter, G+, even such as Google Reader.

Take photos

Number to take pictures this year has been reduced considerably. I think I should take a lot to take because it isn't a goal, indifferently in the future. After that, I entered the dark room for the first time this year in college. Because I want to go again in the near future, I may continue for some time as well.

Go trips

I didn't go anywhere, unfortunately. Since there is no most likely outcome of the three, I want to go somewhere next year.

I won't change the three things for the next year. Have a good year.

How to run Yeti with QUnit testing

2012-11-28T00:00:00-08:00

QUnit is a JavaScript Unit Testing framework by jQuery project. I would like to introduce to the way to run Yeti with QUnit testing since latest Yeti Supporting QUnit test cases.

At first, setup minimum QUnit test case.

<!DOCTYPE html>
<html>
<head>
  <meta charset="utf-8">
  <title>QUnit Example</title>
  <link rel="stylesheet" href="/resources/qunit.css">
</head>
<body>
  <div id="qunit"></div>
  <script src="/resources/qunit.js"></script>
  <script src="/resources/tests.js"></script>
</body>
</html>

And, create test.js just like this.

test( "hello test", function() {
  ok( 1 == "1", "Passed!" );
});

Install Yeti via npm command.

$ npm install -g yeti

Start Yeti as server mode. Yeti Hub waits to execute testing.

$ yeti -s
Yeti Hub started. LAN: http://10.0.1.10:9000
                  Local: http://localhost:9000

And, open the http://localhost:9000/ in some web browsers that you like. Next open new Shell and run test via Yeti command.

$ yeti tests.html
  Agent connected: Chrome (23.0.1271.91) / Mac OS
✓ Testing started on Chrome (23.0.1271.91) / Mac OS
✓ Agent completed: Chrome (23.0.1271.91) / Mac OS
✓ 1 tests passed! (0.21 seconds)

That's all. If there is some browsers you want to test, you simply open the Yeti Hub URL. You can be a very large number of tests on actual browsers via one command. And Yeti also supports more other testing frameworks such as Mocha, Jasmine, YUI Test.

Yeti is a open source project that has very active releases, please check it.

Node.js in YUI

2012-10-30T00:00:00-07:00

Article about Node.js that was released for the first time in YUI Blog was that of 2010. Although more than two years has passed since then, a set of tools around YUI is that it works on all Node.js finally. I think this time I would like to summarize that also serves as an introduction to each tool.

yUglify

A tool that has been wrapped for YUI based on the UglifyJS and cssmin. YUI Compressor that has been used until now will be obsolete in the future We will use this as a successor.

YUI Test

A JavaScript unit testing framework. It has supported Node.js at a relatively early stage. Have tested using YUI Test is also YUI core code.

Yeti

A tool for cross-browser testing. This is a tool that allows you to run a test with a single command to test on multiple browsers and devices. You can implement the proprietary protocols, Yeti is inside is an interesting tool that can be very good. Easy to understand and I would watch the Reid's video and Dav's video.

Grover

It is a tool to run on a headless browser tests of YUI Test using PhantomJS. Please take a look at last month, so I introduced in my blog post.

YUI Doc

It is a tool that generates API documentation from the code of JavaScript. Previously, it had been implemented in Python, Node.js has now become well.

Shifter

It is a tool used to build YUI module corresponding to the successor of YUI Builder. YUI Builder was Java(Ant), Shifter is Node.js base. Please take a look because this is also introduced in the previous blog.

Yogi

This has not been officially announced or still under development, it is still without much documentation. It seems to be something like a support tool for the development of gallery modules and YUI.

Because they are all published on GitHub, you can contribute the code if anyone has signed the CLA of YUI everyone.

Testing JavaScript with PhantomJS and YUI Test

2012-09-30T00:00:00-07:00

There are a variety of what is called a JavaScript test framework, YUI Test is one of them. Also, PhantomJS is famous as headless browser, the JavaScript code by using the PhantomJS you can be run from the command line. If you install PhantomJS the application of this becomes possible to test JavaScript code on the server. Grover is a tool to run test cases of YUI Test on PhantomJS.

Install Grover

You can easily install it via npm command since Grover are a matched package npm.

npm install -g grover

Must be installed PhantomJS. Download it, they are provided for binary Mac OS X and Windows, Linux.

Create test case for YUI Test

YUI Test supports many features, write a simple test case as test.html.

<script src="http://yui.yahooapis.com/3.7.2/build/yui/yui-min.js"></script>
<script>
YUI().use('test', function (Y) {
  var testCase = new Y.Test.Case({
    name: 'My Test Case',
    test1: function () {
      Y.Assert.areEqual(10, 10);
    },
    test2: function () {
      Y.Assert.isArray([1, 2, 3]);
    }
  });
  Y.Test.Runner.add(testCase);
  Y.Test.Runner.run();
});
</script>

Run Grover

The test is performed on PhantomjS, results will be display simply by running Grover.

$ grover test.html
Starting Grover on 1 files with PhantomJS@1.7.0
  Running 15 concurrent tests at a time.
✔ [testSuite_yui_3_7_2_1_1348986046983_9]: Passed: 2 Failed: 0 Total: 2 (ignored 0)
----------------------------------------------------------------
✔ [Total]: Passed: 2 Failed: 0 Total: 2 (ignored 0)
  [Timer] 3.265 seconds

More advantage

This is the simplest example of YUI Test and Grover. Since there are many more features, please look at the document.

Building YUI module with shifter

2012-08-28T00:00:00-07:00

YUI Builder tool that has been used to build the module for YUI until now. This is a tool that can be used as well as YUI core module, in the same manner if you have own YUI module or YUI Gallery module. YUI Builder works with Ant (Java), and it can define the information and settings to build each module. In addition, a convenient macro has been defined by default in YUI Builder, and through JSLint, and compressed with YUI Compressor, and build JavaScript code for debugging, you can build them by one command ("ant all"). It is useful Ant because flexibly combine various settings, but there are no very fast in practice (it took about 10 minutes when I try to build all YUI core modules on my Mac). It has been increasing more and more core modules of YUI, YUI was one of the challenges of the time it takes to build.

Currently, Dav from YUI team working on a new tool called shifter for build YUI module. Node.js based command line tools, shifter is the future of the YUI module is likely to use the shifter (the transition to the shifter has already begun even YUI core modules). I would like to introduce to shifter can be migrated easily from YUI Builder existing modules.

shifter is since the npm package, you can install that via npm command.

$ npm install -g shifter

I think the case of an existing YUI module, YUI Builder and configuration files are named "*.properties". If this file exists, shifter will switch to the new build system to generate a "build.json" from this file automatically. If there is a "build.json", shifter referring to prioritize the "build.json". In other words, it is you only need to remove the "build.json" if you want to re-create the "build.json" from "*.properties".

Future, if you create a new YUI module looks like this.

$ mkdir -p my-module/src/module-foo/js
$ cd my-module/src/module-foo
$ touch my-module/src/module-foo/js/foo.js
$ touch my-module/src/module-foo/build.json

"build.json" smallest is as follows.

{
  "name": "module-foo",
  "builds": {
    "foo": {
      "jsfiles": [
        "js/foo.js"
      ]
    }
  }
}

Run shifter command.

$ shifter
shifter [info] revving up
shifter [info] looking for build.json file
shifter [info] found build.json file, shifting
shifter [info] putting the hammer down, let's build this thing!
shifter [info] putting the hammer down
shifter [info] shifting into gear for my-module
shifter [info] using preferred jslint setting
shifter [queu] writing RAW file
shifter [queu] compressing
shifter [queu] writing -min file
shifter [info] shifting for coverage
shifter [queu] coverage file read, starting coverage
shifter [queu] writing coverage file
shifter [info] done racing, the gears are toast
shifter [info] finished in 1.259 seconds, pretty fast huh?

This completes the build is successful when you run shifter command. JavaScript file is being output to the directory for the build if build is successful.

$ ls -l ../../build/my-module
total 32
-rw-r--r--  1 okuryu  staff  1330 Aug 27 23:12 my-module-coverage.js
-rw-r--r--  1 okuryu  staff    84 Aug 27 23:12 my-module-debug.js
-rw-r--r--  1 okuryu  staff    52 Aug 27 23:12 my-module-min.js
-rw-r--r--  1 okuryu  staff    84 Aug 27 23:12 my-module.js

In addition to the features of the YUI Builder, shifter has some useful features. That is what is on and that the lint feature by default, through JSLint against JavaScript files in the build process of the shifter. It is divided into modules that actual yui-lint. They will monitor changes in the file and run the shifter with a "--watch" option also, it will be me also through lint build runs automatically every time you save the file.

For more infomation about shifter, look Dav's post on YUI Blog and shifter user guide. I think the shifter will still be improved in the future, please try to file a ticket on GitHub if there is a bug and requests.

iYQL on Node.js

2012-07-31T00:00:00-07:00

In the past, Diego Souza implemented iYQL. This is command line based simple YQL client. I liked this approach, but its not easy to install on my machine for me (need install Haskell) and I met a few strange bugs on my environment for some reason.

Since I just published "iyql" npm module that has features similar to that one on npmjs.org. And, its open sourced on my GitHub repository. Please read just below if you are familiar with Node.js.

Installation

$ npm install -g iyql

Note: Currently, depend on Node.js 0.8.x.

Usage

$ iyql -h
Usage: iyql [options]

Options:
  -p, --endpoint set YQL endpoint URL
                 default: http://query.yahooapis.com/v1/public/yql
  -e, --env      set YQL env URL
  -h, --help     print help
  -v, --version  print version

You can pass YQL statements into iyql REPL prompt.

$ iyql
iyql> desc weather.forecast
{
  "query": {
    "count": 1,
    "created": "2012-07-30T14:45:14Z",
    "lang": "en-US",
    "diagnostics": {
      "publiclyCallable": "true",
      "url": {
        "execution-start-time": "0",
        "execution-stop-time": "575",
        "execution-time": "575",
        "id": "4a00f6a7-0c5d-4d86-877a-c211fa3e88bb",
        "proxy": "DEFAULT",
        "content": "http://www.datatables.org/alltables.env"
      },
      "user-time": "626",
      "service-time": "588",
      "build-version": "29152"
    },
    "results": {
      "table": {
        "hash": "aae78b1462a6a8fbc748aec4cf292767",
        "name": "weather.forecast",
        "security": "ANY",
        "meta": {
          "author": "Yahoo! Inc",
          "description": "Weather forecast table",
          "documentationURL": "http://developer.yahoo.com/weather/",
          "sampleQuery":
            "select * from weather.forecast where woeid=2502265"
        },
        "request": {
          "select": [
            {
              "key": [
                {
                  "name": "location",
                  "required": "true",
                  "type": "xs:string"
                },
                {
                  "name": "u",
                  "type": "xs:string"
                }
              ]
            },
            {
              "key": [
                {
                  "name": "woeid",
                  "required": "true",
                  "type": "xs:string"
                },
                {
                  "name": "u",
                  "type": "xs:string"
                }
              ]
            }
          ]
        }
      }
    }
  }
}
iyql> select * from geo.places where text="hikarigaoka"|truncate(count=1)
{
  "query": {
    "count": 1,
    "created": "2012-07-30T14:51:20Z",
    "lang": "en-US",
    "diagnostics": {
      "publiclyCallable": "true",
      "url": [
        {
          "execution-start-time": "0",
          "execution-stop-time": "577",
          "execution-time": "577",
          "id": "313d9c69-0140-4b3c-970d-3f5ce33cd66e",
          "proxy": "DEFAULT",
          "content": "http://www.datatables.org/alltables.env"
        },
        {
          "execution-start-time": "625",
          "execution-stop-time": "655",
          "execution-time": "30",
          "content":
            "http://where.yahooapis.com/v1/places.q(hikarigaoka);
            start=0;count=10"
        }
      ],
      "user-time": "656",
      "service-time": "618",
      "build-version": "29152"
    },
    "results": {
      "place": {
        "lang": "en-US",
        "uri": "http://where.yahooapis.com/v1/place/28414615",
        "woeid": "28414615",
        "placeTypeName": {
          "code": "10",
          "content": "Local Administrative Area"
        },
        "name": "Hikarigaoka",
        "country": {
          "code": "JP",
          "type": "Country",
          "content": "Japan"
        },
        "admin1": {
          "code": "JP-13",
          "type": "Prefecture",
          "content": "Tokyo Prefecture"
        },
        "admin2": {
          "code": "",
          "type": "Gun/Ku",
          "content": "Nerima-ku"
        },
        "admin3": null,
        "locality1": {
          "type": "Town",
          "content": "Tokyo"
        },
        "locality2": null,
        "postal": null,
        "centroid": {
          "latitude": "35.761822",
          "longitude": "139.631378"
        },
        "boundingBox": {
          "southWest": {
            "latitude": "35.753571",
            "longitude": "139.621826"
          },
          "northEast": {
            "latitude": "35.770081",
            "longitude": "139.640945"
          }
        },
        "areaRank": "1",
        "popRank": "0"
      }
    }
  }
}

This is my experiment implements yet. I would like to enhance more useful features. So please watch my repository, file a issue on GitHub if you are interested in this one.

node-iyql on GitHub

PhantomJS 1.6 Changes

2012-06-27T00:00:00-07:00

Recently, PhantomJS 1.6 has released. PhantomJS has a flower name for each releases, this version has "Lavender". This version is minor update, but it's has some new features in view of the release note, I tried a few points.

Support for passing arguments to WebPage's evaluate

You can now pass the variable to the callback function of page.evaluate.

var prefix = 'Title:',
  result;

result = page.evaluate(function (p) {
  return p + document.title;
}, prefix);

console.log(result);

Callbacks for JavaScript onConfirm and onPrompt

onConfirm, onPrompt of JavaScript callbacks has been added.

var result;

page.onConfirm = function(msg) {
  console.log(msg);
};

result = page.evaluate(function() {
  return window.confirm('Hello Confirm!');
});

Support for Cookies handling

Cookie data has been supported. Until now was not only pass in the options of the command of PhantomJS, but you can now be specified in the page object.

page.cookies = [{
  'name': 'Cookie-Name',
  'value': 'Cookie-Value',
  'domain': 'localhost'
}];

'os' object to the system module

The 'os' object has been added into system module.

var os = require('system').os;

for (var p in os) {
  console.log(p + ': ' + os[p]);
}

The result is like this:

architecture: 32bit
name: mac
version: 10.7 (Lion)

Support for asynchronous evaluation

You can now asynchronously evaluation of the page. This is useful if you don't need the results of evaluation.

page.evaluateAsync(function () {
  // do something
});

Complete changes to release note since it is written, please check it out.

Introduce jscomplete-vim

2012-05-24T00:00:00-07:00

jscomplete-vim is the modern complement Vim plugin for JavaScript guys.

Using as omnifunc

Set jscomplete#CompleteJS to omnifunc in your .vimrc like this.

autocmd FileType javascript setlocal omnifunc=jscomplete#CompleteJS

Then available auto complement properties after ., [ keywords.

Using as neocomplcache plugin

neocomplcache is the Vim plugin to keyword completion. No more is necessary to basically using.

Optional extensions

Extension scripts under the autoload/js/ will be loaded with set list to g:jscomplete_use or b:jscomplete_use in your .vimrc like this.

let g:jscomplete_use = ['dom', 'moz']

dom: Adding DOM keywords completion.
moz: Adding Mozilla JavaScript keywords completion.
dom: Adding Mozilla XPCOM component keywords completion.

Idiomatic JavaScript in Japanese

2012-04-28T00:00:00-07:00

Recently, I just translated into Japanese a document called Idiomatic JavaScript.

I don't see any reason that you should have to be particular about relating to this document, but if you need to write new JavaScript code now, this is very useful for you. If you are already have any rules in your team or projects, you should follow it.

Please remember that the code that wrote has a possibility to modified frequently, used for a long time, or taken over by someone else.

Your code won't belong only to you anyone. We always need to understand the engineering and keep to write right code.

Time to YUI 3

2012-03-23T00:00:00-07:00

What should we when to move to YUI 3 from YUI 2? That is yesterday!

YUI 2 is still available via Yahoo! CDN, but YUI team already announced that they will not fix any issues on YUI 2. And, any features will be probably not added to YUI 2. YUI team's all resources already moved to YUI 3.

YUI 2.9.0 Release Update » Yahoo! User Interface Blog (YUIBlog)

Next week the YUI team will begin planning for release 2.9.0 to be shipped in the second half of Q1 2011. YUI 2.9.0 will be the last major dot-release of the 2.x codeline, and the team will be aggressively reviewing all open tickets against the YUI 2 project and either assigning them to be a part of the 2.9.0 release, closing them as “WON’T FIX”, or moving them to the YUI 3 project.

For the migration, incompatible APIs could be a potential setback, but Node module already has migration table as core API of YUI 3. Additionally, the migration might take many times with scale of your applications, but I think to it may not be so difficult, because YUI 3's documents is enhanced to offer useful information on yuilibrary.com.

Only one important point with you using YUI 3. That is, YUI 3 is oriented module. YUI 3's module is sheared into fragments (look build directory). You should specify module names that you want use into use() function. Actually, you can use these module within callback function, it is called YUI sandbox.

YUI().use('node-base', function (Y) {

    var h1 = Y.one('h1');

});

Please read explanation of YUI Global Object for more understanding YUI global object, sandbox, loading module.

If you must need to use YUI 2, YUI 3 has the feature to loading YUI 2 module.

YUI().use('yui2-treeview', function (Y) {

    var YAHOO = Y.YUI2;
    var tree = new YAHOO.widget.TreeView('tree');

});

But I am not recommend to using this feature, because the fact remains that you still using YUI 2. This is used as tentative.

If you develop problems with migration, you can try to file a ticket on yuilibrary.com, and if you can provide patch for YUI, you can send "Pull Request" on GitHub.

And, see also the discussion about migration on yuilibrary.com.

HTML5 Boilerplate 3.0 in Japanese

2012-02-18T00:00:00-08:00

I just completed to translate HTML5 Boilerplate 3.0 in Japanese. HTML5 Boilerplate is the template sets that uses Web technologies such as HTML5 and CSS3. You may not have a chance to use them as a whole, but I think the techniques and know-hows one individual is going to be very helpful.

And, please let me know or send to "Pull Request" to GitHub repository if you found wrong translation.

Move to Jekyll

2012-01-22T00:00:00-08:00

In the past, I have used static files by manual operations, or a CMS tools like Movable Type for manage web site. From now on, I had decided to use Jekyll. Jekyll is simple tool to manage static files. Currently, GitHub Pages is introducing Jekyll and it being able to easy hosting files that manage by Jekyll. In addition, if you configure DNS, it will be possible hosting with a domain that you like. If there are any wrong on this site, you can send "pull request" to my repository on GitHub.

About languages which using on this site. I can read, write, listen, speak only Japanese. It may be easy for me, but English is able to convey my things to more many people. From now on, I'll use English and Japanese as it may chance on this site. If you can't read it, you can use a translate service like Google Translate.

In addition, I moved off FeedBurner. The new feed URL is http://www.okuryu.com/atom.xml. Please update your feed reader, If you want to continue to subscribe my update.