From ef256c958066c19bb10cbe9745bdf96b6514762d Mon Sep 17 00:00:00 2001 From: Derrell Lipman Date: Tue, 6 Feb 2007 03:23:52 +0000 Subject: r21167: - Upgrade to latest released qooxdoo. This is step 1 of the upgrade process, which involves adding the latest SDK. This new version has not 2, but 4 icon themes. In order to quiet Andrew B. who thinks that 9000+ files in a gui api is too many (come on, disk space is free these days :-), I have removed 3 of the 4 icon themes, leaving only the default, Nuvola. That lowers the file count by 1/3. I'm sure Andrew still isn't happy, but I hope he's a bit happier... Step 2 will make him happier yet. (This used to be commit d161c1382c36238105b85d0499d5a1011f580f52) --- .../source/class/feedreader/Application.js | 410 +++++++++++ .../source/class/feedreader/ArticleView.js | 85 +++ .../application/feedreader/source/index.html | 15 + .../feedreader/source/resource/css/reader.css | 54 ++ .../feedreader/source/resource/feeds/ajaxian.xml | 789 +++++++++++++++++++++ .../source/resource/feeds/febo-feeds.opml.xml | 29 + .../source/resource/feeds/qooxdoo-blog.xml | 278 ++++++++ .../source/resource/feeds/qooxdoo-news.xml | 284 ++++++++ .../feedreader/source/resource/feeds/safari.xml | 223 ++++++ .../source/resource/feeds/zimbra-atom.xml | 699 ++++++++++++++++++ .../feedreader/source/resource/images/locale.png | Bin 0 -> 811 bytes .../feedreader/source/resource/proxy/proxy.php | 60 ++ .../application/feedreader/source/translation/C.po | 93 +++ .../feedreader/source/translation/de.po | 95 +++ .../feedreader/source/translation/en.po | 93 +++ .../feedreader/source/translation/es.po | 94 +++ .../feedreader/source/translation/it.po | 94 +++ .../feedreader/source/translation/ru.po | 94 +++ .../feedreader/source/translation/sv.po | 93 +++ .../feedreader/source/translation/tr.po | 95 +++ 20 files changed, 3677 insertions(+) create mode 100755 webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/class/feedreader/Application.js create mode 100644 webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/class/feedreader/ArticleView.js create mode 100755 webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/index.html create mode 100644 webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/css/reader.css create mode 100644 webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/feeds/ajaxian.xml create mode 100644 webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/feeds/febo-feeds.opml.xml create mode 100644 webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/feeds/qooxdoo-blog.xml create mode 100644 webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/feeds/qooxdoo-news.xml create mode 100644 webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/feeds/safari.xml create mode 100644 webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/feeds/zimbra-atom.xml create mode 100644 webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/images/locale.png create mode 100644 webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/proxy/proxy.php create mode 100644 webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/translation/C.po create mode 100644 webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/translation/de.po create mode 100644 webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/translation/en.po create mode 100644 webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/translation/es.po create mode 100644 webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/translation/it.po create mode 100644 webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/translation/ru.po create mode 100644 webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/translation/sv.po create mode 100644 webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/translation/tr.po (limited to 'webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source') diff --git a/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/class/feedreader/Application.js b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/class/feedreader/Application.js new file mode 100755 index 0000000000..aa76800f31 --- /dev/null +++ b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/class/feedreader/Application.js @@ -0,0 +1,410 @@ +/* ************************************************************************ + + qooxdoo - the new era of web development + + http://qooxdoo.org + + Copyright: + 2004-2007 1&1 Internet AG, Germany, http://www.1and1.org + + License: + LGPL: http://www.gnu.org/licenses/lgpl.html + EPL: http://www.eclipse.org/org/documents/epl-v10.php + See the LICENSE file in the project's top-level directory for details. + + Authors: + * Fabian Jakobs (fjakobs) + +************************************************************************ */ + +/* ************************************************************************ + +#resource(feeds:feeds) +#resource(css:css) +#resource(proxy:proxy) +#resource(images:images) +#embed(feedreader.proxy/*) +#embed(feedreader.feeds/*) +#embed(feedreader.css/*) +#embed(feedreader.images/*) +#embed(qx.icontheme/16/actions/dialog-ok.png) +#embed(qx.icontheme/16/actions/dialog-cancel.png) +#embed(qx.icontheme/16/actions/help-about.png) +#embed(qx.icontheme/16/actions/view-refresh.png) + +************************************************************************ */ + +/** + * qooxdoo news reader Application class. + */ +qx.OO.defineClass("feedreader.Application", qx.component.AbstractApplication, +function () { + qx.component.AbstractApplication.call(this); + + qx.manager.object.ImageManager.getInstance().setIconTheme(qx.theme.icon.VistaInspirate.getInstance()); + //this.fetchFeedDesc(); + this.setFeeds([]); +}); + +qx.OO.addProperty({name: "feeds"}); +qx.OO.addProperty({name: "selectedFeed"}); + +qx.Settings.setDefault("resourceUri", "./resource"); + + + +/* +--------------------------------------------------------------------------- + METHODS +--------------------------------------------------------------------------- +*/ + +if (qx.core.Client.getInstance().getRunsLocally()) +{ + qx.Class._feedDesc = [ + { + url: "feedreader/feeds/qooxdoo-news.xml", + name: "qooxdoo-blog" + }, + { + url: "feedreader/feeds/qooxdoo-blog.xml", + name: "qooxdoo-news" + }, + { + url: "feedreader/feeds/ajaxian.xml", + name: "ajaxian" + }, + { + url: "feedreader/feeds/safari.xml", + name: "Surfin' Safari" + } + ]; +} +else +{ + qx.Class._feedDesc = [ + { + url: "feedreader/proxy/proxy.php?proxy=" + encodeURIComponent("http://feeds.feedburner.com/qooxdoo/blog/content"), + name: "qooxdoo-blog" + }, + { + url: "feedreader/proxy/proxy.php?proxy=" + encodeURIComponent("http://feeds.feedburner.com/qooxdoo/news/content"), + name: "qooxdoo-news" + }, + { + url: "feedreader/proxy/proxy.php?proxy=" + encodeURIComponent("http://feeds.feedburner.com/ajaxian"), + name: "ajaxian" + }, + { + url: "feedreader/proxy/proxy.php?proxy=" + encodeURIComponent("http://webkit.org/blog/?feed=rss2"), + name: "Surfin' Safari" + } + ]; +} + +qx.Proto.initialize = function(e) +{ + // Define alias for custom resource path + qx.manager.object.AliasManager.getInstance().add("feedreader", qx.Settings.getValueOfClass("feedreader.Application", "resourceUri")); + + // Include CSS file + qx.html.StyleSheet.includeFile(qx.manager.object.AliasManager.getInstance().resolvePath("feedreader/css/reader.css")); +}; + +qx.Proto.main = function(e) +{ + // create main layout + var dockLayout = new qx.ui.layout.DockLayout(); + dockLayout.set({ + height: "100%", + width: "100%" + }); + + // create header + var header = new qx.ui.embed.HtmlEmbed("

qooxdoo reader

"); + header.setCssClassName("header"); + header.setHeight(50); + dockLayout.addTop(header); + + // define commands + var reload_cmd = new qx.client.Command("Control+R"); + reload_cmd.addEventListener("execute", function(e) { + this.fetchFeeds(); + this.debug(this.tr("reloading ...").toString()); + }, this); + + var about_cmd = new qx.client.Command("F1"); + about_cmd.addEventListener("execute", function(e) { + alert(this.tr("qooxdoo feed reader.")); + }, this); + + // create toolbar + var toolBar = new qx.ui.toolbar.ToolBar(); + toolBar.add(new qx.ui.toolbar.Button(this.trn("Add feed", "Add feeds", 2), "icon/16/actions/dialog-ok.png")); + toolBar.add(new qx.ui.toolbar.Button(this.tr("Remove feed"), "icon/16/actions/dialog-cancel.png")); + toolBar.add(new qx.ui.toolbar.Separator()); + + var reload_btn = new qx.ui.toolbar.Button(this.tr("Reload"), "icon/16/actions/view-refresh.png"); + reload_btn.setCommand(reload_cmd); + reload_btn.setToolTip(new qx.ui.popup.ToolTip(this.tr("(%1) Reload the feeds.", reload_cmd.toString()))); + toolBar.add(reload_btn); + + toolBar.add(new qx.ui.basic.HorizontalSpacer()); + + // poulate languages menu and add it to the toolbar + var locales = { + en: this.tr("English"), + de: this.tr("German"), + en: this.tr("English"), + tr: this.tr("Turkish"), + it: this.tr("Italian"), + es: this.tr("Spanish"), + sv: this.tr("Swedish"), + ru: this.tr("Russian") + } + var availableLocales = qx.locale.Manager.getInstance().getAvailableLocales(); + var locale = qx.locale.Manager.getInstance().getLocale(); + var lang_menu = new qx.ui.menu.Menu(); + var radioManager = new qx.manager.selection.RadioManager("lang"); + for (var lang in locales) { + if (availableLocales.indexOf(lang) == -1) { + continue; + } + var menuButton = new qx.ui.menu.RadioButton(locales[lang], null, locale == lang); + menuButton.setUserData("locale", lang); + lang_menu.add(menuButton); + radioManager.add(menuButton); + } + radioManager.addEventListener("changeSelected", function(e) { + var lang = e.getData().getUserData("locale"); + this.debug("lang:" + lang); + qx.locale.Manager.getInstance().setLocale(lang); + }); + lang_menu.addToDocument(); + toolBar.add(new qx.ui.toolbar.MenuButton("", lang_menu, "feedreader/images/locale.png")); + + var about_btn = new qx.ui.toolbar.Button(this.tr("Help"), "icon/16/actions/help-about.png"); + about_btn.setCommand(about_cmd); + about_btn.setToolTip(new qx.ui.popup.ToolTip("(" + about_cmd.toString() + ")")); + toolBar.add(about_btn); + + dockLayout.addTop(toolBar); + + // add tree + var tree = new qx.ui.tree.Tree(this.tr("News feeds")); + tree.set({height:"100%", width:"100%"}); + tree.setOverflow("auto"); + tree.setBorder(qx.renderer.border.BorderPresets.getInstance().inset); + tree.setBackgroundColor("#EEEEEE"); + + var feedDesc = feedreader.Application._feedDesc; + for (var i=0; i 0) { + item.author = qx.dom.Element.getTextContent(eItem.getElementsByTagName("author")[0].getElementsByTagName("name")[0]); + } else { + item.author = "" + } + item.date = qx.dom.Element.getTextContent( + eItem.getElementsByTagName("created")[0] || + eItem.getElementsByTagName("published")[0] || + eItem.getElementsByTagName("updated")[0] || + empty + ); + item.content = qx.dom.Element.getTextContent(eItem.getElementsByTagName("content")[0] || empty); + item.link = eItem.getElementsByTagName("link")[0].getAttribute("href"); + items.push(item); + } + return items; +} + + +qx.Proto.parseRSSFeed = function(xml) { + var eItems = xml.getElementsByTagName("item"); + var empty = xml.createElement("empty"); + var items = []; + for (var i=0; i"); + + html.add("

"); + html.add(item.title); + html.add("

"); + + html.add("
"); + html.add(item.date); + html.add("
"); + + html.add("
"); + html.add(item.content); + html.add("
"); + + html.add(""); + html.add(this.tr("read more ...")); + html.add(""); + + html.add(""); + + return html; +} \ No newline at end of file diff --git a/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/index.html b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/index.html new file mode 100755 index 0000000000..4f5bf3d13a --- /dev/null +++ b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/index.html @@ -0,0 +1,15 @@ + + + + qooxdoo » Demo » Feed Reader + + + + + + diff --git a/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/css/reader.css b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/css/reader.css new file mode 100644 index 0000000000..e59f36b63e --- /dev/null +++ b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/css/reader.css @@ -0,0 +1,54 @@ +.header { + margin: 0px; + padding: 0px; + background-color: #134275; +} + +.header h1 { + font-family: "Trebuchet MS", "Lucida Grande", Verdana, sans-serif; + font-size: 18px; + font-weight: bold; + color: #DEFF83; + padding: 12px 20px; + margin: 0px; +} + +.blogEntry { + font-family: Verdana, "Lucida Grande", "Bitstream Vera Sans", Tahoma, "Lucida Sans Unicode", Arial, sans-serif; + font-size: 11px; + line-height: 150%; + padding: 5px; + background: #FBFFEF; +} + +.blogEntry h1.blog { + font-family: "Trebuchet MS", "Lucida Grande", Verdana, sans-serif; + color: #134275; + line-height: 120%; +} + +.blogEntry { + overflow: auto; +} + +.blogEntry div.date { + font-weight: bold; + color: #1D65B3; + padding: 5px; +} + +.blogEntry a:link, +.blogEntry a:visited{ + color: #134275; +} + +.blogEntry a:hover, +.blogEntry a:active{ + color: #134275; + text-decoration: underline; +} + +.blogEntry .description { + margin-top: 10px; + margin-bottom: 10px; +} \ No newline at end of file diff --git a/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/feeds/ajaxian.xml b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/feeds/ajaxian.xml new file mode 100644 index 0000000000..68a2581df6 --- /dev/null +++ b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/feeds/ajaxian.xml @@ -0,0 +1,789 @@ + + + + + Ajaxian + http://ajaxian.com + Cleaning up the web with Ajax + Tue, 28 Nov 2006 14:55:53 +0000 + http://wordpress.org/?v=1.5.2 + en + + This is an XML content feed. It is intended to be viewed in a newsreader or syndicated to another site, subject to copyright and fair use. + Tasks added to Google Calendar by Milkers + http://ajaxian.com/archives/tasks-added-to-google-calendar-by-milkers + http://ajaxian.com/archives/tasks-added-to-google-calendar-by-milkers#comments + Tue, 28 Nov 2006 14:55:53 +0000 + Dion Almaer + + Front Page + Showcase + Calendar + http://ajaxian.com/archives/tasks-added-to-google-calendar-by-milkers + + The Remember the Milk folks have added task management to Google Calendar (something many wish Google had added themselves).

+

We know that many of you are managing your tasks with Remember The Milk and your events with Google Calendar, and we thought it would be very cool if we could bring the two together. This new feature adds a small task icon to the top of each day in Google Calendar — click on the icon to:

+
    +
  • Review your tasks for the day
    • +
  • Add new tasks and edit existing ones
    • +
  • Easily complete and postpone tasks
    • +
  • Review your overdue tasks
    • +
  • Optionally show tasks with no due date
    • +
  • See where your tasks are located on a map (Google Maps integration)
    • +
+

This is really interesting. An outside group was able to add an important feature that we can not all use in a Google app itself.

+

+

+ +
]]> + http://ajaxian.com/archives/tasks-added-to-google-calendar-by-milkers/feed/ + + + YUI Resizable Component + http://ajaxian.com/archives/yui-resizable-component + http://ajaxian.com/archives/yui-resizable-component#comments + Tue, 28 Nov 2006 13:38:06 +0000 + Dion Almaer + + Front Page + Examples + Yahoo! + http://ajaxian.com/archives/yui-resizable-component + + Jack Slocum keeps 'em coming with his detailed post on a reusable component for resizing elements.

+

Jack's YAHOO.ext.Resizable component does what it says on the tin, and he shows you:

+
    +
  • Basic Resizable div
    • +
  • Wrapped elements (e.g. text area inside)
    • +
  • Preserve Ration (e.g. image resizing)
    • +
  • Transparent Handles
    • +
  • Customizable Handles
    • +
  • Snapping to increments
    • +
  • Animated Transitions
    • +
+
+
+
+var animated = new YAHOO.ext.Resizable('animated', {
+    width: 200,
+    height: 100,
+    minWidth:100,
+    minHeight:50,
+    animate:true,
+    easing: YAHOO.util.Easing.backIn,
+    duration:.6
+});
+ 
+
+
+

YUI Resizable +

+ +
]]> + http://ajaxian.com/archives/yui-resizable-component/feed/ + + + Mootools Primer + http://ajaxian.com/archives/mootools-primer + http://ajaxian.com/archives/mootools-primer#comments + Mon, 27 Nov 2006 15:58:12 +0000 + Dion Almaer + + Front Page + Examples + http://ajaxian.com/archives/mootools-primer + + Aaron Newton has posted a Mootools Primer / Tutorial that includes "a how-to tutorial on the Mootools library. Most of the code examples will allow you execute them by clicking on the "execute this code" link above the example. Clicking this will echo out the code and the result in the Firebug debugging plugin for Firefox. You'll need that plugin installed to see any results of most of the code examples."

+

Currently the tabbed widget shows documentation for the core Moo.js, extensions of JavaScript objects and helpers, Addon libraries, and plugins.

+

It behaves a little weird for me with FF2 + Firebug 1.beta, but I can get to the meat of the matter.

+

Mootools Primer +

+ +
]]> + http://ajaxian.com/archives/mootools-primer/feed/ + + + Google Docs and Spreadsheets Team: Web native matters + http://ajaxian.com/archives/google-docs-and-spreadsheets-team-web-native-matters + http://ajaxian.com/archives/google-docs-and-spreadsheets-team-web-native-matters#comments + Mon, 27 Nov 2006 15:25:50 +0000 + Dion Almaer + + Front Page + Editorial + http://ajaxian.com/archives/google-docs-and-spreadsheets-team-web-native-matters + + Richard MacManus linked to a Gizbuzz interview of Jen Mazzon and Sam Schillace of the Google Docs and Spreadsheets team (both ex-Writely).

+

Nothing ground-breaking, but it is interesting to hear about their thoughts on Ajax:

+
+

Browser compatibility issues - like the early graphic Web

+

Next was a question about browser compatibility issues and how that affects D&S - and indeed the future of rich web applications. Sam responded that "it is definitely an issue [...] these apps are all cutting edge - it kind of reminds me of the early days of the graphical web, when you couldn't count on the browsers to render tables correctly [...]".

+

But he thinks it's "just growing pains" and it'll take about a year to sort those issues out.

+

Also on the question of whether Ajax is better than Flash and Laszlo etc, Sam thinks that Ajax is currently more web native.

+

It's about being Web native, not cloning desktop apps

+

Later in the interview, Jen stresses that they're "not trying to clone desktop apps". They want to be familiar to people, "but we're trying to do something that's actually more native to the Internet, more usable on the Internet."

+

Sam says they've had a lot of feedback that people like the fact they're not trying to copy desktop apps. He said "copying the existing stuff just feels irrelevant to us - we're not trying to copy, we're trying to re-invent."

+

Both Jen and Sam re-affirmed that collaboration and sharing is their main focus with D&S, as well as being web native - rather than trying to compete on features with desktop apps. +

+

If you were asked "why is Ajax a better fit for some apps than Flash?" what would you say? Do you agree? Does the open web matter? What if Adobe fully opened up their format? +

+ +
]]> + http://ajaxian.com/archives/google-docs-and-spreadsheets-team-web-native-matters/feed/ + + + Review of ‘Pro Ajax and Java Frameworks’ + http://ajaxian.com/archives/review-of-pro-ajax-and-java-frameworks + http://ajaxian.com/archives/review-of-pro-ajax-and-java-frameworks#comments + Mon, 27 Nov 2006 14:14:42 +0000 + Dietrich Kappe + + Front Page + Book Reviews + http://ajaxian.com/archives/review-of-pro-ajax-and-java-frameworks + + bcm.gif

