Group items tagged

Quick LinksGet a TrialEnterprise On DemandEnterprise On PremiseFAQHelpContact UsWhy Adeptol?Document SupportSupport for more than 300 document types out of boxNot a Virtual PrinterMultitenant platform for high end document viewingNo SoftwaresNo need to install any additional softwares on serverNo ActiveX/PluginsNo plugins or active x or applets need to be downloaded on client side.Fully customizableAdvanced API offers full customization and UI changes.Any OS/Any Prog LanguageInstall Adeptol Server on any OS and integrate with any programming language.AwardsAdeptol products receive industry awards and accolades year after year  View a DemoAttend a WebcastContact AdeptolView a Success StoryNo ActiveX, No Plug-in, No Software's to download. Any OS, Any Browser, Any Programming Language. That is the Power of Adeptol. Adeptol can help you retain your customers and streamline your content integration efforts. Leverage Web 2.0 technologies to get a completely scalable content viewer that easily handles any type of content in virtually unlimited volume, with additional capabilities to support high-volume transaction and archive environments. Our enterprise-class infrastructure was built to meet the needs of the world's most demanding global enterprises. Based on AJAX technology you can easily integrate the viewer into your application with complete ease. Support for all Server PlatformsCan be installed on Windows   (32bit/64bit) Server and Linux   (32bit/64bit) Server. Click here to see technical specifications.Integrate with any programming languageWhether you work in .net, c#, php, cold fusion or JSP. Adeptol Viewer can be integrated easily in any programming language using the easy API set. It also comes with sample code for all languages to get you started.Compatibility with more than 99% of the browsersTested & verified for compatibility with 99% of the various browsers on different platforms. Click here to see browser compatibility report.More than 300 Document T

Well, not quite.  More IBM happy talk about interoperability and easy document interchange.  While i agree with the static versus interactive - collaborative document perspective, it's far more complicated. Today we have a world of "native"  docs and "visual" docs.   Native docs are bound to their authoring productivity environment, and are stubbornly NOT interchangeable.  Even for ODF and OOXML formats. Visual documents are spun from natives, and they are highly interchangeable, but interactively limited.  They lack the direct interaction of native authoring environments.  The Visual document phenomenon starts with PDF and the virtual print driver.  Any authoring application(s) in a productivity environment can print a PDF using the magic of the virtual print driver.   In 2008, when ISO stamped PDF with "accessibility tags", a new, highly interactive version of PDF was offically recognized.  We know this as "Tagged PDF".  And it has led the sweeping revolution of wide implementation of the paperless transaction process. The Visual Document phenomenon doesn't stop there.  The highly mobile WebKit revolution ushered in by the 2008 iPhone phenomenon led to wide acceptance of highly interactive and collaborative, but richly visual versions of SVG and HTML5-CSS3-JSON-JavaScript documents. Today we have SVG-HTML+ type visually immersive documents spun out of Server side publication presses such as FlipBoard, Cognito cComics, QWiki, Needle, Sports Illustrated, Push Pop Press, and TreeSaver to name but a few.   Clearly the visually immersive category of documents is exploding, but not for business - productivity documents.  Adobe has proposed a "CSS Regions" standard for richly immersive layout that might change that.  But mostly i think the problem for business documents, reports and forms is that they are "compound documents" bound to desktop productivity environments and workgroups. The great transition from desktop/workgroup productivity environme

