퍼블리셔들에게 희소식이 될만한 코딩방법 입니다.
Aptana, Coda, Espresso 어플에서 사용할 수 있습니다.
부부적인 지원도 가능한 어플도 몇가지 있습니다.

자세한 내용은 아래 동영상을 보시면 감이 오실거 같네요

Zen Coding v0.5 from Sergey Chikuyonok on Vimeo.

http://jquery14.com/day-01

Performance Overhaul of Popular Methods

Many of the most popular and commonly used jQuery methods have seen a significant rewrite in jQuery 1.4. When analyzing the code base we found that we were able to make some significant performance gains by comparing jQuery against itself: Seeing how many internal function calls were being made and to work to reduce the complexity of the code base.

View the cropped chart.

In jQuery 1.4 we’ve significantly reduced the complexity of the most popular methods in jQuery. The full performance details can be found below.

Easy Setter Functions

For a while now, you’ve been able to pass a function into .attr() and the return value of that function is set into the appropriate attribute. This functionalilty has now been extended into all setter methods: .css(), .attr(), .val(), .html(), .text(), .append(), .prepend(), .before(), .after(), .replaceWith(), .wrap(), .wrapInner(), .offset(), .addClass(), .removeClass(), and .toggleClass().

Addtionally, for the following options, the current value of the item is passed into the function as the second argument: .css(), .attr(), .val(), .html(), .text(), .append(), .prepend(), .offset(), .addClass(), .removeClass(), and .toggleClass().

This enables code like:

// find all ampersands in A's and wrap with a span
$('a').html(function(i,html){
  return html.replace(/&amp;/gi,'<span>&amp;</span>');
});
 
// Add some information to the title of the anchors
$('a[target]').attr("title", function(i,title){
  return title + " (Opens in External Window)";
});

Ajax

Nested param serialization (jQuery.param() Documentation, Commit 1, Commit 2)

jQuery 1.4 adds support for nested param serialization in jQuery.param, using the approach popularized by PHP, and supported by Ruby on Rails. For instance, {foo: ["bar", "baz"]} will be serialized as “foo[]=bar&foo[]=baz”.

In jQuery 1.3, {foo: ["bar", "baz"]} was serialized as “foo=bar&foo=baz”. However, there was no way to encode a single-element Array using this approach. If you need the old behavior, you can turn it back on by setting the traditional Ajax setting (globally via jQuery.ajaxSettings.traditional or on a case-by-case basis via the traditional flag).

There are three ways to enable the traditional way of serialization:

// Enables for all serialization
jQuery.ajaxSettings.traditional = true;
 
// Enables for a single serialization
jQuery.param( stuff, true );
 
// Enables for a single Ajax requeset
$.ajax({ data: stuff, traditional: true });

More information: jQuery.param() Documentation, jQuery.ajax() Documentation, Commit, Code

JSON and script types auto-detected by content-type (jQuery.ajax Documentation, Commit 1, Commit 2)

If the response to an Ajax request is returned with a JSON mime type (application/json), the dataType defaults to “json” (if no dataType is specified). Additionally, if the response to an Ajax request is returned with a JavaScript mime type (text/javascript or application/x-javascript) , the dataType defaults to “script” (if no dataType is specified), causing the script to automatically execute.

Etag support has been added (jQuery.ajax() Documentation, Commit)

By default, jQuery ignores the Last-Modified header for Ajax requests, preferring to make request and ignore the browser cache. Specifying ifModified: true causes jQuery to use the browser cache if available. jQuery 1.4 will also send the If-None-Match header (for ETag support) if you specify ifModified.

Strict JSON parsing, using native JSON.parse (jQuery.ajax() Documentation, Commit 1, Commit 2, Commit 3)

jQuery 1.3 and earlier used JavaScript’s eval to evaluate incoming JSON. jQuery 1.4 uses the native JSON parser if available. It also validates incoming JSON for validity, so malformed JSON (for instance {foo: "bar"}) will be rejected by jQuery in jQuery.getJSON and when specifying “json” as the dataType of an Ajax request.

Serialize HTML5 elements (jQuery.param() Documentation, Commit)

The new HTML5 input types (such as `datetime` and `range`) will be included when you .serialize() a form.

Context for Ajax Request (jQuery.ajax() Documentation, Commit)

You can now specify a context for an Ajax request, and all callbacks will have that context set (allowing you to simplify your code and possibly avoid having to use closures, or use other objects).