+

This is a review of Pro Ajax and Java Frameworks by Nathaniel T. Schutta and Ryan Asleson. This book seeks to give the experienced developer of Java web applications the knowledge necessary to add Ajax to their webapps. This is another Ajax book that goes broad rather than deep. Instead of investigating one or two frameworks, it delves into more than a half dozen, both Javascript and Java.

+

Quick summary: Chapters 2, 3 and 5 are the strongest in the book with useful information on tools, Javascript libraries and enhancing Struts applications with Ajax. The other chapters are not as strong and spend too much time covering old ground.

+

The book is divided into two parts. Part 1 is an introduction to a variety of Javascript and Java Ajax libraries and frameworks. Part 2 shows how to integrate those libraries and frameworks into existing Java web frameworks such as Struts and JSF. One place that this book differs from other Ajax books is that it doesn't have a chapter introducing the reader to the browser technologies that comprise Ajax. It doesn't dwell on the basics of Javascript, DOM and CSS. It expects you to have already read the Apress books on those topics. Instead, chapter 1 covers what I would call best practices and patterns -- autocomplete, partial page update, draggable DOM.

+

Read more of the review here.

+ +
]]> + http://ajaxian.com/archives/review-of-pro-ajax-and-java-frameworks/feed/ + + + Minus(MO)R a.k.a. Let me write JavaScript but help me! + http://ajaxian.com/archives/minusmor-aka-let-me-write-javascript-but-help-me + http://ajaxian.com/archives/minusmor-aka-let-me-write-javascript-but-help-me#comments + Mon, 27 Nov 2006 14:03:41 +0000 + Dion Almaer + + Front Page + JavaScript + Library + Rails + http://ajaxian.com/archives/minusmor-aka-let-me-write-javascript-but-help-me + + Dan Webb has created two Rails plugins to make RJS even better. He has realised that although for some cases RJS is a great thing, you often do want to just use JavaScript, and it looks really ugly to do this:

+
+
+
+page <<'if (someClientSideVariable) {'
+page['a'].replace_html :partial => 'thing'
+page <<'} else {'
+page['b'].replace_html :partial => 'thong'
+page <<'}' +
+
+
+

He first came out with MinusR which takes of your rjs files and lets you code in JS, but still call out to the ruby style. For example:

+
+
+
+if (someClientSideVariable) {
+  $('a').update(<%=js render(:partial => 'thing') %>);
+} else {
+  $('b').update(<%=js render(:partial => 'thong') %>);
+}
+ 
+
+
+

+MinusR gives you the js helper that calls to_json on any value passed to it so you can drop nicely escaped and formatted data into your script as before. Everyone’s a winner. Well, not quite, I could be going out on a limb here but I really think this is the better way. Go on, give it a go. A bit of javaScript won’t hurt you…. +

+

Then a bunch of people wanted this to be doable, but in a separate file, so Dan created MinusMOR, which let's you do the same thing in .ejs files.

+

It is great to be able to choice your poison, even on a case by case basis, and decide whether JS or Ruby is the ruler. +

+ +
]]> + http://ajaxian.com/archives/minusmor-aka-let-me-write-javascript-but-help-me/feed/ + + + Zamzar: Online file conversion + http://ajaxian.com/archives/zamzar-online-file-conversion + http://ajaxian.com/archives/zamzar-online-file-conversion#comments + Mon, 27 Nov 2006 13:23:12 +0000 + Dion Almaer + + Front Page + Showcase + http://ajaxian.com/archives/zamzar-online-file-conversion + + Zamzar is a simple, single page ajax application that lets you upload a file and convert it to something else. E.g.

+
    +
  • Make your PDF documents editable by converting them to MS Word
    • +
  • Convert your ITunes (aac) files to mp3
    • +
  • Upload up to 5 files at a time to convert simultaneously
    • +
  • Take advantage of over 150 different conversion types
    • +
+

ZamZar +

+ +
]]> + http://ajaxian.com/archives/zamzar-online-file-conversion/feed/ + + + CSS Evolution + http://ajaxian.com/archives/css-evolution + http://ajaxian.com/archives/css-evolution#comments + Sat, 25 Nov 2006 17:12:26 +0000 + Dion Almaer + + Front Page + Fun + CSS + http://ajaxian.com/archives/css-evolution + +

+

Evolution of the web in real-time. I hope you are having a good weekend (a Thanksgiving one for the US folk). +

+ +
]]> + http://ajaxian.com/archives/css-evolution/feed/ + + + Poly9’s Polyvalent Javascript URL Parser + http://ajaxian.com/archives/poly9s-polyvalent-javascript-url-parser + http://ajaxian.com/archives/poly9s-polyvalent-javascript-url-parser#comments + Sat, 25 Nov 2006 15:00:34 +0000 + Dion Almaer + + Front Page + JavaScript + Library + http://ajaxian.com/archives/poly9s-polyvalent-javascript-url-parser + + Denis Laprise and the Poly9 Group needed a robust URL parser in JavaScript, so they created the Polyvalent Javascript URL Parser.

+
+
+
+var p = new Poly9.URLParser('http://user:password@poly9.com/pathname?arguments=1#fragment');
+p.getHost() == 'poly9.com';
+p.getProtocol() == 'http';
+p.getPathname() == '/pathname';
+p.getQuerystring() == 'arguments=1';
+p.getFragment() == 'fragment';
+p.getUsername() == 'user';
+p.getPassword() == 'password';

+

p.setURL('another.url.com');
+p.getHost() == 'another.url.com';
+p.getProtocol() == '';

+

p.setURL('dsdsad'); // throws an exception
+ 

+
+
+

This smells like a Java group writing JavaScript to me with the camelCase and thus p.getUsername() instead of p.username.

+

You can check out the implementation and the test suite (zip). +

+ +
]]> + http://ajaxian.com/archives/poly9s-polyvalent-javascript-url-parser/feed/ + + + DOMContentLoaded.Next + http://ajaxian.com/archives/domcontentloadednext + http://ajaxian.com/archives/domcontentloadednext#comments + Sat, 25 Nov 2006 14:29:00 +0000 + Dion Almaer + + Front Page + JavaScript + Tip + http://ajaxian.com/archives/domcontentloadednext + + Andrea Giammarchi has taken the work of Dean Edwards, Mark Wubben, and Paul Sowden to create his DOMContentLoaded Final Solution.

+

The work comes with a test page for http and https, and is documented in this function:

+
+
+
+function onContent(callback){ // (C) webreflection.blogspot.com
+    // [please note that this code doesn't work]

+

 // private scope variable

+

 var IEStringToWrite =  // this is IE dedicated string

+

  "<script defer src='//:' onreadystatechange='
+  (function(element){
+   
+   // if readystate is complete
+   if(element.readyState === "complete")

+

    // call the global variable
+    window.__onContent__();
+  })(this);
+  '></script>";

+

 // the above string is necessary to use onreadystatechange property
+ // with an undefined page. In this way IE tell us the readyState
+ // of the current document

+

 // to call callback function IE need a global scope variable
+ // this variable could call one or more callback
+ // then if it's already created we need to call the old callback
+ // then this new callback
+ window.__onContent__ = (function(oldCallback){
+ 
+  // returns a function that will delete __onContent__
+  // to remove multiple callbacks with different
+  // events and different ways for each browser

+

  return function(){

+

   // clear __onContent__ as generic function
+   window.__onContent__ = function(){};
+   
+   
+   // checks if oldCallback isn't null or undefined
+   if(oldCallback)
+    oldCallback(); // call them to preserve the right order

+

   callback();  // call this scope callback function
+      // (sent calling onContent)
+  }
+ 
+ })(window.__onContent__); // undefined if is the first time we use __onContent__

+

 // __onContent__ is my function to use as callback

+

 // I need to add this function as event

+

 // Opera 9 and FireFox both support DOMContentLoaded as well as
+ // addEventListener document method
+ if(document.addEventListener)
+  document.addEventListener("DOMContentLoaded", __onContent__, false);

+

 // if some browser supports addEventListener but doesn't support DOMContentLoaded
+ // event I don't need to care about that because this event will never be fired

+

 // at the same time if Safari or KDE one day will support DOMContentLoaded
+ // I prefere use this dedicated in-core
+ // event instead of next trick that's quite horrible but works with Safari,
+ // KDE as Opera 8.5 and lower too

+

 // that's why I don't use an else if but an if ... because the first time
+ // event will be fired __onContent__
+ // became an empty function ... then calling them twice is not a problem

+

 if(
+  // Safari and KDE
+  /WebKit|Khtml/i.test(navigator.userAgent) ||

+

  // Opera less than 9
+  (window.opera && parseInt(window.opera.version())&lt;9)
+ )
+  // runtime anonymous function
+  (function(){

+

   // checks if document.readyState is loaded or complete
+   /loaded|complete/.test(document.readyState) ?

+

    // then call __onContent__ , stopping internal loop
+    window.__onContent__() :

+

    // or loops itself with the faster timeout
+    setTimeout(arguments.callee, 1);
+  })();

+

 // at this point I've setted the DOMContentLoaded event for every browser
+ // but not for Inernet Explorer.
+ else if (/MSIE/i.test(navigator.userAgent))

+

  // I can write dedicated string
+  document.write(IEStringToWrite);
+};
+ 

+
+
+ +
]]> + http://ajaxian.com/archives/domcontentloadednext/feed/ + + + Using the Eclipse AJAX Toolkit Framework (ATF) Webinar + http://ajaxian.com/archives/using-the-eclipse-ajax-toolkit-framework-atf-webinar + http://ajaxian.com/archives/using-the-eclipse-ajax-toolkit-framework-atf-webinar#comments + Sat, 25 Nov 2006 04:04:00 +0000 + Dion Almaer + + Front Page + Presentation + http://ajaxian.com/archives/using-the-eclipse-ajax-toolkit-framework-atf-webinar + + We don't normally post webinars, but thought "what the hell it's Friday".

+

On November 30, the Eclipse foundation will be hosting a 1 hour webinar titled Using the Eclipse Ajax Toolkit Framework (ATF).

+

Eclipse ATF provides exemplary tools for creating and debugging Ajax applications. These tools include enhanced JavaScript editing features such as edit-time syntax checking, an embedded DOM browser, CSS Tools, JavaScript debugger, a JavaScript console, and an embedded Mozilla web browser. This webinar will demonstrate how to use ATF to create, debug, and deploy an Ajax application on both Apache and J2EE servers.

+

Register by emailing webinar-atf@eclipse.org

+ +
]]> + http://ajaxian.com/archives/using-the-eclipse-ajax-toolkit-framework-atf-webinar/feed/ + + + Another trick to allow Array subclasses + http://ajaxian.com/archives/another-trick-to-allow-array-subclasses + http://ajaxian.com/archives/another-trick-to-allow-array-subclasses#comments + Fri, 24 Nov 2006 15:59:15 +0000 + Dion Almaer + + Front Page + JavaScript + Tip + http://ajaxian.com/archives/another-trick-to-allow-array-subclasses + + Dean Edwards talked about his hack that got us the ability to subclass the Array object in JavaScript.

+

Hedger Wang has a new hack that uses window.createPopup instead of an iframe to for IE to fix some issues.

+

If you take a view source to see what is in there, you get the gem:

+
+
+
+;(function(){
+       
+        if(!window.createPopup){return};
+       
+        var fs = function(){
+       
+                /==/
+                var Array2 = parent.Array2 ;
+                var p1 = Array.prototype ;
+                var p2 = Array2.prototype;
+                for(i in p2 ){
+                        p1[i] = p2[i];
+                };
+                parent.Array2 = Array;
+                parent.document.title = 'Array2 is ready';/*debug msg*/
+                /==/
+        };
+       
+        document.title = 'Prepare Array2';/*debug msg*/

+

        fs = (fs + '').split('/==/')[1];
+        window.createPopup().document.body.innerHTML = '<img src="null" onerror="' +  fs + '" />';
+       
+})();

+

var Array2 = function(){};
+        Array2.prototype = new Array;
+        Array2.prototype.bar = function(){
+        alert("this.bar() --> This.Length=" + this.length );
+        }
+ 

+
+
+ +
]]> + http://ajaxian.com/archives/another-trick-to-allow-array-subclasses/feed/ + + + Dropboks: File Storage on One Page + http://ajaxian.com/archives/dropboks-file-storage-on-one-page + http://ajaxian.com/archives/dropboks-file-storage-on-one-page#comments + Fri, 24 Nov 2006 15:51:41 +0000 + Dion Almaer + + Front Page + Prototype + Showcase + http://ajaxian.com/archives/dropboks-file-storage-on-one-page + + Dropboks is a single page application build on Prototype and friends, that allows you to simply upload files for safe keeping.

+

The application is ad free, and survives on user donations. They do a good job at letting you use it pre-signup, and giving good info via tooltips.

+

Dropboks +

+ +
]]> + http://ajaxian.com/archives/dropboks-file-storage-on-one-page/feed/ + + + Spelling Cow: JS Spell Checker + http://ajaxian.com/archives/spelling-cow-js-spell-checker + http://ajaxian.com/archives/spelling-cow-js-spell-checker#comments + Fri, 24 Nov 2006 15:46:11 +0000 + Dion Almaer + + Front Page + http://ajaxian.com/archives/spelling-cow-js-spell-checker + + Spelling Cow allows you add a script tag, and spell check is enabled on your website. There are also some variables you can tweak too if advanced features are needed.

+

This means that you can add spell checking to your applications, but as the latest browsers have added inline spell check, is there use to it?

+

Spelling Cow +

+ +
]]> + http://ajaxian.com/archives/spelling-cow-js-spell-checker/feed/ + + + CSS Tab Designer + http://ajaxian.com/archives/css-tab-designer + http://ajaxian.com/archives/css-tab-designer#comments + Fri, 24 Nov 2006 15:40:05 +0000 + Dion Almaer + + Front Page + CSS + http://ajaxian.com/archives/css-tab-designer + + Now we are getting niche. A tool that lets you design CSS tabs:

+

With the CSS Tab Designer, you can:

+
    +
  • Quickly design your list visually.
    • +
  • Choose from a variety of styles/colors (60+ different designs/colors supported).
    • +
  • Generate strict xhtml compliant code.
    • +
+

+

+ +
]]> + http://ajaxian.com/archives/css-tab-designer/feed/ + + + Open-jACOB Draw2D + http://ajaxian.com/archives/open-jacob-draw2d + http://ajaxian.com/archives/open-jacob-draw2d#comments + Thu, 23 Nov 2006 16:44:35 +0000 + Dion Almaer + + Front Page + JavaScript + Library + Showcase + http://ajaxian.com/archives/open-jacob-draw2d + + Open-jACOB Draw2D is a JavaScript library that allows you to create drawings and diagrams.

+

The User interface allows interactive drawing by using your standard browser.
+No additional software; no third party plug ins. Just run it and use it.

+

Open-jACOB Draw2D is the graph component of the Open-jACOB online
+Workflow editor. The purpose of this experiment is to see if a Visio-type workflow
+editor tool could be developed in a web browser - It is possible.

+

Check out an interactive demo.

+

+

+ +
]]> + http://ajaxian.com/archives/open-jacob-draw2d/feed/ + + + Google Pages Adds Nice Image Editing + http://ajaxian.com/archives/google-pages-adds-nice-image-editing + http://ajaxian.com/archives/google-pages-adds-nice-image-editing#comments + Thu, 23 Nov 2006 16:15:04 +0000 + Dion Almaer + + Front Page + JavaScript + Showcase + Google + UI + http://ajaxian.com/archives/google-pages-adds-nice-image-editing + + When I heard about JotSpot heading to the Googleplex I was excited to know that Abe Fettig (Jot) would be teaming up with the brains at Google Pages, and I can't wait to see what happens in the world of WYSIWYG editing tools.

+

Google Pages just released a few features, and one of them is an improved process for working with images.

+

Firstly, the way you get photos up is simple and clean, but when when you have an image, you can click on it and you are shown a bunch of tools that allow you to manipulate the image inline, right there on the page.

+

Google Pages Image Editing +

+ +
]]> + http://ajaxian.com/archives/google-pages-adds-nice-image-editing/feed/ + + + qooxdoo 0.6.2 Released + http://ajaxian.com/archives/qooxdoo-062-released + http://ajaxian.com/archives/qooxdoo-062-released#comments + Thu, 23 Nov 2006 15:39:07 +0000 + Dion Almaer + + Front Page + JavaScript + Library + http://ajaxian.com/archives/qooxdoo-062-released + + qooxdoo has a new release that adds support for Webkit.

+

+As mentioned above and already announced in our developer blog, qooxdoo now includes support for WebKit. We expect to fully support the next major version Safari 3.0 which will be based on the current development of WebKit. There is only limited support for Safari in its current version 2.0.4, though. Reason is, that Safari 2.0 still has many bugs that can hardly be worked around. Luckily, many of those bugs are already fixed in the nightly builds of WebKit. Besides the various bugs, Safari 2.0's JavaScript engine and its execution speed is not competitive with respect to the latest versions of the other major browsers (Firefox 2.0, IE7, Opera 9). Good news is, that the current builds of WebKit are tremendeously faster than Safari 2.0, approximately by a factor of 7-8 for a typical qooxdoo demo. +

+

Check out the release notes for full details on changes in this release.

+

Some of them are:

+
    +
  • Made qooxdoo completely XHTML compatible. Replaced all uppercase tag names with their lowercase variant.
    • +
  • Improved NativeWindow to support the querying of the load state. Added events for “load” and “close”.
    • +
  • Modified XmlHttpRequest and related APIs to respect the latest suggestions from Microsoft.
    • +
  • Added IframeManager to manage visible iframes in order to protect the application events of the “surrounding” document from getting interrupted while switching document context (particularly drag & drop over embedded iframes)
    • +
  • Added Resizer widget to allow of customization regarding the dimensions of any widget by the user.
    • +
+ +
]]> + http://ajaxian.com/archives/qooxdoo-062-released/feed/ + + + Lollygag: Latest non-Atlas .NET Framework + http://ajaxian.com/archives/lollygag-latest-non-atlas-net-framework + http://ajaxian.com/archives/lollygag-latest-non-atlas-net-framework#comments + Thu, 23 Nov 2006 14:00:50 +0000 + Dion Almaer + + Front Page + JavaScript + Library + Toolkit + .NET + http://ajaxian.com/archives/lollygag-latest-non-atlas-net-framework + + The Lollygag framework is a new Ajax framework for .NET.

+

As Steve the author put it:

+

+We attended the first Ajax Experience conference in San Francisco and we got super excited about the potential for building Ajax applications. Since we have a Microsoft .NET background, we planned to start building Ajax applications using Microsoft’s Atlas framework. However, we quickly encountered several serious issues with Atlas. Doing simple things in Atlas, such as database access and form validation, turned out to be really difficult. We were also disappointed to discover that Microsoft has no plans to support its client-side Atlas framework in the immediate future.

+

