Skip to main content

Home/ Open Web/ Group items tagged #web

Rss Feed Group items tagged

Gary Edwards

Microsoft Reinvents its Cloud Strategy - 0 views

  •  
    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.
Gary Edwards

Overview of apps for Office 2013 - 0 views

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

Mobile banking pioneer mFoundry nabs $18M from MasterCard, Intel Capital and others - 1 views

  •  
    Good stuff. The Internet-payment sector is really heating up: Square, PayPal, mFoundry and my favorite - DWOLLA. The credit-card-payment-industry is still in control, but you can see from the heavy investments they are making in Web based systems, that the mobility phenomenon has them concerned. Dwolla is my favorite because of the innovative way they connect direct to the bank accounts of users, cutting the transaction and reconciliation cost from credit card standard 2.75% o a FLAT $0.25 cents!!!! Outstanding. Could prove very disruptive.
  •  
    Simple, formerly known as "BankSimple" recently won an award as one of the 20 best stratups of 2011. Backed by Visa, Simple aggregates end user bank accounts, proving a single interface. Promises to get rid of bank fees entirely, and become a NEW Mobile Bank. Not sure this can be doen with Visa sitting in the drivers seat.
Paul Merrell

Mozilla Developers Testing Mobile OS - HotHardware - 0 views

  • Mozilla has been experimenting with an interesting idea called Boot 2 Gecko. Essentially, B2G (as it’s called) is a mobile operating system based on the Web, as opposed to what the project’s wiki calls “proprietary, single-vendor stacks”. Mozilla has something there--open Web technologies indeed increasingly provide an intriguing platform for lots of things, mobile and otherwise. The developers on the B2G project are looking at the following areas: New web APIs: build prototype APIs for exposing device and OS capabilities to content (Telephony, SMS, Camera, USB, Bluetooth, NFC, etc.) Privilege model: making sure that these new capabilities are safely exposed to pages and applications Booting: prototype a low-level substrate for an Android-compatible device Applications: choose and port or build apps to prove out and prioritize the power of the system
Gary Edwards

SendWrite - The easiest way to send a card - 2 views

  •  
    It's Kristallnacht for the Open Internet, free speech, right to assemble, the rule of law, and probable cause.  SendWrie provides an easy to use means of sending digital letters to your congress critters.
Gary Edwards

Salesforce.com Professional Edition - Full Review - Reviews by PC Magazine - 0 views

  •  
    Salesforce offers five separate editions of its Sales Cloud 2 product. Contact Manager Edition costs $5 per user per month, and somewhat resembles a cloud-based ACT. It tracks contacts, customer interactions, tasks, and hooks into Outlook and Google Apps, while also offering document sharing and mobile access. Group Edition costs $25 per user per month. It tracks sales opportunities, offers pre-built dashboards and basic reporting, adds the ability to capture leads from your Web site, and tracks Google AdWords performance within Salesforce.com. Group Edition is a good starting point for many SMBs, but Professional Edition is even better. It costs $65 per user per month, and it's is the real SMB sweet spot. It offers full reporting and analytics, custom dashboards, e-mail marketing, sales forecasts, granular permissions, real-time data sharing, and basic customer service tools.
Paul Merrell

Creating mobile Web applications with HTML 5 -- Five "How To" Articles - 0 views

  •  
    HTML 5 is a very hyped technology, but with good reason. It promises to be a technological tipping point for bringing desktop application capabilities to the browser. As promising as it is for traditional browsers, it has even more potential for mobile browsers. Even better, the most popular mobile browsers have already adopted and implemented many significant parts of the HTML 5 specification. In this five-part series, you will take a closer look at several of those new technologies that are part of HTML 5, that can have a huge impact on mobile Web application development. In each part of this series you will develop a working mobile Web application showcasing an HTML 5 feature that can be used on modern mobile Web browsers, like the ones found on the iPhone and Android-based devices
Paul Merrell