jQuery.ajax({
    url: "test.html",
    context: document.body,
    success: function(){
        jQuery(this).addClass("done");
    }
});

Success callback receives XHR object as third argument (jQuery.ajax() Documentation, Commit)

The success callback for any ajax request now receives the XMLHttpRequest object as the third argument. Previously this XHR object was only accessible as the return value for $.ajax and the like.

Explicitly set a content-type (jQuery.ajax() Documentation, Commit)

In jQuery 1.3, the contentType setting was ignored in jQuery.ajax if no data was sent. In jQuery 1.4, the contentType is always sent. This fixes an issue with some backends that used the Content-Type header to decide what kind of response to send.

Explicitly specify a JSONP callback name (jQuery.ajax Documentation, Commit)

You can now specify the name of the JSONP callback in jQuery.ajax() using the jsonpCallback option.

Avoid pre-flighting cross-domain XHR (Commit)

Cross-domain ajax (for the browsers that support it) is smoother with jQuery as preflighting is avoided by default.

jQuery.ajax() is now using onreadystatechange instead of a timer (Commit)

Ajax requests should now take fewer resources by using onreadystatechange instead of polling.

Attributes

The performance of .css() and .attr() has been improved.

The .attr() takes a function setter (.attr() Documentation)

Not only can you use a function with .attr(), but you can also use the current value of the attribute with the function.

jQuery('<img src="enter.png" alt="enter your name" />')
.attr("alt", function(index, value) {
    return "Please, " + value;
});

.val( Function ) (.val() Documentation)

<input class="food" type='text' data-index="0" />
<input class="food" type='text' data-index="1" />

jQuery("input:text.food").hide();
 
jQuery("&lt;ul class='sortable'><li>Peanut Butter&lt;/li>&lt;li>Jelly&lt;/li>&lt;/ul>")
  .sortable()
  .bind("endsort", function() {
    $(":text.food").val(function() {
      return $("ul.sortable li:eq(" + $(this).attr("data-index")  + ")").text();
    });
  });

.text() works on text and CDATA nodes (.text() Documentation, Commit)

Core

Quick Element Construction (jQuery() Documentation, Commit)

When you create a single element with the jQuery function, you can now pass in an object to add attributes and events at the same time:

jQuery("<div/>", {
    id: "foo",
    css: {
        height: "50px",
        width: "50px",
        color: "blue",
        backgroundColor: "#ccc"
    },
    click: function() {
       $(this).css("backgroundColor", "red");
    }
}).appendTo("body");

The keys of the object are functions that will be called with each value passed as an argument.

.eq(-N), .get(-N) (.eq() Documentation, .get() Documentation, Commit)

You can now pass in negative numbers for .get() and .eq(). For example, you can select the second-to-last div or, you can access the DOM element for the same:

$("div").eq(-2);
$("div").get(-2);

New .first() and .last() methods (.first() Documentation, .last() Documentation, Commit)

For convenience, .first() and .last() are aliases of .eq(0) and .eq(-1).

New .toArray() method (.toArray() Documentation, Commit)

.get() has historically returned an Array from the jQuery set. For further clarity, you can use .toArray() to achieve the same thing in jQuery 1.4. Unlike, .get(), however, .toArray() does not take an argument.

jQuery() returns empty set (jQuery() Documentation, Commit)

In jQuery 1.3, jQuery() returned a jQuery set containing just the document. in jQuery 1.4, it returns an empty jQuery set. This can be useful for creating an empty set and adding elements to it dynamically. Note: The jQuery().ready() technique still works in 1.4 but it has been deprecated. Please use either jQuery(document).ready() or jQuery(function(){}).

jQuery(“TAG”) (Element Selector Documentation, Commit)

A faster path is used when passing in a single tag name.

jQuery(“<div>”) jQuery(“<div/>”) and jQuery(“<div></div>”) (jQuery() Documentation, Commit)

All three now use the same code path (using document.createElement), improving performance for jQuery("<div></div>"). Note that if you specify attributes, we use the browser’s native parsing (using innerHTML).

CSS

The performance of the .css() method has seen a 2x performance improvement.

The performance of the .addClass(), .removeClass(), and .hasClass() methods has seen a 3x performance improvement.

.toggleClass() can toggle multiple classes (.toggleClass() Documentation, Commit)

You can now call .toggleClass() with multiple selectors and they will all be toggled.

$("div").toggleClass("current active");

Data

.data() returns Object and .data(Object) sets the object (.data() Documentation, Commit 1, Commit 2)