We built the Lollygag framework in order to build true Ajax applications in the .NET environment. We wanted to build single page Web applications that never perform postbacks. All updates are performed through Ajax calls to the web server. +

+

Features

+
    +
  • Powerful Widget Framework: The Lollygag framework includes a rich set of client-side widgets that you can use to display database data, perform form validation, and create rich animations. You declare widgets in a page in exactly the same way as you declare HTML tags.
    • +
  • Autocomplete Support: When you declare Lollygag widgets in a page, you get full autocomplete support while you type. To get autocomplete support, you must use an XML aware development environment such as Microsoft Visual Studio .NET.
    • +
  • Declarative Database Access: Accessing database data with the Lollygag framework is easy. You can bind client-side widgets directly to data exposed by a database or you can bind widgets to data exposed by a business object.
    • +
  • Secure Form Validation: When taking advantage of the Lollygag framework, you specify how a form field is validated only once. The validation is automatically applied on both the server and the client. Unlike other frameworks that only provide validation on the client, the Lollygag framework prevents malicious users from bypassing client-side validation and submitting data directly to the server.
    • +
  • Rich Animation Framework: Lollygag includes an entire animation framework. You can take advantage of animations to create different effects such as fades and wipes.
    • +
  • Cross-Browser Support: The full Lollygag framework works on the latest versions of Internet Explorer, Firefox, Safari, and Opera.
    • +
  • Automatic JavaScript Compression: The Lollygag framework compresses all JavaScript sent to the browser automatically. Any custom JavaScript code that you write as a developer is also compressed automatically.
    • +
  • Powered by .NET: The server-side portion of Lollygag is built on the Microsoft .NET 2.0 Framework. You can build server-side business objects using standard .NET languages such as C# and VB.NET. Lollygag client-side widgets can consume data exposed through server-side objects.
    • +
+

Hello World

+
+
+
+<?xml version="1.0" encoding="utf-8" ?>
+<?xml-stylesheet type="text/xsl" href="/lollygagSite/lollygagframework/0_1/lollygag.xsl"?>
+<lolly :application title="Hello World" xmlns="http://www.w3.org/1999/xhtml" xmlns:lolly="http://lollygagframework.com/core">
+  <lolly :button id="btnSumit" label="Click Here!" onClick="alert('Hello!')" />
+</lolly>
+ 
+
+
+

Resources

+

How does it compare to Atlas? Read their thoughts on the matter.

+

Demos

+

Sample Application +

+ +
]]> + http://ajaxian.com/archives/lollygag-latest-non-atlas-net-framework/feed/ + + + Google Book Search gets an Ajax upgrade + http://ajaxian.com/archives/google-book-search-gets-an-ajax-upgrade + http://ajaxian.com/archives/google-book-search-gets-an-ajax-upgrade#comments + Thu, 23 Nov 2006 00:03:44 +0000 + Dion Almaer + + Front Page + Showcase + Google + http://ajaxian.com/archives/google-book-search-gets-an-ajax-upgrade + + Nathan Naze and his team at Google have upgraded Google Books:

+
+
    +
  • Zoom in on text and images. Here's a cool full-page sketch of a ship from an 1898 book on steam navigation. Looking for something less dated? Perhaps this colorful page of a room from a book on interior design. Want a better look? You can now zoom in and out — just click on the zoom in and zoom out buttons. Play with it until you find a size you like.
    • + +
  • One book, one web page. No more reloads! In one-page mode (just click the one page button), pages appear one below the other, like a scroll of paper. For full-view books, there's also a two-page mode (two page button) in which pages appear side by side, just like in a physical book (perfect for two-page images). In both modes, you'll be able to use previous page button and next page button to turn pages.
    • + +
  • Scroll, scroll, scroll your book… using the scrollbar or your mouse wheel, or by dragging (in most browsers, you'll see a hand). You can also use the keyboard (try the spacebar, page up, page down, and the arrow keys). Or you can click on a link in the table of contents or your search results to jump right to that page (like this photo from the 1906 book Geronimo's Story of His Life).
    • + +
  • This page was made for reading. We've tried to tidy up the clutter to leave as much room as possible for what's important — the book. We've put all the information about the book in a scrollable side menu. Still not enough room? You can put the screen in fullscreen mode with fullscreen button, so you can use the whole window for browsing. Try it with a nice illustrated book of Celtic fairy tales or, for some lighter reading, electromagnetic wave theory.
    • +
+
+

There are keystrokes here too, such as hitting space to scroll down (moving down smoothly). It is nice to see more and more unification to Google apps these days. When you use Reader it feels like Mail, etc.

+

One question is, where are the GWT apps? :)

+

Google Book Search +

+ +
]]> + http://ajaxian.com/archives/google-book-search-gets-an-ajax-upgrade/feed/ + + + diff --git a/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/feeds/febo-feeds.opml.xml b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/feeds/febo-feeds.opml.xml new file mode 100644 index 0000000000..633e184282 --- /dev/null +++ b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/feeds/febo-feeds.opml.xml @@ -0,0 +1,29 @@ + + + Thunderbird OPML-Export + Fri, 08 Dec 2006 12:00:29 GMT + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/feeds/qooxdoo-blog.xml b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/feeds/qooxdoo-blog.xml new file mode 100644 index 0000000000..241d450954 --- /dev/null +++ b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/feeds/qooxdoo-blog.xml @@ -0,0 +1,278 @@ + + + + + qooxdoo Blog + http://blog.qooxdoo.org + The blog of the qooxdoo developers + Sun, 26 Nov 2006 15:53:14 +0000 + http://wordpress.org/?v=2.0.5 + en + 384287 + Safari support for qooxdoo coming + http://feeds.feedburner.com/~r/qooxdoo/blog/content/~3/48836959/safari-support-for-qooxdoo-coming + http://blog.qooxdoo.org/safari-support-for-qooxdoo-coming#comments + Mon, 13 Nov 2006 14:46:19 +0000 + Fabian Jakobs + + Announcements + + Safari + + Technical + + http://blog.qooxdoo.org/safari-support-for-qooxdoo-coming + + Safari support for qooxdoo is coming along nicely. qooxdoo support for the nightly build of WebKit is near to complete. Most demos and examples are working, including the API viewer . The screenshot shows the “At a Glance” example running in WebKit. Safari 2.0.4 shipped with the current OS X 10.4 is usable but still has some rendering issues.

+
WebKit - "At a Glance" example WebKit - API viewer
+

For the next qooxdoo release we plan to fully support WebKit, which hopefully builds the basis for the next major release of Safari shipped with the upcoming OS X 10.5. We decided to target WebKit because of its improved standard support and its dramatically faster JavaScript engine. Some qooxdoo examples are up to seven times faster using WebKit compared to Safari 2. Even if we would fully support Safari 2, it will never be a good platform for big JavaScript applications.

+ +
]]> + http://blog.qooxdoo.org/safari-support-for-qooxdoo-coming/feed/ + http://blog.qooxdoo.org/safari-support-for-qooxdoo-coming + + Tamarin Follow-ups + http://feeds.feedburner.com/~r/qooxdoo/blog/content/~3/46350978/tamarin-follow-ups + http://blog.qooxdoo.org/tamarin-follow-ups#comments + Tue, 07 Nov 2006 21:53:17 +0000 + Sebastian Werner + + Firefox + + Performance + + Adobe + + http://blog.qooxdoo.org/tamarin-follow-ups + + +

I have just found some more interesting stuff regarding our Tamarin post today: 

+ +

+

+ +
]]> + http://blog.qooxdoo.org/tamarin-follow-ups/feed/ + http://blog.qooxdoo.org/tamarin-follow-ups + + Project Tamarin to boost JavaScript + http://feeds.feedburner.com/~r/qooxdoo/blog/content/~3/46219737/project-tamarin-to-boost-javascript + http://blog.qooxdoo.org/project-tamarin-to-boost-javascript#comments + Tue, 07 Nov 2006 12:55:22 +0000 + Andreas Ecker + + Firefox + + Performance + + Adobe + + http://blog.qooxdoo.org/project-tamarin-to-boost-javascript + + +

Good news, everyone! 

+

Recently we have been puzzled by some statements of Brendan Eich, the creator of the JavaScript programming language.

+

In Brendan's blog he wrote "For Mozilla 2, we will have a JIT-oriented JavaScript VM (details soon) that supports the forthcoming ECMAScript Edition 4 ("JS2") language" (October 13, 2006). Well, could hardly wait for any details. Another statement that made us curious was at The Ajax Experience this fall. In his slides about JavaScript 2.0 he mentioned  "Open source optimizing VMs coming soon. Look for an announcement in a few weeks" (October 25, 2006). Interestingly, this mysterious announcement was in a section he called "JavaScript Fun Facts".

+

Well done Brendan, you are our Master of Suspense! Finally, as a revelation today came the announcement that is going to boost JavaScript. Congratulations to Adobe for their decision of contributing the ActionScript Virtual Machine (AVM) as open source to the Mozilla project. And a warm open-source welcome to all the developers of the AVM! The code has just been committed into the Mozilla repository.

+

This is great news for qooxdoo being a client-side JavaScript framework. Performance has always been one of our major concerns, and we think we have pushed the limit for JavaScript based web applications, e.g. for qooxdoo's powerful browser-independent layout engine. Can't wait to tweak the last bit of performance out of any new Mozilla browser backed by the new JavaScript VM. This is going to change the future of browser-based applications. Cheers!

+

+

+ +
]]> + http://blog.qooxdoo.org/project-tamarin-to-boost-javascript/feed/ + http://blog.qooxdoo.org/project-tamarin-to-boost-javascript + + Adobe improves JavaScript performance + http://feeds.feedburner.com/~r/qooxdoo/blog/content/~3/46178140/adobe-improves-javascript-performance + http://blog.qooxdoo.org/adobe-improves-javascript-performance#comments + Tue, 07 Nov 2006 12:01:29 +0000 + Sebastian Werner + + Firefox + + Flash + + Adobe + + http://blog.qooxdoo.org/adobe-improves-javascript-performance + + +

In my opinion there was never a reason why JavaScript should be slower than other typical script languages e.g. Python, Perl, Ruby, … With the newest committment from Abobe to Mozilla we could reach a new level of performance in web applications. 

+

As news.com reports "Adobe will provide the same software, called the ActionScript Virtual Machine, which it uses to run script code in the Adobe Flash Player 9. This virtual machine is expected to be built into future versions of the Firefox browser by the first half of 2008, said Frank Hecker, the executive director of the Mozilla Foundation."

+

Via news.com

+

+

+ +
]]> + http://blog.qooxdoo.org/adobe-improves-javascript-performance/feed/ + http://blog.qooxdoo.org/adobe-improves-javascript-performance + + Keep yourself up-to-date + http://feeds.feedburner.com/~r/qooxdoo/blog/content/~3/37261107/keep-yourself-up-to-date + http://blog.qooxdoo.org/keep-yourself-up-to-date#comments + Sat, 14 Oct 2006 21:41:08 +0000 + Sebastian Werner + + Development + + http://blog.qooxdoo.org/keep-yourself-up-to-date + + There is a new feed available on our homepage. You can now easily follow the development in our SVN repository. Hope you like this. Especially interesting for users who want to be up-to-date. Also a nice alternative to our qooxdoo-commit mailing list. +

+ +
]]> + http://blog.qooxdoo.org/keep-yourself-up-to-date/feed/ + http://blog.qooxdoo.org/keep-yourself-up-to-date + + Only five days to IE7 + http://feeds.feedburner.com/~r/qooxdoo/blog/content/~3/36678532/5-days-to-ie7 + http://blog.qooxdoo.org/5-days-to-ie7#comments + Fri, 13 Oct 2006 08:42:36 +0000 + Sebastian Werner + + Internet Explorer + + http://blog.qooxdoo.org/5-days-to-ie7 + + Following a report of Microsoft Higher Education - Mid-Atlantic it seems that IE7 will be released on the 18th this month. In just 5 days. The most changes are only interesting for typical web developers (e.g. CSS fixes) while the latest improvements to the JavaScript engine are also an interesting point for us and other big JavaScript frameworks. I hope we will see a market share of 50 percent after the first six months. +

+ +
]]> + http://blog.qooxdoo.org/5-days-to-ie7/feed/ + http://blog.qooxdoo.org/5-days-to-ie7 + + IE7 CSS changes + http://feeds.feedburner.com/~r/qooxdoo/blog/content/~3/32468983/ie7-css-changes + http://blog.qooxdoo.org/ie7-css-changes#comments + Wed, 04 Oct 2006 20:04:27 +0000 + Sebastian Werner + + Bookmark + + http://blog.qooxdoo.org/ie7-css-changes + + An interesting read for all web developers: Cascading Style Sheet Compatibility in Internet Explorer 7.
+

+ +
]]> + http://blog.qooxdoo.org/ie7-css-changes/feed/ + http://blog.qooxdoo.org/ie7-css-changes + + Support for compression of local variables added + http://feeds.feedburner.com/~r/qooxdoo/blog/content/~3/32241766/support-for-compression-of-local-variables-added + http://blog.qooxdoo.org/support-for-compression-of-local-variables-added#comments + Wed, 04 Oct 2006 11:06:46 +0000 + Sebastian Werner + + Development + + Technical + + http://blog.qooxdoo.org/support-for-compression-of-local-variables-added + + +

A few hours ago I've committed a change which adds a variable name optimizer into the qooxdoo trunk. This optimizer replaces the names of local variables with shorter ones. The result is a size reduction of the compiled JavaScript file by 10%. This new behavior is enabled per default for all the included Makefiles. So after an SVN update you can build your (again) better optimized version of qooxdoo.

+

This can also been seen as a next step in bringing support for obfuscation another step forward. I have also updated the online demos and the API viewer to use this new feature. I would like to invite you to give me feedback as soon as possible. Maybe you also find some bugs. If so, please report them immediately. Thank you.

+

+

+ +
]]> + http://blog.qooxdoo.org/support-for-compression-of-local-variables-added/feed/ + http://blog.qooxdoo.org/support-for-compression-of-local-variables-added + + AJAX framework survey + http://feeds.feedburner.com/~r/qooxdoo/blog/content/~3/26565493/ajax-framework-poll + http://blog.qooxdoo.org/ajax-framework-poll#comments + Sun, 24 Sep 2006 09:04:41 +0000 + Sebastian Werner + + Discussion + + Survey + + http://blog.qooxdoo.org/ajax-framework-poll + + +

The guys at ajaxian.com have reported about a current survey regarding the popularity of common AJAX frameworks. It is quite clear why prototype is the winner. It's well-known, small and easily embedable into existing pages. However I think it is interesting that Mochikit is less widely used, because the targets of these libraries are comparable in my opinion. And Mochikit does not depends on extensions of native objects (especially Object.prototype) which makes it the better choice.

+

I should mention that in my opinion the whole survey is quite problematic because of their comparison of different levels of so named "AJAX frameworks". For a next survey I would suggest to divide the list into these groups:

+

AJAX wrappers & DOM utilities:

+
    +
  • Prototype & Scriptaclous & Rico
    • +
  • Moo.fx
    • +
  • jQuery
    • +
  • Yahoo UI
    • +
  • Mochikit
    • +
  • XAJAX
    • +
  • DWR (includes backend code, too)
    • +
+

Framework & Toolkits:

+
    +
  • Dojo
    • +
  • Atlas
    • +
  • GWT
    • +
  • qooxdoo (seems to be missing ;) ) 
    • +
+

I've grouped together Scriptaclous and Rico because they both depend on Prototype which means they are more or less an extension of this library and not a real separate solution.

+

What do you think? 

+

+

+ +
]]> + http://blog.qooxdoo.org/ajax-framework-poll/feed/ + http://blog.qooxdoo.org/ajax-framework-poll + + Dramatically improved IE7 JavaScript performance + http://feeds.feedburner.com/~r/qooxdoo/blog/content/~3/21793941/dramatically-improved-ie7-javascript-performance + http://blog.qooxdoo.org/dramatically-improved-ie7-javascript-performance#comments + Wed, 13 Sep 2006 11:35:53 +0000 + Sebastian Werner + + Internet Explorer + + Technical + + Performance + + http://blog.qooxdoo.org/dramatically-improved-ie7-javascript-performance + + +

Really good news. My vocabulary may to be too limited to tell you how great the latest changes in IE7 RC1 are. Microsoft announced that they have "recently made some great fixes to our engine to improve the garbage collection routine and to reduce unbounded memory growth." and that one "should see noticeable improvements on AJAX sites in the Release Candidate we shipped last week". Yes indeed, we do see tremendeous improvements. :-)

+

In fact many demos of qooxdoo run much faster now in IE7 compared to IE6. And they are even faster than in Firefox 1.5 in many cases. This is a huge jump in performance. Microsoft did not tell about their exact modifications, of course. Anyway, they have fixed the major problem of large JavaScript-based web applications. This problem, despite having a catchy name, was mentioned many times before like here, here and there: If you have many objects created, which are simply accessible in the current scope, all methods and features of JavaScript slow down dramatically. Yeah, right, the entire execution speed drops significantly. No other browser besides IE shows such a strange behavior. It is quite interesting that IE6 really gets slower the larger the total number of (accessible) objects. Sure, it is logical that more instanciated objects need more memory, but it is not logical that at the same time this will dramatically reduce the performance of any code (that is not even accessing this data).

+

With the release candidate RC1 of their new browser version IE7, it seems that they have finally fixed this issue. You can test it yourself in this test case, which has been available in qooxdoo for several months to analyze and measure the IE performance problems. Please look at status bar of your browser (maybe you need to enable the status bar in the IE7 security settings). It will display the execution time of each loop while a large number of objects exists. On my machine the IE6 needs ~1400ms, while IE7 needs ~30ms, which is roughly the time Firefox 1.5 needs. Definitely incredible! Bright future for modern web applications. :-)

+

+

+ +
]]> + http://blog.qooxdoo.org/dramatically-improved-ie7-javascript-performance/feed/ + http://blog.qooxdoo.org/dramatically-improved-ie7-javascript-performance + + diff --git a/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/feeds/qooxdoo-news.xml b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/feeds/qooxdoo-news.xml new file mode 100644 index 0000000000..3b17a19c73 --- /dev/null +++ b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/feeds/qooxdoo-news.xml @@ -0,0 +1,284 @@ + + + + + qooxdoo News + http://news.qooxdoo.org + The qooxdoo news section + Sun, 26 Nov 2006 15:52:09 +0000 + http://wordpress.org/?v=2.0.5 + en + 390072 + qooxdoo 0.6.2 released + http://news.qooxdoo.org/qooxdoo-062-released + http://news.qooxdoo.org/qooxdoo-062-released#comments + Wed, 22 Nov 2006 14:13:38 +0000 + Andreas Ecker + + Announcements + + Release + + http://news.qooxdoo.org/qooxdoo-062-released + + Good news, everyone!

+

Despite of the minor change in version number, this release is again a major step in strengthening qooxdoo's position of being one of the most comprehensive and innovative AJAX frameworks. It now even includes support for WebKit and future versions of Safari!

+

It came as quite a surprise how many fixes, changes and additions we were actually able to include in this fine little package. During the eight weeks after release 0.6.1, many people have made contributions. Thanks to all qooxdoo users, contributors, patch monsters and supporters for helping to make the framework more mature and feature-complete!

