Group items tagged

Florian's docx reader is now available for iOS high-touch devices.  Extreme fidelity for reading/viewing native docx documents.  I hope he is working on a Chrome eXtension version!!!!   The world urgently needs WEB ready - Web view-able docx business documents.   Conversion of docx to HTML sucks.   The ultimate Visual Document system would enable users to work entirely in the native document format of the authoring system.  Florian's reader can do this, but so far he's limited to iOS.  Seems to me that the exploding sync-share-store market sector (DropBox, Box, Egnyte, SugarSync, etc) really need native document viewers that are HTM5 browser ready. " Naverage Reader HD Features: ... Designed for business documents. View your business document in an unbelievable quality. .....Tracked Changes Support. View text insertions, text deletions and comments on your iPad. ..... Layout Fidelity. Headers and footers, footnotes, tables, paragraph numbering, frames, graphics layout optimized for business documents. .....Font Embedding. Corporate fonts on your iPad. .docx-compatible. Compatible with the new Microsoft® Word format (.docx)."

Web site for Andreessen Horowitz VC. List of blogs for general partners. The reason for linking into a16z is the $11.2 Million they invested in Meteor! Meteor is awesome. My guess is that Meteor will provide a very effective Cloud platform to replace or extend the Windows Client/Server business productivity platform. Many VC watchers are wondering if a16z can recover the investment? Say what? IMHO this is for all the marbles. Platform is everything, and Cloud Computing is certain to replace Client/Server over time. Meteor just move that time frame from a future uncertainty to NOW. The Windows Productivity Platform has dominated Client/Server computing since the introduction of Windows 4 WorkGroups (v3.11) in 1992. Key technologies that followed or were included in v3.11 were DDE, OLE, MAPI, ODBC, ActiveX, and Visual Basic scripting - to name but a few. Meteor is an open source platform that hits these technologies directly with an approach that truly improves the complicated development of all Cloud based Web Apps - including the sacred Microsoft Cow herd of client/server business productivity apps. Meteor nails OLE and ODBC like nothing i've ever seen before. Very dramatic stuff. Maybe they are nailing shut the Redmond coffin in the process - making that $11.2 Mill a drop in the bucket considering the opportunity Meteor has cracked open. The iron grip Microsoft has on business productivity is so tight and so far reaching that one could easily say that Windows is the client in Client/Server. But it took years to build that empire. With this investment, Meteor could do it in months. Compound documents are the fuel in Windows business productivity and office automation systems. Tear apart a compound document, and you'll find embedded logic for OLE and ODBC. Sure, it's brittle, costly to develop, costly to maintain, and a bear to distribute. Tear apart a Meteor productivity service and you'll find the same kind of OLE-ODBC-Script

Although you need Chrome for the new Google Docs pagination feature, the key here is that gDocs now supports the CSS3 pagination module!   excerpt: Today, we're doing another first for web browsers by adding a classic word processing feature-pagination, the ability to see visual pages on your screen. We're also using pagination and some of Chrome's capabilities to improve how printing works in Google Docs. Native Printing: Pagination also changes what's possible with printing in modern browsers. We've worked closely with the Chrome team to implement a recent web standard, CSS3, so we can support a feature called native printing. Before, if you wanted to print your document we'd need to first convert it into a PDF, which you would then need to open and print yourself. With native printing, you can print directly from your browser and the printed document will always exactly match what you see on your screen.

Move over FlipBoard and QWiki and meet Needle.  The emerging market space for automating the process of collecting Web information to analyse, re-purpose and re-publish is getting crowded.   Needle is designed to: acquire data from multiple sources:  A simple tagging process quickly imports structured data from complex websites, XML feeds, and spreadsheets into a unified database of your design.merge, deduplicate and cleanse: Needle uses intelligent semantics to help you find and merge variant forms of the same record.  Your merges, edits and deletions persist even after the original data is refreshed from its source. merge, deduplicate and cleanse: Needle uses intelligent semantics to help you find and merge variant forms of the same record.  Your merges, edits and deletions persist even after the original data is refreshed from its source. build and publish custom data views: Use Needle's visual UI and powerful query language to configure exactly your desired view of the data, whether as a list, table, grid, or map.  Then, with one click, publish the data for others to see, or export a feed of the clean data to your own local database. Flipboard is famous for the slick republishing / packaging process focused on iOS devices.  Allows end users to choose sources. QWiki takes republishing to the extreme, blending voice over (from wikipedia text) with a slide show of multimedia information.  Edn user does not yet have control and selection of information sources with QWiki. The iOS Sports Illustrated app seems to be the starting point for "immersive webzines", with the NY Times close behind.  Very very slick packaging of basic Web information. Flipboard followed the iOS re-publishing wave with an end-user facing immersive webzine packaging design.  And now we have Needle. Still looking for a business document FlipBoard, where a "project" is packaged in a FlipBoard immersive container.  The iPack would be similar to an iPUB book with the added featur