Dr Dobbs - HTML5 Web Storage - 0 views

  • HTML5 Web Storage is an API that makes it easy to persist data across web requests. Before the Web Storage API, remote web servers had to store any data that persisted by sending it back and forth from client to server. With the advent of the Web Storage API, however, developers can now store data directly in a browser for repeated access across requests, or to be retrieved long after you completely close the browser, thus greatly reducing network traffic. One more reason to use Web Storage is that this is one of few HTML5 APIs that is already supported in all browsers, including Internet Explorer 8.
  • In many cases, the same results can be achieved without involving a network or remote server. This is where the HTML5 Web Storage API comes in. By using this simple API, developers can store values in easily retrievable JavaScript objects, which persist across page loads. By using either sessionStorage or localStorage, developers can choose to let values survive either across page loads in a single window or tab, or across browser restarts, respectively. Stored data is not transmitted across the network, and is easily accessed on return visits to a page. Furthermore, larger values -- as high as a few megabytes -- can be persisted using the HTML5 Web Storage API. This makes Web Storage suitable for document and file data that would quickly blow out the size limit of a cookie.
Paul Merrell

Last Call Working Draft -- W3C Authoring Tool Accessibility Guidelines (ATAG) 2.0 - 0 views

  • This is a Working Draft of the Authoring Tool Accessibility Guidelines (ATAG) version 2.0. This document includes recommendations for assisting authoring tool developers to make the authoring tools that they develop more accessible to people with disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, motor difficulties, speech difficulties, and others. Accessibility, from an authoring tool perspective, includes addressing the needs of two (potentially overlapping) user groups with disabilities: authors of web content, whose needs are met by ensuring that the authoring tool user interface itself is accessible (addressed by Part A of the guidelines), and end users of web content, whose needs are met by ensuring that all authors are enabled, supported, and guided towards producing accessible web content (addressed by Part B of the guidelines).
  • Examples of authoring tools: ATAG 2.0 applies to a wide variety of web content generating applications, including, but not limited to: web page authoring tools (e.g., WYSIWYG HTML editors) software for directly editing source code (see note below) software for converting to web content technologies (e.g., "Save as HTML" features in office suites) integrated development environments (e.g., for web application development) software that generates web content on the basis of templates, scripts, command-line input or "wizard"-type processes software for rapidly updating portions of web pages (e.g., blogging, wikis, online forums) software for generating/managing entire web sites (e.g., content management systems, courseware tools, content aggregators) email clients that send messages in web content technologies multimedia authoring tools debugging tools for web content software for creating mobile web applications
  • Web-based and non-web-based: ATAG 2.0 applies equally to authoring tools of web content that are web-based, non-web-based or a combination (e.g., a non-web-based markup editor with a web-based help system, a web-based content management system with a non-web-based file uploader client). Real-time publishing: ATAG 2.0 applies to authoring tools with workflows that involve real-time publishing of web content (e.g., some collaborative tools). For these authoring tools, conformance to Part B of ATAG 2.0 may involve some combination of real-time accessibility supports and additional accessibility supports available after the real-time authoring session (e.g., the ability to add captions for audio that was initially published in real-time). For more information, see the Implementing ATAG 2.0 - Appendix E: Real-time content production. Text Editors: ATAG 2.0 is not intended to apply to simple text editors that can be used to edit source content, but that include no support for the production of any particular web content technology. In contrast, ATAG 2.0 can apply to more sophisticated source content editors that support the production of specific web content technologies (e.g., with syntax checking, markup prediction, etc.).
  •  
    Link is the latest version link so page should update when this specification graduates to a W3C recommendation.
Gary Edwards