+

Targeted as a maintenance release it includes many bugfixes and only minor changes in functionality or API. We recommend to upgrade any applications based on qooxdoo 0.6.1. Of course, there is migration support available, even if it is hardly needed this time.

+

As mentioned above and already announced in our developer blog, qooxdoo now includes support for WebKit. We expect to fully support the next major version Safari 3.0 which will be based on the current development of WebKit. There is only limited support for Safari in its current version 2.0.4, though. Reason is, that Safari 2.0 still has many bugs that can hardly be worked around. Luckily, many of those bugs are already fixed in the nightly builds of WebKit. Besides the various bugs, Safari 2.0's JavaScript engine and its execution speed is not competitive with respect to the latest versions of the other major browsers (Firefox 2.0, IE7, Opera 9). Good news is, that the current builds of WebKit are tremendeously faster than Safari 2.0, approximately by a factor of 7-8 for a typical qooxdoo demo.

+

We think it is worth to either use WebKit for now or wait for Safari 3.0 due in early 2007. There is probably not much sense in devoting more time and effort for Safari 2.0 specific problems. There are still some known issues concerning WebKit support (particularly for widgets that use scrollbars). It would be great if Mac users could give qooxdoo 0.6.2 a try and report any problem in bugzilla. Please use the most recent nightly build of WebKit and include its version information in any bug report.

+

For more detailed information about qooxdoo 0.6.2 please consult the corresponding release notes.

+

Enjoy!

+ + +
]]> + http://news.qooxdoo.org/qooxdoo-062-released/feed/ + + + IE7 released, finally + http://news.qooxdoo.org/ie7-released-finally + http://news.qooxdoo.org/ie7-released-finally#comments + Thu, 19 Oct 2006 12:26:18 +0000 + Andreas Ecker + + Announcements + + http://news.qooxdoo.org/ie7-released-finally + + +

Good news to every developer of modern web applications. After more than 5 years (IE6 was released in August 2001) we all hope to see IE7 fix some of the most severe problems and bugs of IE6. All qooxdoo-based applications are expected to benefit from IE7, particularly due to the dramatic JavaScript performance improvements that we reported earlier.

+

qooxdoo fully supports IE7. It would be great if qooxdoo users and developers could continue to test and double-check their applications for IE7 compatibility. Please report any IE7 issues in bugzilla as soon as possible.

+

Enjoy … and good luck! 

+

+

+ +
]]> + http://news.qooxdoo.org/ie7-released-finally/feed/ + + + qooxdoo 0.6.1 released + http://news.qooxdoo.org/qooxdoo-061-released + http://news.qooxdoo.org/qooxdoo-061-released#comments + Wed, 20 Sep 2006 18:49:16 +0000 + Andreas Ecker + + Announcements + + Release + + http://news.qooxdoo.org/qooxdoo-061-released + + +

After only two weeks since the ground-breaking release of qooxdoo 0.6 quite a lot of progress has been made. We have received many contributions and bugfixes from the community. These patches as well as our own  modifications have been integrated into the code base in the ongoing effort to raise qooxdoo's stability.

+

As has been previously announced, we try to release often, now that some of the most challenging reconstructions like namespaces have been mastered. While API changes for this minor release are negligible, migration scripts are available to upgrade existing applications, of course.

+

Preliminary browser support for Safari has been introduced. It would be great if Safari users could help in identifying, analyzing and fixing the various layout problems. It is still not recommended to use qooxdoo applications in Safari-based production environments.

+

Besides bugfixes and stability improvements there are some interesting additions as well. Tabs may optionally include close buttons, the tree widget TreeFullControl now supports multiple root nodes. Iframes containing external documents now have built-in blocking support to not interrupt user actions like drag & drop.

+

Application development is even faster than before: the easy-to-use make shell commands that generate optimized and tailor-made custom applications run much faster. Users get a jump-start for their application development by using the skeletons included in the qooxdoo SDK.

+

We would like to thank all people involved in qooxdoo development for their help and contribution. Every user's feedback is important to continuously improve qooxdoo as one of the most amazing JavaScript frameworks around. Enjoy!

+ +

+

+ +
]]> + http://news.qooxdoo.org/qooxdoo-061-released/feed/ + + + qooxdoo 0.6 released + http://news.qooxdoo.org/qooxdoo-06-released + http://news.qooxdoo.org/qooxdoo-06-released#comments + Thu, 07 Sep 2006 17:49:13 +0000 + Sebastian + + Announcements + + Release + + http://news.qooxdoo.org/qooxdoo-06-released + + +

Here comes the most advanced qooxdoo version ever! qooxdoo 0.6 introduces namespaces as the most noticeable change. This step has been combined with a long thought-out and at the end well-structured directory layout.

+

Integrated is one of the most advanced build systems. This new system allows you to generate tailor-made user applications linked against the qooxdoo framework. You can even include your own project classes and optimize them along with qooxdoo. Using this new build system you can generate blazingly fast and highly optimized qooxdoo builds.

+

A new ground-breaking qooxdoo-based API viewer was added to make software development with qooxdoo easier than ever before. Supposed to become every qooxdoo users' number one resource, it shows all available packages, classes, properties and methods. All related information is connected by hyperlinks which gives you a highly convenient way to access the relevant information.

+

Of course there are also new widgets. A new advanced table widget has been introduced which is a virtual list view component that allows to handle many thousands of entries. Its features also make it possible to dynamically load the data from a remote server (using RPC for example). A splitpane - one of the long-awaited widgets - is now included. Full-blown logging capabilities featuring various appenders are available as well.

+

There are a lot more changes and enhancements. For details please take a look at the release notes. Migration support simplifies the switch from the last qooxdoo release 0.5.3. qooxdoo 0.6 is the perfect framework to build highly-interactive web applications. Why don't you start now? Just download qooxdoo today!

+

+

+ +
]]> + http://news.qooxdoo.org/qooxdoo-06-released/feed/ + + + Introduce new tree compiler + http://news.qooxdoo.org/introduce-new-tree-compiler + http://news.qooxdoo.org/introduce-new-tree-compiler#comments + Thu, 31 Aug 2006 16:02:27 +0000 + Sebastian + + Announcements + + Development + + http://news.qooxdoo.org/introduce-new-tree-compiler + + +

Another step forward to highly optimized applications based on qooxdoo: I would like to introduce the tree "compiler". The tree compiler is able to "compile" a syntax tree (generated by treegenerator.py which uses the tokenizer.py) back to optimized JavaScript code. Its feature set is comparable to the old compiler, which was directly based on the result of the tokenizer.py script. It completely removes comments, whitespaces and other optional stuff from the original JavaScript code.

+

This tree compiler is an important step, because it will allow us to do the following awesome things in the future:

+
    +
  • Remove complete methods (debug statements, …)
    • +
  • Remove cross-browser constructions and generate a version for each browser/engine.
    • +
  • Compress variable names
    • +
  • Lay out strings and reduce usage of simple constants (like "auto", "100%", …) for considerable IE performance improvements
    • +
  • Obfuscate the whole application (variable, function and class names)
    • +
+

etc.

+

Now the interesting part: The tree compiler is the default from now on. It is already available in SVN and will be in the final release of qooxdoo 0.6. The tree compiler was tested against qooxdoo and another big internal project so we think it's quite stable already. It may not be free of bugs however, but I'm happy to fix bugs as fast as you can report them ;)

+

If you have problems with this new compiler, you can use the old one using the "–use-token-compiler" argument (generator.py). Each Makefile which is included in qooxdoo, has a new variable (OLDCOMPILER) in the first lines of the file which lets you select the compiler (simply set it to "true").

+

I hope you enjoy this new era of JavaScript optimization. Kudos to Til - without the treegenerator.py developed by him, qooxdoo would maybe not have seen such a tree-based optimizer.

+

You can immediately test the new compiler. Its results can also been seen online in the online demos and the API viewer.

+

For all SDK/source version users: Please make sure to delete the directory ".cache". A simple "make distclean" will do this for you.

+

+

+ +
]]> + http://news.qooxdoo.org/introduce-new-tree-compiler/feed/ + + + qooxdoo 0.6 (Release Candidate 1) available + http://news.qooxdoo.org/qooxdoo-06-release-candidate-1-available + http://news.qooxdoo.org/qooxdoo-06-release-candidate-1-available#comments + Sat, 19 Aug 2006 02:31:26 +0000 + Andreas Ecker + + Release + + http://news.qooxdoo.org/qooxdoo-06-release-candidate-1-available + + +

Many aspects of qooxdoo have been improved to make it an even more professional and complete JavaScript framework.

+

A lot of issues, that have been brought up and discussed on the mailing list before, have been addressed. Some of the most noticable additions include a qooxdoo-based viewer for the auto-generated API documentation, a more powerful virtual list view and a smart build process that makes optimizing, compressing, linking and deployment of custom applications a snap.

+

A Release Candidate 1 is now available for easy download. That way people can immediately start to get themselves familiar with the most important improvements.

+

We would like to thank all users, contributors and fellow developers for their ongoing help and support. Keep up the good work!

+

Try online demos

+

Digg this 

+

+

+ +
]]> + http://news.qooxdoo.org/qooxdoo-06-release-candidate-1-available/feed/ + + + Branch “namespaces” discontinued + http://news.qooxdoo.org/branch-namespaces-discontinued + http://news.qooxdoo.org/branch-namespaces-discontinued#comments + Wed, 16 Aug 2006 21:38:12 +0000 + Andreas Ecker + + Announcements + + http://news.qooxdoo.org/use-trunk-instead-of-namespaces-branch + + +

IMPORTANT: Until recently the major development work towards the next release 0.6 has been done in a development branch named "namespaces". This branch is now discontinued. Its content has been transfered into the SVN trunk.

+

Future development of qooxdoo will concentrate on changes made in the trunk. Anyone interested in an up-to-date version of the framework should simply checkout the latest revision of the SVN trunk . Clearly, these snapshots are not expected to be stable enough for production use. They are not even supposed to be functional at all. It may happen that the trunk is broken for not only hours (delibaretely) but even days (rather by accident). Think of the trunk as a permanent work-in-progress that after potentially unstable phases finally leads to the next official release.

+

The content of the previous SVN trunk has been moved to a branch named "legacy_0_5_x". This branch may see some changes, particularly bugfixes and backports of modifications made in the trunk. Please do not expect many substantial improvements in this 0.5 line of qooxdoo, though. There may be a release 0.5.4 sometime, but this clearly depends on user contribution for this now "old" line of qooxdoo.

+

Please note, that the existing documentation has still to be updated to reflect the switch from the "namespaces" branch to the trunk. Information formerly specific to the "namespaces" branch should now be valid for the trunk.

+

We are getting closer to qooxdoo 0.6  :-)

+

+

+ +
]]> + http://news.qooxdoo.org/branch-namespaces-discontinued/feed/ + + + Planned Improvements for qooxdoo 0.6 + http://news.qooxdoo.org/planned-improvements-for-qooxdoo-06 + http://news.qooxdoo.org/planned-improvements-for-qooxdoo-06#comments + Thu, 10 Aug 2006 09:05:40 +0000 + Andreas Ecker + + Announcements + + http://news.qooxdoo.org/planned-improvements-for-qooxdoo-06 + + +

There is an extended update of an older post with respect to new features and modifications that are currently being implemented.

+

All interested qooxdoo users are welcome to bring themselves up-to-date and are invited to get involved in qooxdoo development. It takes not more than checking-out qooxdoo from a subversion repository and doing a "make" on your shell afterwards.

+

A couple of significant differences that are being addressed are:

+
    +
  • Namespaces
    • +
  • Documentation
    • +
  • Building and Deployment
    • +
  • Table
    • +
  • Remote Procedure Calls 
    • +
+

+

+ +
]]> + http://news.qooxdoo.org/planned-improvements-for-qooxdoo-06/feed/ + + + qooxdoo 0.5.3 released + http://news.qooxdoo.org/qooxdoo-053-released + http://news.qooxdoo.org/qooxdoo-053-released#comments + Wed, 12 Jul 2006 09:09:27 +0000 + Sebastian + + Announcements + + Release + + http://news.qooxdoo.org/announcements/qooxdoo-053-released + + This is just a small release with some bugfixes for the users of any previous 0.5.x release. Also take a look at the release notes. Download the new version here at sourceforge. +

+ +
]]> + http://news.qooxdoo.org/qooxdoo-053-released/feed/ + + + Bugzilla mailing list + http://news.qooxdoo.org/bugzilla-mailing-list + http://news.qooxdoo.org/bugzilla-mailing-list#comments + Mon, 19 Jun 2006 09:24:26 +0000 + Sebastian + + Bugs + + Mailing lists + + http://news.qooxdoo.org/uncategorized/bugzilla-mailing-list + + I’ve just registered and configured a new mailing list, which is used to monitor the bug activity. Bugs in qooxdoo are also used to manage feature additions and enhancement wishes.

+

You can register yourself to always stay up-to-date with the further development of qooxdoo. +

+ +
]]> + http://news.qooxdoo.org/bugzilla-mailing-list/feed/ + + + diff --git a/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/feeds/safari.xml b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/feeds/safari.xml new file mode 100644 index 0000000000..9fc3180811 --- /dev/null +++ b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/feeds/safari.xml @@ -0,0 +1,223 @@ + + + + + + Surfin' Safari + http://webkit.org/blog + All about WebKit development + Sat, 18 Nov 2006 22:18:02 +0000 + http://wordpress.org/?v=1.5.1.2 + en + + + Rob Buis is a WebKit Reviewer + http://webkit.org/blog/?p=82 + http://webkit.org/blog/?p=82#comments + Sat, 18 Nov 2006 22:17:52 +0000 + maciej + + Uncategorized + http://webkit.org/blog/?p=82 + + Rob Buis is now a qualified WebKit reviewer. Rob was one of the main driving forces behind ksvg2 and kcanvas, along with Nikolas Zimmerman. The code from these libraries has been integrated into WebKit to provide fully integrated HTML/SVG support. Since then, Rob has submitted many WebKit patches for SVG and in many other areas, including DOM, CSS, graphics support and general refactoring.

+

Please join me in congratulating Rob. +

+]]> + http://webkit.org/blog/?feed=rss2&p=82 + + + Google Web Toolkit 1.2 Uses WebKit + http://webkit.org/blog/?p=81 + http://webkit.org/blog/?p=81#comments + Sat, 18 Nov 2006 08:59:10 +0000 + aroben + + Uncategorized + http://webkit.org/blog/?p=81 + + Google has just released version 1.2 of the Google Web Toolkit (GWT) with full Mac OS X support provided by WebKit. GWT allows web developers to create shiny AJAX web applications entirely in Java, which GWT compiles to JavaScript. While Mac users were able to use the GWT compiler in previous versions, they couldn’t use GWT’s hosted browser to debug their web apps. WebKit has made it possible for Google to bring these development tools to the Mac, and, as a surprise Mac-only bonus, web developers using GWT get to use the Web Inspector, too! +

+]]> + http://webkit.org/blog/?feed=rss2&p=81 + + + Zack Rusin is a WebKit Reviewer for the Qt Port + http://webkit.org/blog/?p=79 + http://webkit.org/blog/?p=79#comments + Thu, 16 Nov 2006 02:32:07 +0000 + maciej + + Uncategorized + http://webkit.org/blog/?p=79 + + Zack Rusin is now a qualified reviewer for Qt platform code in WebKit. Although he has not yet submitted many patches to WebKit as such, he has a long history working with KHTML and did much of the Unity porting work originally. As such, he is likely one of the best reviewers for Qt platform code. Congrats, Zack, and thank you. +

+]]> + http://webkit.org/blog/?feed=rss2&p=79 + + + The Safari Team’s Favorite Websites + http://webkit.org/blog/?p=77 + http://webkit.org/blog/?p=77#comments + Tue, 07 Nov 2006 03:00:46 +0000 + maciej + + Uncategorized + http://webkit.org/blog/?p=77 + + Usually this blog has serious content about WebKit. But one of the great things about the web is that it’s actually lots of fun.
+To give you a bit of the flavor of the Safari/WebKit Team’s personality, here are a few of our favorite websites.
+Please post some of your favorite websites in the comments.

+

Apple Stuff

+ +

News & Information

+ +

Media & Celebrities

+ +

Amusement

+ +

Communication

+ +

Shameless Nerdery

+ +]]> + http://webkit.org/blog/?feed=rss2&p=77 + + + ADC Article about Apple Nightly Builds + http://webkit.org/blog/?p=78 + http://webkit.org/blog/?p=78#comments + Sat, 04 Nov 2006 02:33:23 +0000 + maciej + + Uncategorized + http://webkit.org/blog/?p=78 + + Apple Developer Connection has posted an article on using nightly builds. Most of this content won’t be news to people who are already using nightlies. But it might be of interest to web developers and application developers who have not tried nightlies yet. There is also some interesting info about canvas changes. +

+]]> + http://webkit.org/blog/?feed=rss2&p=78 + + + Sam Weinig is a WebKit Reviewer + http://webkit.org/blog/?p=76 + http://webkit.org/blog/?p=76#comments + Wed, 01 Nov 2006 01:00:05 +0000 + maciej + + Uncategorized + http://webkit.org/blog/?p=76 + + Sam Weinig is now a qualified WebKit reviewer. Sam has done a lot of coding in different areas of WebKit, including large refactoring changes and coding style cleanup, as well as large projects like autogenerating the Objective-C DOM bindings. At this point, he probably knows the coding style guidelines better than most of the existing reviewers. And now you get to bug him to review your patches.

+

Please join me in congratulating Sam.

+]]> + http://webkit.org/blog/?feed=rss2&p=76 + + + Optimizing Page Load Time (and a little about the Debug menu) + http://webkit.org/blog/?p=75 + http://webkit.org/blog/?p=75#comments + Tue, 31 Oct 2006 06:28:04 +0000 + maciej + + Uncategorized + http://webkit.org/blog/?p=75 + + We don’t usually just repost content from other blogs here. But a lot of web developers seem to read this site, and those of us who work on WebKit are totally into loading web pages as fast as possible. With that in mind, here’s a great article on Optimizing Page Load Time. I recommend reading and applying much of the advice here. However, I’ll note that we have experimented with using HTTP pipelining for Safari in the past, too many major servers gave garbage results in the face of it. While we may periodically re-evaluate this, we are not holding back on it out of spite or anything.

+

Another tip you might find handy as a web developer is the “Show Page Load Test Window” option in the Safari Debug menu. You can turn on the Debug menu by typing defaults write com.apple.Safari IncludeDebugMenu YES at a shell prompt, and then restarting Safari. This menu includes a number of rough debugging tools that we created mainly for browser testing, but you may find some of them handy for web development. The page load test in particular is interesting because it measures page load time in a more precise way than either onload timing or just using a stopwatch. If you change the “Suite” pop-up menu to “URL”, you can type the URL of your choice and get a fairly precise time for loading it. If you empty the cache first, you can get an uncached time.

+

I recommend trying this a couple of times as you test your site. We’ve found that it’s a lot easier to improve performance when you have a precise way to measure it.

