Creative Cloud plugin UI.

[Toto RoToTO]

Has anyone successfully created a UI for a  c++ plugin?

using Extension builder 3 (HTML5) or a third party library (Qt, ...).

Has anyone successfully make them (plugin - UI) communicate? 

Thanks,

Thomas.

[A. Patterson]

Not sure what you mean. We have lots of UI based on Qt in our C++ plugin. I'm not sure what you mean about having them communicate? They're in the same plugin, so I assume you're talking about having the UI in a separate plugin, though I don't know why that would be necessary.

[Toto RoToTO]

I got in mind the way flash-based extension and c++ plugin work.

- UI defined in the extension.

- Logic, business model in the c++ plugin.

- And finally CSXS events to make them share the datas.

Effectively, with Qt or such library, there is no such process to share the datas.

My explanation was not clear at all

[A. Patterson]

Well, if you really want to do that, I don't see why not. Its been a while since MAPublisher operated as multiple plugins, but back when it did, I discovered that a pointer in one plugin was usable in another plugin if you shared it, so long as the source plugin is never unloaded.

So I don't see why you couldn't have two C++ plugins, one with plugin logic and one with UI logic and have the first send objects to the second or vice versa.

[Toto RoToTO]

What about using tools provided by Adobe to create UI.

Eclipse and Extension Buidler 3.0, to create the HTML5-based extension containing the UI.

Xcode or Visual Studio and Illustrator CC SDK to create the plugin.

Then using events to make them communicate.

But right now, I do not know how to correctly create this extension and how to share datas with my c++ plugin.

Documentations provided by Adobe are not finished yet, I guess.

- Adobe has just provided a pre-alpha revision of Extension Builder 3.0 ?

- There is no explanations in the CC SDK documentation on how c++ plugin could communicate with HTML-based       extension.

- Flash-based extensions will be deprecated.

I need to port all I have already done to CC, but I don't know how to do such a thing.....

[A. Patterson]

I'm a PC guy so I can't answer any of those questions unfortunately. We don't use any of the Adobe stuff (Flash, HTML5, etc.) for our UI, just Qt.

[Toto RoToTO]

So you have already port all your stuff to CC?

To do that you just have to compile against the right revision of Qt, and that's all?

I guess I should consider this option in the near future.

[Guest]

i've tried to adopt this InDesign CC Plug-In example: http://blogs.adobe.com/indesignsdk/html-extensions-in-indesign/ ...but didn't succeed.

my test plugin (c++) doesn't respond to the 'OkClicked' event....

var evt = new CSEvent("com.adobe.csxs.events.OkClicked", "APPLICATION", "ILST", "mytestplugin1");

[Toto RoToTO]

This is quite confusing. Not being able to start porting our stuff just because definitve tools are not released yet.

[Guest]

did you try to adopt the InDesign code I was referring to?

[Toto RoToTO]

No yet, but I will asap and let you know if it works.

[Toto RoToTO]

Test in progress......

[Rick E Johnson]

Thomas, have you found a good tool for UI yet? I'm leaning toward HTML5 for CC on, as it seems to be the one that'll be around for a while. If I read Adobe's site correctly, the Enterprise membership required to use their Interface Builder is prohibitively expensive for me. I wonder if something like DreamWeaver is of any value in creating an HTML5 UI.

[Toto RoToTO]

Hi,

Actually, we use WebStorm as IDE for our extensions development.

WebStorm Features

We also use React (A JavaScript library for building user interfaces).

https://facebook.github.io/react/

UIs are defined in jsx files. We don't use Interface Builder.