Yahoo Could Be A Big Winner In The Battle For Developers - 0 views

  •  
    Last year Bartz vented to me about Yahoo's infrastructure problems - the company, she explained, was a compilation of fundamentally disconnected vertical silos, each with its own P&L, codebase, infrastructure, and culture. It was nearly impossible to roll out products that cut across, say, Mail, Homepage, Finance, IM, Search, and Flickr, because each instance required custom integration and coding. Yahoo was literally broken underneath, even as it looked consistent at the UI layer. Add in the issues of internationalization, and you went from nearly impossible to "not even worth considering." That mean stagnation, and on more than one axis. For one, it means it's very hard to find leverage between your internal resources, or to roll out new products that build on more than one stack. For another, it means it's next to impossible to open your company's resources up to third party developers (there's that word) who might want to add value to the ecosystem you've created.
Paul Merrell

RDFa API - 0 views

  • RDFa APIAn API for extracting structured data from Web documentsW3C Working Draft 08 June 2010
  • RDFa [RDFA-CORE] enables authors to publish structured information that is both human- and machine-readable. Concepts that have traditionally been difficult for machines to detect, like people, places, events, music, movies, and recipes, are now easily marked up in Web documents. While publishing this data is vital to the growth of Linked Data, using the information to improve the collective utility of the Web for humankind is the true goal. To accomplish this goal, it must be simple for Web developers to extract and utilize structured information from a Web document. This document details such a mechanism; an RDFa Document Object Model Application Programming Interface (RDFa DOM API) that allows simple extraction and usage of structured information from a Web document.
  • This document is a detailed specification for an RDFa DOM API. The document is primarily intended for the following audiences: User Agent developers that are providing a mechanism to programatically extract RDF Triples from RDFa in a host language such as XHTML+RDFa [XHTML-RDFA], HTML+RDFa [HTML-RDFA] or SVG Tiny 1.2 [SVGTINY12], DOM tool developers that want to provide a mechanism for extracting RDFa content via programming languages such as JavaScript, Python, Ruby, or Perl, and Developers that want to understand the inner workings and design criteria for the RDFa DOM API.
Gary Edwards

OpenStack Open Source Cloud Computing Software - 0 views

  •  
    OpenStack: The 5-minute Overview What the software does: The goal of OpenStack is to allow any organization to create and offer cloud computing capabilities using open source software running on standard hardware. OpenStack Compute is software for automatically creating and managing large groups of virtual private servers. OpenStack Storage is software for creating redundant, scalable object storage using clusters of commodity servers to store terabytes or even petabytes of data. Why open matters: All of the code for OpenStack is freely available under the Apache 2.0 license. Anyone can run it, build on it, or submit changes back to the project. We strongly believe that an open development model is the only way to foster badly-needed cloud standards, remove the fear of proprietary lock-in for cloud customers, and create a large ecosystem that spans cloud providers. Who it's for: Institutions and service providers with physical hardware that they'd like to use for large-scale cloud deployments. (Additionally, companies who have specific requirements that prevent them from running in a public cloud.) How it's being used today: Organizations like Rackspace Hosting and NASA are using OpenStack technologies to manage tens of thousands of compute instances and petabytes of storage. Timeline: Openstack was announced July 19th, 2010. While many components of OpenStack have been used in production for years, we are in the very early stages of our efforts to offer these technologies broadly as open source software. Early code is now available on LaunchPad, with an inital release for OpenStack Storage expected in mid-September and an initial release for OpenStack Compute expected in mid-October.
Gary Edwards

4 Pillars for Web Content Management Site & Content Optimization - 0 views

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

Life after Google: Brad Neuberg's HTML5 start-up | Deep Tech - CNET News - 0 views

  •  
    Pretty funny quote: "I think the future is going to WebKit". Brad Neuberg is leaving the gDOCS-Chrome JavaScritpt team to strat his own "HTML5" business. He's an expert on the SVG Web. About a year ago i read a lament from a web developer concluding that SVG was destined to be the Web docuemnt format, replacing HTML. Now i wonder if that guy was Neuberg? http://news.cnet.com/8301-30685_3-20018687-264.html Sent at 10:05 AM on MondayGary: Finally, the money shot: "Somebody will take some HTML5, and geolocation, and mobile applications, hook into Facebook perhaps, and they're going to do something unexpected." Read more: http://news.cnet.com/8301-30685_3-20018687-264.html#ixzz124U9xTZ3 Sent at 10:13 AM on MondayGary: I think Brad is right about the combination of location with the rest of the App Web. Olivia and i have had our EVO's for about two weeks now and it's amazing. She also has Citania's iPAD, also an amazing device. What stuns me about the Android EVO is how extraordinary the apps are that combine location with information specific to that location. Incredible. I don't know how i ever lived withou this. One things for sure, my desktop can't do this and neither can my notebook. Sent at 10:16 AM on MondayGary: There is another aspect i see that i guess could be called "location switiching". This is when you QR Scan QR barcode on something and the location of that objects life is at your fingertips. Everything from maps, street views, web sites, product history, artist/designer/developer and on and on. We went to the San Carlos Wine and Art Festival yesterday, where Laurel and San Carlos streets are closed off to traffic, and lined with food, wine and beer vendors of all sorts, artists and craftsmen, and even an antigue car show with ully restored automobiles and other vehicles. It was amazing. But then i started QR scanning! Wow. The Web merged with life like nothing i've ever imagined possible.The key was having the Internet in my pocket, and the Internet k
Gary Edwards

oEmbed: How New Twitter Could Help Combine Content From Different Sites - 0 views

  •  
    transclusion of hypertext documents. Transclusion is technically defined as "when you put that one thing in that other thing". In its current implementation, Twitter has declared that media which is shown within the Twitter interface comes from selected partners. But actually, the technology to allow embedding of rich media from almost any site already exists, using a system called OEmbed. Geeky stuff, but it's made by nice people who are pretty smart, and it lets any site say, "Hey, if you want to put our thing in your thing, do it like this". It works. Lots of sites do it. Nobody's getting rich off of it, but nobody's getting sued, and in between those two extremes lies most of what makes the Web great.
Gary Edwards

oEmbed - Web OLE - 0 views

  •  
    OLE for the Web: oEmbed is a format for allowing an embedded representation of a URL on third party sites. The simple API allows a website to display embedded content (such as photos or videos) when a user posts a link to that resource, without having to parse the resource directly. Table Of Contents Quick Example Full Spec Security considerations Discovery More examples Authors Implementations
Gary Edwards

Reinventing Copy and Paste - Anil Dash - 0 views

  •  
    We can all learn a lot of lessons from the history of DDE/OLE/ OLE3/COM /ActiveX/DCOM /COM+ (you can start reading up on Wikipedia to get some background) and how we went from everyone using best-of-breed standalone apps to one integrated, nearly monolithic Office. It basically all started with copy and paste. People who never spent a lot of time in singletasking, character-mode operating environments like the DOS command line don't recall that simply copying-and-pasting information between apps was difficult at the time. And part of the revelation of Windows for mainstream users (or Mac, for leading-edge tech fans), was being able to easily share data in that way. This was different than what Unix users were used to with the command-line pipe, or from what most applications do with feeds today, in allowing structured information flows between applications. There's a desire to combine data from different sources in an arbitrary way, and to have the user interface display the appropriate tools for whatever context you're in. The dominant model here, probably because of the influence of the early PARC demos, is to have toolbars or UI widgets change depending on what kind of content you're manipulating. Microsoft was really into this in the early 90s with OLE2, where your Word toolbars would morph into Excel toolbars if you double-clicked on an embedded spreadsheet. It was ungainly and ugly and slow, especially if you had less than an exorbitant 8MB of RAM, but the idea was pretty cool. And it still is. People are so focused on data formats and feeds that they're ignoring consensus around UI interoperability. The Atom API and Metaweblog API give me a good-enough interface if I want to treat a discrete chunk of information (like a blog post) as an undifferentiated blob. But all the erstwhile spec work around microformats and structured blogging (I forget which one is for XML and which one's for XHTML) doesn't seem to have addressed user experience or editing behavior
‹ Previous 21 - 40 of 108 Next › Last »
Showing 20 items per page