+]]> + http://webkit.org/blog/?feed=rss2&p=75 + + + Adobe Apollo Uses WebKit + http://webkit.org/blog/?p=74 + http://webkit.org/blog/?p=74#comments + Mon, 30 Oct 2006 10:11:55 +0000 + maciej + + Uncategorized + http://webkit.org/blog/?p=74 + + A few months ago, Adobe announced Apollo, a tool that lets you build desktop applications based on Flash and web technologies like HTML and JavaScript. A bunch of blog posts have features whizzy screenshots. This is pretty cool stuff, you can use all your web development skills to make slick looking desktop apps.

+

Even more exciting, Adobe has announced that Apollo will use WebKit as its HTML layout engine. Welcome to the world of WebKit, Adobe.

+]]> + http://webkit.org/blog/?feed=rss2&p=74 + + + Color Spaces + http://webkit.org/blog/?p=73 + http://webkit.org/blog/?p=73#comments + Sun, 22 Oct 2006 11:37:48 +0000 + hyatt + + Uncategorized + http://webkit.org/blog/?p=73 + + I was pointed to this article about color spaces in Web browsers. The ultimate point of the article, that it would be good for a Web browser to be “Color Smart”, i.e., to support not only embedded color profiles in images but also to correct unprofiled images to sRGB is a sound one. However, the author takes a few potshots at Web browsers on the Mac, and I thought I’d respond to make it clear what the technical hurdles are with this problem.

+

First of all, if you correct unprofiled images to sRGB, you have to correct all drawing to sRGB. This includes everything drawn by CSS (borders, backgrounds, text). This is not difficult to do under the hood, although it is difficult to do it with no performance regression in our benchmarks at all. In fact we even tried this during the Tiger development cycle (just correcting everything drawn to sRGB), but it slowed us down.

+

The big hurdle that we ran into, though, was with the drawing we did not control, namely the Flash plug-in. The problem is that designers specify colors in Flash and colors in CSS in the Web page, and they expect those colors to match. Because Flash’s drawing isn’t correcting to sRGB, if we did it in Safari, there would be color mismatches all over the place. These mismatches look far worse than if we just don’t correct at all.

+

(This mismatch with plug-ins is presumably the reason that this feature was not enabled by default in Mac IE.)

+]]> + http://webkit.org/blog/?feed=rss2&p=73 + + + Safari Market Share Continues to Increase + http://webkit.org/blog/?p=71 + http://webkit.org/blog/?p=71#comments + Tue, 10 Oct 2006 20:23:16 +0000 + maciej + + Uncategorized + http://webkit.org/blog/?p=71 + + According to recent reports, Safari market share is still increasing. According to one survey, it’s up to 3.56%. The total including other WebKit-based browsers could be even higher, it’s hard to tell from the somewhat thin stats. It’s cool to see WebKit getting more and more users in any case. +

+]]> + http://webkit.org/blog/?feed=rss2&p=71 + + + diff --git a/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/feeds/zimbra-atom.xml b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/feeds/zimbra-atom.xml new file mode 100644 index 0000000000..2a09b9118d --- /dev/null +++ b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/feeds/zimbra-atom.xml @@ -0,0 +1,699 @@ + + +Zimbra - Blog + +2006-11-15T04:46:36Z +All things Zimbra +tag:www.zimbra.com,2006:/blog//1 +Movable Type +Copyright (c) 2006, Kevin + +What's new in ZCS 4.5 Beta 1 + +2006-11-15T04:46:36Z +2006-11-15T04:12:42Z +tag:www.zimbra.com,2006:/blog//1.129 +2006-11-15T04:12:42Z +We posted the first beta of Zimbra 4.5 this past Friday. Major new features of 4.5 include complex password enforcement, identities, personal distro lists's, server performance improvements, backup/restore in the admin console, a search builder in the admin console, user-set... + +Kevin +www.zimbra.comkevinh@zimbra.com +Kevin Henrikson +We posted the first beta of Zimbra 4.5 this past Friday.

+ +

Major new features of 4.5 include complex password enforcement, identities, personal distro lists's, server performance improvements, backup/restore in the admin console, a search builder in the admin console, user-set default fonts for HTML compose, an upgrade to use MySQL 5.0, and a Lotus Domino migration wizard. More details can be found in the beta release notes.

]]> + + + + +How much data does Zimbra Mobile use? + +2006-11-15T04:11:35Z +2006-11-15T03:49:42Z +tag:www.zimbra.com,2006:/blog//1.128 +2006-11-15T03:49:42Z +Lots of people have asked how much data Zimbra Mobile uses over the wire. Just got my Cingular bill so thought I'd post a screen shot to help explain. ... + +Kevin +www.zimbra.comkevinh@zimbra.com +Kevin Henrikson +Lots of people have asked how much data Zimbra Mobile uses over the wire. Just got my Cingular bill so thought I'd post a screen shot to help explain.

]]> +This is just a snapshot of one day Nov 7th and the total is for the previous 30days. My Nokia E61 is configured to sync every 15min from 8am -> 8pm 7days a week and then every 4hrs overnight (8pm->8am) On avg each check for mail, calendar, and contacts consumes ~20KB which turns out to be about 1.3MB per day or ~40MB per month. Cingular has a $19.99 Media Max plan that gives you unlimited data and 200 txt msgs so it works out pretty well.

+ +

Zimbra Mobile Data Usage
+

]]> + + + +Taking Zimbra Offline + +2006-11-09T19:43:13Z +2006-11-09T17:32:10Z +tag:www.zimbra.com,2006:/blog//1.127 +2006-11-09T17:32:10Z +Zimbra users have been asking for how they can take the Zimbra AJAX UI offline. Today at Web 2.0 we demo'd this for the first time. ... + +Kevin +www.zimbra.comkevinh@zimbra.com +Kevin Henrikson +Zimbra users have been asking for how they can take the Zimbra AJAX UI offline. Today at Web 2.0 we demo'd this for the first time.

]]> + The design goal is to have the same user experience with Zimbra both online and offline. Technically the Zimbra Offline client is the same AJAX client UI but now connecting to a local sync'd cache of the data and more importantly the ability to search, tag, organize, etc without network access. The two way sync of mail, calendar, contacts, and documents will allow Zimbra user's to take their collaboration data together with the Zimbra AJAX experience with them on the road or in places without a network connection and when they come back online - all of the changes made while offline (like composing, deleting, moving, creating messages, contacts, events or folders) are sync'd back to the cloud. Just like traditional offline mail clients - messages pending to be sent are stored in an Outbox where you can edit and view them until re-connected. You'll notice in the screenshots that both POP accounts and RSS feed folders are sync'd when in offline mode just as when online. RSS folders have been part of Zimbra for a while. POP aggregation will be part of our next major release and IMAP will be added shortly after that. Mail identities allows you to respond with the FROM and REPLY-TO addresses that the mail come with - responding to mail POP'd from gmail; Zimbra will automatically set the FROM address to your @gmail.com account. This feature is also useful for people who would like to respond as support@company.com when responding on behalf of a support team mail list for example. Mail identities will also be part of Zimbra's next major release. Watch this space for more on the architecture of the offline sync cache - meanwhile below are some screenshots. The beta version of the offline client for email and contacts will be available in Q4.

+ +

Zimbra Outbox

+ +

Zimbra Offline Compose

+ +

Zimbra Offline POP accounts

+ +

Zimbra Offline Sync

+ +

Zimbra Mail Identities

+ +

+ +

]]> + + + +Busy week @ Zimbra + +2006-11-07T00:08:50Z +2006-11-06T23:53:34Z +tag:www.zimbra.com,2006:/blog//1.126 +2006-11-06T23:53:34Z +Several events going on this week. Satish, John and Greg will be at VMWorld where Satish will take part in tomorrow's keynote. Later this week at ISPCon I'll be on a panel - What the Web 2.0?. Last but not... + +Kevin +www.zimbra.comkevinh@zimbra.com +Kevin Henrikson +Several events going on this week. Satish, John and Greg will be at VMWorld where Satish will take part in tomorrow's keynote. Later this week at ISPCon I'll be on a panel - What the Web 2.0?. Last but not least Satish will be back on the main stage at Web 2.0. For those who missed it last year; Zimbra launched at Web 2.0.

]]> + + + + +The Ajax Experience, Oct 23-25, Boston, MA + +2006-11-02T20:10:26Z +2006-10-29T19:08:04Z +tag:www.zimbra.com,2006:/blog//1.125 +2006-10-29T19:08:04Z +Below are random thoughts on three days in Boston at The Ajax Experience. I gave a talk titled Ajax in the Enterprise.... + +Conrad +cdamon@zimbra.com +Conrad Damon +Below are random thoughts on three days in Boston at
+The Ajax Experience. I gave a talk titled Ajax in the Enterprise.

]]> +... AOL was giving away T-shirts by the hundreds, in solid, bright colors with
+words like "Geek" or "2.0" on them. Some conferencegoers walked away with
+several, which wasn't discouraged - there seemed to be an endless supply. Every
+time I walked by the booth I wanted ("want" isn't the right word, it's more the
+primal lust for free stuff) to grab a shirt or two, when the last thing in the
+world I need is more T-shirts. Eight years ago when I moved I gave 99 shirts,
+most of them unworn, to the Salvation Army. These were garish and ugly, and
+trying in AOL's typically disingenuous way to plug into geek culture. Plus,
+there's the associated guilt of all those unopened CDs taking up landfill space.
+Hence the little cartoon angel on my right shoulder. Of course, the little
+cartoon devil on my left shoulder made himself heard: "Dude, it's FREE! Don't be
+such a Herb! If you don't take one, someone else will get it. You've earned it.
+And dude: it's FREE!" So it went, and every walk past the AOL booth became an
+exercise in self-denial of something I didn't actually want at all, and the
+thimbleful of pride I felt on passing by empty-handed made me feel like some sort of
+lame modern-day ascetic.

+ +

... speaking of AOL (I don't mean to pick on AOL, even the newly warm and fuzzy
+AOL, but they make it really easy), one of their minions gave a keynote during
+which he screened a movie where they went up to people on the street or in the
+grocery store and asked them what they thought "Ajax" was. And OH MY GAWD (the
+voice here should be Dr Cox from Scrubs), they thought it was a cleanser! What a
+bunch of losers!

+ +

Crikey.

+ +

... really regret my get-out-of-Dodge trip planning, which made me miss Brendan
+Eich's closing keynote on Javascript 2.

+ +

... "stack" is the new "solution".

+ +

... Selenium, a product for doing functional client
+testing in an Ajax environment, got a lot of buzz. Our QA team is looking into it. They've had to
+pound on Mercury's QTP pretty hard to get it to work with our client, and I'm hoping
+Selenium will be way more straightforward.

+ +

... the booths from some of the sponsors such as Google, Sun, and Ask were more
+focused on recruiting than on demos, always a sign of a technology on its way up.

+ +

... after the experts' panel on Monday night, I headed to the hotel bar and met
+up with the Netflix crew. As a longtime Netflix member, I couldn't resist rattling on
+about what I liked and disliked about their site and service. Not only did they
+listen - brave souls - they bought me beer. The more beer I had in me, the more
+clever and insightful I became, and I think they caught on to that.

+ +

The Netflix UI makes for a great case study in how going from HTML to Ajax
+can improve the user experience.

+ +

... there is a bewildering array of Ajax toolkits out there, and at least two of
+the presentations were overviews of frameworks. The space has exploded, and
+sooner rather than later, it will contract. Documentation, often overlooked,
+will be key to adoption. It's hard to bet against
+Dojo, with its breadth, careful design, and technical impressiveness.
+I heard good things about jQuery, and YUI looks clean. For all-Java shops there's
+GWT, and possibly DWR.

+ +

... My ad hoc plan of attack, and reviews, in order of attendance:

+ +

Leveraging Ajax for Enterprise Application Development - mostly good
+content, somewhat awkwardly delivered. Best part was practical tips for shops
+coming up to speed on Ajax.

+ +

Javascript Exposed: There's a Real Programming Language in There (Pt 1), by
+Glenn Vanderburg - had intended to go to Mahemoff's talk on design patterns, but
+he didn't make it to the conference. Glenn's an engaging presenter, which eased
+the fact that it was mostly a tutorial of what you'd find in the O'Reilly book.
+Glenn did a good job of focusing on important bits of the language that are
+often glossed, and I really liked his lists of what he believes the language
+designers got right and wrong.

+ +

Ruining the User Experience, by Aaron Gustafson - the scope of this presentation
+was smaller than I had hoped. From the summary, I thought it would cover UI
+idioms that have been made possible by Ajax but which don't improve the user
+experience, but it was almost all about what to do when Javascript is
+disabled.

+ +

Frameworks Guide, by Nathaniel Schutta - came to this one as a refugee from a
+TIBCO-centric talk on building desktop-like apps in Ajax. It was good to get an
+overview, delivered capably and neutrally, since having developed our own
+toolkit I'm not familiar with others.

+ +

Intro to Dojo / Dojo in Depth, by Alex Russell - Dojo looks pretty awesome, and
+Alex is super-smart. Dojo obviously goes beyond Ajax, and even within Ajax it
+offers much more than widgets and neat effects. Their event system, the new
+SVG/VML support, and XhrIframeRequest were highlights. I'll be looking soon into
+using its package system to leverage deferred loading of ZCS components.

+ +

IE7: From Ajax to RSS and More: How to Take Full Advantage, by Chris Wilson -
+acutally: quite: interesting. IE7 will make app developers very happy, and app
+maintainers very unhappy. It's really frightening to think of the untold numbers
+of websites out there that rely on the many ways in which IE6 is broken (insert
+truism about reaping what you sow). As much grief as they deservedly get, MS
+appears to be committing to standards as far as its browser goes (thank you,
+market forces). Best news for me is that they fixed the garbage collector, so
+memory no longer leaks at the drop of a hat. They also fixed the SELECT
+element's behavior with regard to z-index, the gzip caching problem, and untold
+CSS bugs.

+ +

JSON: The X in Ajax, by Douglas Crockford - the case for JSON is a strong one,
+as XML is often overkill for shuttling data around. I love its simplicity and
+compactness. Of particular interest: JSONRequest and a proposed MODULE tag to
+address cross-domain security issues. Near the end there was an odd moment when
+John Resig (jQuery) posed a reasonable-sounding question about whether JSON
+performance scales well across large datasets when compared with XML, and the
+immediate response was "Next question." Not sure what to conclude from that.

+ +

Designing for Ajax, by Bill Scott - bailed on a performance talk that turned out
+to be Gomez-centric and came here. Great presentation. Bill used Yahoo as well
+as other sites to point out good and bad Ajax-enabled interaction patterns.
+Makes me want to check out the Yahoo design patterns library.

+ +

Case Study: Building Great UI, the Netflix Way, by Sean Kane - everyone loves
+Hypnotoad, I mean Netflix. What was interesting here (aside from the obvious
+fascination with the service) was how extensively they test in UI labs with
+regular folks before rolling out changes, often trying out several possible
+versions of a UI feature. It would be nice if we could eventually get real-world
+data like that.

]]> + + + +Firefox 2 vs IE 7 + +2006-10-25T23:56:26Z +2006-10-25T21:33:29Z +tag:www.zimbra.com,2006:/blog//1.124 +2006-10-25T21:33:29Z +Last week I posted an entry comparing IE 7 with Firefox 1.5 and the venerable IE 6. Lot's of folks have since asked for Firefox 2 to be added to the mix. The reason we didn't initially include Firefox 2... + +Ross +ross@zimbra.com +Ross Dargahi +Last week I posted an entry comparing IE 7 with Firefox 1.5 and the venerable IE 6. Lot's of folks have since asked for Firefox 2 to be added to the mix. The reason we didn't initially include Firefox 2 is because it was not at the time officially released and so we felt it unfair for it to be included.

]]> +The graph below shows the cumulative time it took for IE 7 and Firefox 2 to execute the Zimbra Web Client (ZWC) peformance tests at various dates leading up to the final release of each browser. As can be seen, both IE and Firefox showed improvement in their final release, and so we think leaving Firefox 2 out of last week's tests was indeed the fair thing to do.

+ +


+trend.jpg

+ +

So now that Firefox 2 has been officially released, how does if fare against IE 7?

+ +

We ran each browser over a common set of Zimbra Web Client (ZWC) operations such as logging in, viewing messages, navigating around various folders, changing options, viewing contacts, and performing various calendar operations. As the graph below shows, Firefox 2 beat out IE 7 in just about every operation - sometimes by significant margins.

+ +


+FF2vsIE7.jpg

+ +

We also tested Firefox 2 vs Firefox 1.5. As seen below, Firefox 2 has not made substantial performance improvements over Firefox 1.5, and has certainly not shown the same order of gain as IE 7 has over IE6.

+ +


+FF2vsFF15.jpg

+ +

I think the net result is that for highly JavaScript intensive AJAX applications such as the ZWC, Firefox is still the winner by quite a wide margin. Of course your mileage will vary depending on the type and footprint of your client.

+ +

I would like to end by saying that we are able to present this data thanks to lots of hard work by Raja Rao of the Zimbra QA department who has spent many long hours building our AJAX client testing framework, and executing the performance tests against the various browsers.

]]> + + + +IE 7 vs IE 6 + +2006-10-19T18:12:50Z +2006-10-19T18:13:00Z +tag:www.zimbra.com,2006:/blog//1.123 +2006-10-19T18:13:00Z +Back in April I wrote an entry complaining about IE's performance as a Web 2.0 platform: "From a Web 2.0 application developers perspective (developers who use a lot of JavaScript and DOM manipulation), IE 6 is plagued by a number... + +Ross +ross@zimbra.com +Ross Dargahi +Back in April I wrote an entry complaining about IE's performance as a Web 2.0 platform:

+ +

"From a Web 2.0 application developers perspective (developers who use a lot of JavaScript and DOM manipulation), IE 6 is plagued by a number of well known problems such as its ability to readily leak memory. Regrettably, Microsoft's next release of Internet Explorer, IE 7, does little to resolve these issues."

+ +

I am happy to say that I was wrong.

]]> +Microsoft's IE team has clearly been hard at work on improving their browser's memory management and JavaScript performance. IE 7 has made some significant leaps forward based on some initial in house testing here at Zimbra. We are in general observing about a 2x performance improvement with IE 7 vs IE 6 when using the Zimbra Web Client (ZWC).

+ +

As is well documented, IE 6 is notoriously bad at leaking memory, particularly due to circular references that include COM objects. The good news is that our tests indicate that this problem has been solved in IE 7. While in our test profile, it appears to consume more memory than Firefox, IE 7 seems to have solved the horrendous memory leaks exhibited in IE 6.

+ +

We also looked at the performance of Firefox, IE 6, and IE 7 over a set of common ZWC operations such as logging in, viewing messages, navigating around various folders, viewing contacts, and performing various calendar operations. The graph below shows the relative performance of each browser against the other:

+ +

browserperf.jpg

+ +

Again we see that across just about every operation, IE 7 performs better than IE 6; however, for the most part Firefox still beats out IE 7. When we looked at the sum total time it takes for all operations to be performed (admittedly a coarse grained metric), we noticed that IE 7 was about twice as fast as IE 6; however, Firefox was more than twice as fast as IE 7 and about four times faster than IE 6.

