Group items tagged

Open Source framework for building visually-immersive mobile ready magazines in HTML5-CSS3-JavaScript. excerpt:  Pugpig is an open source framework that enables you to publish HTML5 content in the form of a magazine, book or newspaper to iPhone and iPad devices. It's slick and feels like you are using a native app (we tested the it on the iPad) Pugpig is an HTML reader for iOS. It's basically a hybrid - part native application, part web app, designed to prove that you can have an HTML-based app that feels like it's native. Your app sits on top of the Pugpig framework. It can be customized and extended. For example, you can link to your own data source, change the navigation and look and feel. It can also be multi-lingual - for example, the sample app I tested leverages the AJAX API for the Microsoft Translator. Additional Pugpig benefits are its low memory footprint and ability to store a lot magazine/newspaper editions within the device, for easy offline viewing. You can offer your app in either the App Store or the new iOS 5 Newsstand (integration with the framework is in progress now).

excerpt: The trend in Office development is the migration of solutions away from in-application scripted processing toward more data-centric development. Of course this is a primary purpose of Open XML, and it is great to see the amount of activity in this area. We've seen customers scripting Word in a server environment to batch process / print documents or for other automation tasks. In reality Word isn't built to do that on a large scale, it is better to work directly against the document rather than via the application whenever possible. The Open XML SDK unlocks a "whole nuther" environment for document processing, and gets you out of the business of scripting client apps on servers to do the work of a true server application (not to mention the licensing problems created by installing Office on a server). comment:  Gray makes a very important point here.  The dominance of the desktop based MSOffice Productivity Environment was largely based the embedded logic driving "in-process" documents that was application and platform (Win32 API) specific.  Tear open any of these workgroup-workflow oriented compound documents and you find application specific scripts, macros, OLE, data bindings, security settings and other application specific settings.  These internal components are certain to break whenever these highly interactive and "live" compound documents are converted to another format, or application use.  This is how MSOffice documents and the business processes they represent become "bound" to the MSOffice Productivity Environment. What Gray is pointing to here is that Microsoft is moving the legacy Productivity Environment to an MSWeb based center where OpenXML, Silverlight, CAML, XAML and a number of other .NET-WPF technologies become the workgroup drivers.  The key applications for the MS WebStack are Exchange/SharePoint/SQL Server.  To make this move, documents had to be separated from the legacy desktop Productivity Environment settings. Note th

Excellent presentation discussing the AtomPub protocol as a key Open Web API . 52 slides, and everyone worth some study.

Dion Hinchcliffe has an excellent article casting Google Wave as an Enterprise game-changer. He walks through Wave first, and then through some important enterprise features: ".....to fully understand Google Wave, one should appreciate the separation of concerns between the product Google is offering and the protocols and technologies behind it, which are open to the Web community: Google Wave has three layers: the product, the platform, and the protocol: The Google Wave product (available as a developer preview) is the web application people will use to access and edit waves. It's an HTML 5 app, built on Google Web Toolkit. It includes a rich text editor and other functions like desktop drag-and-drop (which, for example, lets you drag a set of photos right into a wave). Google Wave can also be considered a platform with a rich set of open APIs that allow developers to embed waves in other web services, and to build new extensions that work inside waves. The Google Wave protocol is the underlying format for storing and the means of sharing waves, and includes the "live" concurrency control, which allows edits to be reflected instantly across users and services. The protocol is designed for open federation, such that anyone's Wave services can interoperate with each other and with the Google Wave service. To encourage adoption of the protocol, we intend to open source the code behind Google Wave.

Join your on-premises data sources with the web without coding. Feed data from/to APIs, mashups, and mashup building tools.

Overview: Aspose.Word is a powerful .NET component that allows any .NET application to work with Microsoft Word documents without utilizing Microsoft Word and Office Automation. Aspose.Word supports a wide array of features including new document creation, document manipulation, powerful mail merge abilities, exporting to multiple formats (DOC, PDF & HTML) and much, much more. Aspose.Word is truly the most affordable, fastest, feature rich Word component on the market. Aspose.Word application programming interface (API) is powerful and easy to use at the same time. Classes, properties and method names are easy to remember and understand: for example, Document represents a Word document, DocumentBuilder is responsible for building a document dynamically, and so on. Although this guilde provides many code samples, intuitively understandable interface allows you create working document producing applications having minimal knowledge of C# or VB.NET and Microsoft Word features. $899

