some extremely important game-changers:
jQuery, JSON, Node.js, and HTML5.
1More
GMailr: An Unofficial Javascript API for GMail - ReadWriteCloud - 1 views
-
Google has pretty much given up on developing a JavaScript API for GMail. There was once a Greasemonkey script Google developed for GMail but that broke and Google shows no sign of fixing it. James Yu is now trying to fix that scenario with GMailr, a JavaScript API for GMail. It is made from the code he wrote for 0Boxer, an extension for GMail that turns organizing your inbox into a game. Yu is also a lead developer at Scribd. Yu said developing the API took him on a path fraught with frustrations and dead ends. He writes there is supported official JavaScript API for Gmail. The Greasemonkey script is broken and no one has yet released a frontend API for Gmail. He said he needed access to the various user actions in the UI as the backend APIs were not going to work as he wished. He decided to write his own library from scratch.
15More
shared by Gary Edwards on 07 Jun 11
- No Cached
Why a JavaScript hater thinks everyone needs to learn JavaScript in the next year - O'R... - 1 views
radar.oreilly.com/...time-to-learn-javascript.html
JavaScript HTML+ Node.JS JQuery web-apps web-application-development
![](/images/link.gif)
-
.js has the potential to revolutionize web development. It is a framework for building high performance web applications: applications that can respond very quickly and efficiently to a high volume of incoming requests.
- ...11 more annotations...
-
HTML5, then, isn't really a major advance in angle-bracket-based tagging; it's about enabling JavaScr
-
JavaScript has long been the workhorse for implementing dynamic features in HTML. But there have always been two problems: browser incompatibilities, and the awkwardness of working directly with the DOM. The JQuery library has elegantly solved both problems, and is the basis for modern client-side browser development.
-
Web servers, rich web client libraries, HTML5, databases, even JavaScript-based languages: I see JavaScript everywhere.
-
OK, this article gets my vote as the most important read of the year. We all know that the the Web is the future of both computing and communications/connectivity. But wha tis the future of the Web? Uber coder Mike Loukides says it's JavaScript, and what a compelling case he builds. This is a must read. Key concepts are diigo highlighted :) excerpt: JavaScript has "grown up." I'm sure there are many JavaScript developers who would take issue with that judgement, and argue that JavaScript has been a capable, mature, and under-appreciated language all along. They may be right, though you can write any program in any complete programming language, including awful things like BASIC. What makes a language useful is some combination of the language's expressiveness and the libraries and tools available. JavaScript clearly passed the expressiveness barrier a long time ago, even if the ceremony required for creating objects is distasteful. But recently, we've seen some extremely important game-changers: jQuery, JSON, Node.js, and HTML5. JavaScript may have been a perfectly adequate language in the past, but these changes (and a few others that I'll point out) have made JavaScript a language that is essential for every developer to know. If there's one language you need to learn in the next year, it's JavaScript. Insightful comment: HTML5 is a JavaScript API, introducing new elements but significantly redefining ALL elements as objects or classes. Elements can be expressed with tags. Or, you can use DOM JavaScripting to create elements.
1More
Google Chrome OS: Web Platform To Rule Them All -- InformationWeek - 0 views
-
Some good commentary on chrome OS from InformationWeek's Thomas Claburn. Excerpt: With Chrome OS, Google aims to make the Web the primary platform for software development....... The fact that Chrome OS applications will be written using open Web standards like JavaScript, HTML, and CSS might seem like a liability because Web applications still aren't as capable as applications written for specific devices and operating systems. But Google is betting that will change and is working to effect the change on which its bet depends. Within a year or two, Web browsers will gain access to peripherals, through an infrastructure layer above the level of device drivers. Google's work with standards bodies is making that happen..... ..... According to Matt Womer, the "ubiquitous Web activity lead" for W3C, the Web standards consortium, Web protocol groups are working to codify ways to access peripherals like digital cameras, the messaging stack, calendar data, and contact data. There's now a JavaScript API that Web developers can use to get GPS information from mobile phones using the phone's browser, he points out. What that means is that device drivers for Chrome OS will emerge as HTML 5 and related standards mature. Without these, consumers would never use Chrome OS because devices like digital cameras wouldn't be able to transfer data. Womer said the standardization work could move quite quickly, but won't be done until there's an actual implementation. That would be Chrome OS...... ..... Chrome OS will sell itself to developers because, as Google puts it, writing applications for the Web gives "developers the largest user base of any platform."
2More
Project Summary - 3 views
-
Maqetta is an open source technology initiative at Dojo Foundation that provides WYSIWYG tooling in the cloud for HTML5 (desktop and mobile). Maqetta allows User Experience Designers (UXD) to perform drag/drop assembly of live UI mockups. One of Maqetta's key design goals is to create developer-ready UI mockups that promote efficient hand-off from designers to developers. The user interfaces created by Maqetta are real-life web applications that can be handed off to developers, who can then transform the application incrementally from UI mockup into final shipping application. While we expect the Maqetta-created mockups often will go through major code changes, Maqetta is designed to promote preservation of visual assets, particularly the CSS style sheets, across the development life cycle. As a result, the careful pixel-level styling efforts by the UI team will carry through into the final shipping application. To help with the designer/developer hand-off, Maqetta includes a "download into ZIP" feature to create a ZIP image that can be imported into a developer tool workspace (e.g., Eclipse IDE). For team development, Maqetta includes a web-based review&commenting features with forum-style comments and on-canvas annotations.
-
Maqetta includes: a WYSIWYG visual page editor for drawing out user interfaces drag/drop mobile UI authoring within an exact-dimension device silhouette, such as the silhouette of an iPhone simultaneous editing in either design or source views deep support for CSS styling (the application includes a full CSS parser/modeler) a mechanism for organizing a UI prototype into a series of "application states" (aka "screens" or "panels") which allows a UI designer to define interactivity without programming a web-based review and commenting feature where the author can submit a live UI mockup for review by his team members a "wireframing" feature that allows UI designers to create UI proposals that have a hand-drawn look a theme editor for customizing the visual styling of a collection of widgets export options that allow for smooth hand-off of the UI mockups into leading developer tools such as Eclipse Maqetta's code base has a toolkit-independent architecture that allows for plugging in arbitrary widget libraries and CSS themes.
1More
shared by Gary Edwards on 02 Oct 10
- Cached
Ex-Apple Javascript Guru: HTML5 and Native Apps Can Live Together: Tech News « - 0 views
gigaom.com/...arles-jolley-srpoutcore-strobe
Strobe Charles-Jolley SproutCore WebKit Mobility HTML5-Native-Client
![](/images/link.gif)
-
Good interview with Charles Jolley - SproutCore - WebKit (met Charles at Web 2.0). He has left Apple and started a SproutCore Web App development company called "Strobe". Looking very good Charles! The Blended Brew Apps have become a preferred way of accessing information on mobile devices. But developers want to provide a unified experience, and that is why Jolley believes that we will soon have apps that use HTML5 inside a native app wrapper. "People are looking for an either/or solution, but it is not going to end up like that," he said. Think of Strobe's offerings as a way to create an experience that is a blend of HTML5 and native mobile apps. How this works is that an application is developed in HTML5 instead of proprietary formats. It is wrapped in a native app wrapper for, say, the iPhone, but when accessed through a web browser on a PC or any other device, like tablet, it offers the same user experience. This is a good way to solve a problem that is only going to get compounded many fold as multiple endpoints for content start to emerge. The co-existence of web and native apps also means content publishers need to think differently about content and how it is offered to consumers. The multiplicity of endpoints (iPhone, iPad, TV and PC) is going to force content producers to think differently about how they build the user experiences for different sets of screens. Jolley argues that the best way to do so is to stop taking a document-centric view that is part of the PC-era. In the touch-based mobile device era, folks need to think of ways to have a single technology stack married to the ability to create unique experiences for different devices. And if you do that, there is no doubt that HTML5 and native apps can live in harmony.
1More
Diary Of An x264 Developer » Flash, Google, VP8, and the future of internet v... - 0 views
-
In depth technical discussion about Flash, HTML5, H.264, and Google's VP8. Excellent. Read the comments. Bottom line - Google has the juice to put Flash and H.264 in the dirt. The YouTube acquisition turns out to be very strategic. excerpt: The internet has been filled for quite some time with an enormous number of blog posts complaining about how Flash sucks-so much that it's sounding as if the entire internet is crying wolf. But, of course, despite the incessant complaining, they're right: Flash has terrible performance on anything other than Windows x86 and Adobe doesn't seem to care at all. But rather than repeat this ad nauseum, let's be a bit more intellectual and try to figure out what happened. Flash became popular because of its power and flexibility. At the time it was the only option for animated vector graphics and interactive content (stuff like VRML hardly counts). Furthermore, before Flash, the primary video options were Windows Media, Real, and Quicktime: all of which were proprietary, had no free software encoders or decoders, and (except for Windows Media) required the user to install a clunky external application, not merely a plugin. Given all this, it's clear why Flash won: it supported open multimedia formats like H.263 and MP3, used an ultra-simple container format that anyone could write (FLV), and worked far more easily and reliably than any alternative. Thus, Adobe (actually, at the time, Macromedia) got their 98% install base. And with that, they began to become complacent. Any suggestion of a competitor was immediately shrugged off; how could anyone possibly compete with Adobe, given their install base? It'd be insane, nobody would be able to do it. They committed the cardinal sin of software development: believing that a competitor being better is excusable. At x264, if we find a competitor that does something better, we immediately look into trying to put ourselves back on top. This is why
1More
shared by Gary Edwards on 20 May 11
- No Cached
Chrome Developer Tools: Remote Debugging - Google Chrome Developer Tools - Google Code - 0 views
code.google.com/...remote-debugging.html
chrome-webkit developer-tool-interface HTML5-CSS3 JSON OTXML
![](/images/link.gif)
-
Incredible. I'm wondering if either Jason or florian has thought about using the Chrome JSON messaging layer to expose docx conversions to OTXML? Essentially, when Florian breaks a .docx document, he only deals with the objects and how they are positioned (layout) on a page. Once captured and described, these xObjects could then be converted to JSON. The Chrome web client/ web server port (9222) could then, theoretically be used to observe the JSON xObjects? Interesting. intro: Under the hood, Chrome Developer Tools is a web application written in HTML, JavaScript and CSS. It has a special binding available at JavaScript runtime that allows interacting with chrome pages and instrumenting them. Interaction protocol consists of commands that are sent to the page and events that the page is generating. Although Chrome Developer Tools is the only client of this protocol, there are ways for third parties to bypass it and start instrumenting browser pages explicitly. We will describe the ways it could be done below. Contents Protocol Debugging over the wire Using debugger extension API
1More
Nokia Targets Web Developers -- Web Developer Tools -- InformationWeek - 0 views
-
Nokia on Tuesday introduced a set of developer tools that seeks to make it easier for Web developers to create widgets for mobile phones. Nokia released Web Runtime plug-ins for Microsoft's Visual Studio, Adobe's Dreamweaver, and Aptana Studio, enabling third parties to create mobile widgets using HTML, CSS, JavaScript, Ajax, and other standard Web development code. The company said this should streamline the development process, as well as attract a new set of content creators who may not have mobile experience.
1More
New tools for web design and development: May 2013 | Feature | .net magazine - 1 views
-
Quick review of a new crop of Web Development - JavaScript tools. Includes ICE Coder! "The crop of new development tools this month is rich and varied. Taking in web-based IDEs, testing tools, programming paradigms and more, there's enough raw material here to entertain a keen mind for months. If you wanted to be selective you could just study and apply new approaches like lazy loading, or reactive programming. Or maybe you'd prefer to tighten cross-platform consistency with GhostLab. And, if you're feeling particularly clever, you could explore the possibilities of deploying a Bunny 'darknet' from your coffee shop armchair."
48More
shared by Gary Edwards on 01 Nov 13
- No Cached
XML Production Workflows? Start with the Web and XHTML - 1 views
quod.lib.umich.edu/...n-workflows-start-with-the-web
OpenWeb XML XHTML-CSS HTML5-CSS3-JavaScript IDML
![](/images/link.gif)
-
Challenges: Some Ugly Truths The challenges of building—and living with—an XML workflow are clear enough. The return on investment is a long-term proposition. Regardless of the benefits XML may provide, the starting reality is that it represents a very different way of doing things than the one we are familiar with. The Word Processing and Desktop Publishing paradigm, based on the promise of onscreen, WYSIWYG layout, is so dominant as to be practically inescapable. It has proven really hard to get from here to there, no matter how attractive XML might be on paper. A considerable amount of organizational effort and labour must be expended up front in order to realize the benefits. This is why XML is often referred to as an “investment”: you sink a bunch of time and money up front, and realize the benefits—greater flexibility, multiple output options, searching and indexing, and general futureproofing—later, over the long haul. It is not a short-term return proposition. And, of course, the returns you are able to realize from your XML investment are commensurate with what you put in up front: fine-grained, semantically rich tagging is going to give you more potential for searchability and recombination than a looser, more general-purpose approach, but it sure costs more. For instance, the Text Encoding Initiative (TEI) is the grand example of pouring enormous amounts of energy into the up-front tagging, with a very open-ended set of possibilities down the line. TEI helpfully defines a level to which most of us do not have to aspire.[5] But understanding this on a theoretical level is only part of the challenge. There are many practical issues that must be addressed. Software and labour are two of the most critical. How do you get the content into XML in the first place? Unfortunately, despite two decades of people doing SGML and XML, this remains an ugly question.
-
Practical Challenges In 2009, there is still no truly likeable—let alone standard—editing and authoring software for XML. For many (myself included), the high-water mark here was Adobe’s FrameMaker, substantially developed by the late 1990s. With no substantial market for it, it is relegated today mostly to the tech writing industry, unavailable for the Mac, and just far enough afield from the kinds of tools we use today that its adoption represents a significant hurdle. And FrameMaker was the best of the breed; most of the other software in decent circulation are programmers’ tools—the sort of things that, as Michael Tamblyn pointed out, encourage editors to drink at their desks. The labour question represents a stumbling block as well. The skill-sets and mind-sets that effective XML editors need have limited overlap with those needed by literary and more traditional production editors. The need to think of documents as machine-readable databases is not something that comes naturally to folks steeped in literary culture. In combination with the sheer time and effort that rich tagging requires, many publishers simply outsource the tagging to India, drawing a division of labour that spans oceans, to put it mildly. Once you have XML content, then what do you do with it? How do you produce books from it? Presumably, you need to be able to produce print output as well as digital formats. But while the latter are new enough to be generally XML-friendly (e-book formats being largely XML based, for instance), there aren’t any straightforward, standard ways of moving XML content into the kind of print production environments we are used to seeing. This isn’t to say that there aren’t ways of getting print—even very high-quality print—output from XML, just that most of them involve replacing your prepress staff with Java programmers.
-
Why does this have to be so hard? It’s not that XML is new, or immature, or untested. Remember that the basics have been around, and in production, since the early 1980s at least. But we have to take account of a substantial and long-running cultural disconnect between traditional editorial and production processes (the ones most of us know intimately) and the ways computing people have approached things. Interestingly, this cultural divide looked rather different in the 1970s, when publishers were looking at how to move to digital typesetting. Back then, printers and software developers could speak the same language. But that was before the ascendancy of the Desktop Publishing paradigm, which computerized the publishing industry while at the same time isolating it culturally. Those of us who learned how to do things the Quark way or the Adobe way had little in common with people who programmed databases or document-management systems. Desktop publishing technology isolated us in a smooth, self-contained universe of toolbars, grid lines, and laser proofs. So, now that the reasons to get with this program, XML, loom large, how can we bridge this long-standing divide?
- ...44 more annotations...
-
Using the Web as a Production Platform The answer, I think, is right in front of you. The bridge is the Web, a technology and platform that is fundamentally based on XML, and which many publishers are by now comfortably familiar with. Perhaps not entirely comfortably, but at least most publishers are already working with the Web; they already either know or have on staff people who understand it and can work with it. The foundation of our argument is this: rather than looking at jumping to XML in its full, industrial complexity, which seems to be what the O'Reilly-backed StartWithXML initiative[6] is suggesting, publishers instead leverage existing tools and technologies—starting with the Web—as a means of getting XML workflows in place. This means making small investments and working with known tools rather than spending tens of thousands of dollars on XML software and rarefied consultants. It means re-thinking how the existing pieces of the production toolchain fit together; re-thinking the existing roles of software components already in use. It means, fundamentally, taking the Web seriously as a content platform, rather than thinking of it as something you need to get content out to, somehow. If nothing else, the Web represents an opportunity to think about editorial and production from outside the shrink-wrapped Desktop Publishing paradigm.
-
Is the Web made of Real XML? At this point some predictable objections can be heard: wait a moment, the Web isn’t really made out of XML; the HTML that makes up most of the Web is at best the bastard child of SGML, and it is far too flaky/unstructured/underpowered to be taken seriously. We counter by arguing that although HTML on the Web exists in a staggering array of different incarnations, and that the majority of it is indeed an unstructured mess, this does not undermine the general principle that basic, ubiquitous Web technologies can make a solid platform for content management, editorial process, and production workflow.
-
With the advent of a published XML standard in the late 1990s came the W3C’s adoption of XHTML: the realization of the Web’s native content markup as a proper XML document type. Today, its acceptance is almost ubiquitous, even while the majority of actual content out there may not be strictly conforming. The more important point is that most contemporary Web software, from browsers to authoring tools to content management systems (from blogs to enterprise systems), are capable of working with clean, valid XHTML. Or, to put the argument the other way around, clean, valid XHTML content plays absolutely seamlessly with everything else on the Web.[7]
-
The objection which follows, then, will be that even if we grant that XHTML is a real XML document type, that it is underpowered for “serious” content because it is almost entirely presentation (formatting) oriented; it lacks any semantic depth. In XHTML, a paragraph is a paragraph is a paragraph, as opposed to a section or an epigraph or a summary.
-
n contrast, more “serious” XML document types like DocBook[8] or DITA-derived schemas[9] are capable of making semantic distinctions about content chunks at a fine level of granularity and with a high degree of specificity.
-
So there is an argument for recalling the 80:20 rule here. If XHTML can provide 80% of the value with just 20% of the investment, then what exactly is the business case for spending the other 80% to achieve that last 20% of value? We suspect the ratio is actually quite a bit steeper than 80:20 for most publishers.
-
Furthermore, just to get technical for a moment, XHTML is extensible in a fairly straightforward way, through the common “class” attribute on each element. Web developers have long leveraged this kind of extensibility in the elaboration of “microformats” for semantic-web applications.[10] There is no reason why publishers shouldn’t think to use XHTML’s simple extensibility in a similar way for their own ends.
-
XHTML, on the other hand, is supported by a vast array of quotidian software, starting with the ubiquitous Web browser. For this very reason, XHTML is in fact employed as a component part of several more specialized document types (ONIX and ePub among them).
-
It is worth pausing for a moment to consider the role of XHTML in the ePub standard for ebook content. An ePub file is, anatomically, a simply disguised zip archive. Inside the zip archive are a few standard component parts: there are specialized files that declare metadata about the book, and about the format of the book. And then there is the book’s content, represented in XHTML. An ePub book is a Web page in a wrapper.
-
To sum up the general argument: the Web as it already exists presents incredible value to publishers, as a platform for doing XML content management with existing (and often free) tools, and without having to go blindly into the unknown. At this point, we can offer a few design guidelines: prefer existing and/or ubiquitous tools over specialized ones wherever possible; prefer free software over proprietary systems where possible; prefer simple tools controlled and coordinated by human beings over fully automated (and therefore complex) systems; play to our strengths: use Web software for storing and managing content, use layout software for layout, and keep editors and production people in charge of their own domains.
-
At the SFU Master of Publishing Program, we have been chipping away at this general line of thinking for a few years. Over that time, Web content management systems have been getting more and more sophisticated, all the while getting more streamlined and easier to use. (NB: if you have a blog, you have a Web content management system.) The Web is beginning to be recognized as a writing and editing environment used by millions of people. And the ways in which content is represented, stored, and exchanged online have become increasingly robust and standardized.
-
The missing piece of the puzzle has been print production: how can we move content from its malleable, fluid form on line into the kind of high-quality print production environments we’ve come to expect after two decades of Desktop Publishing?
-
Anyone who has tried to print Web content knows that the existing methods leave much to be desired (hyphenation and justification, for starters). In the absence of decent tools for this, most publishers quite naturally think of producing the print content first, and then think about how to get material onto the Web for various purposes. So we tend to export from Word, or from Adobe, as something of an afterthought.
-
While this sort of works, it isn’t elegant, and it completely ignores the considerable advantages of Web-based content management.
-
Content managed online is stored in one central location, accessible simultaneously to everyone in your firm, available anywhere you have an Internet connection, and usually exists in a much more fluid format than Word files. If only we could manage the editorial flow online, and then go to print formats at the end, instead of the other way around. At SFU, we made several attempts to make this work by way of the supposed “XML import” capabilities of various Desktop Publishing tools, without much success.[12]
-
In the winter of 2009, Adobe solved this part of the problem for us with the introduction of its Creative Suite 4. What CS4 offers is the option of a complete XML representation of an InDesign document: what Adobe calls IDML (InDesign Markup Language).
-
The IDML file format is—like ePub—a simply disguised zip archive that, when unpacked, reveals a cluster of XML files that represent all the different facets of an InDesign document: layout spreads, master pages, defined styles, colours, and of course, the content.
-
IDML is a well thought-out XML standard that achieves two very different goals simultaneously: it preserves all of the information that InDesign needs to do what it does; and it is broken up in a way that makes it possible for mere mortals (or at least our Master of Publishing students) to work with it.
-
What this represented to us in concrete terms was the ability to take Web-based content and move it into InDesign in a straightforward way, thus bridging Web and print production environments using existing tools and skillsets, with a little added help from free software.
-
We would take clean XHTML content, transform it to IDML-marked content, and merge that with nicely designed templates in InDesign.
-
The result is an almost push-button publication workflow, which results in a nice, familiar InDesign document that fits straight into the way publishers actually do production.
-
The simplest method for this conversion—and if you want to create Web content, this is an excellent route—was to use Adobe’s “Export to Digital Editions” option, which creates an ePub file.
-
Recall that ePub is just XHTML in a wrapper, so within the ePub file was a relatively clean XHTML document. It was somewhat cleaner (that is, the XHTML tagging was simpler and less cluttered) than InDesign’s other Web-oriented exports, possibly because Digital Editions is a well understood target, compared with somebody’s website.
-
In order to achieve our target of clean XHTML, we needed to do some editing; the XHTML produced by InDesign’s “Digital Editions” export was presentation-oriented. For instance, bulleted list items were tagged as paragraphs, with a class attribute identifying them as list items. Using the search-and-replace function, we converted such structures to proper XHTML list and list-item elements. Our guiding principle was to make the XHTML as straightforward as possible, not dependent on any particular software to interpret it.
-
We broke the book’s content into individual chapter files; each chapter could then carry its own basic metadata, and the pages conveniently fit our Web content management system (which is actually just a wiki). We assembled a dynamically generated table of contents for the 12 chapters, and created a cover page. Essentially, the book was entirely Web-based at this point.
-
When the book chapters are viewed online, they are formatted via a CSS2 stylesheet that defines a main column for content as well as dedicating screen real estate for navigational elements. We then created a second template to render the content for exporting; this was essentially a bare-bones version of the book with no navigation and minimal styling. Pages (or even the entire book) can be exported (via the “Save As...” function in a Web browser) for use in either print production or ebook conversion. At this point, we required no skills beyond those of any decent Web designer.
-
Integrating with CS4 for Print Adobe’s IDML language defines elements specific to InDesign; there is nothing in the language that looks remotely like XHTML. So a mechanical transformation step is needed to convert the XHTML content into something InDesign can use. This is not as hard as it might seem.
-
Both XHTML and IDML are composed of straightforward, well-documented structures, and so transformation from one to the other is, as they say, “trivial.” We chose to use XSLT (Extensible Stylesheet Language Transforms) to do the work. XSLT is part of the overall XML specification, and thus is very well supported in a wide variety of tools. Our prototype used a scripting engine called xsltproc, a nearly ubiquitous piece of software that we found already installed as part of Mac OS X (contemporary Linux distributions also have this as a standard tool), though any XSLT processor would work.
-
In other words, we don’t need to buy InCopy, because we just replaced it with the Web. Our wiki is now plugged directly into our InDesign layout. It even automatically updates the InDesign document when the content changes. Credit is due at this point to Adobe: this integration is possible because of the open file format in the Creative Suite 4.
-
We wrote an XSLT transformation script[18] that converted the XHTML content from the Web into an InCopy ICML file. The script itself is less than 500 lines long, and was written and debugged over a period of about a week by amateurs (again, the people named at the start of this article). The script runs in a couple of seconds, and the resulting .icml file can then be “placed” directly into an InDesign template. The ICML file references an InDesign stylesheet, so the template file can be set up with a house-styled layout, master pages, and stylesheet definitions for paragraphs and character ranges.
-
Rather than a public-facing website, our system relies on the Web as a content management platform—of course a public face could easily be added.
-
It should be noted that the Book Publishing 1 proof-of-concept was artificially complex; we began with a book laid out in InDesign and ended up with a look-alike book laid out in InDesign. But next time—for instance, when we publish Book Publishing 2—we can begin the process with the content on the Web, and keep it there throughout the editorial process. The book’s content could potentially be written and edited entirely online, as Web content, and then automatically poured into an InDesign template at proof time. “Just in time,” as they say. This represents an entirely new way of thinking of book production. With a Web-first orientation, it makes little sense to think of the book as “in print” or “out of print”—the book is simply available, in the first place online; in the second place in derivative digital formats; and third, but really not much more difficult, in print-ready format, via the usual InDesign CS print production system publishers are already familiar with.
-
Creating Ebook Files Creating electronic versions from XHTML source is vastly simpler than trying to generate these out of the existing print process. The ePub version is extremely easy to generate; so is online marketing copy or excerpts for the Web, since the content begins life Web-native.
-
Since an ePub file is essentially XHTML content in a special wrapper, all that is required is that we properly “wrap” our XHTML content. Ideally, the content in an ePub file is broken into chapters (as ours was) and a table of contents file is generated in order to allow easy navigation within an ebook reader. We used Julian Smart’s free tool eCub[19] to simply and automatically generate the ePub wrapper and the table of contents. The only custom development we did was to create a CSS stylesheet for the ebook so that headings and paragraph indents looked the way we wanted. Starting with XHTML content, creating ePub is almost too easy.
-
today, we are able to put the process together using nothing but standard, relatively ubiquitous Web tools: the Web itself as an editing and content management environment, standard Web scripting tools for the conversion process, and the well-documented IDML file format to integrate the layout tool.
-
Our project demonstrates that Web technologies are indeed good enough to use in an XML-oriented workflow; more specialized and expensive options are not necessarily required. For massive-scale enterprise publishing, this approach may not offer enough flexibility, and the challenge of adding and extracting extra semantic richness may prove more trouble than it's worth.
-
But for smaller firms who are looking at the straightforward benefits of XML-based processes—single source publishing, online content and workflow management, open and accessible archive formats, greater online discoverability—here is a way forward.
-
The result is very simple and easy to use. Our demonstration requires that a production editor run the XSLT transformation script manually, but there is no reason why this couldn’t be built directly into the Web content management system so that exporting the content to print ran the transformation automatically. The resulting file would then be “placed” in InDesign and proofed.
-
The final piece of our puzzle, the ability to integrate print production, was made possible by Adobe's release of InDesign with an open XML file format. Since the Web's XHTML is also XML, is can be easily and confidently transformed to the InDesign format.
-
Such a workflow—beginning with the Web and exporting to print—is surely more in line with the way we will do business in the 21st century, where the Web is the default platform for reaching audiences, developing content, and putting the pieces together. It is time, we suggest, for publishers to re-orient their operations and start with the Web.
-
I was looking for an answer to a problem Marbux had presented, and found this interesting article. The issue was that of the upcoming conversion of the Note Case Pro (NCP) layout engine to the WebKit layout engine, and what to do about the NCP document format. My initial reaction was to encode the legacy NCP document format in XML, and run an XSLT to a universal pivot format like TEI-XML. From there, the TEI-XML community would provide all the XSLT transformation routines for conversion to ODF, OOXML, XHTML, ePUB and HTML/CSS. Researching the problems one might encounter with this approach, I found this article. Fascinating stuff. My take away is that TEI-XML would not be as effective a "universal pivot point" as XHTML. Or perhaps, if NCP really wants to get aggressive; IDML - InDesign Markup Language. As an after thought, i was thinking that an alternative title to this article might have been, "Working with Web as the Center of Everything".
4More
Last Call Working Draft -- W3C Authoring Tool Accessibility Guidelines (ATAG) 2.0 - 0 views
-
This is a Working Draft of the Authoring Tool Accessibility Guidelines (ATAG) version 2.0. This document includes recommendations for assisting authoring tool developers to make the authoring tools that they develop more accessible to people with disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, motor difficulties, speech difficulties, and others. Accessibility, from an authoring tool perspective, includes addressing the needs of two (potentially overlapping) user groups with disabilities: authors of web content, whose needs are met by ensuring that the authoring tool user interface itself is accessible (addressed by Part A of the guidelines), and end users of web content, whose needs are met by ensuring that all authors are enabled, supported, and guided towards producing accessible web content (addressed by Part B of the guidelines).
-
Examples of authoring tools: ATAG 2.0 applies to a wide variety of web content generating applications, including, but not limited to: web page authoring tools (e.g., WYSIWYG HTML editors) software for directly editing source code (see note below) software for converting to web content technologies (e.g., "Save as HTML" features in office suites) integrated development environments (e.g., for web application development) software that generates web content on the basis of templates, scripts, command-line input or "wizard"-type processes software for rapidly updating portions of web pages (e.g., blogging, wikis, online forums) software for generating/managing entire web sites (e.g., content management systems, courseware tools, content aggregators) email clients that send messages in web content technologies multimedia authoring tools debugging tools for web content software for creating mobile web applications
-
Web-based and non-web-based: ATAG 2.0 applies equally to authoring tools of web content that are web-based, non-web-based or a combination (e.g., a non-web-based markup editor with a web-based help system, a web-based content management system with a non-web-based file uploader client). Real-time publishing: ATAG 2.0 applies to authoring tools with workflows that involve real-time publishing of web content (e.g., some collaborative tools). For these authoring tools, conformance to Part B of ATAG 2.0 may involve some combination of real-time accessibility supports and additional accessibility supports available after the real-time authoring session (e.g., the ability to add captions for audio that was initially published in real-time). For more information, see the Implementing ATAG 2.0 - Appendix E: Real-time content production. Text Editors: ATAG 2.0 is not intended to apply to simple text editors that can be used to edit source content, but that include no support for the production of any particular web content technology. In contrast, ATAG 2.0 can apply to more sophisticated source content editors that support the production of specific web content technologies (e.g., with syntax checking, markup prediction, etc.).
1More
Method for invoking UOML instructions - Patent application - Embodiments of the present... - 1 views
-
Patent application filed on OASIS UOML access by API. 0002]The present invention relates to electronic document processing technologies, and particularly to a method for encapsulating Unstructured Operation Markup Language (UOML) into an Application Programming Interface (API). BACKGROUND OF THE INVENTION [0003]The UOML standard includes a series of docbase management system instructions defined according to a format of "action+object" in Extensible Markup Language (XML), which has been explained in detail in an UOML Standard published by of the Organization for the Advancement of Structured Information Standards (OASIS ). Since XML works across different platforms and with different languages, the UOML standard can enable the docbase management system instructions to be exchanged across the different platforms in the different languages. However, in practical applications, operations on a docbase are usually controlled by using programs written in programming languages, hence the programs need to parse and process UOML XML texts. If every application developer designs his/her own way of parsing and processing UOML XML texts in his/her programs, the workload of coding will increase significantly and the efficiency of coding will drop sharply. SUMMARY OF THE INVENTION [0004]The objective of the present invention is to provide a method for encapsulating Unstructured Operation Markup Language (UOML) into an Application Programming Interface (API) of a programming language so as to improve the development efficiency of docbase management system application developers. [0005]The method provided by the present invention for encapsulating UOML into an API includes: Read more: http://www.faqs.org/patents/app/20090187927#ixzz0xVS2ZUSr
1More
Google coding tool advances cloud computing | Deep Tech - CNET News - 0 views
-
Google has released a programming tool to help move its Native Client project--and more broadly, its cloud-computing ambitions--from abstract idea to practical reality. The new Native Client software developer kit, though only a developer preview version, is designed to make it easier for programmers to use the Net giant's browser-boosting Native Client technology. "The Native Client SDK preview...includes just the basics you need to get started writing an app in minutes," Google programmer David Springer said Wednesday in a blog post announcing the SDK, a week before the developer-oriented Google I/O conference. "We'll be updating the SDK rapidly in the next few months."
1More
Amazon's "Elastic Beanstalk": Cloud Computing For The Masses - Eric Savitz - Tech Musin... - 0 views
-
Developers simply upload their application, and Elastic Beanstalk automatically handles the deployment details of capacity provisioning, load balancing, auto-scaling, and application health monitoring," the company said this morning in announcing the service. "At the same time, with Elastic Beanstalk, developers retain full control over the [Amazon Web Services] resources powering their application and can access the underlying resources at any time." Customers pay nothing for Elastic Beastalk, paying instead for the resources used to run their applications. Elastic Beanstalk provides a quick way for developers to make use of a range of Amazon services - Amazon EC2 (for computing power), Amazon S3 (for data storage), Amazon Simple Notification Service, Elastic Load Balancing, and Auto-Scaling. "Elastic Beanstalk handles the provisioning and deployment of the infrastructure needed to run the application," the company said.
1More
Strobe Launches Game-Changing HTML5 App Platform | TechCrunch - 1 views
-
Today, Strobe Inc. is launching a new platform that helps developers build HTML5-based Web applications for desktops, smartphones and tablets, and centrally manage them from a single interface. The launch is a major leap forward in HTML5 app development. From one interface, teams can manage code (both test code and production code), configure the app's deployment across platforms (Web, Android, iOS, etc.), add additional services (social, push notifications, authentication, etc.), and even track analytics within an easy-to-use dashboard. In short, it's a comprehensive platform that makes building apps with Web technologies, like HTML5 and JavaScript, not just possible, but easy, straightforward and fast. The company was co-founded by Ruby on Rails Core Team member Carl Lerche, Ruby on Rails, jQuery and SproutCore Core team member Yehuda Katz, and Charles Jolley, formerly the JavaScript Frameworks Manager for Apple. At Apple, Jolley worked on Apple's Web products like MobileMe and iCloud. He's also the creator of the open source JavaScript framework, SproutCore, which powered Apple's Web services and is now a key part of the Strobe platform. In addition to SproutCore, Strobe also uses PhoneGap, the popular HTML5 app platform. PhoneGap lets developers author apps using Web technologies then deliver them in a native wrapper to the iTunes App Store, Android Marketplace and other app stores. It also happens to integrate nicely with SproutCore.
1More
shared by Gary Edwards on 12 Aug 09
- Cached
Microsoft's Answer to the Web Platform Threat? CHEAT!!!! - Microsoft Web Apps are actu... - 0 views
www.informationweek.com/...JSORXIUMXLBQE1GHOSKH4ATMY32JVN
web-apps microsoft msoffice silverlight Openweb
![](/images/link.gif)
-
For most of this decade, web developers have been suffering the shortcomings of Internet Explorer. Like 1998 limited HTML-CSS support. And nothing for the language of the Web - HTML+ :: HTML5, CSS3, SVG/Canvas and advanced JavaScript. That hasn't bothered Microsoft (NSDQ: MSFT) too much, because the company has historically focused on developing "real" applications that run only on Windows and don't use the browser as a platform. With the new Office web apps, many thought that Microsoft might actually have to experience the living nightmare that web app development can be. Yet the company has figured out a way to make things easier: cheat. MIcrosof thas figured out how to provide MSOffice as Web Apps, without having to use the language of the Web: HTML+. Instead, they use protpietary formats, protocols and interfaces to create an interesting dichotomy - a rich MS-Web, and a poor, 1998 Open-Web.
1More
OpenCandy's Pokki Brings Web Apps To The Desktop, With Style - 0 views
-
Pokki Web-to-Native App Framework..... excerpt: So what exactly is Pokki? It's a framework built on Chromium that allows developers to build basic applications using standard web technologies, but with a few key additions. First, these applications support nice notification tags in the menu bar (similar to iOS's badge system). They're also handy by design - click one, and it will pop up in a small window that you can use to access your Facebook wall, Gmail inbox, or whatever other application you've installed. Click outside of the Pokki, and it disappears. It's very lightweight. Pokki is initially offering a set of eight applications to users, including apps for Gmail, Facebook, Groupon, eBay, the WSJ, Living Social, and Twitter. That's a solid start, but today's launch is primarily about introducing developers to the Pokki SDK, which isavailable beginning today, and will let developers turn whatever website they like (provided it has an API) into a Pokki. Note that most of the Pokkis launching today were built in-house by SweetLabs. To use Pokki, users have to install the basic framework first, but this will come bundled with all Pokki apps - the company expects users will download a Pokki from one of their favorite sites, and then continue to add more using the integrated Pokki app browser. The apps are launching with support for Windows today, with Mac and Linux support coming down the line.
1More
MaidSafe - The New Decentralized Internet - 0 views
-
The New Decentralized Internet MaidSafe is a fully decentralized platform on which application developers can build decentralized applications. The network is made up by individual users who contribute storage, computing power and bandwidth to form a world-wide autonomous system. Read more... Calling Decentralized Application Developers How would you like to create the next Dropbox, Facebook, Google, LinkedIn, Twitter, Candy Crush, or secure email service? The SAFE network offers every developer the opportunity to create applications without any infrastructure costs and without any barrier to entry. Read more...
1More