The king of clicks returns!  No doubt there was a time when the mere mention of ODF and the now legendary XML "document" format wars with Microsoft could drive click counts into the statisphere.  Sorry to say though, those times are long gone. It's still a good story though.  Even if the fate of mankind and the future of the Internet no longer hinges on the outcome.  There is that question that continues defy answer; "Did Microsoft win or lose?"  So the mere announcement of supported formats in MSOffice XX is guaranteed to rev the clicks somewhat. Veteran ODF clickmeister SVN does make an interesting observation though: "The ironic thing is that, while this was as hotly debated am issue in the mid-2000s as are mobile patents and cloud implementation is today, this news was barely noticed. That's a mistake. Updegrove points out, "document interoperability and vendor neutrality matter more now than ever before as paper archives disappear and literally all of human knowledge is entrusted to electronic storage." He concluded, "Only if documents can be easily exchanged and reliably accessed on an ongoing basis will competition in the present be preserved, and the availability of knowledge down through the ages be assured. Without robust, universally adopted document formats, both of those goals will be impossible to attain." Updegrove's right of course. Don't believe me? Go into your office's archives and try to bring up documents your wrote in the 90s in WordPerfect or papers your staff created in the 80s with WordStar. If you don't want to lose your institutional memory, open document standards support is more important than ever. "....................................... Sorry but Updegrove is wrong.  Woefully wrong. The Web is the future.  Sure interoperability matters, but only as far as the Web and the future of Cloud Computing is concerned.  Sadly neither ODF or Open XML are Web ready.  The language of the Web is famously HTML, now HTML5+

excellent comparison between Amazon S3 champion, DropBox, and Rackspace champion JungleDisk.  DropBox kicks ass.  Again.  Amazing. The stages of Cloud Document / Content Management Stack: ......... Backup-restore ........... backup-restore-store .............. backup-store-share ......... sync-share-store ............. sync-share-store-collaborate   (wikiWORD-SPoint) ......... Visual Document Portfolio DropBox has moved the industry to the sync-share-store level.  Collaboration remains a mystery to most, relying on Google Docs or Zoho (Rackspace). Google Cloud Connect can match DropBox for ease and reliability at the sync-share-store level.  MS-Live/Azure/SkyDrive however fails miserably at this level. The problem with Google Collaboration is that it breaks the Native Documents when converting to the Google collaboration format.  GCC (Google Cloud Connect) does store the original Native document, but does not keep track of revisions to the native!  Advantage DropBox! DropBox however does not have collaboration. The Visual Document Portfolio model is a design that saves the Native document to a Cloud Folder, and the system provides all visual representations on demand from that Native.  A Visual representation would be PDF, SVG (fixed), HTML (flow), ePUB or an HTML5 immersive visual representation packaged as a webzine.

Good discussion, but it really deserves a more in-depth thrashing.  The basic concept is that a perfect storm of mobility, cloud-computing and HTML5-JavaScript has set the stage for a major, massive shift in application development.  The shift from C++ to Java is now being replaced by a greater shift from Java and C++ to JavaScript-JSON-HTML5. Interesting, but i continue to insist that the greater "Perfect Storm" triggered in 2008, is causing a platform shift from client/server computing to full on, must have "cloud-computing".   There are three major "waves"; platform shifts in the history of computing at work here.  The first wave was "Mainframe computing", otherwise known as server/terminal.  The second wave was that of "client/server" computing, where the Windows desktop eventually came to totally dominate and control the "client" side of the client/server equation. The third wave began with the Internet, and the dominance of the WWW protocols, interfaces, methods and formats.  The Web provides the foundation for the third great Wave of Cloud-Computing. The Perfect Storm of 2008 lit the fuse of the third Wave of computing.  Key to the 2008 Perfect Storm is the world wide financial collapse that put enormous pressure on businesses to cut cost and improve productivity; to do more with less, or die.  The survival maxim quickly became do more with less people - which is the most effective form of "productivity".  The nature of the collapse itself, and the kind of centralized, all powerful bailout-fascists governments that rose during the financial collapse, guaranteed that labor costs would rise dramatically while also being "uncertain".  Think government controlled healthcare. The other aspects of the 2008 Perfect Storm are mobility, HTML5, cloud-computing platform availability, and, the ISO standardization of "tagged" PDF.   The mobility bomb kicked off in late 2007, with the introduction of the Apple iPhone.  No further explanation needed :) Th