It is sometimes desirable to work with the data attached to an element as a complete object. A common example would be wanting to copy the entire data from one element to another. In jQuery 1.4, .data() with no parameter returns the entire object, and .data(Object) sets the object. Keep in mind that this object includes events bound to the element, so use caution.

Data cache is no longer created if it isn’t needed (Commit 1, Commit 2, Commit 3)

jQuery uses a unique expando on DOM elements that is used to get the .data() for a particular element. jQuery now avoids creating that expando when data is looked up but no data has been added. This potentially increases performance and avoids polluting the DOM in these cases.

Effects

Per-property Easing (Per-property Easing Documentation, Commit)

In addition to being able to specify an easing function for an animation you can now specify an easing animation for individual properties. James Padolsey has more information and demos in his blog post.

$("#clickme").click(function() {
  $("div").animate({
    width: ["+=200px", "swing"],
    height: ["+=50px", "linear"],
  }, 2000, function() {
      $(this).after("<div>Animation complete.</div>");
  });
});

Events

New Method: jQuery.proxy() (jQuery.proxy() Documenation, Commit 1, Commit 2)

If you want to ensure that “this” inside a function will be permanently bound to a particular value, you can use jQuery.proxy to return a new function with that scope.

var obj = {
  name: "John",
  test: function() {
    alert( this.name );
    $("#test").unbind("click", obj.test);
  }
};
 
$("#test").click( jQuery.proxy( obj, "test" ) );

Event Multi-binding (.bind() Documentation)

You can now pass an object of many events to bind to an element.

$("div.test").bind({
  click: function(){
    $(this).addClass("active");
  },
  mouseenter: function(){
    $(this).addClass("inside");
  },
  mouseleave: function(){
    $(this).removeClass("inside");
  }
});

`change` and `submit` events normalized (Change Documentation, Submit Documentation)

The change and submit events work reliably across browsers for both normal and live events. We override the normal change and submit events in Internet Explorer and replace them with events that work identically to the other browsers.

New events: `focusin` and `focusout` (.focusin() Documentation, .focusout() Documentation, Commit)

focusin and focusout are generally equivalent to focus and blur but bubble, which helps tremendously if you are writing your own event delegation behavior. Please note that `focus` and `blur` will not work with the live() method; this was a design decision due to the DOM Events spec defining focus/blur do not bubble.

$("form").focusout(function(event) {
    var tgt = event.target;
    if (tgt.nodeName == "INPUT" && !tgt.value) {
        $(tgt).after("<span>nothing here</span>");
    }
});

All Events Can Be Live Events (.live() Documentation)

With the exception of ready, focus (use focusin instead), and blur (use focusout instead), all events that can be bound using .bind() can also be live events.

We’re very proud to count some addtional events amongst those supported by live(). 1.4 introduces cross-browser support for
change, submit, focusin, focusout, mouseenter, and mouseleave via the event delegation in .live().

Note that if you need a live focus event, you should use focusin and focusout rather than focus and blur, because, as mentioned, focus and blur do not bubble.

Also, live() also now accepts a data object, just as bind() has. (Commit)

live/die now work with context (Commit)

You can now specify a context to the selector that will be used to bind a live event. If you do, only elements under that context will be bound. While the elements themselves do not need to exist when you create the live event, the context must exist.

Make sure ready event has body at least (Commit)

jQuery now checks to see whether the body exists, and falls back to polling for the body if it does not.

Unload is sped up in non-IE browsers that don’t need memory leak hand-holding. (Commit)

Manipulation

A number of DOM manipulation methods have seen dramatic overhauls in performance in jQuery 1.4.

Performance of .append(), .prepend(), .before(), and .after() has been improved.

Performance of .html() has been improved by nearly 3x.

Performance of .remove() and .empty() has seen over a 4x speed increase.

New Method: .detach() (.detach() Documentation, Commit)

detach() removes an element from the DOM but does not remove the associated event handlers. This is appropriate for temporarily removing an element to manipulate and then return.

var foo = $("#foo").click(function() {
    // do something
});
foo.detach();
// foo retains event handlers
foo.appendTo("body");

New unwrap() method (documentation, commit)

The new unwrap method will take the children of a given parent and replace said parent with them. Like so:

<body>
    <div>
        <p>annie</p> <p>davey</p> <p>stevie</p>
    </div>
</body>

$('div').unwrap();

<body>
   <p>annie</p> <p>davey</p> <p>stevie</p>
