Skip to main content

Home/ Open Web/ Group items tagged business-management

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Gary Edwards

Cloud file-sharing for enterprise users - 1 views

www.computerweekly.com/...e-sharing-for-enterprise-users

SurDoc Sync-Share-Store sync-share-store-collaboration DropBox

shared by Gary Edwards on 30 Aug 13 - No Cached
  • Gary Edwards on 30 Aug 13
     
    Quick review of different sync-share-store services, starting with DropBox and ending with three Open Source services. Very interesting. Things have progressed since I last worked on the SurDocs project for Sursen. No mention in this review of file formats, conversion or viewing issues. I do know that CrocoDoc is used by near every sync-share-store service to convert documents to either pdf or html formats for viewing. No servie however has been able to hit the "native document" sweet spot. Not even SurDocs - which was the whole purpose behind the project!!! "Native Documents" means that the document is in it's native / original application format. That format is needed for the round tripping and reloading of the document. Although most sync-share-store services work with MSOffice OXML formatted documents, only Microsoft provides a true "native" format viewer (Office 365). Office 365 enables direct edit, view and collaboration on native documents. Which is an enormous advantage given that conversion of any sort is guaranteed to "break" a native document and disrupt any related business processes or round tripping need. It was here that SurDoc was to provide a break-through technology. Sadly, we're still waiting :( excerpt: The availability of cheap, easy-to-use and accessible cloud file-sharing services means users have more freedom and choice than ever before. Dropbox pioneered simplicity and ease of use, and so quickly picked up users inside the enterprise. Similar services have followed Dropbox's lead and now there are dozens, including well-known ones such as Google Drive, SkyDrive and Ubuntu One. cloud.jpg Valdis Filks , research director at analyst firm Gartner explained the appeal of cloud file-sharing services. Filks said: "Enterprise employees use Dropbox and Google because they are consumer products that are simple to use, can be purchased without officially requesting new infrastructure or budget expenditure, and can be installed qu
  • Paul Merrell on 11 Sep 13
     
    Odd that the reporter mentions the importance of security near the top of the article but gives that topic such short shrift in his evaluation of the services. For example, "secured by 256-bit AES encryption" is meaningless without discussing other factors such as: [i] who creates the encryption keys and on which side of the server/client divide; and [ii] the service's ability to decrypt the customer's content. Encrypt/decryt must be done on the client side using unique keys that are unknown to the service, else security is broken and if the service does business in the U.S. or any of its territories or possessions, it is subject to gagged orders to turn over the decrypted customer information. My wisdom so far is to avoid file sync services to the extent you can, boycott U.S. services until the spy agencies are encaged, and reward services that provide good security from nations with more respect for digital privacy, to give U.S.-based services an incentive to lobby *effectively* on behalf of their customer's privacy in Congress. The proof that they are not doing so is the complete absence of bills in Congress that would deal effectively with the abuse by U.S. spy agencies. From that standpoint, the Switzerland-based http://wuala.com/ file sync service is looking pretty good so far. I'm using it.
Gary Edwards

Ricoh Spends US$ 300m to Shift Focus to Managed Document Services - 0 views

www.cmswire.com/...d-document-services-009905.php

cloud-computing sursen Document-Management-System Ricoh

shared by Gary Edwards on 26 Jan 11 - No Cached
  • Ricoh said the US$ 300 million would be invested in its managed document services infrastructure with a revenue target of US$ 3.3 billion by 2013.
  • Ricoh believes the shift is so profound that it is investing this amount of money in re-aligning its business.
  • Ricoh has identified shifts in the document management market that are focused on better enterprise returns based on more efficient document management.
  • Gary Edwards on 26 Jan 11
     
    Last September, Xerox launched a very expensive campaign to rebrand itself as a document management heavyweight. This week, Xerox's MFP rival, Ricoh (news, site), has just announced that it will be investing US$ 300 million over three years to "aggressively" accelerate its shift into the managed document services or outsourced document management space. Using its core hardware and software technologies, the shift will see Ricoh focusing not just on the provision of hardware and software, but offering entire document management services from capture to printing. At a press briefing held in New York, London and Tokyo earlier this week that underlined the global nature of the business shift, Ricoh said the US$ 300 million would be invested in its managed document services infrastructure with a revenue target of US$ 3.3 billion by 2013. Document Management Market Shift So, what is all this about? It seems simple enough - Ricoh has identified shifts in the document management market that are focused on better enterprise returns based on more efficient document management. No surprise there. However, what is surprising, is that Ricoh believes the shift is so profound that it is investing this amount of money in re-aligning its business.
Gary Edwards

XML Production Workflows? Start with the Web and XHTML - 1 views

quod.lib.umich.edu/...n-workflows-start-with-the-web

OpenWeb XML XHTML-CSS HTML5-CSS3-JavaScript IDML

shared by Gary Edwards on 01 Nov 13 - No Cached
  • Challenges: Some Ugly Truths The challenges of building—and living with—an XML workflow are clear enough. The return on investment is a long-term proposition. Regardless of the benefits XML may provide, the starting reality is that it represents a very different way of doing things than the one we are familiar with. The Word Processing and Desktop Publishing paradigm, based on the promise of onscreen, WYSIWYG layout, is so dominant as to be practically inescapable. It has proven really hard to get from here to there, no matter how attractive XML might be on paper. A considerable amount of organizational effort and labour must be expended up front in order to realize the benefits. This is why XML is often referred to as an “investment”: you sink a bunch of time and money up front, and realize the benefits—greater flexibility, multiple output options, searching and indexing, and general futureproofing—later, over the long haul. It is not a short-term return proposition. And, of course, the returns you are able to realize from your XML investment are commensurate with what you put in up front: fine-grained, semantically rich tagging is going to give you more potential for searchability and recombination than a looser, more general-purpose approach, but it sure costs more. For instance, the Text Encoding Initiative (TEI) is the grand example of pouring enormous amounts of energy into the up-front tagging, with a very open-ended set of possibilities down the line. TEI helpfully defines a level to which most of us do not have to aspire.[5] But understanding this on a theoretical level is only part of the challenge. There are many practical issues that must be addressed. Software and labour are two of the most critical. How do you get the content into XML in the first place? Unfortunately, despite two decades of people doing SGML and XML, this remains an ugly question.
  • Practical Challenges In 2009, there is still no truly likeable—let alone standard—editing and authoring software for XML. For many (myself included), the high-water mark here was Adobe’s FrameMaker, substantially developed by the late 1990s. With no substantial market for it, it is relegated today mostly to the tech writing industry, unavailable for the Mac, and just far enough afield from the kinds of tools we use today that its adoption represents a significant hurdle. And FrameMaker was the best of the breed; most of the other software in decent circulation are programmers’ tools—the sort of things that, as Michael Tamblyn pointed out, encourage editors to drink at their desks. The labour question represents a stumbling block as well. The skill-sets and mind-sets that effective XML editors need have limited overlap with those needed by literary and more traditional production editors. The need to think of documents as machine-readable databases is not something that comes naturally to folks steeped in literary culture. In combination with the sheer time and effort that rich tagging requires, many publishers simply outsource the tagging to India, drawing a division of labour that spans oceans, to put it mildly. Once you have XML content, then what do you do with it? How do you produce books from it? Presumably, you need to be able to produce print output as well as digital formats. But while the latter are new enough to be generally XML-friendly (e-book formats being largely XML based, for instance), there aren’t any straightforward, standard ways of moving XML content into the kind of print production environments we are used to seeing. This isn’t to say that there aren’t ways of getting print—even very high-quality print—output from XML, just that most of them involve replacing your prepress staff with Java programmers.
  • Why does this have to be so hard? It’s not that XML is new, or immature, or untested. Remember that the basics have been around, and in production, since the early 1980s at least. But we have to take account of a substantial and long-running cultural disconnect between traditional editorial and production processes (the ones most of us know intimately) and the ways computing people have approached things. Interestingly, this cultural divide looked rather different in the 1970s, when publishers were looking at how to move to digital typesetting. Back then, printers and software developers could speak the same language. But that was before the ascendancy of the Desktop Publishing paradigm, which computerized the publishing industry while at the same time isolating it culturally. Those of us who learned how to do things the Quark way or the Adobe way had little in common with people who programmed databases or document-management systems. Desktop publishing technology isolated us in a smooth, self-contained universe of toolbars, grid lines, and laser proofs. So, now that the reasons to get with this program, XML, loom large, how can we bridge this long-standing divide?
  • ...44 more annotations...
  • Using the Web as a Production Platform The answer, I think, is right in front of you. The bridge is the Web, a technology and platform that is fundamentally based on XML, and which many publishers are by now comfortably familiar with. Perhaps not entirely comfortably, but at least most publishers are already working with the Web; they already either know or have on staff people who understand it and can work with it. The foundation of our argument is this: rather than looking at jumping to XML in its full, industrial complexity, which seems to be what the O'Reilly-backed StartWithXML initiative[6] is suggesting, publishers instead leverage existing tools and technologies—starting with the Web—as a means of getting XML workflows in place. This means making small investments and working with known tools rather than spending tens of thousands of dollars on XML software and rarefied consultants. It means re-thinking how the existing pieces of the production toolchain fit together; re-thinking the existing roles of software components already in use. It means, fundamentally, taking the Web seriously as a content platform, rather than thinking of it as something you need to get content out to, somehow. If nothing else, the Web represents an opportunity to think about editorial and production from outside the shrink-wrapped Desktop Publishing paradigm.
  • Is the Web made of Real XML? At this point some predictable objections can be heard: wait a moment, the Web isn’t really made out of XML; the HTML that makes up most of the Web is at best the bastard child of SGML, and it is far too flaky/unstructured/underpowered to be taken seriously. We counter by arguing that although HTML on the Web exists in a staggering array of different incarnations, and that the majority of it is indeed an unstructured mess, this does not undermine the general principle that basic, ubiquitous Web technologies can make a solid platform for content management, editorial process, and production workflow.
  • With the advent of a published XML standard in the late 1990s came the W3C’s adoption of XHTML: the realization of the Web’s native content markup as a proper XML document type. Today, its acceptance is almost ubiquitous, even while the majority of actual content out there may not be strictly conforming. The more important point is that most contemporary Web software, from browsers to authoring tools to content management systems (from blogs to enterprise systems), are capable of working with clean, valid XHTML. Or, to put the argument the other way around, clean, valid XHTML content plays absolutely seamlessly with everything else on the Web.[7]
  • The objection which follows, then, will be that even if we grant that XHTML is a real XML document type, that it is underpowered for “serious” content because it is almost entirely presentation (formatting) oriented; it lacks any semantic depth. In XHTML, a paragraph is a paragraph is a paragraph, as opposed to a section or an epigraph or a summary.
  • n contrast, more “serious” XML document types like DocBook[8] or DITA-derived schemas[9] are capable of making semantic distinctions about content chunks at a fine level of granularity and with a high degree of specificity.
  • So there is an argument for recalling the 80:20 rule here. If XHTML can provide 80% of the value with just 20% of the investment, then what exactly is the business case for spending the other 80% to achieve that last 20% of value? We suspect the ratio is actually quite a bit steeper than 80:20 for most publishers.
  • Furthermore, just to get technical for a moment, XHTML is extensible in a fairly straightforward way, through the common “class” attribute on each element. Web developers have long leveraged this kind of extensibility in the elaboration of “microformats” for semantic-web applications.[10] There is no reason why publishers shouldn’t think to use XHTML’s simple extensibility in a similar way for their own ends.
  • XHTML, on the other hand, is supported by a vast array of quotidian software, starting with the ubiquitous Web browser. For this very reason, XHTML is in fact employed as a component part of several more specialized document types (ONIX and ePub among them).
  • Why re-invent a general-purpose prose representation when XHTML already does the job?
  • It is worth pausing for a moment to consider the role of XHTML in the ePub standard for ebook content. An ePub file is, anatomically, a simply disguised zip archive. Inside the zip archive are a few standard component parts: there are specialized files that declare metadata about the book, and about the format of the book. And then there is the book’s content, represented in XHTML. An ePub book is a Web page in a wrapper.
  • To sum up the general argument: the Web as it already exists presents incredible value to publishers, as a platform for doing XML content management with existing (and often free) tools, and without having to go blindly into the unknown. At this point, we can offer a few design guidelines: prefer existing and/or ubiquitous tools over specialized ones wherever possible; prefer free software over proprietary systems where possible; prefer simple tools controlled and coordinated by human beings over fully automated (and therefore complex) systems; play to our strengths: use Web software for storing and managing content, use layout software for layout, and keep editors and production people in charge of their own domains.
  • Putting the Pieces Together: A Prototype
  • At the SFU Master of Publishing Program, we have been chipping away at this general line of thinking for a few years. Over that time, Web content management systems have been getting more and more sophisticated, all the while getting more streamlined and easier to use. (NB: if you have a blog, you have a Web content management system.) The Web is beginning to be recognized as a writing and editing environment used by millions of people. And the ways in which content is represented, stored, and exchanged online have become increasingly robust and standardized.
  • The missing piece of the puzzle has been print production: how can we move content from its malleable, fluid form on line into the kind of high-quality print production environments we’ve come to expect after two decades of Desktop Publishing?
  • Anyone who has tried to print Web content knows that the existing methods leave much to be desired (hyphenation and justification, for starters). In the absence of decent tools for this, most publishers quite naturally think of producing the print content first, and then think about how to get material onto the Web for various purposes. So we tend to export from Word, or from Adobe, as something of an afterthought.
  • While this sort of works, it isn’t elegant, and it completely ignores the considerable advantages of Web-based content management.
  • Content managed online is stored in one central location, accessible simultaneously to everyone in your firm, available anywhere you have an Internet connection, and usually exists in a much more fluid format than Word files. If only we could manage the editorial flow online, and then go to print formats at the end, instead of the other way around. At SFU, we made several attempts to make this work by way of the supposed “XML import” capabilities of various Desktop Publishing tools, without much success.[12]
  • In the winter of 2009, Adobe solved this part of the problem for us with the introduction of its Creative Suite 4. What CS4 offers is the option of a complete XML representation of an InDesign document: what Adobe calls IDML (InDesign Markup Language).
  • The IDML file format is—like ePub—a simply disguised zip archive that, when unpacked, reveals a cluster of XML files that represent all the different facets of an InDesign document: layout spreads, master pages, defined styles, colours, and of course, the content.
  • IDML is a well thought-out XML standard that achieves two very different goals simultaneously: it preserves all of the information that InDesign needs to do what it does; and it is broken up in a way that makes it possible for mere mortals (or at least our Master of Publishing students) to work with it.
  • What this represented to us in concrete terms was the ability to take Web-based content and move it into InDesign in a straightforward way, thus bridging Web and print production environments using existing tools and skillsets, with a little added help from free software.
  • We would take clean XHTML content, transform it to IDML-marked content, and merge that with nicely designed templates in InDesign.
  • The result is an almost push-button publication workflow, which results in a nice, familiar InDesign document that fits straight into the way publishers actually do production.
  • Tracing the steps To begin with, we worked backwards, moving the book content back to clean XHTML.
  • The simplest method for this conversion—and if you want to create Web content, this is an excellent route—was to use Adobe’s “Export to Digital Editions” option, which creates an ePub file.
  • Recall that ePub is just XHTML in a wrapper, so within the ePub file was a relatively clean XHTML document. It was somewhat cleaner (that is, the XHTML tagging was simpler and less cluttered) than InDesign’s other Web-oriented exports, possibly because Digital Editions is a well understood target, compared with somebody’s website.
  • In order to achieve our target of clean XHTML, we needed to do some editing; the XHTML produced by InDesign’s “Digital Editions” export was presentation-oriented. For instance, bulleted list items were tagged as paragraphs, with a class attribute identifying them as list items. Using the search-and-replace function, we converted such structures to proper XHTML list and list-item elements. Our guiding principle was to make the XHTML as straightforward as possible, not dependent on any particular software to interpret it.
  • We broke the book’s content into individual chapter files; each chapter could then carry its own basic metadata, and the pages conveniently fit our Web content management system (which is actually just a wiki). We assembled a dynamically generated table of contents for the 12 chapters, and created a cover page. Essentially, the book was entirely Web-based at this point.
  • When the book chapters are viewed online, they are formatted via a CSS2 stylesheet that defines a main column for content as well as dedicating screen real estate for navigational elements. We then created a second template to render the content for exporting; this was essentially a bare-bones version of the book with no navigation and minimal styling. Pages (or even the entire book) can be exported (via the “Save As...” function in a Web browser) for use in either print production or ebook conversion. At this point, we required no skills beyond those of any decent Web designer.
  • Integrating with CS4 for Print Adobe’s IDML language defines elements specific to InDesign; there is nothing in the language that looks remotely like XHTML. So a mechanical transformation step is needed to convert the XHTML content into something InDesign can use. This is not as hard as it might seem.
  • Both XHTML and IDML are composed of straightforward, well-documented structures, and so transformation from one to the other is, as they say, “trivial.” We chose to use XSLT (Extensible Stylesheet Language Transforms) to do the work. XSLT is part of the overall XML specification, and thus is very well supported in a wide variety of tools. Our prototype used a scripting engine called xsltproc, a nearly ubiquitous piece of software that we found already installed as part of Mac OS X (contemporary Linux distributions also have this as a standard tool), though any XSLT processor would work.
  • In other words, we don’t need to buy InCopy, because we just replaced it with the Web. Our wiki is now plugged directly into our InDesign layout. It even automatically updates the InDesign document when the content changes. Credit is due at this point to Adobe: this integration is possible because of the open file format in the Creative Suite 4.
  • We wrote an XSLT transformation script[18] that converted the XHTML content from the Web into an InCopy ICML file. The script itself is less than 500 lines long, and was written and debugged over a period of about a week by amateurs (again, the people named at the start of this article). The script runs in a couple of seconds, and the resulting .icml file can then be “placed” directly into an InDesign template. The ICML file references an InDesign stylesheet, so the template file can be set up with a house-styled layout, master pages, and stylesheet definitions for paragraphs and character ranges.
  • Rather than a public-facing website, our system relies on the Web as a content management platform—of course a public face could easily be added.
  • It should be noted that the Book Publishing 1 proof-of-concept was artificially complex; we began with a book laid out in InDesign and ended up with a look-alike book laid out in InDesign. But next time—for instance, when we publish Book Publishing 2—we can begin the process with the content on the Web, and keep it there throughout the editorial process. The book’s content could potentially be written and edited entirely online, as Web content, and then automatically poured into an InDesign template at proof time. “Just in time,” as they say. This represents an entirely new way of thinking of book production. With a Web-first orientation, it makes little sense to think of the book as “in print” or “out of print”—the book is simply available, in the first place online; in the second place in derivative digital formats; and third, but really not much more difficult, in print-ready format, via the usual InDesign CS print production system publishers are already familiar with.
  • Creating Ebook Files Creating electronic versions from XHTML source is vastly simpler than trying to generate these out of the existing print process. The ePub version is extremely easy to generate; so is online marketing copy or excerpts for the Web, since the content begins life Web-native.
  • Since an ePub file is essentially XHTML content in a special wrapper, all that is required is that we properly “wrap” our XHTML content. Ideally, the content in an ePub file is broken into chapters (as ours was) and a table of contents file is generated in order to allow easy navigation within an ebook reader. We used Julian Smart’s free tool eCub[19] to simply and automatically generate the ePub wrapper and the table of contents. The only custom development we did was to create a CSS stylesheet for the ebook so that headings and paragraph indents looked the way we wanted. Starting with XHTML content, creating ePub is almost too easy.
  • today, we are able to put the process together using nothing but standard, relatively ubiquitous Web tools: the Web itself as an editing and content management environment, standard Web scripting tools for the conversion process, and the well-documented IDML file format to integrate the layout tool.
  • Our project demonstrates that Web technologies are indeed good enough to use in an XML-oriented workflow; more specialized and expensive options are not necessarily required. For massive-scale enterprise publishing, this approach may not offer enough flexibility, and the challenge of adding and extracting extra semantic richness may prove more trouble than it's worth.
  • But for smaller firms who are looking at the straightforward benefits of XML-based processes—single source publishing, online content and workflow management, open and accessible archive formats, greater online discoverability—here is a way forward.
  • The result is very simple and easy to use. Our demonstration requires that a production editor run the XSLT transformation script manually, but there is no reason why this couldn’t be built directly into the Web content management system so that exporting the content to print ran the transformation automatically. The resulting file would then be “placed” in InDesign and proofed.
  • The final piece of our puzzle, the ability to integrate print production, was made possible by Adobe's release of InDesign with an open XML file format. Since the Web's XHTML is also XML, is can be easily and confidently transformed to the InDesign format.
  • Such a workflow—beginning with the Web and exporting to print—is surely more in line with the way we will do business in the 21st century, where the Web is the default platform for reaching audiences, developing content, and putting the pieces together. It is time, we suggest, for publishers to re-orient their operations and start with the Web.
  • Using the Web as a Production Platform
  • Gary Edwards on 01 Nov 13
     
    I was looking for an answer to a problem Marbux had presented, and found this interesting article.  The issue was that of the upcoming conversion of the Note Case Pro (NCP) layout engine to the WebKit layout engine, and what to do about the NCP document format. My initial reaction was to encode the legacy NCP document format in XML, and run an XSLT to a universal pivot format like TEI-XML.  From there, the TEI-XML community would provide all the XSLT transformation routines for conversion to ODF, OOXML, XHTML, ePUB and HTML/CSS. Researching the problems one might encounter with this approach, I found this article.  Fascinating stuff. My take away is that TEI-XML would not be as effective a "universal pivot point" as XHTML.  Or perhaps, if NCP really wants to get aggressive; IDML - InDesign Markup Language. As an after thought, i was thinking that an alternative title to this article might have been, "Working with Web as the Center of Everything".
Gary Edwards

Furious Over End Of Google Reader - Business Insider - 1 views

www.businessinsider.com/er-end-of-google-reader-2013-3

google-reader

shared by Gary Edwards on 16 Mar 13 - No Cached
  • Gary Edwards on 16 Mar 13
     
    "Gary Edwards on Mar 15, 8:25 PM said: There are only three apps i load at boot-up: gMail, gReader, and gWave. Ooops! Google Wave was cancelled over a year ago. Owning the end-users attention at boot-up proved to be an essential factor to the Microsoft monopoly. They built an iron fisted empire out of owning the point of boot-up. So it's very strange to see Google give up the very thing other cloud platform contenders would no doubt kill for. Very strange. Even stranger though is the perception that Google + will somehow now move to center stage? The only reason i use Google+ is because it's easy to point to an article and post a comment from Google Reader to my + circles. Other than that i have no use for +. Nicolas Carr posted an interesting comment on Google's cancellation of gReader yesterday. He tried to argue that there is a difference between "tools" and "platforms", and Google was more interested in building a platform than maintaining "tools" like gReader. So, Google+ is now essential to the Google Platform? Unfortunately, the otherwise brilliant and cosmic insightful Mr. Carr, fails to make that case. Microsoft became a platform when they succeeded in positioning their OS as the essential factor bridging an explosively innovative and rapidly commoditiz'ing Windows hardware reference platform, and, he equally rapid and innovative Windows software application platform. Both software and hardware were being written and developed to the Windows OS, with features doubling and costs being halved at a rate that even Moore's Law envied. Microsoft fully cemented the emerging hardware - OS - application platform with a business productivity environment that necessitated the use of the MS Office suite of servers and apps. That lock on business productivity has yet to be broken. And even though the mighty Google Apps has made some progress convincing businesses to rip-out-and-replace their legacy business productivity systems and re write to the Google Cloud P
Gary Edwards

Is productivity in the workplace possible with Surface 2 or iPad? | ZDNet - 0 views

www.zdnet.com/h-surface-2-or-ipad-7000022220

Cloud-Computing Cloud-Productivity-Platform mobile-computing business-productivity

shared by Gary Edwards on 22 Oct 13 - No Cached
  • Gary Edwards on 22 Oct 13
     
    Not surprisingly, Microsoft is going to pound on "productivity" as the key differential between their desktop-cloud-mobile computing products, and those of mobile-productivity platform challengers, Apple and Google. There are three platform contenders, and this article points out that it is Google Apps that is keeping Apple in the business productivity game. Very interesting insight. Especially since a recent Forrester Report has the Apple platform capturing 65% of all mobile business application development. And Microsoft with only 1%. Google weighs in with 13%. This is a stunning setback for Microsoft. The MS monopolist empire is built on business productivity, with 98% of clinet/server marketshare. excerpt: "Over time, Microsoft has tried to tilt the marketing message to position Surface as a "productivity tablet". Now that Surface 2 is out, the "productivity tablet" message is coming across loud and clear. But can what people use tablets at work for actually be described as "productive"? Surface might be new, but the idea of using tablets in business is not. Although Microsoft would like us to believe that a tablet that doesn't run Office and doesn't have a good solution for a keyboard can't be used in business, the iPad has been used in business since its release in April 2010. Mobile device management (MDM) allows enterprises to control which apps are available on both on BYOD and enterprise-supplied tablets. Some MDM vendors publish reports and surveys on what their customers' allow and disallow. This information can provide some insight into what apps people are typically using. Back in June, my ZDNet colleague Adrian Kingsley-Hughes reported on a report put out by one such vendor. Fiberlink gave this list of iOS apps that are commonly whitelisted: iBooks Adobe Reader Google Citrix Receiver Numbers Dropbox Pages iTunes U Keynote WebEx Along with those apps, you also need to add that apps that come with the device - namely web browsing, email,
Gary Edwards

Ticked off: How stock market decimalization killed IPOs and ruined our economy ~ I, Cri... - 0 views

www.cringely.com/...ed-ipos-and-ruined-our-economy

Productivity Wealth-Creation Jobs IPO's

shared by Gary Edwards on 13 Sep 12 - No Cached
  • Gary Edwards on 13 Sep 12
     
    Really interesting blog from Robert X.  Wealth through productivity vs wealth through accumulation and the important but seriously declining role of IPO's. excerpt: "Big business grows by economies of scale, economies of scale are gained by increasing efficiency, and increased efficiency in big business always - always - means creating more economic output with fewer people. More economic output is good, but fewer people is bad if you need 100,000 new jobs per month just to provide for normal U.S. population growth. This is the ultimate irony of policies that declare companies too big to fail when in fact they are more properly too big to survive. Our policy obsession with helping big business no matter which party is in power has been a major factor in our own economic demise because it doesn't create jobs. Our leaders and would-be leaders are really good at talking about the value of small and medium size businesses in America but really terrible about actually doing much to help. Now here comes the important part: if small businesses, young businesses, new businesses create jobs, then Initial Public Offerings create wealth. Wealth creation is just as important as job creation in our economy but too many experts get it wrong when they think wealth creation and wealth preservation are the same things, because they aren't." ................. The fundamental error of trickle-down (Supply Side) economics is that it is dependent on rich people spending money which they structurally can't do fast enough to matter, and philosophically won't do because their role in the food chain is about growth through accumulation, not through new production. ..............................................
  • Paul Merrell on 17 Sep 12
     
    I'm less than convinced that IPOs create wealth, in terms of the aggregate wealth of the nation. Most of the "wealth" created by IPOs goes to the previous owner's of the business, plus whatever speculators can maneuver to acquire through capital gains. But waving the "IPO wand" does not magically boost productivity, business outputs, or business profitability. So if "wealth" is created, it is faux wealth. I think Cringely ventures too far from what the real argument is about: levels of government taxation and creating jobs. Supply Side economics is in reality an argument against taxing the wealthy. But Cringely doesn't even touch on the taxation issue. I also do not agree with his "Steve Jobs created 50,000 new jobs" schtick because he does not take into account how many jobs were destroyed in the process. But modern information technology has unquestionably destroyed more jobs than it has created; the technology never would have succeeded had it not boosted individual productivity to a point that massive numbers of employees could be laid off. For example, remember the days when you could call a business and have a human being answer the phone and direct your call to the right person? That lady doesn't have that job anymore because of voice menu/mail technology. IT is all about doing more with fewer people. In the context of jobs and taxation levels, the fundamental error of Supply Side Economics is not the distinction between wealth accumulation and wealth creation. The real fundamental error is globalism, government policies that create enormous incentives to invest capital outside the U.S. Supply Side Economics simply blinks past that enormously inconvenient reality. To illustrate, let's try remodeling trickle-down economics in a way that has a prayer of producing more and better-paying jobs in the U.S. (Over-simplification warning.) -- The U.S. withdraws from all trade agreements standing in the way and repeals all laws inconsistent with the goal of
Gary Edwards

No Jitter | Post | Cisco Or Microsoft? Who Wins the Line-of-Business War? - 0 views

www.nojitter.com/...ho-wins-the-lineofbusiness-war

Cloud-Productivity-Platform

shared by Gary Edwards on 23 Jul 13 - No Cached
  • The multitude of services gives Microsoft an early edge when it comes to cloud, but the channel-enablement model for Cisco can create much greater scale than a direct to line-of-business model. The key is ensuring its resellers are fully trained in selling to line-of-business, which isn't a simple undertaking. Bottom line: With regard to cloud, Microsoft has a faster route to market, but Cisco's should give it an advantage over time.
  • Putting cloud aside, Cisco and Microsoft have markedly different approaches in selling to lines of business. For Microsoft, the key lies in its developer community. Developers build applications that business people use and buy. Many of these applications use Microsoft as an underlying technology without the purchaser really even being aware of that fact. Microsoft gets pulled through with really no involvement from Microsoft, providing a low- to no-cost sales model for the company. The only down side is that the application brand often overshadows the underlying brand.
  • Microsoft has made a living off selling products, many of them sub-par, into business because of its developer relationships. Does anyone really think Microsoft gained monopoly-like share with desktop operating systems because of quality of product and ease of use? Hardly. Windows became the de facto standard for developers because of the quality of the developer program. Microsoft does a good job of meeting the needs of its large software vendors, but does an even better job of making sure those millions of small ISVs have access to Microsoft platforms and developer support.
  • ...6 more annotations...
  • Cisco has been trying to build its own "Cisco Developer Network" (CDN) for the better part of a decade. The company kicked off this initiative way back in the early 2000s when it bought a company called Metreos that had some interesting VoIP applications and a slick developer interface. Back then, the program was known as CTDP, Cisco Technology Developer Program, and was run by VoIP people, not individuals that understand software and how to build a developer environment. Since then the program has undergone a number of facelifts and Cisco appears to have some real software people running the group, so there is some potential.
  • With regards to UC, as this market transitions away from products to platforms, services will play a significant role. Cisco's services plays a role similar to IBM services. IBM's consulting group works with its top tier customers to understand how to solve business problems through compute-centric solutions. Cisco services works with its customers to create solutions through networking- and communications-related products. As more and more organizations look to leverage UC strategically, I would expect Cisco services to target its top-tier customers. The key for Cisco then is to take these solutions and push them down through its channel for scale and market share gains.
  • So developer-led or services-led?
  • Microsoft should get an early advantage, as many in-house developers will look to Lync; but the services strategy by Cisco should create longer, more sustainable value, as it has for IBM.
  • The key for Microsoft is being able to adapt its developer environment faster as market trends change. Obviously, compute is moving away from the traditional desktop to mobile clients and the cloud, and there are far more single-use, purpose-built applications being built in the consumer world. I think Microsoft's Developer Network is oriented towards more old-school developers.
  • The key for Cisco is having the patience to work with its lead customers and find those unique, game-changing applications and use cases that it can then push down into the channel. It's the right strategy for Cisco, but it might take a bit more time to bear some fruit.
  • Gary Edwards on 23 Jul 13
     
    excerpt: "Developer-led or services-led? Microsoft should get an early advantage, but the services strategy by Cisco should create longer, more sustainable value, Last month I wrote a blog outlining how the line-of-business manager holds the key to winning the Cisco versus Microsoft war. A number of you commented that this was obvious and both companies are already doing it. I'll agree that this is something both companies are trying to do, but neither is doing a great job. Microsoft is a company with high appeal to IT pros and Cisco to network managers, with high brand familiarity to line of business managers but low appeal beyond this."
Gary Edwards

101 Small Business Web Applications You Must Check Out - 1 views

smallbiztrends.com/...business-web-applications.html

web-apps

shared by Gary Edwards on 28 Apr 11 - No Cached
  • Gary Edwards on 28 Apr 11
     
    Excellent List:  Check out these 101 small business web applications - software in the cloud. The selections reflect the breadth of innovative ideas and new business pursuits at play in the small business technology cloud landscape. From sales to legal to productivity tools, we can attest that the small business technology is alive, kicking and doing extremely well in 2011. It's getting much easier and cheaper to operate a business than ever before. Absolutely great news for small business! Here is the list of categories we will cover on this post: Business Development Email Marketing Event Marketing Video Marketing Social Media Marketing Online Sales Online Payment Presentation Billing and Accounting Funding Hiring and Team Building File Sharing Legal Building Websites Website Testing Market Research CRM Productivity Customer Service Team Management Voice Communication Online Education
Gary Edwards

RuleLab.Net Server: Web system for design, implementation and management of business pr... - 0 views

www.pcworld.com/...description.html

RuleLab.net business-processes

shared by Gary Edwards on 05 Feb 11 - No Cached
  • Gary Edwards on 05 Feb 11
     
    RuleLab.Net is a web-based system for designing and implementing the business rules that operate on an application's XML data. Extend your existing applications by adding Rule building and Business Rules Engine (BRE) capabilities. Consolidate your business logic in an easy to read format, build, test, share, and deploy your Rules using the web browser; and integrate them into your system via the BRE. Intuitive GUI, English-like syntax, and centralized repository empower business users with direct access to the Rules.In the RuleLab.Net system, Business Rules are composed and managed over the Internet or Intranet using the web-based Rules Designer. It allows users to associate an application XML data template with Rules, create a vocabulary of natural terms, graphically build complex logical expressions, test the Rules on data samples, and store the Rules in a database. Features include strong data types, reasoning, rule priorities and dependencies, calculation formulas, looping-data-structure support, and a built-in set of computational, aggregate and other data processing functions. Rules and other system objects are stored in XML files that can be downloaded, modified, and uploaded to the online repository. Rule changes made online can be instantly deployed for runtime use by the applications integrated with the BRE. The forward chaining BRE parses XML application data against the ruleset, updates your data XML document, and returns it back to the application along with the comprehensive state information. Written in .NET, the BRE component can be utilized as a managed assembly, a COM object, or through the Web Service.
Gary Edwards

Treeno Software: The Treeno Document Vault 2.0 Document Management Network Appliance - 0 views

www.sfgate.com/...article.cgi

Treeno DMS wiki-WORD

shared by Gary Edwards on 14 Jun 11 - No Cached
  • Gary Edwards on 14 Jun 11
     
    A Complete Document Management System packaged as a server appliance.  Still needs wiki-WORD sync-share-collaborate.  Still needs portable "native client" docx viewer/editor with fixed/flow/flock options. Good solution for SMB:  instead of trusting business documents to a Cloud provider, they can purchase the Treeno DMS-Cloud appliance and do it themselves. Treeno Document Vault 2.0 - document management appliance. The new Treeno Document Vault is designed specifically for the small to medium sized business. It is a completely self-contained plug-and-play document management server appliance. Treeno's EDM solutions include document, imaging, email and document workflow management. Treeno Software's mission is to provide their customers with operational workflow efficiencies and measureable return on investment (ROI) through the fast installation and implementation of their fully secure, highly reliable, and easy-to-use, web-based Enterprise Document Management (EDM) Solution. For more information on Treeno Software, please visit www.treenosoftware.com
Gary Edwards

I'll tell you something about Windows: Joe Wilcox does the numbers - 0 views

www.betanews.com/...1311357232

Microsoft Windows Microsoft-Desktop-Platform-Numbers Joe-Wilcox

shared by Gary Edwards on 22 Jul 11 - No Cached
  • Gary Edwards on 22 Jul 11
     
    Microsoft already got its big Windows 7 sales bang -- 400 million licenses sold since the operating system shipped nearly two years ago. The global install base of PCs is around 1 billion. The majority of licenses are going to emerging markets. Microsoft estimates that they totaled 40 million PC shipments for the quarter or -- get this -- half of global volume. It's simply a stunning number that represents faster recovering economies in many emerging markets and new sales. The majority of Windows sold in developed markets are resales -- to existing customers. Microsoft is still getting some bang from businesses. During yesterday's earnings conference call, Bill Koefoed, general manager of Microsoft Investor Relations, said that "business PC refresh cycle continued and drove estimated business PC growth of 8 percent". Those business deployments won't last forever, however. The reality is this: If not for Windows Vista's market failure, successor 7's sales situation might be a whole lot worse today. Windows 7 released with about 80 percent of the install base on XP. Upgrades were inevitable in developed markets. Whenever Windows 8 ships, much of the established install base will be on 7 or moving that way. Enterprises don't deploy overnight. For now, Koefoed says that "90 percent of enterprises have committed to a deployment plan" and one-quarter of their desktops have Windows 7. Windows 7's lifeblood is two-fold, then: Pent-up demand from businesses still using Windows XP and sales to emerging markets. It's not a sustainable growth business, although legacy sales should keep the Windows & Windows Live division profitable for some time. Microsoft's Business Division long ago passed Windows as the big revenue and profit generator, $5.78 billion and $3.6, respectively, in fiscal Q4. Windows & Windows Live generated $4.7 billion in revenue and $2.9 billion in profit. Actually, Server and Tools division nearly generated as much revenue as Windows & Windows Live -- $4.6 b
Gary Edwards

Why Microsoft's Office 365 will clobber Google Apps | VentureBeat - Peter Yared - 0 views

venturebeat.com/...e-365-will-clobber-google-apps

Office365 Google-Apps Web-Productivity-Platform cloud-productivity

shared by Gary Edwards on 01 Jul 11 - No Cached
  • Gary Edwards on 01 Jul 11
     
    Good comparison of Microsoft and Google "Cloud" initiatives.  Sure, Microsoft has the numbers.  They own the legacy desktop productivity platform.  But their execution in the Cloud is horrific.  Businesses will always opt for integrating existing desktop apps with Cloud productivity systems over rip-out-and-replace platform alternatives.   But the benefits of highly interoperable and universally accessible Cloud communications and collaborative computing have to be there.  So far MS has failed to deliver, and miserably so.   excerpt:  With Office 365, Microsoft has finally delivered an end-to-end cloud platform for businesses that encompass not only its desktop Office software, but also its server software, such as Exchange and SharePoint. Contrary to Google's narrative, cloud based office software is still a wide open market. The three million businesses that have "Gone Google" - proclaimed on billboards in San Francisco airport's new Terminal 2 - are for the most part Gmail users, who are still happily using Microsoft Office and even Microsoft Outlook. Gmail is a fast, cheap, spam-free and great solution for business email, especially relative to the expensive, lumbering email service providers. Google Apps has definitely found a niche for online collaboration, but generally for low-end project management types of spreadsheets and small documents. The presentation and drawing Google Apps are barely used. Yes, there are definitely Google Apps wins, since it seems cheap. On implementation, businesses find that switching to Gmail is one thing, but switching their entire business infrastructure to Google Apps is a completely different animal that goes far beyond simply changing how employees are writing memos.
Gary Edwards

SohoOS - Online Small and Micro Business Management. Everything a business needs to flo... - 0 views

www.sohoos.com/...basics

sohoOS sursen trellis cloud-computing

shared by Gary Edwards on 31 Jan 11 - No Cached
  • Gary Edwards on 31 Jan 11
     
    An all inclusive free business management solution Everything a business needs in order to flourish is now readily available with a single click. Managing your business was never this easy. Open your free account today
Navin Goel

Manage your car rental business with fast and efficient car rental software - 0 views

www.marketpressrelease.com/ental-software-1355721568.html

car rental software

shared by Navin Goel on 17 Dec 12 - No Cached
  • Navin Goel on 17 Dec 12
     
    The new age business requires you to manage your finances and resources effectively in order to maximize your returns on investment. The car rental software is the best solution when you are looking to manage vehicle fleet efficiently.
Gary Edwards

Opportunities for ISVs Moving to the Cloud - 0 views

feedproxy.google.com/...BM4i45k0IzI

Sanjeev-Kumar iBE Cloud-Computing

shared by Gary Edwards on 31 Jul 12 - No Cached
  • Gary Edwards on 31 Jul 12
     
    Nice article by Sanjeev Kumar of iBE.net explaining how ISV's can move their customer business systems and processes to the Cloud, and why. Sanjeev is Product Manager for Business Analytics at iBE.net, which builds mobile and cloud-based business management software for small and midsized organizations. For more information visit www.ibe.net.
Gary Edwards

How To Win The Cloud Wars - Forbes - 0 views

www.forbes.com/...how-to-win-the-cloud-wars

Cloud-Computing

shared by Gary Edwards on 19 Sep 12 - No Cached
  • Gary Edwards on 19 Sep 12
     
    Byron Deeter is right, but perhaps he's holding back on his reasoning.  Silicon Valley is all about platform, and platform plays only come about once every ten to twenty years.  They come like great waves of change, not replacing the previous waves as much as taking away and running with the future.   Cloud Computing is the fourth great wave.  It will replace the PC and Network Computing waves as the future.  It is the target of all developers and entrepreneurs.   The four great waves are mainframe, workstation, pc and networked pc, and the Internet.  Cloud Computing takes the Internet to such a high level of functionality that it will now replace the pc-netwroking wave.  It's going to be enormous.  Especially as enterprises move their business productivity and data / content apps from the desktop/workgroup to the Cloud.  Enormous. The key was the perfect storm of 2008, where mobility (iPhone) converged with the standardization of tagged PDF, which converged with the Cloud Computing application and data model, which all happened at the time of the great financial collapse.   The financial collapase of 2008 caused a tectonic shift in productivity.  Survival meant doing more with less.  Particularly less labor since cost of labor was and continues to be a great uncertainty.  But that's also the definition of productivity and automation.  To survive, companies were compelled to reduce labor and invest in software/hardware systems based productivity.  The great leap to a new platform had it's fuel; survival. Social applications and services are just the simplest manifestation of productivity through managed connectivity in the Cloud.  Wait until this new breed of productivity reaches business apps!  The platform wars have begun, and it's for all the marbles. One last thought.  The Internet was always going to win as the next computing platform wave.  It's the first time communications have been combined and integrated into content, and vast dat
Gary Edwards

Staggering Growth Predicted In Cloud Computing - Smarthouse - 0 views

smarthouse.com.au/...B7E5P7T6

cloud-computing sursen

shared by Gary Edwards on 21 Jan 11 - No Cached
  • Gary Edwards on 21 Jan 11
     
    The home business and small office sectors are leading the adoption of Cloud computing services, with business spending on Cloud services predicted to surpass $13 Billion by 2014. Cloud computing enables businesses to access computer servers and data storage over the Internet and internal networks, allowing them to lower data costs and move content more nimbly. One of the key concerns over adoption of Cloud services to date has been security issues. Recent research from the IT Governance Institute (ITGI) in the US suggested companies were holding back on Cloud investments over fears for the security of their data in the Cloud. Half of the 834 executives from 21 countries polled said they were delaying Cloud implementation because of security concerns, and over a third said they were waiting to get the full value from installed systems. Research by IDC confirmed this view, with organisations claiming identity management and access control over who has access to Cloud data was a worrying factor, along with governance issues over privacy and compliance of both Cloud data and apps. Nevertheless, the fast-growing trend has been seen to be boosting demand for infrastructure and fueling consolidation in the data-storage sector. According to the In-Stat report which forecasts trends in cloud computing and managed hosting spending in the US, the growth in Cloud Computing will be 'staggering', rising from a figure of less than 3 billion currently.
Gary Edwards

Cloud Computing Set to 'Skyrocket,' Driven by Economy: Survey - Forbes - 0 views

www.forbes.com/...ocket-driven-by-economy-survey

Cloud-Computing

shared by Gary Edwards on 05 Oct 11 - No Cached
  • Gary Edwards on 05 Oct 11
     
    Cloud computing is becoming more than a tactical measure adopted by managers and professionals seeking quick solutions to business and technical problems. It is increasingly being seen as a strategic initiative. Not only are most executives now planning to adopt some form of cloud computing for their organizations, they also expect these technology services to help position their organizations to succeed in today's rough-and-tumble economy. These are some of the findings of a new survey of 900 executives released by KPMG International and Forbes Insight. The majority, 81%, say their organizations have already moved at least some business activities to the cloud and expect 2012 investment "to skyrocket, with some companies planning to spend more than a fifth of their IT budget on cloud next year," the study finds. Economic factors were cited by 76% as an important driver for cloud adoption, bringing strategic benefits such as transforming their business models to gain a competitive advantage. Other considerations for moving to cloud computing include improving processes to offer more agility across the enterprise (80%), and offering technical benefits that they otherwise could not gain from their own data centers (76%). Eighty-seven percent of executives feel that the changes delivered by cloud will be "significant." This view is consistent among companies of all sizes and whether the respondents work within IT functions or business units.  KPMG summarized the transformative effects cloud is delivering:
Gary Edwards

Two Microsofts: Mulling an alternate reality | ZDNet - 0 views

www.zdnet.com/n-alternate-reality-7000016916

Microsoft microsoft-monopoly Judge-Thomas-Penfield-Jackson

shared by Gary Edwards on 19 Jun 13 - No Cached
  • Judge Jackson had it right. And the Court of Appeals? Not so much
  • Judge Jackson is an American hero and news of his passing thumped me hard. His ruling against Microsoft and the subsequent overturn of that ruling resulted, IMHO, in two extraordinary directions that changed the world. Sure the what-if game is interesting, but the reality itself is stunning enough. Of course, Judge Jackson sought to break the monopoly. The US Court of Appeals overturn resulted in the monopoly remaining intact, but the Internet remaining free and open. Judge Jackson's breakup plan had a good shot at achieving both a breakup of the monopoly and, a free and open Internet. I admit though that at the time I did not favor the Judge's plan. And i actually did submit a proposal based on Microsoft having to both support the WiNE project, and, provide a complete port to WiNE to any software provider requesting a port. I wanted to break the monopolist's hold on the Windows Productivity Environment and the hundreds of millions of investment dollars and time that had been spent on application development forever trapped on that platform. For me, it was the productivity platform that had to be broken.
  • I assume the good Judge thought that separating the Windows OS from Microsoft Office / Applications would force the OS to open up the secret API's even as the OS continued to evolve. Maybe. But a full disclosure of the API's coupled with the community service "port to WiNE" requirement might have sped up the process. Incredibly, the "Undocumented Windows Secrets" industry continues to thrive, and the legendary Andrew Schulman's number is still at the top of Silicon Valley legal profession speed dials. http://goo.gl/0UGe8 Oh well. The Court of Appeals stopped the breakup, leaving the Windows Productivity Platform intact. Microsoft continues to own the "client" in "Client/Server" computing. Although Microsoft was temporarily stopped from leveraging their desktop monopoly to an iron fisted control and dominance of the Internet, I think what were watching today with the Cloud is Judge Jackson's worst nightmare. And mine too. A great transition is now underway, as businesses and enterprises begin the move from legacy client/server business systems and processes to a newly emerging Cloud Productivity Platform. In this great transition, Microsoft holds an inside straight. They have all the aces because they own the legacy desktop productivity platform, and can control the transition to the Cloud. No doubt this transition is going to happen. And it will severely disrupt and change Microsoft's profit formula. But if the Redmond reprobate can provide a "value added" transition of legacy business systems and processes, and direct these new systems to the Microsoft Cloud, the profits will be immense.
  • ...1 more annotation...
  • Judge Jackson sought to break the ability of Microsoft to "leverage" their existing monopoly into the Internet and his plan was overturned and replaced by one based on judicial oversight. Microsoft got a slap on the wrist from the Court of Appeals, but were wailed on with lawsuits from the hundreds of parties injured by their rampant criminality. Some put the price of that criminality as high as $14 Billion in settlements. Plus, the shareholders forced Chairman Bill to resign. At the end of the day though, Chairman Bill was right. Keeping the monopoly intact was worth whatever penalty Microsoft was forced to pay. He knew that even the judicial over-site would end one day. Which it did. And now his company is ready to go for it all by leveraging and controlling the great productivity transition. No business wants to be hostage to a cold heart'd monopolist. But there is huge difference between a non-disruptive and cost effective, process-by-process value-added transition to a Cloud Productivity Platform, and, the very disruptive and costly "rip-out-and-replace" transition offered by Google, ZOHO, Box, SalesForce and other Cloud Productivity contenders. Microsoft, and only Microsoft, can offer the value-added transition path. If they get the Cloud even halfway right, they will own business productivity far into the future. Rest in Peace Judge Jackson. Your efforts were heroic and will be remembered as such. ~ge~
  • Gary Edwards on 19 Jun 13
     
    Comments on the latest SVN article mulling the effects of Judge Thomas Penfield Jackson's anti trust ruling and proposed break up of Microsoft. comment: "Chinese Wall" Ummm, there was a Chinese Wall between Microsoft Os and the MS Applciations layer. At least that's what Chairman Bill promised developers at a 1990 OS/2-Windows Conference I attended. It was a developers luncheon, hosted by Microsoft, with Chairman Bill speaking to about 40 developers with applications designed to run on the then soon to be released Windows 3.0. In his remarks, the Chairman described his vision of commoditizing the personal computer market through an open hardware-reference platform on the one side of the Windows OS, and provisioning an open application developers layer on the other using open and totally transparent API's. Of course the question came up concerning the obvious advantage Microsoft applications would have. Chairman Bill answered the question by describing the Chinese Wall that existed between Microsoft's OS and Apps develop departments. He promised that OS API's would be developed privately and separate from the Apps department, and publicly disclosed to ALL developers at the same time. Oh yeah. There was lots of anti IBM - evil empire stuff too :) Of course we now know this was a line of crap. Microsoft Apps was discovered to have been using undocumented and secret Window API's. http://goo.gl/0UGe8. Microsoft Apps had a distinct advantage over the competition, and eventually the entire Windows Productivity Platform became dependent on the MSOffice core. The company I worked for back then, Pyramid Data, had the first Contact Management application for Windows; PowerLeads. Every Friday night we would release bug fixes and improvements using Wildcat BBS. By Monday morning we would be slammed with calls from users complaining that they had downloaded the Friday night patch, and now some other application would not load or function properly. Eventually we tracked th
Navin Goel

Car Rental Software Can Help You Manage Your Vehicle Fleet Effectively and Efficiently ... - 0 views

goarticles.com/...7229488

Car rental software

shared by Navin Goel on 17 Dec 12 - No Cached
  • Navin Goel on 17 Dec 12
     
    Software can cut wastages and add to your productivity in car rental biz. Improve your biz efficiency with the employment of car rental software that leads to automated solutions of managing customer bookings, fleet management etc.
1 - 20 of 62 Next › Last »
Showing 20▼ items per page