Nvidia chief executive Jen-Hsun Huang is on a mission to get graphics chips into everything from handheld computers to smart phones. He expects, for instance, that low-cost Netbooks will become the norm and that gadgets will need to have battery life lasting for days. Holding up an Ion platform, which couples an Intel low-cost Atom processor with an Nvidia integrated graphics chip set, he said his company is looking to determine "what is the soul of the new PC." With Ion, Huang said he is prepared for the future of the computer industry. But first, he has to deal with Intel. Good interview. See interview with Charlie Rose! The Dance of the Sugarplum Documents is about the evolution of the Web document model from a text-typographical/calculation model to one that is visually rich with graphical media streams meshing into traditional text/calc. The thing is, this visual document model is being defined on the edge. The challenge to the traditional desktop document model is coming from the edge, primarily from the WebKit - Chrome - iPhone Community. Jen-Hsun argues on Charlie Rose that desktop computers featured processing power and applications designed to automate typewritter (wordprocessing) and calculator (spreadsheet) functions. The x86 CPU design reflects this orientation. He argues that we are now entering the age of visual computing. A GPU is capable of dramatic increases in processing power because the architecture is geared to the volumes of graphical information being processed. Let the CPU do the traditional stuff, and let the GPU race into the future with the visual processing. That a GPU architecture can scale in parallel is an enormous advantage. But Jen-Hsun does not see the need to try to replicate CPU tasks in a GPU. The best way forward in his opinion is to combine the two!!!

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

Incredible project exploring new methods of story telling that make full use of an emerging interactive, graphical and multimedia rich, extraordinarily visual Web platform.  Awesome use of Web technology and a great story to boot!   While the Snow Fall Project is hardly the first Visual Document, it's truly a landmark effort.  Hopefully the business process and systems editing tools for Web based Visual Productivity will not be far behind simple Visual Web publication tools. Marbux viewed the source code and pointed out the great efforts that the NY Times had gone to to provide cross browser compatibility.  That in turn reminded me just how close the world came to having Microsoft seize the Web and take control of its future.  A very close call if ever there was one.  Many thanks to Marc Andresssen and the Netscape investors for their heroic efforts to stop Bill Gates and his Microsoft monopoly.

"You have to think that the addition of apps to Office 365 is the continuation of the evolution of documents from static entities that only change when you change them, to living creations that that can update themselves. And by giving documents apps, Microsoft essentially is transforming documents into apps … all the while and not incidentally giving you, me, and any Joe Blow Nonprogrammer the ability to build things that only short years ago would have required extensive development. Not only is Microsoft is making office productivity tools more like the web, it's giving us the ability to create mashups of data and analysis and visualization on the fly. "

Recently the Rocketman and i have been arguing about webkit/Chromium DOM capabilities and limitations; like the failure to fully implement CSS3! Especially missing is support for CSS3 page layout / page break innovations. I realized that i didn't have a good understanding of browser DOM - client side issues, and came across this interesting post from Dave Ward concerning DOM and jQuery.
The core issue behind my discussions with the Rocketman have to do with creating a DOM view from OpenXML and ODF documents, and then passing that view to the webkit/Chromium engine. So we weren't all that interested in cross browser support or in how IE8 handles DOM-JavaScript. Dave Ward however not only provides a good discussion about DOM-JavaScript and the importance of jQuery as a force of interoperability, he also points out that Microsoft supports jQuery - including direct support within Visual Studio!
".....Though JavaScript itself is a great programming language, the document object model (DOM) can be a web developer's worst nightmare.  The DOM is a method through which browsers expose an interface allowing JavaScript code to manipulate elements, handle events, and perform other tasks related to a document within the browser.  While almost every browser implements an ECMA standard version of JavaScript, their DOM implementations are inconsistent and quirky at best.  In fact, if you've had bad experiences with client-side programming in the past, it's likely that the DOM was the true source of your frustrations, not JavaScript itself.  This is exactly the pain point which jQuery addresses....
..... "Officially supported by Microsoft - For many Microsoft developers, this official blessing is the clincher. Not only will Microsoft begin including jQuery with Visual Studio, but it is part of the default ASP.NET MVC project template. What's more, Microsoft Product Support Services has already begun offering support for jQuery."....

