EchoSign @ Adobe

EchoSign is Adobe’s electronic signature service that “just works.” Or rather it just ROCKS! You simply login to their web site, enter the signer’s email, add a document and bam! The recipient gets an email they can sign immediately, forward to the correct person or return to the sender for changes. A recipient can even sign from their mobile device!

Continue reading…

Part 4 of MAX session follow up – BONUS – Packaging your component

This blog post is a quick overview on packing your CQ components for distribution.

This is a follow up to our MAX session on creating custom components.

Part 3 of MAX session follow up – Creating a new component

This is part 3 of our MAX Session(see link below). This video will cover how to create a brand new component from scratch.

This is a follow up to our MAX session on creating custom components.

Code walkthrough package

Part 2 of MAX session follow up – Creating an inherited component

This is part 2 of our MAX session follow up. In this code walkthrough I go over how to create a new component that inherits from a base stock CQ component.

This is a follow up to our MAX session on creating custom components.

Code walkthrough package

Walkthrough of overlaying or overriding a stock CQ or ADEP WEM component

In this code walkthrough I will show you how to overlay (override) the stock WEM/CQ TEXT component system wide.  This is a follow up to our MAX session on creating custom components.

Code walkthrough package

Halloween Fun with Arduino – Part II

Part II now complete! In this post, David Benge outlines the code and configuration steps he took to create his electronic Arduino controlled skull.

Halloween Fun with Arduino – Part 1

A Halloween Special from the A@A Team!  Adobe@Adobe Developer (and part time Pizza Deliver Guy) David Benge shows off his mechanized skull for putting the fright into the local trick-or-treaters at Halloween.  In Part 1, Dave shows off his setup using an Arduino microcontroller board, some LED’s and a light sensor to control his scary skull.

Happy Halloween!

Adobe Unified Communications Tool – Proof of Concept

The Adobe@Adobe Team would like to share some of the current progress being made on the Adobe Unified Communications Tool, or Unicom, as it is being labeled.  The vision behind Unicom is to have an all-in-one tool for finding and interacting with co-workers at Adobe.  Unicom would bring together phone, email, chat, the Adobe Directory, and Adobe Vibe, so employees would have one single application for communicating with one another.  The application encompasses SIP integration for phone (using Flash Media Gateway), XMPP for messaging, MS Exchange, and Adobe Connect.  The application is being targeted for tablets (iOS, Android, Playbook), smart phones, and desktop.

In the video, Jamie Godin (Senior UX/Visual Designer) and Mark Ellis (Product Solution Developer) take you through the design, as well as some of the features we’re currently envisioning.  It’s an exciting application that has the potential to dramatically alter the way we communicate with each other at Adobe!

Putting the Multi in Multiscreen

At this years Adobe MAX conference, I will be giving a session on “Putting the Multi in Multiscreen”. I’ll be presenting tip and tricks to take one code base and deploy it across OSX, Windows, iOS, Android and the Blackberry Playbook.

Check out the video below for a sneak peek at my session!

Display AIR version

When we were building our internal employee directory application we found a need to help determine what AIR version our employees had installed. With the following method you can enable end users to easily determine their AIR version right inside your application.
 
As an AIR application developer you can display the AIR version right in your application and make identifying this information for your users easier.
 
Some benefits of Displaying AIR runtime version in your applications: –

  • Troubleshoot application/runtime specific issues.
  • Helps identify pre-release or labs version of AIR runtime.
  • Troubleshoot air update framework related issues.

 
The NativeApplication class in the AIR SDK represents the currently running air application. The NativeApplication object is a singleton object, created automatically at startup and provides application information, application-wide functions, and dispatches application-level events. To get the NativeApplication instance of an application object refer with the static property NativeApplication.nativeApplication.

Code:
<?xml version="1.0" encoding="utf-8"?>
<s:WindowedApplication xmlns:fx="http://ns.adobe.com/mxml/2009"
xmlns:s="library://ns.adobe.com/flex/spark"
xmlns:mx="library://ns.adobe.com/flex/mx">
<fx:Script>
<![CDATA[
public function get airRuntimeVersion() : String
{
return NativeApplication.nativeApplication.runtimeVersion ;
}
public function get airRuntimePatchLevel() : int
{
return NativeApplication .nativeApplication.runtimePatchLevel ;
}
]]>
</fx:Script>
<fx:Declarations>
<!-- Place non-visual elements (e.g., services, value objects) here -->
</fx:Declarations>
<s:Label text='{ "AIR " + this.airRuntimeVersion + " Patch Level " + this.airRuntimePatchLevel }' />
</s:WindowedApplication>

I hope this small code is useful for you.