General session keynote - Day 2
Kevin Lynch
mtv.adobe.com - MTV contest. Cards will be on your tables at Lunch.
Bruce Chizen
“What keeps me going” (Why still CEO of Adobe) Pains associated with the role - financial community working with them is like going to the dentist for a drilling without Novicane. Dealing with the press is facinating. Words flow, print the words. but put it around other stuff - words are the same, but the words surrounding them is not what he meant to say. Privacy. Anywhere he goes in the Bay Area, somebody knows who he is - people will point and so on - weird and awkward. And everyone knows how much he makes, and everyone thinks it’s too much. Legal risk - something he says today could put him into jail in 5 years. So why does he keep doing this? Two examples of why he puts up with all the time: 1st) Took wife and son and CFO and family to go see Dave Matthews Band, and there was an Adobe employee who knows a member of the band crew, and could get him backstage passes (!) — standing there with drummer, keyboard, lighting guy - and he’s in awe of them, and they can’t stop talking about Adobe products and how they want to try CS3. Felt it is great that he represents a company that impacts someone as famous and impacts DMB. 2nd) Dawns on him during general session that there are 4000 of us who have paid to come to MAX. Get the sense that we are truly connecting with one another, hope that learning from each other. Objective is to inspire the community, but can ensure community is inspiring Chizen and Adobe employees.
Kevin Lynch
Services, servers, and tooling areas - to be covered.
Business logic is being written and written over again. Lot of common patterns on how people are working together and sharing information. Trying to bake some of that stuff on both client and server side to help out that. Best user service + best server side logic together.
Steven Webster - take us through enterprise applications.
Experience matters, and are measured and well understood. What happens behind the glass? What happens when you hit the submit button? What happens on the backend can ruin the experience if it doesn’t work well. Going to cover LiveCycle ES - and those who will platform on top of LiveCycle #S.
mfg.com. They have people in different time zones, languages, etc - everything very technical, lots of data to be collected. Bad user experience. Can real time match customers to suppliers anywhere in the world. Can upload files, process them automatically into 3D pdfs, set policies and permissions to control access to that file. Can expire rights to view based on certain events. More control over IP using the LiveCycle ES stuff. What the internet was meant to do.
LiveCycle ES exposes a lot of useful experiences. mfg is a Flex app on top of Java archtecture. Has a lot of data to process - data and service oriented, and turns data into valuable information. 3D cad drawing, upload, and create a request for a quote (RFQ).
Wizard can help you out here - guide builder. Use a design pattern called a “Form guide”. Make the form into a RIA - you can style, skin and embed it into your existing experience. You can scan a piece of paper, it will recognize the form, and turn it into a RIA automatically. Form services.
Rights mgmt, digital signatures. IP is sometimes critical. Rights mgmt: you might have supplier A and B - send a quote, and ask for credentials (username and password), and they can then open and view information, and go one step further — you can prevent people from emailing a document, or even printing a document. Can go one step further — say Supplier A has been successful and wins the bid. Supplier B no longer needs the info - so their rights to view the document has been retired/revoked, Supplier A can still view it.
Service browser in LCycle- you can look for them, pick them, assemble them. You can even use 3rd party services, or write your own services. You have a Workspace with LiveCycle - flex based. So you can see the RFQs, and people can go into the workflow and see what’s going on and participate. All the Flex components are available, so you can build your own process management experiences. Lots of services available.
Available in the Developer Center for free. Even in the enterprise, and on both sides of the glass (front end and back end), experience matters.
Kevin Lynch.
Starting to make these available as hosted services, so you can start integrating them in your applications. We’re working on some services. Some available, and some in the works.
1) Scene7, hosted services.
Doug Mak. Scene7.
Leading “One Demand” rich media publishing systems. Easy to let you get rich media up to websites.
Enables creation of enhanced website experiences.
Automation makes it all easier. About getting more content out with your existing teams. Let you focus on value-added, take out the monkeywork.
Notion of single-master image, and the system dynamically renders whatever version you need. Saw tons of customers online, and see that most people using Adobe stuff. - Feeding it out to an Adobe viewer (Flash, Flex, PDF) — fill a gap between the content and the viewers.
Once you put up your rich media server, it’s just a web call to pull in the content.
Looking at Gucci.com. Site focuses on the content. Opens up a new page, and calls upon scene7 to open up a higher res view of the image. You can get a dramatic zoom in, and allow the user to drag and pan the image too. The customer can rotate the image as well. Designer can take the content for granted, and design the best experience that they can envision.
The URL you are calling has a lot of parameters. Those paramemters change, and you can call back a different size or whatever of the image. This is the basics. What if you can’t predict everything that you need? You can let the customer control their own application.
Showing teamworkathletic.com.
You can change the characteristics of the item - color, accent colors — change the color of a layer. You can go beyond the customization. You can even put graphics onto the image — he’s putting a number on a uniform that he has already change the color of. You can even customze the graphic. Graphic looks like it’s actually on the uniform (all sort of folded like the shirt and everything)
Customers will want to push their own images. So users can upload their own images (he uploads a MAX image and places it on the uniform).
You can print out the image — you can see that there is texture on the images that he has uploaded and everything — it renders a very photo-realistic image.
As simple as a URL call that you pull into the webiste. It’s a “software as a service” — you can email the URL to a person, or you can send them to a scene7 repository too.
Scene7 is strong in imagery, graphics, creating great web experiences. Called up QVC and asked if we could build a new AIR application with FLV and scene7 imagery.
Simulating a live stream from the show, and DVR like controls in this single scene environment. Or you can watch things that haven’t been broadcast yet. AIR means you don’t need to have browser controls there. And you can interact and browse along side the broadcast. Incremental information (cross-merchandising, other colors available). You can also look at 3rd party services — incorporate a complete view for the customer. You can email to a friend, shop with a friend, and so on. You can even index parts of the show — “heel cup” will take you to a specific part of the video that discusses that feature of the shoe.
Where going now other than AIR? Cross-media workflows. Going to take advantage of Adboe technology to be equally strong in print so you can do campaigns and so on. Next year launch a web self serving company so individuals or very small companies can sign up and create great experiences too.
Andrew Shebanow
Share beta. New service introducing - make it easy for people to share files, important documents with other people inside and outside the firewall, access anywhere on internet, big files. Free Gig of store - and people always have access to the latest versions of the files you’re sharing.
Experience - put things front and center : the most important part of the workflow. Can take files from library, desktop, and share files. Choose access level - anyone, or limited access (only people sent email to). Click open access, and click Share. Upload the file, sent an email to person shared it work, and in the background also thumbnailing the document. It lets you see who you have shared things with in the past — always remember who you have shared with, who has seen the document. Don’t have to manage the content.
Things interesting when you see what people see when they see the document. Combines flex and PDF — Flash preview of the document (like Flashpaper on steroids). You can zoom way in, pan around, and great performance. From here, other people can sign up and log in and get 1gig. You can see what other people have shared with you.
Also want to let people share on wikis, blogs, web pages — so there is an embedded view as well. Shows a blog, and you can add a bit of embed code. Now there is a view of the document of a presentation right in the blog — page through, switch to a specific page number, and you can click “share/download”, and you can get the source file from the author.
Fully resizable too - so you can either make a thumbnail embed, or a large one.
Has full set of REST APIs - upload and download, share docs, set permissions, retrieve doc thumbnails and previews, manage downloads. Allow for interesting mashups.
Also have set of AS3 libraries, so you can easily use the REST apis in your applications. Use standard XML to look at data returned, process, etc.
Simple application, will be interesting to see the apps you create. More stuff coming. Working on:
Improved file organization, tags filters, user defined.
On the server conversion for open document files.
Create a PDF and share from applciations.
adobe.com/go/share. Will allow in a few hundred more people at noon.
Danielle Deibler
Pacifica - creating a service that hope developers will use to incorporate high quality voice messaging, presence into their apps.
Talking to Dom remotely - he’s using USB mic and video. Starting an editing session. Dominic is actually going to be mixing a clip in remotely.
Focused on voice for now.
Eliminate complex back end - simple point to point connection, enabled by Flex components on top of the Pacifica service. High quality voice chat.
Text instnant messaging
Presence
NAT/firewall traversal - enable point-to-point
All in the existing apis that you use
Future:
- video chat
- P2P implementation
- AIR support
- PSTM access (traditional telephone network)
Private beta starting this month. Looking for developers with exisiting RIA that would be enhanced with this service. Also hiring developers and QA. Will also give some sneak peeks this evening.
By this time next year, want you to be showcasing applications that use this technology.
Nigel Pegg - CoCoMo
Real time client/server platform.
Lots of changes - rebuilt the entire client UI in Flex.
Took of all spare time because of moving to Flex - so remade UI a set of UI components. All of the pods have UI components with styles, skins and so on.
YOU can develop connect stuff in Flex.
Have foundation classes for Connect.
Real time AV streaming.
Also refactored, and opening up worldwie hosted service structure. Means that any Flex application that wants to mash up real time mutliple user experiences.
All take to build these kinds of applications is client-side Flex.
Made programming really easy so any client that embeds kokomo and has access can use.
Removed a lot of the async programming that would have taken to get into this.
Providing foundation classes that allow users to access low level stuff.
Shared whiteboard — full whiteboard from Connect offered as a real-time component.
Mash up these new components into anything you build.
Will be deploying with next version of Connect. Will have “adobe hosted services web APIs and mashups” today at MAX.
Collaborative methods: go to adobe.com/go/adc.
Kevin Lynch
Next category - tooling!
Figure out how to enable more people to create RIAs.
THERMO!
Enable people to design with some embedded logic.
Mark Anders Steven Heintz
Presents a component based model that makes sense to developers. But this doesn’t make sense to designers — they draw something and then give it to devs to implement. Thermo is to make the workflow between designers and devs to work together.
Allows designers to start with static images, and to transform it in place into a running applications. Wire interactivity (clicks, etc), and do it without writing any code. One of the hardest things to work with data… allows designers to create apps that use data without code or access to data source.
Thermo is a seamless workflow for devs working with FlexBuilder. Allows designers to take design much further and be part of the production application without loss of fidelity. Own the design during the development process.
Steven:
Looks and feels like a designer tool. PS IL and FW users will feel comfortable in it.
Creating a new blank application canvas. Use drawing tools to create parts of the application, add or manipulate graphics from another place.
Drag a rectangle that gives you an in-context display of x and y and so on. Then you get a panel that pops up where you can change properties.
Mark:
Thermo is creating a Flex application, and it’s creating the source code while you add things. Tags represent the graphics. Thermo has a complete representation of the graphics that Flash has, but becuase it’s Flex you can add states and transitions to make things come alive.
Steven:
Going to Photoshop, pulling up a comp that’s static of an app. Intended to be a music browser. Hard to express how you want the behavior to look and feel - put the images within layers though. Can work with this easily in Thermo when you import it.
Starting a new RIA but now going to import a PSD file. Have some options when you bring it in - how you want to treat layers. Want them as PNGs so you can work with it, and text as text (and preserve). Now it’s on the Thermo canvas — it has been converted to MXML. Showing code. Can use this code and use it to turn it into a real app. But still a picture of a Flex app… now going to turn it into a real app.
Rectangle is supposed to be a combobox. You can right click and “convert artwork” into a text input box (!! applause). Just with one change, you can run the app and now you can type into the text box. It picked up all of the font information that they had there.
When they go into the source code view, it highlights the asset that you have selected in the design view.
Thermo took the picture, extracted info about size and position and created a text control. Picked up the text and font in the graphic and set as properties of text control. Turned bitmap images into the inline skin of the txt control. Has the same look that the designer had.
Thermo will help you separate out the graphic so you can have a smooth workflow.
Now going to more complicated example - major UI of this particular app is 3 rows of images that sit on layer folders - represent selections. So we want to turn them into actual lists. If you were to do this in the actual application, it’s going to be dynamic data and pull in real album titles.
Using some dummy data in the application. Selecting artwork and converting artwork into a list. It will put a new list in place of these items, and we want to add behaviors so something happens when artwork is selected. And you can put them into design time data collection. Gives a name for the data collection. Design time data collection is now available so you can work with it when you explore the transitions and so on.
Define what happens when you mouse over the item. Select the item, and you go into an edit in place. In context display (pop up panel in context of your selection), and you can define an event — and it gives you a kind of “normal mode” coding widget that writes the code for you. Set Event / Action / Transition using pull down menus.
Thermo is detecting that there’s a transition/event that happens. In details state you’re adding aditional information - adding artist name for each album. Adding album name as well. Can tweak the design and animation using a timeline like thing at the bottom - sort of in the Property inspector area.
Now have an artist and album column in the design-time collection. You can enter real values into a property inspector. So going to add some data throughout dummy data. So adding lorem ipsum data feature, and you can add a number of words to add (so, 4 lorem ipsum words added into dummy data automatically).
Designer drew a scroll bar in the Photoshop comp. Scrollbars typically have several logical pieces (track. thumb, right and left arrows). Thermo knows how to handle this. You use the Convert Artwork to > Horizontal scrollbar feature. You can edit the scrollbar in place — you can see the common elements that the scrollbar has in the layers panel, and each bit that the scrollbar needs is in layers area. So now you can move artwork into the “thumb” layer so thermo treats it appropriately.
Now want to associate the scrollbar with the list. Need to click on scrollbar, and you have an indicator that lets you wire it up with another control. You get a wiring handle that lets you see other components that can accept this. So you pretty much can bind the albums to the scrollbar, so you can scroll them.
So you want to test the scroll - you can tell Thermo to duplicate the items you have so you have twice as many and you can scroll them. testing it, it works beautifually <big cheers>
A developer can open up the same project in FlexBuilder - at the same time. So the designer can keep working in Thermo, while te developer works on the logic and store and whatever.
Make it so designers don’t have to change the way they work, and they can give the developer something that makes sense. In lots of other environments, you would have to write a lot more code.
When get Thermo? This is an early sneak. You can expect something next year that you can experiment with.
Danielle Deibler
Pacifica - creating a service that hope developers will use to incorporate high quality voice messaging, presence into their apps.
Talking to Dom remotely - he’s using USB mic and video. Starting an editing session. Dominic is actually going to be mixing a clip in remotely.
Focused on voice for now.
Eliminate complex back end - simple point to point connection, enabled by Flex components on top of the Pacifica service. High quality voice chat.
Text instnant messaging
Presence
NAT/firewall traversal - enable point-to-point
All in the existing apis that you use
Future:
- video chat
- P2P implementation
- AIR support
- PSTM access (traditional telephone network)
Private beta starting this month. Looking for developers with exisiting RIA that would be enhanced with this service. Also hiring developers and QA. Will also give some sneak peeks this evening.
By this time next year, want you to be showcasing applications that use this technology.
Nigel Pegg - CoCoMo
Real time client/server platform.
Lots of changes - rebuilt the entire client UI in Flex.
Took of all spare time because of moving to Flex - so remade UI a set of UI components. All of the pods have UI components with styles, skins and so on.
YOU can develop connect stuff in Flex.
Have foundation classes for Connect.
Real time AV streaming.
Also refactored, and opening up worldwie hosted service structure. Means that any Flex application that wants to mash up real time mutliple user experiences.
All take to build these kinds of applications is client-side Flex.
Made programming really easy so any client that embeds kokomo and has access can use.
Removed a lot of the async programming that would have taken to get into this.
Providing foundation classes that allow users to access low level stuff.
Shared whiteboard — full whiteboard from Connect offered as a real-time component.
Mash up these new components into anything you build.
Will be deploying with next version of Connect. Will have “adobe hosted services web APIs and mashups” today at MAX.
Collaborative methods: go to adobe.com/go/adc.
Kevin:
Patterns emerging on the user interface. How can we share? We have a team called XD (Experience design). Inviting up Mike Sundermeyer
Over the last couple days, seen lots of things you can do with platform and authoring tools. How do you create an effective experience? XD has been working for 5 years developing Flex and Flash applications. Wanted to share with you some thoughts of what they’ve learned .
Adobe Inspire XD site. http://xd.adobe.com
Top level are case studieis - examples of great experiences. Defining and designing RIAs - less it more, what makes a good experience. Research library - design patterns, and in the future, components. Adding new sections : 10 minute design review where you can post your own work, and people will give advice (from XD and the community). Along side everything are community comments.
Case study: TV 2.0. Talks about challenges, what’s the heart of this thing (what’s the “spark”). So controls are small and only where needed in this TV app because the content is king, and what you want to look at. You can add comments everywhere, and there are x-refs, so you can go find patterns and principles that relate to the case study that you’re looking at. Single to the user where you are, where you go to, where you’ve been. In context displays and so on not to overwhelm user with too much information.
Have hot topics which are comments.
Alpha site, please take a look and give feedback.
Kevin Lynch:
Biggest Flash device in the world: Last year Jaguar, this year: yacht. IntelliSea — systems that tells diagnostics (monitor water, and whatever else) and so on (inputs from around vessel, and broadcast all the data to the server, and then they’re sent to Flex UIs). Flex brings ease of development, speed of development, Flash Player is fast so they can handle all the real life sensors (GPS, XM, and so on). RIFD tag system so they can tag crew members, so the alerm will sound “man overboard” voice. hehe.
Roadmap:
Moviestar beta on Labs.
Today at MAX: betas of AMP, buzzword, flex, share, AIR, Flash Lite 3 to manufactuers
Weeks: Moviestar, Pacifica beta,
2008 release: AMP release, Buzzword released, AIR, Flex 3, FMS, Flash Player Astro.
beyond: Thermo, Pacifica, CoCoMo, CF “Centaur”.
MAX awards tonight. Send your vote anytime to 48477 - send the letter M followed by the number of the MAX award person you want to win.
<video of AIR bus>

Loading ...
Recent Comments