</body>

Caching in domManip (commit)

jQuery caches the resulting nodes created using methods like jQuery("<div>") and .after("<div>"). This results in significantly faster performance on pages that do DOM manipulation with strings using these methods.

before, after, replaceWith on disconnected nodes (commit)

You can now use before, after, and replaceWith on nodes that are not attached to the DOM. This allows you to do more complex manipulations before inserting the final structure into the DOM. This also prevents reflows from occuring while the manipulation is taking place.

jQuery("<div/>").before("<p>Hello</p>").appendTo("body")

.clone(true) also clones data (documentation, commit)

In jQuery 1.3, .clone(true) did a deep clone, but did not clone data. In jQuery 1.4, it clones data, which means that events are cloned as well. This uses the same semantics as jQuery.extend, so plain objects and Arrays are cloned, while custom objects are not.

Offset

.offset( coords | Function ) (.offset() documentation, commit)

It is now possible to set the offset of an element. Offset, like all setter methods, can now also accept a function as a second argument.

Queueing

Queueing has undergone an overhaul, improving the experience of working with queues other than the default fx.

New .delay() method (.delay() documentation, commit)

The .delay() method will delay any further elements in the queue for the specified number of milliseconds. By default, it will use the fx queue. You can specify an alternate queue as an optional second parameter to the delay function.

$("div").fadeIn().delay(4000).fadeOut();

Queue next (.queue() documentation, commit)

In jQuery 1.4 the function that’s called is passed in another function, as the first argument, that when called automatically dequeues the next item and keeps the queue moving.