+ +

In conclusion, IE 7 has made some quite significant improvements over IE 6, both in terms of performance and memory management; however, there is still room to improve - particularly against Firefox, a challenge I hope the IE team will be taking up.

]]> + + + +Zimbra Collaboration Suite 4.0.3 Released + +2006-10-17T23:09:27Z +2006-10-17T23:09:23Z +tag:www.zimbra.com,2006:/blog//1.122 +2006-10-17T23:09:23Z +ZCS 4.0.3 includes fixes for 55 bugs and enhancements. It has significant improvements in calendar behavior and fixes a bug in Trash folder viewing that was troubling many folks. It also includes upgrade speed improvements. This allows the upgrade to... + +Kevin +www.zimbra.comkevinh@zimbra.com +Kevin Henrikson +ZCS 4.0.3 includes fixes for 55 bugs and enhancements. It has significant improvements in calendar behavior and fixes a bug in Trash folder viewing that was troubling many folks. It also includes upgrade speed improvements. This allows the upgrade to take much better advantage of installs that have multiple disks available to MySQL.

+ +

Zimbra - Forums - Zimbra Collaboration Suite 4.0.3 Released

+ +

]]> + + + + +Thoughts on Office 2.0 (Reprise) + +2006-10-21T20:01:05Z +2006-10-17T11:43:14Z +tag:www.zimbra.com,2006:/blog//1.121 +2006-10-17T11:43:14Z +(FYI: I've made some enhancements/corrections based on Zimbra's participation at the Office 2.0 Conference; pointer below. May or may not be worth a quick reread.) Yes, the "2.0" hype is getting out of hand. However, just as with Web 2.0,... + +Scott +www.zimbra.comscott.dietzen@zimbra.com +Scott Dietzen +(FYI: I've made some enhancements/corrections based on Zimbra's participation at the Office 2.0 Conference; pointer below. May or may not be worth a quick reread.)

+ +

Yes, the "2.0" hype is getting out of hand. However, just as with Web 2.0, the technology evolution we are participating in is sufficent to at least justify the discussion. So while I am still dubious about the Office 2.0 moniker, there is no doubt that the Web authoring, sharing, and collaboration technologies under the Web 2.0 umbrella are allowing us to do many of the things we used to do within proprietary Office 1.0 desktop applications, and to do so from any browser on the net. So before you dismiss Office 2.0 as yet another buzz word du jour, please consider some (modest) over-generalizations:

]]> +Office 1.0 Users: Power users (information workers/professionals)
+Office 2.0 Users: "All hands" (most everyone who browses)

+ +

1.0 Model: Client-centric (desktop applications)
+2.0 Model: Network-centric (web applications)

+ +

1.0 Sharing (in the small): Pass by value (Email), pass by reference (Public folders)
+2.0 Sharing (in the large): Adds the ability to use the Internet to pass by value (Email, VoIP, IM, ...) and (effectively) by reference (XHTML pages/hyperlinks, Wiki, Blogs, iCalendar/CalDAV, iTasks, WebDAV, ...), all with access control

+ +

1.0 Navigation (sans meta-data): Folders
+2.0 Navigation (with meta-data): Hyperlinks, indexing & search, tagging, mash-ups …

+ +

1.0 Editing: Via proprietary desktop applications; WYSIWYG with change tracking
+2.0 Editing: From any browser; WYSIWYG (via Ajax authoring) with versioning and history

+ +

1.0 Data types: Proprietary
+2.0 Data types: Open (XHMTL, ODF, microformats, XML such as via Service-Oriented Architecture/SOA, REST, SOAP, etc.)

+ +

1.0 Content: Relatively static, with intra-desktop dynamic components
+2.0 Content: More dynamic (including web application-generated content, SOA mash-ups, …)

+ +

1.0 Multi-document: Object Linking & Embedding (OLE), Bonobo, …
+2.0 Multi-document: Hyperlinks, Ajax Linking & Embedding (ALE), mash-ups, ...

+ +

(No doubt the above takes a rather expansive view of Office 2.0, but then again Office 1.0 arguably covered most all computer-assisted authoring of content. Please also note: The above content would have proved substantially more compelling in an HTML table authored, say, with a WYSIWYG Ajax editor, like that included within the Zimbra Documents applications.)

+ +

All this is not to say that Office 2.0 can or should supercede Office 1.0---Zimbra spreadsheets, for example, will not support pivot tables any time soon. I believe our goal should not be to reproduce Office 1.0 functionality on a Web 2.0 platform, but rather to realize an easier to use (a.k.a. less complex) collaborative authoring and sharing model that scales with the Internet. Office 2.0 users should be able to (1) author content from anywhere; (2) appropriately reuse and adapt (mash up) content (both static and dynamic) already published on the Internet; and (3) securely collaborate with others in whatever ad hoc fashion best meets their needs. The fun with "Office 2.0" is that thanks to the maturing of the underlying Web 2.0 technologies and near universal success of the Internet, this vision is close to realization.

+ +

One thing I'm not yet happy with is that the above description does not draw a very compelling line between Web 2.0 and Office 2.0. Some technologies are more obvious: for example, Ajax, RSS, and SOA/XML fit under Web 2.0, while Ajax authoring and ALE arguably fit more naturally under Office 2.0. Given the emphesis on collaboration and authoring inherent in the Web 2.0 definition, I think these two potential categories are going to be tough to keep separate. After all, both Office 1.0 and Web 2.0 are about authoring rich content---the difference is that the former is focused on the desktop and "sharing in the small", while the latter is targeting the network and "sharing in the large". Office 2.0 then may merely mean leveraging Web 2.0 technologies to do many/most (?) of the things we used to do in Office 1.0.

+ +

(Some of this thinking came out our our panel session at the Office 2.0 Conference in San Francisco, and our Web 2.0 Kongress session in Germany the day before. Just doing our bit to keep the airlines in the black :-).)

]]> + + + +Zimbra Collaboration Suite 4.0 Webinar + +2006-10-05T02:35:45Z +2006-10-01T23:07:51Z +tag:www.zimbra.com,2006:/blog//1.120 +2006-10-01T23:07:51Z +Zimbra Collaboration Suite 4.0 Webinar When: Thurs, October 5th at 10am PST. Length: 60 minutes. Subject: Modern Collaboration with Zimbra Collaboration Suite (ZCS) 4.0 Overview: Fueled by demand for better productivity, the web is exploding as the primary communication medium... + +Kevin +www.zimbra.comkevinh@zimbra.com +Kevin Henrikson +Zimbra Collaboration Suite 4.0 Webinar
+When:

+ +

Thurs, October 5th at 10am PST. Length: 60 minutes.

+ +

Subject: Modern Collaboration with Zimbra Collaboration Suite (ZCS) 4.0

+ +

Overview:
+Fueled by demand for better productivity, the web is exploding as the primary communication medium for the modern organization.

+ +

ZCS leads the way, providing powerful next-generation messaging and collaboration.

+ +

Join our CTO Scott Dietzen for this free live webinar to see:

+ +

* How ZCS 4.0 is the right solution for today's collaboration demands
+ * Discuss and demo features such as Zimbra Documents, Admin UI, Zimlets, Mobile device sync, Active Directory integration and more…
+ * Why ZCS 4.0 enables organizations to realize the true benefits of an innovative and cost-effective collaboration solution.
+ * Plus live Q & A

+ +

Sign up:

+ +

Please register; space is limited!

]]> + + + + +Zimbra 4.0.2 released, Ubuntu preview release + +2006-09-26T06:11:30Z +2006-09-26T05:48:24Z +tag:www.zimbra.com,2006:/blog//1.119 +2006-09-26T05:48:24Z +We released Zimbra 4.0.2 today and there were a few extras that came along for the ride. First off the Fedora Core 5 build is now GA. We also added a new developer/preview release on Ubuntu. This has been a... + +Kevin +www.zimbra.comkevinh@zimbra.com +Kevin Henrikson +We released Zimbra 4.0.2 today and there were a few extras that came along for the ride. First off the Fedora Core 5 build is now GA. We also added a new developer/preview release on Ubuntu. This has been a popular hack in our forums for sometime.

+ +

Here's a sample of some of the other changes/fixes in 4.0.2:

+ +

- perf improvements for IMAP (new MySQL indexes)
+- > 2GB support in the Zimbra Outlook Connector
+- i18n and some l10n for the Zimbra Outlook Connector
+- disabling AS/AV causes mail deferral
+- cursor fails to appear in Firefox
+- mailbox quota page does not contain any entries
+- several all day event and timezone bugs fixed

]]> + + + + +Look Ma, No Mouse: Keyboard Navigation and Shortcuts in the Zimbra Collaboration Suite and The Kabuki Ajax Toolkit + +2006-09-13T07:28:26Z +2006-09-13T07:25:00Z +tag:www.zimbra.com,2006:/blog//1.118 +2006-09-13T07:25:00Z +Keyboard shortcuts and navigation are indispensable time savers for an application's frequent and power users. Who among us has not quickly learned the keyboard shortcuts for performing common tasks within an application that we use regularly? Unfortunately, one of the... + +Ross +ross@zimbra.com +Ross Dargahi +Keyboard shortcuts and navigation are indispensable time savers for an application's frequent and power users. Who among us has not quickly learned the keyboard shortcuts for performing common tasks within an application that we use regularly?

+ +

Unfortunately, one of the more common complaints against web-based applications is that they are, in many instances, lacking when it comes to supporting keyboard shortcuts and navigation. Frankly, the lack of keyboard support (both shortcuts and navigation) is something that has annoyed me about the Zimbra Collaboration Suite (ZCS), and it is something that I have been wanting to add to both Kabuki (the Zimbra Ajax Toolkit) and the ZCS; however, I didn't want to just stuff in some basic keyboard shortcuts and call it a day. Instead, I wanted to have a go at implementing the same level of keyboard support that most traditional UI toolkits and desktop applications support. This actually turned out to involve quite a bit of work - for example, since only input elements may have focus (in most browsers) we needed to simulate and track focus for toolkit components which frequently have no native input element associated with them - but at the end of the day, I think it was worth the effort.

]]> +So the good news is that Kabuki now provides a pretty rich keyboard model that in many ways approximates the level of support found in more traditional UI toolkits. Specifically, this includes support for a canonical focus model, customizable key bindings in UI widgets (not all of them just yet), as well as full support for tab group hierarchies for navigating native and toolkit visual components in an orderly fashion via the tab and arrow keys. Conrad (one of Zimbra's lead Ajax architects), took this work to the next level by implementing keyboard navigation and shortcuts throughout the ZCS and by improving the framework itself. As a result the ZCS now has significant keyboard support in version 4.0, about 80% coverage at the moment, and we are working towards making that even higher. Future work also includes normalized mappings among browsers (very high on our list), I18N support, and supporting custom user-defined bindings.

+ +

The bottom line is that the ZCS now supports some pretty spiffy keyboard actions (over 100 of them) including:
+

  • Navigating among the various ZCS apps
    +
  • Navigation and selection within a list of items
    +
  • Composing and sending an email message
    +
  • Creating calendar appointments
    +
  • Switching among calendar views
    +
  • Creating new tags, folders, calendars, etc
    +
  • Popping up the Zimbra Assistant
    +
  • Changing views
    +
  • Popping up, interacting with, and dismissing context menus
    +

+ +

You can find a more complete list of supported keyboard events on the Zimbra Wiki

+ +

Now onto some of the more technical details on Zimbra's keyboard support.

+ +

The keyboard management infrastructure is implemented in the DHTML Widget Toolkit (DWT), which is the Kabuki Ajax toolkit's UI framework. DWT consists of a component model, numerous widgets, an event model, drag and drop infrastructure, and now a keyboard shortcut and navigation model. DWT is loosely modeled after SWT. There are several elements that compose DWT's keyboard management framework:

+ +

Key Maps

+A key map is a set of key bindings. A key binding maps a key sequence to an action. For example, I may decide that "Ctrl+U" marks an email message as unread, or I may decide that a multi-key sequence such as "Ctrl+N" followed by the letter "M" will create a new mail message (Note that by default, there is a 750ms timeout between keys for a multiple-key sequence, though this is configurable via the DwtKeyboardMgr class described later). + +

DwtKeyMap is the base class for key maps and provides bindings for DWT widgets. Below is a snippet from DwtKeyMap's constructor showing the key bindings for some of the widgets. Note how key sequences bind to the symbolic constants representing keyboard actions:

+ +
+function DwtKeyMap() {
+    [snip...]
+    this._map["DwtDialog"] = {
+        "Enter":  DwtKeyMap.ENTER,
+        "Esc":    DwtKeyMap.CANCEL
+    };
+    this._map["DwtButton"] = {
+        "Enter":        DwtKeyMap.SELECT_CURRENT,
+        "ArrowDown":    DwtKeyMap.SELECT_SUBMENU
+    };
+    this._map["DwtListView"] = {
+        "Space":             DwtKeyMap.SELECT_CURRENT,
+        "Ctrl+Space":        DwtKeyMap.ADD_SELECT_CURRENT,
+        "Ctrl+`":            DwtKeyMap.ADD_SELECT_CURRENT, // Mac FF
+        "ArrowDown":         DwtKeyMap.SELECT_NEXT,
+        "Shift+ArrowDown":   DwtKeyMap.ADD_SELECT_NEXT,
+        "Ctrl+ArrowDown":    DwtKeyMap.NEXT,
+        "ArrowUp":           DwtKeyMap.SELECT_PREV,
+        "Shift+ArrowUp":     DwtKeyMap.ADD_SELECT_PREV,
+        "Ctrl+ArrowUp":      DwtKeyMap.PREV,
+        "Ctrl+A":            DwtKeyMap.SELECT_ALL,
+        "Home":              DwtKeyMap.SELECT_FIRST,
+        "End":               DwtKeyMap.SELECT_LAST,
+        "Enter":             DwtKeyMap.DBLCLICK,
+        "Comma":             DwtKeyMap.ACTION,
+        "Shift+Comma":       DwtKeyMap.ACTION,
+        "Ctrl+Enter":        DwtKeyMap.ACTION,
+        "Ctrl+M":            DwtKeyMap.ACTION  // Mac FF
+    };
+    this._map["DwtMenu"] = {
+        "Esc":          DwtKeyMap.CANCEL,
+        "Enter":        DwtKeyMap.SELECT_CURRENT,   
+        "ArrowDown":    DwtKeyMap.SELECT_NEXT,
+        "ArrowUp":      DwtKeyMap.SELECT_PREV,
+        "ArrowLeft":    DwtKeyMap.SELECT_PARENTMENU,
+        "ArrowRight":   DwtKeyMap.SELECT_SUBMENU
+    };
+    [snip...]
+};
+
+ +

Applications may inherit from the above class and add their own maps or override existing ones (for example when subclassing widgets). Note that component and application authors don't need to worry about key sequences, rather they just need to implement the actions that their components support. The keyboard management framework takes care of handling the mapping from key sequences to actions. Once a key sequence has been mapped to an action, the action is passed to the handleKeyAction() method defined by the component (See the sections of DwtKeyboardMgr and DwtControl below for more details).

+ +

Decoupling key bindings and actions makes it easy to change the key binding for a given action, or to allow multiple key bindings for that action. Key maps may inherit (including multiply) from other key maps. This allows for extensions as well as application-wide (or default) key maps.

+ +

The sample code below shows a portion of the ZCS's key map. Notice how the ZmMailListController inherits from the Global key map.

+ +
+function ZmKeyMap() {
+    this._map["Global"] = {   
+        "`":       ZmKeyMap.ASSISTANT,
+        "Shift+`": ZmKeyMap.ASSISTANT,
+        [snip...]
+    }   
+    this._map["ZmMailListController"] = {
+        "INHERIT":  "Global",
+        "R":       ZmKeyMap.REPLY,
+        "A":       ZmKeyMap.REPLY_ALL,
+        "R,S":     ZmKeyMap.REPLY,
+        "R,A":     ZmKeyMap.REPLY_ALL,
+        [snip...]
+    }
+    [snip...]
+}
+
+ +

Key map entries may consist of:

+ +
  • Single keys e.g. "Enter" or "M" +
  • Single keys plus one or more modifiers e.g. "Ctrl+M" or "Ctrl+Shift+M" +
  • Multiple key sequences e.g "M,U" or "M,U,A" +
  • Multiple key sequences plus modifiers e.g. "Shift+M, U" or "Shift+M, Shift+U, A" +
+ +

We are currently working on a serialization/deserialization interface so that key maps may be serialized to and deserialized from a textual representation. This will help in with localizations and custom/user defined keymaps, and will do away with the need for the hash tables shown above.

+ +

Tab Groups

+ +

Tab groups permit the definition of a hierarchical keyboard navigation model. A tab group is a tree structure where the intermediate nodes in the tree are other tab groups and the leaf nodes are focusable components i.e. DWT widgets and/or focusable native HTML elements such as input fields. Tab groups represent the order in which components that the user sees on the screen are traversed via the keyboard. The tab group hierarchy (or tree) is traversed "in order" by the user pressing the tab key, or in reverse order when the user typically presses the shift key plus the tab key.

+ +

There is a special tab group called the root tab group. A root tab group has no parent and represents the keyboard navigation order for the components in a given application view. There can be multiple root tab groups within an application, e.g. an email message list view tag group, a calendar new appointment tab group, or a dialog tab group; however, only one root tab group may be active at any given time.

+ +

As will be described in the section on DwtKeyboardMgr, tab groups may be "pushed to" and "popped from" the tab group stack. For example, when a dialog is popped up, its corresponding tab group is pushed onto the tab group stack and becomes the active tab group while that dialog is activated. When the dialog is popped down, its tab group is also popped off the tab group stack bringing the underlying tab group (i.e. the one for the active view) back into play, so that the component that had focus prior to the dialog being activated will once again have focus.

+ +

Tab groups are implemented by the DwtTabGroup class. That class provides the API for manipulating tab groups. Here are some of the member methods:

+ +
  • addMember(index) - Adds a member to the tab group at index position, or at end if index is omitted +
  • addMemberBefore(member) - Adds a member to the tab group positioned before another member +
  • addMemberAfter(member) - Adds a member to the tab group positioned after another member +
  • blockDefaultHandling(block) - Blocks the default handler from being invoked for this tab group +
  • contains(member) - Checks to see if an item is a member of this tab group +
  • removeMember(member) - Removes a member +
  • replaceMember(old, new) - Replaces a member with another one +
  • newParent(newParent) - Sets a new parent for this tab group +
  • getFocusMember() - Gets the current focus member +
  • setFocusMember(member) - Sets the current focus member +
  • getNextFocusMember() - Gets the next focus member +
  • getPrevFocusMember() - Gets the previous focus member +
  • resetFocusMember() - Resets the focus member to the first available member +
+ +

DwtKeyboardMgr

+ +

DwtKeyboardMgr is the engine that drives the keyboard management framework. It is responsible for intercepting key events generated by the browser, mapping them to actions (via the registered keymaps), and then dispatching the action to the correct component. In addition, DwtKeyboardMgr is responsible for enforcing the tab order specified by the currently active tab group. Finally, this class also has the machinery that handles multi-key keymap entires by utilizing a timeout mechanism for resolving such sequences.

+ +

When dispatching actions, DwtKeyboardMgr will first try and resolve a key sequence with the component that has focus (be it a DWT widget or a native component such as an HTML input element). If the component does not have an action binding for a key sequence (an entry in its key map for the current key sequence), then DwtKeyboardMgr checks to see if a default handler has been pushed on its default handler stack (via the pushDefaultHandler method). If one has been pushed, then DwtKeyboardMgr will query it for the name of the keymap that should be used to resolve the key sequence to an action code. If an action code exists in the key map for the key sequence, then DwtKeyboardMgr will dispatch it to the default handler.

+ +

A default handler is analogous to the root tab group. It provides a context for key bindings that are not tied to a specific widget. In a way, the default handler can be thought of as providing a global context. For example, if a button has focus when the character Esc is typed, DwtKeyboardMgr will first give the button a chance to handle the event. If the button does not handle Esc (which is the case), then DwtKeyboardMgr hands the event to the current default handler. So far, there are only two default handlers used within ZCS: an application-level default handler and a dialog-level default handler.

+ +

A default handler must implement the following interface:

+ +
  • getKeymapNameToUse() - This method is called by DwtKeyboardMgr to get the name of the key map that should be used for resolving a key sequence. Of course this is application-specific and may change as the user navigates an application. For example, in the case of the ZCS, a different key map may in play for the calendar application as opposed to the email application. +
  • handleKeyAction(action) - Where the action formal parameter is the action constant bound to the key sequence in the key map. This method is where the real work gets done. Its implementation will perform the work necessary to complete the action. It will return true if it handled the action, or false if it did not. +
+ +

As previously mentioned, DwtKeyboardMgr is also responsible for enforcing the component tab ordering specified by the currently active root tab group - i.e. the one that is on top of the tab group stack. The way this works is that upon intercepting the tab key, DwtKeyboardMgr will call the DwtTabGroup's getNextFocusMember() method. This method returns the next focusable component in the tab group hierarchy (be it a DWT widget or a native HTML input field). DwtKeyboardMgr will then call the blur() method on the previously focused component, followed by calling the focus() method on the component returned by getNextFocusMember(). Note that I intentionally paralleled the native HTML input element focus() and blur() methods within DWT so there is a canonical way of managing the focus state of any UI component (native or DWT). The combination of DwtKeyboardMgr and DwtTabGroup handles all corner cases such as skipping over components that are not enabled (i.e. grayed out), as well as dealing with scenarios such as the currently focused component becoming disabled.

+ +

The following lists some of the more commonly used methods provided by DwtKeyboardMgr:

+ +
  • enable(enable) - Enables or disables keyboard event handling +
  • isEnabled() - Returns true if keyboard event handling is enabled, else returns false +
  • grabFocus(element) - Causes element to grab focus - where element is a DWT widget or an HTML input element +
  • pushDefaultHandler(hdlr) - Pushes a default handler onto the handler stack +
  • popDefaultHandler()- Pops the default handler off the top of the handler stack +
  • pushTabGroup(tabGroup) - Pushes a tab group onto the tab group stack and makes it the active tab group +
  • popTabGroup() - Pops the tab group that is on top of the tab group stack +
  • registerKeyMap(keyMap) - Registers a key map +
  • setKeyTimeout(timeout) - Sets the maximum time to allow between key presses for a multi-key key sequence +
  • setTabGroup(tabGroup) - Replaces the current tab group with the one provided +
+ +

DwtControl

+ +

DwtControl is the base DWT class from which all widgets ultimately inherit behaviour. DwtControl has a number of responsibilities including hooking into the drag and drop system, basic mouse event handling, and integration with the keyboard shortcut and navigation model.

+ +

DwtControl exports public focus() and blur() methods that parallel the native HTML input elements so that there is a canonical set of methods for setting and blurring focus across native and DWT elements. DwtControl also declares four methods that widget authors must implement in order to support keyboard management:

+ +
  • _focus() - This method is called when a control receives focus. Its implementation should provide visual feedback that the control has gained focus (e.g. by drawing a border around the component) +
  • _blur() - This method is called when a control loses focus. Its implementation should provide the visual feedback that the control has lost focus (e.g. by hiding the border around a control) +
  • handleKeyAction(actionCode) - This method is responsible for implementing supported actions. The keyboard framework passes in the actionCode associated with a key sequence in the control's keymap. This method returns true if the control handled the actionCode, else it returns false +
+ +

Using The Keyboard Framework in an Application

+ +

An application programmer wanting to use the keyboard management frameworks typically needs to perform the following steps:

+ +
  1. Create a key map class for the application that inherits from DwtKeyMap. Define any application and/or custom widget key maps in this class. +
  2. Implement one or more default handlers for the application should they be required. Recall that the default handler is called when a visual component does not have a action code binding for a key sequence. Depending on the complexity of the application, multiple handlers may be pushed and popped as the user interacts with the application. +
  3. Create any tab group(s) that may be required. Note that tab groups may be created and manipulated during the application lifecycle. +
  4. Instantiate DwtKeyboardMgr. +
  5. Register the application's key map with DwtKeyboardMgr via the registerKeyMap() method. +
  6. Push the currently applicable default handler via DwtKeyboardMgr's pushDefaultHdlr() method. +
  7. Push or set the current tab group via the pushTabGroup() or setTabGroup() method. +
]]> + + + +Securing Ajax + +2006-09-11T15:22:42Z +2006-09-09T18:45:46Z +tag:www.zimbra.com,2006:/blog//1.117 +2006-09-09T18:45:46Z +To continue the Zimbra blog series on Ajax (recent entries include Ajax innovation is about the server, Ajax optimization techniques (presented at OSCON), OpenAjax update, and Ajax's impact on scaling), we wanted to offer some general thoughts on securing Ajax... + +Scott +www.zimbra.comscott.dietzen@zimbra.com +Scott Dietzen +To continue the Zimbra blog series on Ajax (recent entries include Ajax innovation is about the server, Ajax optimization techniques (presented at OSCON), OpenAjax update, and Ajax's impact on scaling), we wanted to offer some general thoughts on securing Ajax applications gleaned, of course, from our Zimbra experience.

]]> +Ajax security advantages. Less often discussed than Ajax security concerns are inherent security advantages of Ajax clients:
+• Dynamic Ajax client download – Ajax client code is downloaded on demand from the trusted server after a particular user logs-in, automatically ensuring client and server versions are in-sync (for public computers, a shift re-load is better in that it overwrites any Ajax code from that website leftover in the browser cache).
+• No persistent client caching – An exposure with traditional web clients is that they cache HTML pages that can include user/application data on the client disk during normal operation. This can be a security vulnerability for access from public kiosks or other shared computers. Ajax applications like the Zimbra client cache no user data on disk.
+• Server-side control of intranet and Internet mash-ups – Zimlets and other Ajax mash-ups are precluded from accessing arbitrary services on the Internet (unless they open a new iFrame, which can be determined at server deployment time), and must instead (like Java applets) make all invocations back to the originating server (in our case, the Zimbra server). This means the Ajax server can act as a secure, proxy gateway for accessing intranet applications, and can govern which external web services (if any) are accessible for mash-up within the Ajax client.