Note: On April 12th, 2011 Needle was acquired by Google.

This is a must see discussion!!!! Especially if you've seen the Ted Nelson series of talks at Google. (Ted Nelson invented Hypertext, and continues to promote the XANDU view of highly graphical and interactive computing based on an advanced "digital" document model). Jen-Hsu fully embraces the sugarplum document model, dissing i a gentle way the legacy of x86 text-number processing designed to replace typewritters and calculators to produce the same printed document.

Nvidia has also announced an ION based board optimized for the Google Android Mobile-Telecommunications OS!

If you think this isn't a tool for some very serious research, check the short descriptions of the modules here. https://github.com/transparencytoolkit I'll be installing this and doing some test-driving soon. From the source files, the glue for the tools seems to be Ruby on Rails. The development roadmap linked from the last word on this About page is also highly instructive. It ranks among the most detailed dev roadmaps I have ever seen. Notice that it is classified by milestones with scheduled work periods, giving specific date ranges for achievement. Even given the inevitable need to alter the schedule for unforeseen problems, this is a very aggressive (not quite the word I want) development plan and schedule. And the planned changes look to be super-useful, including a lot of "make it easier for the user" changes.   

Good video demonstration of Mailbox, the new iOS app that will be released in the future for Android and the desktop.  Excellent Productivity issue discussion, as the founder of Mailbox explains what they are trying to do.  An excellent video coupled with a great interview and explanation of mobile productivity.   excerpt: "He asked himself, "What are people trying to do with email? What are the goals?" He started with Apple's Mail app for iPhone, which people were already familiar with, and injected elements of to-do apps he liked, since increasingly people are using their inboxes as to-do lists. The point was to create an experience that was distinctly mobile - an app that would let you take meaningful action while you're in line at Starbucks. Mailbox needed to intelligently display emails so you can parse and deal with them as quickly as possible. Most email apps require two or three taps to archive an email - perhaps the most common action you take on emails while you're mobile - but Mailbox only requires one: a swipe to the side. "Our biggest a-ha moment was when we realized that the primary use case of email on the phone is triage," Underwood says. Mailbox takes the reality of people using their inboxes as to-do lists and and builds on what Mail and Sparrow did right (push notifications and nicely threaded messages, respectively). SNOOZING MESSAGES To conserve space, Mailbox turns email conversations into SMS-like bubbles, which lets you quickly fly through an entire email chain. Once you've read a message, it shrinks in size so skimming threads is a snap. "Email will feel more and more like chat, and we'll continue to iterate towards that," Underwood says. "EMAIL WILL FEEL MORE AND MORE LIKE CHAT, AND WE'LL CONTINUE TO ITERATE TOWARDS THAT." Mailbox introduces a few other gestures, such as a swipe to the left that lets you "snooze" a message to be reminded about later. You can choose between a few snooze options: Later Today, This Eveni

Interesting, but do they have a plan to implement ODBC at the Cloud level?  It's one thing to provide connectivity, exploration and analysis to non Cloud data and transaction servers.  And another to connect the data feeds into next generation compound documents.  Seems to me this is an effective first step, but the value remains elusive.  Left a comment on this page. exerpt: The startup's offering, which has not been released yet, will connect to data stored in databases as well as the web and other sources, and adds a visual discovery component to make it easy for users to parse through this data and make sense of the information. The beauty of ClearStory is that it allows businesses to analyze internal and publicly available data at the same time and make this data easy for the masses to understand.

White paper from Intel discusses HTML5 and the future of computing. Intro: Computer programmers have been grappling with cross-platform issues since there was a second platform. Since then, the number of issues has rapidly increased. Today's developers can target at least four operating systems (plus their fragments), running on devices with all shapes, sizes, resolutions, persistence levels, input methods, carrier networks, connection speeds and states, UI conventions, app stores, deployment and update mechanisms, and on and on. Many of the world's developers once looked to Java* as the shining knight of cross-platform development. Indeed, the structured language of Sun* (and now Oracle) continues to solve many cross-platform issues. But it also introduces obstacles, not the least of which is a class structure that heavily burdens even the tiniest of program functions. Java's heft grew still more burdensome as developers turned to the browser for app delivery; Java applets are black boxes that are as opaque to the browser as the language is closed to the developer (with all due deference to the JCP). Around the same time Java was fuelling the browser wars, a like-named interpreted language was beginning to emerge. First called Mocha, later LiveScript, and finally JavaScript*, the language proved more useful than Java in some ways because it could interact with the browser and control content display using HTML's cascading style sheets (CSS). JavaScript support soon became standard in every browser. It is now the programming language of HTML5, which is currently being considered by the World Wide Web Consortium as the next markup-language standard. To better understand HTML5-why it is where it is and where it's going- Intel® Software Adrenaline turned to Moh Haghighat, a senior principal engineer in the Developer Products Division of Intel's Software and Services Group. Moh was the technical lead from Intel's side on the first JavaScript

