Group items matching

in title, tags, annotations or url

Good interview but i'm looking for ways to short Box.net.  I left lots of sticky notes and highlights on this page - all of which are under the Visual Document list since i didn't have a Cloud Productivity list going.  I spend quite a bit of time studying Box.net, DropBox and a ton of other early Cloud sync-share-store operations while doing research for the Sursen SurDocs product.  Also MS-Live/Office/SkyDrive and Google Docs Collaboration.  No one has a good bead on a Cloud Productivity Platform yet.  But Microsoft and Google clearly know what the game is.  They even have a plan on how to get there.  Box.net, on the other hand is totally clueless.  What are these investors thinking?

MSOffice is now "Web ready".  The Office apps are capable of running HTML5-JavaScript apps based on a simple Web page model.  Think of this as the Office apps being fitted with a browser, and developers writing extensions to run in that browser using HTML5 and JavaScript.  Microsoft provides an Office.js library and, a developer "Web App/Page Creator"  Visual Basic toolset called "Napa" Office 365 Development Tools.  Lots of project templates. Key MSOffice apps are Word, Excel, PowerPoint and Outlook.  Develop for Office or SharePoint.  Apps can be hosted on any Web Server. excerpt: Microsoft Office 2013 Developer Environment with HTML5, XML and JavaScript.  Office.js library. "his documentation is preliminary and is subject to change. Published: July 16, 2012 Learn how to use apps for Office to extend your Office 2013 Preview applications. This new Office solution type, apps for Office, built on web technologies like HTML, CSS, JavaScript, REST, OData, and OAuth. It provides new experiences within Office applications by surfacing web technologies and cloud services right within Office documents, email messages, meeting requests, and appointments. Applies to:  Excel Web App Preview | Exchange 2013 Preview | Outlook 2013 Preview | Outlook Web App Preview | Project Professional 2013 Preview | Word 2013 Preview | Excel 2013 Preview  In this article What is an app for Office? Anatomy of an app for Office Types of apps for Office What can an app for Office do? Understanding the runtime Development basics Create your first app for Office Publishing basics Scenarios Components of an app for Office solution Software requirements"

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

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.

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.

Incredible.  Watch the videos then dive in.  Great on a iPhone or Android.  Put Qwiki in the same category as the visually-immersive technologies from TreeSaver, FlipBoard, Apple News, and the immersive Sports Illustrated iOS publication.

Is Intel right?  Is there a "compatibility-interoperability" problem between Windows RT Office (ARM) and legacy (x86) Windows MS Office productivity environments?  It seems to me that the entire reason iPAD, Android and other ARM based tablet systems want MSOffice and MSOffice Visual Document Viewers is exactly because they want and expect a high level of compat-interop with legacy Windows productivity workgroups and client/server systems. What's the truth?  And is there anything x86 providers like Intel and AMD can do about compat-interop and the unstoppable cloud-mobility revolution? excerpt: The Asus tablet has a quad-core Tegra 3 processor from Nvidia. Windows RT comes preloaded with Office 15, a group of widely used productivity applications. Microsoft has said it had to re-engineer Windows RT to deal with expectations for ARM based devices, which include all-day connectivity and low power consumption. The tablet also has an 8-megapixel camera at the rear with LED flash, and a 2-megapixel camera at the front. It has 2GB of RAM, 32GB of storage, Wi-Fi and Bluetooth 4.0. Intel has already started the war of words against ARM around Windows 8, with Intel's CEO Paul Otellini saying that ARM devices will be incompatible with existing Windows applications and drivers. But analysts have said that Windows RT devices will likely be attractive to users who have few ties with legacy Windows PCs. Low prices could also attract users to Windows on ARM devices.

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.

Android Essentials: Dolphin Browser HD still supports gestures, multiple tabs, and browser extensions, but now includes Webzine: a Flipboard-like, magazine layout style for reading web pages.   Very slick!  But there is no way to add RSS feeds?  The new Scribd "Float"  webzine is also lacking RSS.  Since 95% of my news and info management comes from RSS, this is a problem!

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.

Advanced XML, HTML5, XHTML CSS3 editing with conversion to PDF, PDF/A and SVG.  Excellent stuff.  Good Case Studies.  Lots of tools and document source code examples.

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 ).

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

Adobe Systems has proposed a standard that could make it easier to create Web pages with fancy layouts seen more often in magazines. The company proposed a technology it calls CSS Regions (PDF) yesterday to the World Wide Web Consortium, which standardizes the Cascading Style Sheets technology widely used to control formatting on Web pages. Adobe also described the technology at a CSS Working Group meeting in Silicon Valley. "This proposal is intended to support sophisticated, magazine-style layouts using CSS," said Arno Gourdol, director of engineering for runtime foundation at Adobe, in a mailing list posting.

But it was the Russians who hacked the 2016 U.S. election. Really.