불친절한자수씨

URL format

Google Chart API URLs must be in the following format:

http://chart.apis.google.com/chart?<parameter 1>&<parameter 2>&<parameter n>

Note: Each URL must be all on one line.

Parameters are separated with the ampersand (&) character. You can specify as many parameters as you like, in any order. For example, the Chart API returns the following chart in response to the URL below:

http://chart.apis.google.com/chart?
chs=250x100
&chd=t:60,40
&cht=p3
&chl=Hello|World

Where:

• http://chart.apis.google.com/chart? is the Chart API's location.
• & separates parameters.
• chs=250x100 is the chart's size in pixels.
• chd=t:60,40 is the chart's data.
• cht=p3 is the chart's type.
• chl=Hello|World is the chart's label.

You can include a Chart API image in an HTML document by embedding a URL within an <img> tag. For example, the following <img> tag results in the same image as above:

<img src="http://chart.apis.google.com/chart?
chs=250x100
&amp;chd=t:60,40
&amp;cht=p3
&amp;chl=Hello|World"
alt="Sample chart" />


기본 URL: http://chart.apis.google.com/chart
  chs: 차트 사이즈. [width]x[height] ex) chs=200x100
  chd: 차트 데이터
  cht: 차트 타입
  chl: 차트 레이블

PNG 타입의 이미지기 때문에 크기는 6 KB 정도밖에 안되네요

출처: Google Chart API

Introduction

The Google Chart API returns a PNG-format image in response to a URL. Several types of image can be generated: line, bar, and pie charts for example. For each image type you can specify attributes such as size, colors, and labels.

You can include a Chart API image in a webpage by embedding a URL within an <img> tag. When the webpage is displayed in a browser the Chart API renders the image within the page.

All the images in this document were generated with the Chart API. To view the URL of an image :

• if you are using Firefox right-click then select View image or Properties.
• if you are using Internet Explorer right-click then select Properties.

This document describes the required format of Chart API URLs and the available parameters.

- 파라미터에 따라 PNG 형식의 이미지 차트를 생성해주는 구글 차트 API

출처: Google Chart API

Google App Engine

We've just released a preview of Google App Engine, an application-hosting tool that developers can use to build scalable web apps on top of Google's computing infrastructure. The goal is to make it easier for web developers to build and scale applications, instead of focusing on system administration and maintenance. In this preview release, accounts are limited to the first 10,000 signups.

이렇다고 하는데... 흠흠

자세한 건 나중에 슬슬 알아보도록 합시다~ ㅋㅋㅋ

Release Notes for GWT-Ext 2.0.3

Features

• Charts
  Supports for Charting via YUI charts. Line, Bar, Pie, Column charts are all available as a standard GWT-Ext Panel subclass. Charts use the standard Store as thier underlying data source. See demo here.

• Mapping API
  Supports for Mapping API via Mapstraction. The supported Map providers include OpenStreetMap, Yahoo, Google, Microsoft, Map24, MultiMap, MapQuest, FreeEarth and OpenLayers.
  Various Maps are now available as a standard GWT-Ext Panel subclass. The motivation for the GWT-Ext Mapping API is not to compete with the other GWT Google Maps API's which are far more feature rich and complete. This API is over mapstraction which provides several commonly used features such as markers, polylines, GeoRSS and such using the same API.
  The desired map provider can be instantiated by a factory, and the rest of the code remains the same and works across various map providers (some free, and others commercial). This gives users more flexibilty to pick a map provider that meets their needs and license requirements.. See demo here.

• Portal
  Initial Portal support. See demo here here

Changes

• Various Bug Fixes
• Ext.isFirebug() to detect if Firebug is enabled
• GridPanel.clearSortState()
• Support for preserving ordering in PropertyGridPanel
• com.gwtext.client.widgets.menu.Adapter class to allow and Component (like TextField) to be added to a Menu
• API's to access various Button's on PagingToolbar

- Yahoo! UI Library 의 chart 가 추가되었네요~ 다른 버전의 swf 는 지원 안해주나...
- Mapping API 도 추가되어 매쉬업에 편의성이 가미되었네요~
- Portal 도 손쉽게 만들 수 있게 데모까지 제공해주네요~

- 여러가지 버그를 수정하였고
- Ext.isFirebug() 를 통하여 firefox 의 firebug 가 활성화 되어 있는지를 확인할 수 있습니다.
- GridPanel 에 clearSortState() 메소드가 변경되었나... 추가되었나...
- 그 외, PagingToolbar 버튼에 API 로 접근할 수 있게 되었다네요... (ㅠ_ㅠ.. 이거 안되서 다시 만들었는데...)

여튼 잘 발전하고 있는 gwt-ext 를 보면서 뿌듯함을 느낍니다.~

출처 : GWT-Ext Release Notes

6 개월간 javascript 만으로 그룹웨어를 만들어 보고

1년 8개월 여간 GWT 만으로 그룹웨어를 만들어보았다.

gwt-ext 를 접하는 순간 그간 UI 의 퀄리티가 떨어져

천대 받는 설움을 떨치는 것 같은 느낌이랄까...

자바스크립트를 무시하는 분들~ 각성하세요~~

gwt-ext 로 프로그래밍을 하니 점점 자신감이 생기는 것 같았다.

하나하나 알아가는 재미일까...


그나저나 힘든건 매한가지로세....




UMPC 나 하늘에서 뚝 떨어졌으면 좋겠당...

gwt-ext 에서의 Window 는 X 버튼을 누를경우 내부 엘리먼트들을

자동으로 삭제처리를 합니다.. (리스너나 그런것들...)

X 버튼을 누른 후 다시 띄우게 되면 정상적으로 되지 않아 당황스러울 수 도 있는데요...

해결방법은 다음과 같습니다.

GWT 에서 다국어처리는Constants나 Messages 인터페이스를

상속받은 인터페이스를 이용합니다.

간단한 예제로 설명을 해드리겠습니다.

이상입니다 >_<