AJAX Design Pattern: Read/Write Div
A new AJAX convention cropping up in a few places, one that is easy to implement and has real benefit to end users. I haven’t found a description of it anywhere, so I thought I’d write it up here. The basic idea is that user controls (typically for editing the displayed data) should be hidden from the user until needed. At “rest”, an area of the screen displays information in read-only fashion. On
Ajax Design Center - Zimbra : Blog
As it is realized within Zimbra and most other Ajax applications today, development is accomplished via GUI, object-oriented programming in Javascript. (Please see Ajax Programming Report Card and Ajax Sweet Spots.) This is the sort of work that developers with Java SWT, Java Swing, or C# skills will accel in at, but also the sort of work that will leave some Web designers (e.g., Dreamweaver or Fr
Purchase Intent Data for Enterprise Tech Sales and Marketing | TechTarget
Enterprise Strategy Group: Go-to-market Expertise to Help You Win
AJAX Considered Harmful
Please pardon the provocative title, but this post is intended to surface one point I buried in yesterday’s presentation in the hopes that by making it a separate post it will attract a wider audience. I intend for this to post to be constructive, so I will focus on two specific suggestions which hopefully will serve as the seed for the development of a set of best practices for AJAX. Here are th
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
ma.laさんによるライブドアテクノロジーセミナーのプレゼン資料「Technologies for UI」
