Introducing HTML5 Extensions

Hallgrimur,

does it mean, my own flash based extension, developed over the last weeks to months, which just hit the market, will be obsolete from mid 2014 on? Does it mean, the customers of my extension will not be able to use it after their Photoshop CC has been updated by the clouds update mechanisms in mid 2014? Will there be some sort of "compatibility layer" after that "official removement of Flash based Extension support? Why do you have to completely remove the support for flash based extensions in favor of HTML5 based ones? Will your cloud customers be informed or even warned, that they will not be able to use their Flash based extensions any more?

Me as a developer need definitly more informations about that and your plans.

Thank you.

Does this include flash based custom XMP "File Info" panels?  Will they still be supported for CC  ?

Hi Hallgrimur,

What it actually means is that we'll have to have separate versions of the CS Extension for CS6/earlier versions (which many users will continue with forever, if possible), and CC. And this will happen far sooner than we were led to believe it would.

That is a problem, unless Adobe plans to make HTML CS Extensions backward compatible to CS5. You've said nothing about that so far, but it's critically important to CS Extension developers in the real world.

Thanks,

Ole [not Max Dunn, in spite of the login error]

Currently I design my panel interface in Flex Builder (not Extension Builder). Will I be able to use Flex Builder or the Extension Builder will be mandatory for development. Also, like Max has asked, are you planning any backwards compatibility? Otherwise it will be really hard to keep "old users" compatible with the changes...

And what about PlugPlug API technology? will you support it in the future? I mean will be possible use HTML5 UI along with the c++ core?

You do realize that the goals and interests of Adobe and those of the developer community are somewhat diametrical. Adobe wants to sell its latest products or recently to get people to sign up for creative cloud. The developer community wants to offer their products to a broad audience. That is we do care to support at least a couple of software versions into the past. Supporting only CC would really narrow our group of potential customers especially with the group existing that despise of the "software as a service" route of recent days. Now adding new features to PS CC is great, please keep doing that. HTML5 panels seem like an interesting idea, too.

But removing features from PS CC is a bad idea! In that you do two things. You force developers to develop two panel versions – one Flex based for CS4 through CS6 and one HTML5 based for the future PS CC. By removing support for the flash based panels you have been propagating for the last years you bring your customers into a predicament, too. They can’t use stuff they bought and that uses panels. They will not necessarily get free upgrades to any such products nor will such updates even necessarily be available. In the old perpetual license world that would have been no problem. You could keep you PS CSx (where “x” is any version) installed paralelly and be happy with it.

Today - if you don’t also own CSx - can you keep multiple versions of PS CC installed? I think not. Therefore removing functionality from PS CC that once was in PS CC is a really bad idea in my opinion. Especially since the Flash stuff is Adobe’s own technology it seems kind of nonsensical to kill its support.

Amem to that C.Oldendorf (although I think it will not change anything from Adobe's perspective )

Any specify date when Flash support will be removed from Illustrator CC?

Dear Developer Colleagues ,

i think the Change is the best for Photoshop.

Flash Panels are totally inflexible and extreme Slow.

Iam a Developer on C++ and Delphi since 20 Years and hadn't liked Scripting in the Past.

I think the Idea to integrate Webservices,Hybrid Applications and so many much more you don't know at this Time is really Cool.

HTML5 is really nice and much better as the old HTML Standard

The Migration from Configurator is easy.

Some things are a little bit different,you need in your Photoshop.jsx the "," as end of a function looks like this example.

Take the Time to understand the Technology and you have really much fun with extensionbuilder3.

Iam no Scripting freak but i like the Concept.

$._ext_PHXS={ // from the  generated Project its really easy to call they from the index.HTML and ext.JS

If you need functions or global Variables add they before "$._ext_PHXS={" begins.Wheter its goes to add they after that i don't know,i think its much more readable by working Structured :-)

$._ext_PHXS={

run : function

{

do.something

},

at the end is  "};" needed

cheers

Dirk

Flash Panels are totally inflexible and extreme Slow?

HTML5 is really nice and much better?

really?

Regards,

Gegham

Oh Yes :-)

If you worked with Brackets and Nodes you can do all you want.

You can Use Nodes to make Filters in the Addons or other nice things