+ +

Ajax security considerations. Subject to the additional precautions enumerated below, Ajax applications can be made as highly-secure as the web technologies upon which the Ajax model is based.

+ +

The most obvious security issue for Ajax applications is that the associated source code is inherently downloaded to the browser for interpretation. This is a concern for any application logic that contains intellectual property that the author does not want to share with the world: while obviscation and minimization (white space removal, shortening identifier) can certainly render JavaScript much harder to read (and debug), developers should consider Ajax applications to be like HTML in that others will be able to examine the fruits of your labor. The only real alternative is to either (1) limit log-in to the application to trusted users/partners (in this way only licensed/authorized users get to download the Ajax application logic); or else (2) keep closely-held algorithms on the server-side, and simply invoke them via web services from the Ajax client. All this is not an issue for the Zimbra Ajax Client, since it is, after all, open source.

+ +

Zimbra provides the following additional guarantees to further secure Zimbra deployments over even public networks, techniques that we beileve are broadly relevant for securing Ajax applications:
+• Use SSL/TLS (i.e., HTTPS) – In addition to protecting the privacy/integrity XML/JSON HTTP communications to/from the Ajax client, SSL/TLS encryption limits access to the Ajax source code itself to only those that have legitimate log-ins (as per above), since no-one snooping on the network can see the app. logic. Moreover, SSL/TLS protects the Ajax application (JavaScript, CSS, etc.) from potential security attacks while it is in route to the user's browser.
+• No server-side interpretation of JavaScript or other client-submitted code – Zimbra receives vanilla XML requests from the browser client that are validated and then processed by Zimbra server-side Java code. No JavaScript flows from client to server, and there is no server-side interpretation of any application data (e.g., message bodies). In fact, there is no JavaScript execution on the server period. This ensures that there is no way for even a hostile Ajax client with an authentication credentials to inject malicious code for execution on the server-side.
+• Limited or no client-side interpretation of JavaScript within user data – The Zimbra Ajax client is, of course, an Email application that runs within the confines of the web browser. There is an additional risk, then, to displaying the contents of rich HTML messages that themselves contain JavaScript, in that JavaScript within the message might somehow be able to make malicious calls to the Zimbra server (it is generally precluded from making invocations to other sites). Zimbra blocks any “risky” HTML, first on the server and then again (for extra protection) on the client. When a rich HTML message contains any suspect JavaScript, simply better to err on the side of caution. For most Ajax applications, simply maintaining a strict separation of code from data (and never interpretting JavaScript that is included within user data) protects against such attacks.
+• Benign URLs – All Zimbra’s GET-based REST and URL-based APIs are read-only and do not modify data. This ensures that a user (with pre-validated security credentials) cannot be fooled into clicking on a malicious link (that someone sends he or she in an email or posts on his/her external website) that would have harmful side-effects on that user's data. Again, this is broadly relevant for Ajax applications that potentially display clickable URLs in application data.
+• Mash-ups/Zimlet validation – Zimbra's mash-up architecture does provide the opportunity to introduce server-side Java code (most Zimlets run only on the client side), but the introduction of Zimlets requires server administration privileges. Zimbra recommends only deploying Zimlets that have been certified by Zimbra or else which have been vetted by your security architects internally. The key is to ensure that only trustworthy mash-ups can be deployed with your Ajax application, mash-ups that do not expose additional attack points for malicious users.

+ +

The end result is that while an attacker with appropriate security credentials (such as a user's password) could certainly damage that user's server-side data, there is no way for them to compromise other user's data or the server in general. (And, of course, that user could have any damged mailbox state restored to the point before the attack by a Zimbra administrator.)

+ +

Stronger network security can be afforded by additional technologies (such as VPNs, Smartcards, etc.), but that's our recipe in general for leveraging the benefits of Ajax without giving up the security your customers, partners, and business depend on. More detail on the Zimbra-specific approach can be found in the newly updated Zimbra Architecture Overivew (linked within our Community and Product Documentation).

+ +

As always, thanks for listening (particularly to my verbose posts).

]]> + + + +Some thoughts on Mobility and Web 2.0 + +2006-08-29T22:45:39Z +2006-08-29T19:50:57Z +tag:www.zimbra.com,2006:/blog//1.116 +2006-08-29T19:50:57Z +I had the pleasure of joining Motorola, SugarCRM, and Funambol on a panel at LinuxWorld regarding the future of mobility. The depressing bit was that we panelists admitted that we could have made almost identical points three years ago: (1)... + +Scott +www.zimbra.comscott.dietzen@zimbra.com +Scott Dietzen +I had the pleasure of joining Motorola, SugarCRM, and Funambol on a panel at LinuxWorld regarding the future of mobility. The depressing bit was that we panelists admitted that we could have made almost identical points three years ago: (1) the Web (1.0 more than 2.0) is coming soon to mobile devices, but the experience isn't entirely there yet; and (2) the challenge to extending applications for mobile devices continues to be exacerbated by innovation in device profiles (more on that below). However, the good news is (1) that a "smart phone" profile is converging---a profile that is likely the right target for non-consumer mobile applications; and (2) that "over the air" sync to the native Personal Information Management (PIM) software on mobile devices has gotten dramatically easier/cheaper, and provides exciting new opportunities for mobile application extension.

]]> +As an old Web hand, I'm no doubt biased, but I think the Web is a generally the right model for business application extension to mobile devices, simply because the Web does not require any a priori installation of client-side software. After all, if the Web is already the dominant model for B2C and B2B applications on PCs, then it is arguably an even better architectural fit for lower horsepower (CPU, memory) mobile devices. Web 2.0/Ajax clients seem like a natural fit too---Ajax is a zero client install and its client/server interaction model is actually a better fit for higher latency networks like those of the wireless carriers. The challenge is that rich Ajax applications (ones with mouse-overs, drag 'n drop, etc.) consume enough laptop CPU that they are still out of the computational reach of most smart phones/PDAs, let alone basic telephones.

+ +

The alternative application model to the Web (I include WML/HTTP under the Web architecture) is of course more traditional fat client applications---such as those programmed for J2ME, Windows Mobile, Symbian, Palm, or mobile Linux. Fat client app's are ideal for PIM (email, SMS, calendaring, contacts, tasks), games, and other code that handset manufactures or the carriers are willing to preinstall, but a tougher sell for non-expert business and consumer end-user installation.

+ +

However, there is yet another approach that we proposed. It is particularly relevant for applications that can be surfaced via PIM software, such as your customer contacts from your CRM system, your travel itinerary from your procurement application, an urgent notification (via SMS), or even an email request to visit a particular URL. Such items can be submitted to a server like the Zimbra Collaboration Suite (ZCS), and then delivered to the mobile device via "over the air" sync. Zimbra Mobile, for example, can sync contacts, appointments, and messages to Nokia, Motorola, Samsung, Treo, and Blackberry smart phones, and both intranet and Internet applications can securely export to Zimbra over open/standard protocols. Putting the two together allows Web-enabled applications to deliver PIM-oriented data all the way to the mobile device.

+ +

So for applications that can be naturally surfaced via the native mobile PIM, there are now easier/cheaper options for mobile extension. For those business applications that have no such easy fit with PIM, I'm afraid you must still weigh the classic Web versus fat client architectural trade-off. In either case, I think that choosing the smart phone/PDA as the target profile makes more sense because of their relative consistency (screen size, scroll-to-click, J2ME vs. Windows Mobile platform), at least when compared with targeting the continuing stream of ever more compact, ever more personalized mobile phones.

]]> + + + +Open source and IP ownership + +2006-08-16T15:29:47Z +2006-08-15T16:58:03Z +tag:www.zimbra.com,2006:/blog//1.114 +2006-08-15T16:58:03Z +I got myself in a small bit of trouble recently talking about open source IP ownership when I should have been talking about the cool new collaboration and mobile features in the 4.0 release of the Zimbra Collaboration Suite. (Nothing... + +Scott +www.zimbra.comscott.dietzen@zimbra.com +Scott Dietzen +I got myself in a small bit of trouble recently talking about open source IP ownership when I should have been talking about the cool new collaboration and mobile features in the 4.0 release of the Zimbra Collaboration Suite. (Nothing like a developer coming by your cube and saying "You said what?") While I didn't do such a good job at the time, the underlying point is an important one, so I'm going to give it another shot ...

]]> +It is increasingly common practice in open source communities to insist upon a single organization owning the IP rights for a particular project. For example, the Apache and Free Software Foundations do this as well as private firms like Zimbra. The primary goal of IP ownership is to better guarantee "squeaky clean" IP (that is, that all contributed code is unencumbered by any hidden IP rights) for the benefit of the community as well as for customers. This also ensures that open source licensing upgrade decisions can be made for future releases of the open source license itself---without an organizational owner, projects can effectively get locked to a particular version of a license because there is no easy way to get all of the IP owners together to make a decision about upgrading.

+ +

The grief came in particular from my drawing parallels between Zimbra---a for-profit company---with more altruistic non-profit organizations like Apache and FSF regarding IP ownership. No doubt there are clear differences between for-profits and non-profits that the prospective community members have every right to consider, but I think in terms of IP ownership there is more in common than different.

+ +