June 29, 2010 Dear College or University President: We write to express concern on the part of the Department of Justice and the Department of Education that colleges and universities are using electronic book readers that are not accessible to students who are blind or have low vision and to seek your help in ensuring that this emerging technology is used in classroom settings in a manner that is permissible under federal law. A serious problem with some of these devices is that they lack an accessible text-to-speech function. Requiring use of an emerging technology in a classroom environment when the technology is inaccessible to an entire population of individuals with disabilities - individuals with visual disabilities - is discrimination prohibited by the Americans with Disabilities Act of 1990 (ADA) and Section 504 of the Rehabilitation Act of 1973 (Section 504) unless those individuals are provided accommodations or modifications that permit them to receive all the educational benefits provided by the technology in an equally effective and equally integrated manner. ... The Department of Justice recently entered into settlement agreements with colleges and universities that used the Kindle DX, an inaccessible, electronic book reader, in the classroom as part of a pilot study with Amazon.com, Inc. In summary, the universities agreed not to purchase, require, or recommend use of the Kindle DX, or any other dedicated electronic book reader, unless or until the device is fully accessible to individuals who are blind or have low vision, or the universities provide reasonable accommodation or modification so that a student can acquire the same information, engage in the same interactions, and enjoy the same services as sighted students with substantially equivalent ease of use. The texts of these agreements may be viewed on the Department of Justice's ADA Web site, www.ada.gov. (To find these settlemen

Viewing and printing of documents.  Support for PDF, RTF, RTFD, iWork, MSOffice (subject to iOS compatibility), Web archives, HTML, text, source code, and standard iOS multi media.  No discussion yet as tho whether or not Avatron can support Visual fixed/flow viewing of these supported formats. Some interesting support for mounting remote file servers - cloud storage systems like DropBox, Box.net , FTP and secure HTTPS. No WebDav.   Seems to be struggling to make that cross-over from iOS device to desktop to cloud-computing connectivity.

Move over Flipboard, Push Pop and TreeSaver.  Here comes OnSwipe.  Packaging a Web site for a highly interactive and mobile world just got easier. excerpt: OnSwipe does something web developers should have been racing to accomplish ever since the iPad was first unveiled: it makes a website -- any website -- into a tablet-friendly experience. (It's already available to everyone who publishes their blog on Wordpress.com.) It uses HTML5 to make a site feel like an app, even though it's running in the browser. Onswipe points to a future of tablet media delivery that is incredibly simple, even boring: Websites that are designed to look good on tablets. Given the history of creating alternate designs for sites in order to make them mobile-friendly, why anyone ever imagined it would be otherwise is baffling. Probably, it was wishful thinking. IPad magazine app sales are tanking. Media aggregation apps like Flipboard and Zite are re-atomizing publishers' content into pleasurable, full-screen, mostly ad-free experiences. The great do-over that tablets were to represent for publishers like Condé Nast -- a chance to put the free-content genie back in the bottle, and charge for admission -- appears to have gone bust. Onswipe and the startups that will inevitably follow in its wake are the final nail in the coffin of the dream of appification of magazines and other media content

Another HTML5 Application Platform for Cloud Computing.  Provides secure data connections to existing business systems and workflows.  Not an Open Web Platform. summary: Mobile Helix is an enterprise application and data security platform provider focused on enabling unrestricted enterprise productivity. We are redefining endpoint computing by evolving and extending existing IT infrastructure and standards rather than reinventing them. At our core are three fundamental principles that are at the center of everything that we do: 1) we are application- and data-centric - we embrace the blurring lines between phones, tablets and laptops, permitting IT to relinquish control of the endpoint device entirely and embrace a bring-your-own-anything policy; 2) we provide unmatched yet unobtrusive security for sensitive corporate data by intelligently securing the data rather than the devices; and 3) simplicity is embedded into the DNA of our products, our designs and our communications. Our solution, Mobile Helix Link, is the industry's first pure HTML5 platform that combines unparalleled data security, a unique HTML5 application development and delivery platform, and breakthrough patent-pending performance enhancement technology. 

The ultimate goals are to have a computer-viewable display format (XHTML) and at least one printable format. We may also want a post-processing editable format. Our farthest target as yet is XHTML, styled by CSS. For a printed format, one expects a complete target to be able to produce a document that has features which one would expect of any Siddur: page numbers, table of contents, footnotes, side notes, header/page title, etc. XHTML originated as a computer-display format, not a publishing format. Even when combined with CSS 2.1, it does not support some of the features above (with some hacking, side notes, a static header/footer, and page numbers are possible, but it is still missing vital features). CSS3 is more publishing friendly, when implemented, will make life much easier. Until then, we will have to be a bit more creative. The following is a list of software libraries and formats that can help us increase the range of formats that we can target. XSLT or Java are the preferred languages, since the rest of our chain is in XSLT, and driven by Saxon, which is written in Java, allowing us to bundle the entire chain in a portable program, which can be distributed ( with the added bonus of being able to be distributed within a web browser as an applet ).