jQuery("div").queue("ajax", function(next) {
  var self = this;
  jQuery.getJSON("/update", function(json) {
    $(self).html(json.text);
    next();
  };
}).queue("ajax", function() {
  $(this).fadeIn();
});

.clearQueue() (documentation, commit)

Queues can now be cleared. This will remove any unexecuted functions from the queue, but not stop running functions. Using .clearQueue() without any parameters will clear the fx queue.

Selectors

“#id p” is faster (commit) Any selector string that begins with an ID has an optimization to grab that immediately. ID rooted selectors will always be fastest.

Traversing

.index(), .index(String) (documentation, commit)

The .index() method has been rewritten to be more far more intuitive and flexible.

You can now get the index of an element in relation to its siblings:

// get the index of the first <li> in relation to its siblings:
$("li.current").index()

You can get the index of an element in relation to to the current jQuery collection by passing in a selector or DOM element:

// get the index of the <h3 id="more-info"> in relation to all <h3> elements:
$("#more-info").index("h3")

New .has() method (documentation, commit)

This is a method form of the :has() filter. It takes a given jQuery set and returns all of the same elements that contain a given selector.

New .nextUntil(), .prevUntil(), .parentsUntil() methods (.nextUntil() documentation, .prevUntil() documentation, .parentsUntil() documentation, commit)

The new “until” methods function similarly to .nextAll(), .prevAll(), .parents(), but the first argument they take is a selector that will terminate the traversal.

.add(String, Element) (.add() documentation, commit)
The .add() now accepts a context. This is primarily useful in a chain when you want to add in addtional elements (returned from an ajax request, for example) and then manipulate those in addition to the others.

.closest(filter, DOMElement) (.closest() documentation, commit)

The closest method can now accept a context DOMElement as a second argument. Passing in a context will typically make your closest() calls much faster. This also applies to live() which leverages closest() internally.

Utilities

jQuery.isEmptyObject() (jQuery.isEmptyObject() documentation, commit)

This returns true if there are not any properties on the object. You can only pass in objects to jQuery.isEmptyObject(), because jQuery performs an iteration on the object that is passed in without any other checks.

jQuery.isPlainObject() (jQuery.isPlainObject(), commit )

jQuery.isPlainObject() returns true if the object is an object literal and false if the object is another kind of object or a primitive.

jQuery.contains() (jQuery.contains() documentation, commit)

jQuery.contains() returns true if both parameters are DOM nodes and the second parameter is contained inside the first.

jQuery.noop (jQuery.noop() documentation, commit)

jQuery.noop is empty function that can be used where a function is required.

jQuery.unique() (jQuery.unique() documentation)

In jQuery 1.4, the jQuery.unique() method, which is used internally in the creation of the jQuery set, always returns results in document order. This means that jQuery sets returned from jQuery functions should be returned in document order.

Miscellaneous

jQuery.browser is now engine-centric (jQuery.browser documentation, commit)

For example, you can now test for Webkit with jQuery.browser.webkit.

Better support for applets (commit 1, commit 2)

jQuery no longer attempts to bind events or data to Java applets (which throw exceptions).

No longer use arguments.callee (commit)

For compliance with Caja and because it is slated to be deprecated in the upcoming ECMAScript 5 specification, we have removed all references to arguments.callee in jQuery core.

Now use Closure Compiler instead of YUI Min (commit)

Internal Reorganization

One of the major pushes that we made with 1.4 was towards building a more legible, understandable, code base. To achieve that we did some major restructuring of the of the code base internals and began to establish some style guidelines for the code base.

Some of the major changes that were made:

• The old ‘core.js’ file has been split apart into ‘attribute.js’, ‘css.js’, ‘data.js’, ‘manipulation.js’, ‘traversing.js’, and ‘queue.js’.
• The ready event has been moved into core.js (as it’s a fundamental part of jQuery itself).
• The majority of core matches the new jQuery Core Style Guidelines.
• The logic for css and attributes have been split and aren’t so intertwined anymore.

32비트 버전을 설치하는데 운영체제에 설치 할 수 없다는 경고 메시지가 뜨면서 설치가 되질 않더군요!
오기를 가지고 설치가 될대까지 계속 시도를 했습니다 10번 찍어 안넘어가는 나무 없다고, 찍으니깐 넘어가네요.. ㅎㅎ
유용하게 사용하시길.. ^^

(맥기기는 역시 맥과 궁합이 잘 맞습니다, 자주 팅기는 현상이 발생해서 사용하기 어렵네요.. 비추합니다.)

32bit version

64bit version

출처 : http://uneasysilence.com/archive/2009/11/14588/

폭스바겐에서 나온 무료앱 게임입니다.
레이싱 게임중 강력 추천합니다. 한번 해보시면 그매력에 푹 빠지시게 될겁니다. ^^

유료 버전도 현재 6.99 달러에 판중이며  GTI 자동차 모델 28대와 12 가지의 트랙을 제공합니다.
(무료 버전 : 자동차 1대, 트랙 3개)

- 미쿡 계정으로 받으셔야 합니다.

오후 5시쯤 혹시나 하는 마음으로 다시 SHOW 사이트에 접속을 해보았다.

이제야 사이트가 정상적으로 접속이 됩니다.  많은 사용자가 사전예약을 마친듯 하다
아이폰구매를 위해 사전예약 페이지로 이동하여 사전예약을 하는데,
아뿔사 예전에 가입해두었던 아이디가 있었는데 비밀번호를 찾을 수가 없다. ㅠㅠ
사전예약시 회원에게 제공되는 쇼캐쉬 3만5천원을 포기하고 비회원구매를 선택하고 예약을 완료!!
(폰 개통후 114에 전화를 해 알아내 사실이지만 아이디가 있어도 신규 회원가입이 가능했던거였다. ㅠ.ㅠ 아까운 3만5천원 쇼캐쉬)

예약 후로 폰스토어에 매일 방문해 주문정보를 매일같이 발송이 되었는지 개통이 되었는지 확인하며 하루 하루를 보낸다.
빨리 받아 보고 싶은 마음이 간절했지만 발송은 28일 이후에나 될것을 뻔히 알면서도 말이다.

그렇게 시간을 흘러 28일 토요일.
혼자서 무주스키장을 찾았다.
한참 라이딩을 즐기는데 한통의 문자가 날아왔다.
“아이폰이 발송되었습니다.”
라이딩을 포기 하고 바로 집으로 가서 폰스토어에 접속해 현재 배송추적으로 해보고 싶지만, 0910시즌 첫 보딩이라 그러고 싶은 생각은 잠시 뒤로하고 즐거운 보딩을 즐기며  시간을 보냈다.

30일 되던날 점심때쯤 아이폰을 받아 보았습니다.

To be continued…

CSS Nite in SEOUL에 참가하위해 아침 일찍 부터 서둘러 회사동료들을 태우고
행사가 열리는 서울 포스코센터로 향하였습니다.
고속도록 곳곳에 교통사고 처리로 지체가 되는 바람에 점심도 거른체 10분 늦게 행사장에 도착하였습니다.

행사장 안이 너무 비좁았습니다.  미리 도착한 회사 동료가 자리를 맡아 두어 책상이 있는 좌석에 착석을 하고 세미나에 참여를 시작했습니다.

NHN의 웹표준화팀 박태준¹⁾ 팀장의  ‘웹표준을 기반을한 HTML 개발프로세스’를 통해 HTML 개발일정 산출의 수치화, 웹표준, 웹접근성, 코드최적화, 생산량의 수치화, 품질관리 등 많은 시도를 하고 있음을 알수 있었습니다.
아직 우리나라는 웹표준에 대한 HTML개발프로세스가 자리 잡지 못한 상태에서 NHN기업의 웹표준화팀을 통해 서서히 HTML개발프로세스가 자리 잡아갈 수 있도록 지원할수 있는 기회를 마련해줄것을 기대해 봅니다.

발표 이후 미투데이이를 통해 박태준 팀장과 휴식시간에 명함교환을 하고, 현 웹기업들의 웹표준에 대한 인식이라던가, 앞으로 어떤 대안을 통해 성장할 수 있을지에 대한 이런 저런 고민을 하는 시간을 가져보았습니다.

타가노 마사히로²⁾씨의  ‘일본의 웹표준 현실과 제작 프로세스’ 에서는 일본의 CSS정착배경, 웹표준, 웹접근성(jis), 드림위버를 통한 코딩 방법에 대한 예시를 보여주셨는데요, 처음 CSS Nite는 2005년 10월 시작으로 일본 엔지니어들은 많은 교류를 통해 웹표준, 웹접근성에 보다 가깝게 다가가고 있는듯 합니다, 그에 비해 우리나라는 그 당시  웹표준에 대한 생각이라 던지 웹접근성에 대해 고민하고 생각하는 사람은 몇 안되었을 것입니다. 일본보다 많이 늦은 감은 있지만 이런 자리를 통해 많은 웹종사자들의 인식이 일본인들처럼 바뀌었으면 하는 바람입니다.

마시코 다카히로³⁾ 씨의 ‘미래의 웨표준으로써의 HTML5와 CSS3′는 제가 CSS Nite에 꼭 참석하고 싶었던 이유였습니다.
HTML5와 CSS3에 대해 이미 많은 정보를 찾아 보았었고, 새로운것을 추구하고 연구하는 것에 관심이 많은 저로써는 정말 기대되는 세션이었습니다. 예상했던것 보다 새로운 정보를 얻을 수 있었던 자리는 아닌것이 다소 아쉬움이 남는 시간이었지만, 같이 동행한 회사 동료 그리고 CSS Nite에 참여한 모든 분들과 함께 공유할 수 있는 자리를 만들어준것에 대해 감사하는 마음입니다.
HTML5는 현재 IE 브라우져를 빼고는 모든 웹브라우져에서 지원이 되고 있습니다.
정말 안타까운 현실이 아닐수 없습니다. 현재 우리나라 IE사용자는 상당수를 차지하고 있기 때문에 HTML5를 적용하기에는 오랜 시간이 걸릴것으로 예상되어집니다.  IE9가 나온다고는 하지만 이미 IE(6,7,8)에 셋팅되어진 업무환경으로 인해 업그레이드가 불가한게 불보듯 뻔합니다.  이런 환경을 개선하기 위해 많은 기업, 공공기관, 정부는 투자를 아끼지 않아야 하겠죠~!!

CSS3역시 IE에서는 먼 훗날의 얘기로만 여겨집니다. CSS3에서는 다양한 selector가 추가 되었고 CSS Visual Effects도 추가 되어 자바스크립트를 통해 구현했던 Effect를 CSS만으로도 구현이 가능해집니다.

경품 추첨시간에는 같이간 동료와 함께 추첨이 되어 “검색 마케팅” 이야기라는 책을 경품으로 받는 행운의 기회를 잡았습니다.

이후 교류파티가 이루어 졌지만 대전에서 상경(?)한 터라 동료들과 아쉼을 뒤로 한채 행사장을 나서야 했습니다.

앞으로도 이런 행사가 많았으면 합니다.

현재 http://show.co.kr 웹사이트에 예약 접수를 받을 수 있는 웹페이지를 생성하고
예약접수를 기다리고 있는 상태 입니다.

폰스토어(http://phonestore.show.co.kr)에 예약가입한 선착순 1만명에게는
iPhone 전용 액세서리 또는 쇼캐쉬 20,000월을 제공, 예약 가입자중 1,000명 추첨하여
SHOW iPhone 런칭Festival에서 현장 개통하는 기회도 주어진다고 합니다.