Microsoft announces a new plan, "Microsoft Dynamics", to accelerate the transition to replace their traditional / conventional software systems with cloud-ready infrastructure. Dynamics also serves as a migration guide, providing "seamless integration" of services from old IT to new Cloud. Competitors mentioned include SalesForce.com, SAP and Oracle. Lots of focus on integrating CRM into the full line of business applications. This is somewhat similar to the Visual Productivity challenge of integrating gMail into a working productivity system based on the Google Apps platform. Embedding the full range of Visual Web Communications into productivity apps and services is the key at all levels. One thing to consider in this article is that the only Cloud - Productivity - Business systems contenders are SalesForce, Oracle, SAP and Microsoft. Google Apps isn't mentioned. Nor is Amazon, RackSpace or VMware. Apple, Cisco, HP and Facebook are also left out.

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!

I was surprised to learn that Florian's native document parser is a JSON like ripper of OpenXML visual objects.  He doesn't wrestle with structured objects, but simply treats everything as a visual object.  NOOXML might be closer to a virtual print driver than a OpenXML ripper.   So this has me rethinking the OCR/Scan methods used to rip paper documents to create Tagged PDF "structured object" versions.  Structured objects can easily be converted to interactive HTML-CSS or SVG.  Today Google released an OCR enhanced Android gDOCS app.  Not sure if it uses the Bricolage/Bento algorithm, but that would be an interesting approach. excerpt: the Bricolage algorithm for transferring design and content between Web pages. Bricolage employs a novel, structured-prediction technique that learns to create coherent mappings between pages by training on human-generated exemplars. The produced mappings are then used to automatically transfer the content from one page into the style and layout of another. We show that Bricolage can learn to accurately reproduce human page mappings, and that it provides a general, efficient, and automatic technique for retargeting content between a variety of real Web pages.

This is the Dec 2010 interview that totally changed my view of the future of Documents.  Separating content and layout, and then reconstituting is the essence of preparing a publication.  Are documents Web pages?  Are Web sights magazines?   Visually-immersive apps like TreeSaver and Flipboard change everything, as this video demonstrates.  TreeSaver is OpenWeb HTML+.  FlipBoard is iOS platform specific.  Filipe argues why Open Web will win.  Great interview.  Life changing stuff. excerpt: The problem with Flipboard is that it's an app, not the Web, and I keep hoping someone will show me a really well-designed Web app that shows me that the Web can still win. Yesterday Treesaver's Filipe Fortes took me up on my "can the Web be saved" challenge and visited my house to show me what he's been working on for publishers. An open-source JavaScript/HTML5/CSS library of design templates that will help developers at content companies compete with the design aesthetic that Flipboard showed us.

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.   

CSS is a simple, declarative language for creating style sheets that specify the rendering of HTML and other structured documents. This specification is part of level 3 of CSS ("CSS3") and contains features to describe layouts at a high level, meant for tasks such as the positioning and alignment of "widgets" in a graphical user interface or the layout grid for a page or a window, in particular when the desired visual order is different from the order of the elements in the source document. Other CSS3 modules contain properties to specify fonts, colors, text alignment, list numbering, tables, etc. The features in this module are described together for easier reading, but are usually not implemented as a group. CSS3 modules often depend on other modules or contain features for several media types. Implementers should look at the various "profiles" of CSS, which list consistent sets of features for each type of media.

Add this to the Sports Illustrated "immersive" magzine for the iPAD as clear indication that the entire idea of what a visual document is has changed dramatically.  Radically. excerpt: The coolest media experiences that I've seen on the iPad - Operation Ajax, a graphic novel created specifically for the device. At the time, the idea was still very much in development, but today the Operation Ajax application has gone live in Apple's App Store. The major startups in digital comics, ComiXology and Graphic.ly, have focused their energies on making deals with publishers to transfer existing comics to the iPad or other devices. Operation Ajax, on the other hand, was created with the iPad in mind, avoiding some of the issues that come with transferring from print (the iPad screen is slightly smaller than a standard comic book page, for starters), and also making the supplementary material that can't be delivered in print a natural extension of the experience.