Group items matching

in title, tags, annotations or url

Convert Content for Android OS Making your content mobile friendly is harder than it sounds. However, more tools are emerging to help companies create content for multiple platforms, from iPads to smartphones, across a variety of operating systems. Recently, AppsGeyser privately launched a web platform that allows you to convert any web content to an Android App. With AppsGeyser companies can create an Android app three ways: Grabbing any website content block or web widget Copying and pasting HTML code, JavaScript, AJAX or Flash Entering the URL of your website Nifty tool for instantly converting web site widgets into Android Apps.  Looks like a new category of tools to make legacy Web services mobile-ready.  Titanium

Amazon Releases Developer SDKs One interesting and important exception is Amazon's recent release of its Software Development Kits (SDK) for Google's Android and Apple's iOS. With these kits, developers are provided with tools that will simplify development of cloud applications stored on the Amazon Web Services cloud platform, or AWS. Developing apps that can use many of the already popular AWS cloud services offers many new opportunities for the developer community, especially due to its low-barrier-to-entry and affordability, enabling more developers with limited resources  to build and provision new mobile cloud services. The new SDK includes libraries that simplify handling of HTTP connections, request retries and error handling, which used to be complex and arduous. Integration of applications with several AWS cloud services, like the Simple Storage Service (S3), SimpleDB database, Simple Notification Service (SNS) and Simple Queue Service (SQN) will be much more accessible than before. For example, it's going to be interesting to see whether developers will build a viable messaging solution atop the AWS SNS service that can actually compete with mobile SMS services - which have been a long-time major cash-cow for many mobile network operators.

Although there are many open source CMSes available, we're going to focus on those that are based upon PHP. The following CMSes are thus PHP-based, and use a MySQL database. The advantages of using such a CMS include portability, support and a large developer base with frequent updates and improvements. We will discuss the following four CMSes: Drupal - a free open source content management system written in PHP and distributed under the GNU General Public License Joomla - an open source content management system platform for publishing content as a Model-view-controller (MVC) web application framework PHPNuke - a web-based automated news publishing and content management system based on PHP and MySQL Wordpress - an open source CMS, often used as a blog publishing application, and is the most popular blog software in use today

UBS analysts believe that the total market for AWS-type services will be between $5-to-$6 billion in 2010 and will eventually grow to $15-to-$20 billion in 2014. How they arrive at these numbers: * IDC says the total global cloud market in 2010 will be $22 billion and $55 billion in 2014. * IDC says the total servers and storage account for $5 billion-to-$6 billion in 2010 and $15-to-$20 billion in 2015.

First, what is a "cloud OS" and why should I want one? Actually, I don't even know if anyone calls it a "cloud OS", but I couldn't find a better generic term for something like ChromeOS. The basic idea is that apps and data all live on the Internet, which is has been renamed "The Cloud" since that sounds cooler, and your laptop or whatever is basically just a window into that cloud. If your laptop is stolen or catches fire or something, it's not a big deal, because you can just buy another one and nothing has been lost (except your money). Many people characterize this approach as using a "dumb terminal", but that's wrong. Your local computer can still do all kinds of smart computation and data manipulation -- it's just no longer the single point of failure. To me, the defining characteristic of cloud based apps is "information without location". For example, in the bad old days, you would install a copy Outlook or other email software on your PC, it would download all of your email to your computer, and then the email would live on that computer until Outlook corrupted its PST file and everything was lost. If you accidentally left your computer at home, or it was stolen, then you simply couldn't get to your email. Information behaved much like a physical object -- it was always in one place. That's an unnecessary and annoying limitation. By moving my email into "the cloud", I can escape the limitations of physical location and am able to reach it from any number of computers, phones, televisions, or whatever else connects to the Internet. For performance and coverage reasons, those devices will usually cache some of my email, but the canonical version always lives online. The Gmail client on Android phones provides a great example of this. It stores copies of recent messages so that I can access them even when there is no Internet access, and also saves any recent changes (such as new messages or changes to read state), but as soon as possible it sends those chang

Excellent explanation.  Uses the "stack" motif to explain everything having to do with cloud-computing

December 9th, 2010.  Good roll up.  Market is now said to be $1 Trillion in USA alone.  Google and Microsoft are fighting for BIG Federal contracts, thanks to the recent mandate that Cloud Computing be the first consideration for any software purchase.  Google drew first blood with a $8 B GSA contract.  Microsoft got the FDA contract.  And the BIG loser is IBM Lotus Notes - which lost both contracts!!!  Feds plan on spending $5 - $10 B to improve Cloud-computing security.  Guess all those Google and Microsoft contributions to Obama paid off.  