Moving the Point of Assembly Kudos to Zoho. Their efforts remind me of the early days of the Microsoft Productivity Environment where core MSOffice editors expanded their reach through DDE, OLE, rich copy/paste, data binding, merged content and data, VBA scripting and the infamous recorder, and a developer API that meshed platform and productivity apps so deeply into end user information that the binding of business processes to the MOPE is proving near impossible to break. Even for years after the fact. A business ecosystem for client/server was born back in the early 90's, with Microsoft continuing on to own entirely the client side of the equation.

The stripped down "HTML Author" version of the 900 page HTML5 specification.   The bulk of the spec targets "implementers" such as browsers and editors.  It's very exacting and should provide for an unprecedented universal interoperability. Introduction:  This specification provides the details necessary for producers of HTML content to create conformant documents, and for others to wcheck the conformance of existing documents. It is designed: to describe the syntax and structure of the HTML language to describe the semantics of HTML elements and their attributes (that is, to describe what the elements and attributes represent) to be clear and unambiguous to be as concise and readable as possible Certain purposes are intentionally out of scope for this specification; in particular, it: does not provide any conformance criteria for HTML consumers; in particular, it does not attempt to define how Web browsers and other user agents process documents does not define any APIs related to processing of HTML content by HTML consumers. does not attempt to be a tutorial or "how to" authoring guide

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

Microsoft claims that WordPerfect fell into disfavor because it came late to Windows; Novell, which owns the WordPerfect Office technology (after selling the rest of the company to Corel), claims that Microsoft unfairly used its knowledge of Windows APIs to give itself a competitive advantage. There's one very solid piece of evidence in Novell's favor - a 1994 email from Bill Gates that states: "I have decided that we should not publish these extensions. We should wait until we have away to do a high level of integration that will be harder for likes of Notes, WordPerfect to achieve, and which will give Office a real advantage . . . We can't compete with Lotus and WordPerfect/Novell without this."

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.

Haven't yet explored to see what's beneath the marketing hype. And I'm less than excited about the Skype with its NSA tendrils being the vehicle of audio translations of human languages. But given the progress in: [i] automated translations of human texts; [ii] audio screenreaders; and [iii] voice-to-text transcription, this is one we saw coming. Slap the three technologies together and wait until processing power catches up to what's needed to produce a marketable experience. After all, the StarTrek scriptwriters saw this coming too.   Ray Kurzweil, now at Google, should get a lot of the pioneer credit here. His revolutionary optical character recognition algorithms soon found themselves redeployed in text-to-speech synthesis and speech recognition technology. From Wikipedia: "Kurzweil was the principal inventor of the first CCD flatbed scanner, the first omni-font optical character recognition, the first print-to-speech reading machine for the blind, the first commercial text-to-speech synthesizer, the first music synthesizer Kurzweil K250 capable of recreating the grand piano and other orchestral instruments, and the first commercially marketed large-vocabulary speech recognition." Not bad for a guy the same age as my younger brother. But Microsoft's announcement here may be more vaporware than hardware in production and lines of executable code. Microsoft has a long history of vaporware announcements to persuade potential customers to hold off on riding with the competition.  And the Softies undoubtedly know that Google's human language text translation capabilities are way out in front and that the voice to text and text to speech API methods have already found a comfortable home in Android and Chromebook. What does Microsoft have that's ready to ship if anything? I'll check it out tomorrow. 

Secure alternatives to current social media giants.

Google throws in the towel on desktop search, just as Microsoft somehow reached into my WinXP Pro (which never runs with automatic updates turned on) and killed the file search functionality, replaced by a message that file search is no longer supported in Explorer 6, with an invitation to upgrade MSIE or use Bing. As though I would ever let MSIE outside my firewall! 

Wow.  Why fight over the editing of Wikiword when you can make up your own history?  The Microsoft Office - SharePoint Blog team is busy trying to reshape history from the inside out.   This bookmark is going to require a ton of highlights and comments.