For a potential community member, the most important thing is the long-term guarantee of their freedoms: (1) Open source rights (granted under the open source software license) to use the product in perpetuity for free, to produce and redistribute any derivative works thereof for free, and so on; and (2) rights to do whatever they may see fit in perpetuity for any of their own contributions that they made in good faith to the project. (The good contribution agreements grant contributors back all of their rights except those that could interfere with the community, such as the right to withdraw their contribution in the future, the right to charge the community patent royalties down the road, etc. For example, Zimbra's Contributor Agreement can be found here. For another take, check out Dojo, one of our Open Ajax Alliance partners. ) This practice seems to me to strike the right balance between preserving individual freedoms without sacrificing the freedoms of the community as a whole.

+ +

Both non-profit and for-profit open source organizations equally guarantee these freedoms to their communities, the difference being that the for-profit ones (like Zimbra) also strive to sell optional value-added services on the side, much of the proceeds of which then funds the further development of the open source software.

]]> + + + \ No newline at end of file diff --git a/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/images/locale.png b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/images/locale.png new file mode 100644 index 0000000000..0dfece4d3f Binary files /dev/null and b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/images/locale.png differ diff --git a/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/proxy/proxy.php b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/proxy/proxy.php new file mode 100644 index 0000000000..71853e9b86 --- /dev/null +++ b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/resource/proxy/proxy.php @@ -0,0 +1,60 @@ + \ No newline at end of file diff --git a/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/translation/C.po b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/translation/C.po new file mode 100644 index 0000000000..fc408105a1 --- /dev/null +++ b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/translation/C.po @@ -0,0 +1,93 @@ +# Default translation +# +msgid "" +msgstr "" +"Project-Id-Version: qooxdoo feedreader\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2007-01-26 12:52+0100\n" +"PO-Revision-Date: 2006-12-19 16:54+0100\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: source/class/feedreader/Application.js:133 +msgid "reloading ..." +msgstr "" + +#: source/class/feedreader/Application.js:138 +msgid "qooxdoo feed reader." +msgstr "" + +#: source/class/feedreader/Application.js:143 +msgid "Add feed" +msgid_plural "Add feeds" +msgstr[0] "" +msgstr[1] "" + +#: source/class/feedreader/Application.js:144 +msgid "Remove feed" +msgstr "" + +#: source/class/feedreader/Application.js:147 +msgid "Reload" +msgstr "" + +#: source/class/feedreader/Application.js:149 +msgid "(%1) Reload the feeds." +msgstr "" + +#: source/class/feedreader/Application.js:156 +#: source/class/feedreader/Application.js:158 +msgid "English" +msgstr "" + +#: source/class/feedreader/Application.js:157 +msgid "German" +msgstr "" + +#: source/class/feedreader/Application.js:159 +msgid "Turkish" +msgstr "" + +#: source/class/feedreader/Application.js:160 +msgid "Italian" +msgstr "" + +#: source/class/feedreader/Application.js:161 +msgid "Spanish" +msgstr "" + +#: source/class/feedreader/Application.js:162 +msgid "Swedish" +msgstr "" + +#: source/class/feedreader/Application.js:163 +msgid "Russian" +msgstr "" + +#: source/class/feedreader/Application.js:186 +msgid "Help" +msgstr "" + +#: source/class/feedreader/Application.js:194 +msgid "News feeds" +msgstr "" + +#: source/class/feedreader/Application.js:215 +msgid "Subject" +msgstr "" + +#: source/class/feedreader/Application.js:216 +msgid "Sender" +msgstr "" + +#: source/class/feedreader/Application.js:217 +msgid "Date" +msgstr "" + +#: source/class/feedreader/ArticleView.js:79 +msgid "read more ..." +msgstr "" diff --git a/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/translation/de.po b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/translation/de.po new file mode 100644 index 0000000000..099f9855d4 --- /dev/null +++ b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/translation/de.po @@ -0,0 +1,95 @@ +# German translation +# +msgid "" +msgstr "" +"Project-Id-Version: qooxdoo feedreader\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2007-01-26 12:52+0100\n" +"PO-Revision-Date: 2006-12-22 09:59+0100\n" +"Last-Translator: Fabian Jakobs \n" +"Language-Team: \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"X-Generator: KBabel 1.11.4\n" + +#: source/class/feedreader/Application.js:133 +#, fuzzy +msgid "reloading ..." +msgstr "aktualisieren ..." + +#: source/class/feedreader/Application.js:138 +msgid "qooxdoo feed reader." +msgstr "\"qooxdoo\" feed reader" + +#: source/class/feedreader/Application.js:143 +msgid "Add feed" +msgid_plural "Add feeds" +msgstr[0] "Feed hinzufügen" +msgstr[1] "Feeds hinzufügen" + +#: source/class/feedreader/Application.js:144 +msgid "Remove feed" +msgstr "Feed löschen" + +#: source/class/feedreader/Application.js:147 +msgid "Reload" +msgstr "Aktualisieren" + +#: source/class/feedreader/Application.js:149 +msgid "(%1) Reload the feeds." +msgstr "(%1) Feeds aktualisieren." + +#: source/class/feedreader/Application.js:156 +#: source/class/feedreader/Application.js:158 +msgid "English" +msgstr "Englisch" + +#: source/class/feedreader/Application.js:157 +msgid "German" +msgstr "Deutsch" + +#: source/class/feedreader/Application.js:159 +msgid "Turkish" +msgstr "Türkisch" + +#: source/class/feedreader/Application.js:160 +msgid "Italian" +msgstr "Italienisch" + +#: source/class/feedreader/Application.js:161 +msgid "Spanish" +msgstr "Spanisch" + +#: source/class/feedreader/Application.js:162 +msgid "Swedish" +msgstr "Schwedisch" + +#: source/class/feedreader/Application.js:163 +msgid "Russian" +msgstr "Russisch" + +#: source/class/feedreader/Application.js:186 +msgid "Help" +msgstr "Hilfe" + +#: source/class/feedreader/Application.js:194 +msgid "News feeds" +msgstr "Nachrichtenkanäle" + +#: source/class/feedreader/Application.js:215 +msgid "Subject" +msgstr "Betreff" + +#: source/class/feedreader/Application.js:216 +msgid "Sender" +msgstr "Absender" + +#: source/class/feedreader/Application.js:217 +msgid "Date" +msgstr "Datum" + +#: source/class/feedreader/ArticleView.js:79 +msgid "read more ..." +msgstr "weitere Informationen ..." diff --git a/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/translation/en.po b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/translation/en.po new file mode 100644 index 0000000000..e24d30878b --- /dev/null +++ b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/translation/en.po @@ -0,0 +1,93 @@ +# English translation +# +msgid "" +msgstr "" +"Project-Id-Version: qooxdoo feedreader\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2007-01-26 12:52+0100\n" +"PO-Revision-Date: 2006-12-21 10:17+0100\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=ASCII\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: source/class/feedreader/Application.js:133 +msgid "reloading ..." +msgstr "reloading ..." + +#: source/class/feedreader/Application.js:138 +msgid "qooxdoo feed reader." +msgstr "qooxdoo feed reader." + +#: source/class/feedreader/Application.js:143 +msgid "Add feed" +msgid_plural "Add feeds" +msgstr[0] "Add feed" +msgstr[1] "Add feeds" + +#: source/class/feedreader/Application.js:144 +msgid "Remove feed" +msgstr "Remove feed" + +#: source/class/feedreader/Application.js:147 +msgid "Reload" +msgstr "Reload" + +#: source/class/feedreader/Application.js:149 +msgid "(%1) Reload the feeds." +msgstr "(%1) Reload the feeds." + +#: source/class/feedreader/Application.js:156 +#: source/class/feedreader/Application.js:158 +msgid "English" +msgstr "English" + +#: source/class/feedreader/Application.js:157 +msgid "German" +msgstr "German" + +#: source/class/feedreader/Application.js:159 +msgid "Turkish" +msgstr "Turkish" + +#: source/class/feedreader/Application.js:160 +msgid "Italian" +msgstr "Italian" + +#: source/class/feedreader/Application.js:161 +msgid "Spanish" +msgstr "Spanish" + +#: source/class/feedreader/Application.js:162 +msgid "Swedish" +msgstr "Swedish" + +#: source/class/feedreader/Application.js:163 +msgid "Russian" +msgstr "Russian" + +#: source/class/feedreader/Application.js:186 +msgid "Help" +msgstr "Help" + +#: source/class/feedreader/Application.js:194 +msgid "News feeds" +msgstr "News feeds" + +#: source/class/feedreader/Application.js:215 +msgid "Subject" +msgstr "Subject" + +#: source/class/feedreader/Application.js:216 +msgid "Sender" +msgstr "Sender" + +#: source/class/feedreader/Application.js:217 +msgid "Date" +msgstr "Date" + +#: source/class/feedreader/ArticleView.js:79 +msgid "read more ..." +msgstr "read more ..." diff --git a/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/translation/es.po b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/translation/es.po new file mode 100644 index 0000000000..cb1e02ccb0 --- /dev/null +++ b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/translation/es.po @@ -0,0 +1,94 @@ +# Spanish translation +# +msgid "" +msgstr "" +"Project-Id-Version: feedreader\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2007-01-26 12:52+0100\n" +"PO-Revision-Date: 2007-01-24 20:54+0100\n" +"Last-Translator: Carsten Rammoser \n" +"Language-Team: \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Poedit-Language: Spanish\n" +"X-Poedit-Country: COLOMBIA\n" + +#: source/class/feedreader/Application.js:133 +msgid "reloading ..." +msgstr "actualizando ..." + +#: source/class/feedreader/Application.js:138 +msgid "qooxdoo feed reader." +msgstr "lector de feeds qooxdoo." + +#: source/class/feedreader/Application.js:143 +msgid "Add feed" +msgid_plural "Add feeds" +msgstr[0] "Agregar feed" +msgstr[1] "Agregar feeds" + +#: source/class/feedreader/Application.js:144 +msgid "Remove feed" +msgstr "Eliminar feed" + +#: source/class/feedreader/Application.js:147 +msgid "Reload" +msgstr "Actualizar" + +#: source/class/feedreader/Application.js:149 +msgid "(%1) Reload the feeds." +msgstr "(%1) Actualizar los feeds." + +#: source/class/feedreader/Application.js:156 +#: source/class/feedreader/Application.js:158 +msgid "English" +msgstr "Inglés" + +#: source/class/feedreader/Application.js:157 +msgid "German" +msgstr "Alemán" + +#: source/class/feedreader/Application.js:159 +msgid "Turkish" +msgstr "Turco" + +#: source/class/feedreader/Application.js:160 +msgid "Italian" +msgstr "Italiano" + +#: source/class/feedreader/Application.js:161 +msgid "Spanish" +msgstr "Español" + +#: source/class/feedreader/Application.js:162 +msgid "Swedish" +msgstr "Sueco" + +#: source/class/feedreader/Application.js:163 +msgid "Russian" +msgstr "Ruso" + +#: source/class/feedreader/Application.js:186 +msgid "Help" +msgstr "Ayuda" + +#: source/class/feedreader/Application.js:194 +msgid "News feeds" +msgstr "Feeds de noticias" + +#: source/class/feedreader/Application.js:215 +msgid "Subject" +msgstr "Asunto" + +#: source/class/feedreader/Application.js:216 +msgid "Sender" +msgstr "Remitente" + +#: source/class/feedreader/Application.js:217 +msgid "Date" +msgstr "Fecha" + +#: source/class/feedreader/ArticleView.js:79 +msgid "read more ..." +msgstr "leer más ..." diff --git a/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/translation/it.po b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/translation/it.po new file mode 100644 index 0000000000..1431458283 --- /dev/null +++ b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/translation/it.po @@ -0,0 +1,94 @@ +# Italian translation +# +msgid "" +msgstr "" +"Project-Id-Version: qooxdoo feedreader\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2007-01-23 17:57+0100\n" +"PO-Revision-Date: 2006-12-21 22:55+0100\n" +"Last-Translator: Alessandro Sala \n" +"Language-Team: Italiano \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"X-Generator: KBabel 1.11.4\n" + +#: source/class/feedreader/Application.js:130 +msgid "reloading ..." +msgstr "ricarico..." + +#: source/class/feedreader/Application.js:135 +msgid "qooxdoo feed reader." +msgstr "lettore di feed di qooxdoo" + +#: source/class/feedreader/Application.js:140 +msgid "Add feed" +msgid_plural "Add feeds" +msgstr[0] "Aggiungi un feed" +msgstr[1] "Aggiungi dei feed" + +#: source/class/feedreader/Application.js:141 +msgid "Remove feed" +msgstr "Rimuovi un feed" + +#: source/class/feedreader/Application.js:144 +msgid "Reload" +msgstr "Ricarica" + +#: source/class/feedreader/Application.js:146 +msgid "(%1) Reload the feeds." +msgstr "(%1) Ricarica i feed" + +#: source/class/feedreader/Application.js:153 +#: source/class/feedreader/Application.js:155 +msgid "English" +msgstr "Inglese" + +#: source/class/feedreader/Application.js:154 +msgid "German" +msgstr "Tedesco" + +#: source/class/feedreader/Application.js:156 +msgid "Turkish" +msgstr "Turco" + +#: source/class/feedreader/Application.js:157 +msgid "Italian" +msgstr "Italiano" + +#: source/class/feedreader/Application.js:158 +msgid "Spanish" +msgstr "Spagnolo" + +#: source/class/feedreader/Application.js:159 +msgid "Swedish" +msgstr "Svedese" + +#: source/class/feedreader/Application.js:160 +msgid "Russian" +msgstr "Russo" + +#: source/class/feedreader/Application.js:183 +msgid "Help" +msgstr "Aiuto" + +#: source/class/feedreader/Application.js:191 +msgid "News feeds" +msgstr "Feed di notizie" + +#: source/class/feedreader/Application.js:212 +msgid "Subject" +msgstr "Oggetto" + +#: source/class/feedreader/Application.js:213 +msgid "Sender" +msgstr "Mittente" + +#: source/class/feedreader/Application.js:214 +msgid "Date" +msgstr "Data" + +#: source/class/feedreader/ArticleView.js:77 +msgid "read more ..." +msgstr "continua..." diff --git a/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/translation/ru.po b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/translation/ru.po new file mode 100644 index 0000000000..b728919dbf --- /dev/null +++ b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/translation/ru.po @@ -0,0 +1,94 @@ +# Russian translation +# +msgid "" +msgstr "" +"Project-Id-Version: qooxdoo feedreader\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2007-01-23 17:57+0100\n" +"PO-Revision-Date: 2006-12-20 23:22+0200\n" +"Last-Translator: \n" +"Language-Team: \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=INTEGER; plural=EXPRESSION;\n" +"X-Generator: KBabel 1.11.4\n" + +#: source/class/feedreader/Application.js:130 +msgid "reloading ..." +msgstr "загрузка..." + +#: source/class/feedreader/Application.js:135 +msgid "qooxdoo feed reader." +msgstr "qooxdoo RSS reader" + +#: source/class/feedreader/Application.js:140 +msgid "Add feed" +msgid_plural "Add feeds" +msgstr[0] "Добавить канал" +msgstr[1] "Добавить каналы" + +#: source/class/feedreader/Application.js:141 +msgid "Remove feed" +msgstr "Удалить канал" + +#: source/class/feedreader/Application.js:144 +msgid "Reload" +msgstr "Перечитать" + +#: source/class/feedreader/Application.js:146 +msgid "(%1) Reload the feeds." +msgstr "{%1) Перечитать все каналы." + +#: source/class/feedreader/Application.js:153 +#: source/class/feedreader/Application.js:155 +msgid "English" +msgstr "Английский" + +#: source/class/feedreader/Application.js:154 +msgid "German" +msgstr "Немецкий" + +#: source/class/feedreader/Application.js:156 +msgid "Turkish" +msgstr "" + +#: source/class/feedreader/Application.js:157 +msgid "Italian" +msgstr "" + +#: source/class/feedreader/Application.js:158 +msgid "Spanish" +msgstr "" + +#: source/class/feedreader/Application.js:159 +msgid "Swedish" +msgstr "" + +#: source/class/feedreader/Application.js:160 +msgid "Russian" +msgstr "" + +#: source/class/feedreader/Application.js:183 +msgid "Help" +msgstr "Помощь" + +#: source/class/feedreader/Application.js:191 +msgid "News feeds" +msgstr "Новостные каналы" + +#: source/class/feedreader/Application.js:212 +msgid "Subject" +msgstr "Тема" + +#: source/class/feedreader/Application.js:213 +msgid "Sender" +msgstr "Отправитель" + +#: source/class/feedreader/Application.js:214 +msgid "Date" +msgstr "Дата" + +#: source/class/feedreader/ArticleView.js:77 +msgid "read more ..." +msgstr "далее..." diff --git a/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/translation/sv.po b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/translation/sv.po new file mode 100644 index 0000000000..f1a03b3b52 --- /dev/null +++ b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/translation/sv.po @@ -0,0 +1,93 @@ +# Swedish translation +# +msgid "" +msgstr "" +"Project-Id-Version: qooxdoo feedreader\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2007-01-23 17:57+0100\n" +"PO-Revision-Date: 2006-12-19 11:10+0100\n" +"Last-Translator: Henric Johansson \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=INTEGER; plural=EXPRESSION;\n" + +#: source/class/feedreader/Application.js:130 +msgid "reloading ..." +msgstr "uppdaterar..." + +#: source/class/feedreader/Application.js:135 +msgid "qooxdoo feed reader." +msgstr "qooxdoo feed läsare." + +#: source/class/feedreader/Application.js:140 +msgid "Add feed" +msgid_plural "Add feeds" +msgstr[0] "Lägg till feed" +msgstr[1] "Lägg till feeds" + +#: source/class/feedreader/Application.js:141 +msgid "Remove feed" +msgstr "Ta bort feed" + +#: source/class/feedreader/Application.js:144 +msgid "Reload" +msgstr "Uppdatera" + +#: source/class/feedreader/Application.js:146 +msgid "(%1) Reload the feeds." +msgstr "(%1) Uppdatera feedsen." + +#: source/class/feedreader/Application.js:153 +#: source/class/feedreader/Application.js:155 +msgid "English" +msgstr "Engelska" + +#: source/class/feedreader/Application.js:154 +msgid "German" +msgstr "Tyska" + +#: source/class/feedreader/Application.js:156 +msgid "Turkish" +msgstr "" + +#: source/class/feedreader/Application.js:157 +msgid "Italian" +msgstr "" + +#: source/class/feedreader/Application.js:158 +msgid "Spanish" +msgstr "" + +#: source/class/feedreader/Application.js:159 +msgid "Swedish" +msgstr "" + +#: source/class/feedreader/Application.js:160 +msgid "Russian" +msgstr "" + +#: source/class/feedreader/Application.js:183 +msgid "Help" +msgstr "Hjälp" + +#: source/class/feedreader/Application.js:191 +msgid "News feeds" +msgstr "Nyhetsfeed" + +#: source/class/feedreader/Application.js:212 +msgid "Subject" +msgstr "Ämne" + +#: source/class/feedreader/Application.js:213 +msgid "Sender" +msgstr "Avsändare" + +#: source/class/feedreader/Application.js:214 +msgid "Date" +msgstr "Datum" + +#: source/class/feedreader/ArticleView.js:77 +msgid "read more ..." +msgstr "läs mer..." diff --git a/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/translation/tr.po b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/translation/tr.po new file mode 100644 index 0000000000..f3ccc949b8 --- /dev/null +++ b/webapps/qooxdoo-0.6.5-sdk/frontend/application/feedreader/source/translation/tr.po @@ -0,0 +1,95 @@ +# Turkish translation +# +msgid "" +msgstr "" +"Project-Id-Version: qooxdoo feedreader\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2007-01-23 17:57+0100\n" +"PO-Revision-Date: 2006-12-18 21:51+0200\n" +"Last-Translator: Fatih Tolga Ata \n" +"Language-Team: \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Poedit-Language: Turkish\n" +"X-Poedit-Country: Turkey\n" +"X-Poedit-SourceCharset: utf-8\n" + +#: source/class/feedreader/Application.js:130 +msgid "reloading ..." +msgstr "yenileniyor ..." + +#: source/class/feedreader/Application.js:135 +msgid "qooxdoo feed reader." +msgstr "qooxdoo besleme okuyucu." + +#: source/class/feedreader/Application.js:140 +msgid "Add feed" +msgid_plural "Add feeds" +msgstr[0] "Besleme ekle" +msgstr[1] "Beslemeler ekle" + +#: source/class/feedreader/Application.js:141 +msgid "Remove feed" +msgstr "Besleme sil" + +#: source/class/feedreader/Application.js:144 +msgid "Reload" +msgstr "Yenile" + +#: source/class/feedreader/Application.js:146 +msgid "(%1) Reload the feeds." +msgstr "(%1) Beslemesini yenile." + +#: source/class/feedreader/Application.js:153 +#: source/class/feedreader/Application.js:155 +msgid "English" +msgstr "İngilizce" + +#: source/class/feedreader/Application.js:154 +msgid "German" +msgstr "Almanca" + +#: source/class/feedreader/Application.js:156 +msgid "Turkish" +msgstr "" + +#: source/class/feedreader/Application.js:157 +msgid "Italian" +msgstr "" + +#: source/class/feedreader/Application.js:158 +msgid "Spanish" +msgstr "" + +#: source/class/feedreader/Application.js:159 +msgid "Swedish" +msgstr "" + +#: source/class/feedreader/Application.js:160 +msgid "Russian" +msgstr "" + +#: source/class/feedreader/Application.js:183 +msgid "Help" +msgstr "Yardım" + +#: source/class/feedreader/Application.js:191 +msgid "News feeds" +msgstr "Haber beslemeleri" + +#: source/class/feedreader/Application.js:212 +msgid "Subject" +msgstr "Konu" + +#: source/class/feedreader/Application.js:213 +msgid "Sender" +msgstr "Gönderen" + +#: source/class/feedreader/Application.js:214 +msgid "Date" +msgstr "Tarih" + +#: source/class/feedreader/ArticleView.js:77 +msgid "read more ..." +msgstr "daha fazla ..." -- cgit