With the increased interest in cloud, software as a service (SaaS), and mobile computing, applications are jockeying across multiple networks, both in terms of how services are assembled, as well in how users in different environments access and respond to these critical applications. Indeed, cloud computing forces a collapse in the gaps between the former silos of private, public, and personal networking domains. Since the network management and governance tasks have changed and continue to evolve rapidly, so too must the ways in which solutions and technologies address the tangled networks environment we all now live and work in.

The General Services Administration made a bold decision to move its email and collaboration systems to the cloud.  This is a huge win for cloud-computing, but perhaps should have been expected since last week the Feds announced a new requisition and purchase mandate that cloud-computing had to be the FIRST consideration for federal agency purchases.  Note that the General Services Administration oversees requisitions and purchases for all Federal agencies!  This is huge.  Estimated to be worth $8 billion to cloud-computing providers. The cloud-computing market is estimated to be $30 Billion, but Gartner did not anticipate or expect Federal Agencies to embrace cloud-computing let alone issue a mandate for it.   In the RFP issued last June, it was easy to see their goals in the statement of objectives: This Statement of Objectives (SOO) describes the goals that GSA expects to achieve with regard to the 1. modernization of its e-mail system; 2. provision of an effective collaborative working environment; 3. reduction of the government's in-house system maintenance burden by providing related business, technical, and management functions; and 4. application of appropriate security and privacy safeguards. GSA announced yesterday that they choose Google Apps for email and collaboration and Unisys as the implementation partner. So what does this mean? What it means (WIM) #1: GSA employees will be using a next-generation information workplace. And that means mobile, device-agnostic, and location-agile. Gmail on an iPad? No problem. Email from a home computer? Yep. For GSA and for every other agency and most companies, it's important to give employees the tools to be productive and engage from every location on every device. "Work becomes a thing you do and not a place you go." [Thanks to Earl Newsome of Estee Lauder for that quote.] WIM #2: GSA will save 50% of the cost of email over five years. This is also what our research on the cost of email o

Excellent product release.  MarkLogic is trying to become the Google Search, Organize and Work for all things MSOffice.  Focus on MSOffice 2007 OOXML documents.

Quest Software, Inc. (QSFT 25.89, -0.08, -0.31%) today unveiled 11 technology predictions for 2011 based on results of its annual survey conducted at The Experts Conference (TEC) U.S., hosted earlier this year by Quest. Survey results were analyzed by Quest experts to extract key insights and compelling trends. Based on analysis of this year's TEC conference survey responses from in-the-trenches IT practitioners, as well as historical perspective gleaned from conducting annual surveys, Quest offers the following 11 predictions about key technology trends and practices. To download the complete description of the predictions or to view the full survey data, please visit

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

4 Pillars for Web Content Management Site & Content Optimization.  Excellent review of the basics of WCM - DMS. Billy Cripe from Oracle.

Excellent review of 9 CMS solutions going mobile.  Fascinating

good list of interviews with leading CMS providers

A while back I included the following as one of the areas of interest of the PDF/D Consortium: Structured Documents and Single Sourcing: improving round-trips to document softwareWhat did I mean by Structured Documents? For years Solid Documents has been converting PDF files to Word documents with a focus on retaining format and layout to allow customers to repurpose the content. While this is a great solution for a large amount of customers, it is not the only type of reconstruction that is interesting. PDF is by nature a "document" format: the layout is in the form of pages. Content also needs to exist in alternate formats like a continuously flowing stream. Use cases for continuously flowing content include:conversion to HTML to reflow for form factors other than "pages"conversion to content management systems where structure is more important than layout and formattingconversion for alternate readers for people with disabilities (text to speech, etc)Reconstruction for these use cases focuses more on the structure of the document than on the layout and formatting. For example, we need to take unstructured PDF files and recognize columns, tables, lists, headers and footers, etc. This allows us to organize the content in a logical structure. Ultimately, we'll recognize topics and sections too so that we can produce logical hierarchies from plain old non-tagged PDF files. One great example of where conventional PDF pages are not the most appropriate way to read a document are on small screens of handheld devices. For example, the typical Blackberry has a 3"x2" screen with a resolution something like 320x240 pixels.

According to a new Forrester report, though Microsoft Office continues to be a mainstay both in the enterprise and at home, developing concerns about productivity as they relate to mobile, cloud, and collaboration may bring a shift in enterprise behaviors.