Eine Reaktion zu “27.05 | Design+Develop Meeting: BlazeDS und Interaction Design Tool in Aktion”

Kommentare abonnieren (RSS) oder TrackBack URL

Es gab j a noch einige offene Fragen zum Thema Flash Catalyst.
Mihai hat mal rumgefragt und konnte dem Entwicklungsteam einige Antworten entlocken:

1. Are custom components skinnable in FC? Using Metatags (required part etc)?

We don’t have custom component support in Catalyst for 1.0. You can create them from Catalyst and skin them but you can’t bring custom components in from Builder and skin them in Catalyst.

2. Will there be external stylesheet support in FC, so that the styles aren’t created inline. MAybe that several CSS files are generated like in the structure of the Style Explorer(Buttons.css, Containers.css, Lists.css …etc)

No CSS support in Catalyst 1.0 either. I’m not sure what the long term plans are.

3. Will there be support import Photoshop Layer Comps as Viewstates in FC ?

I think we will in CS5 but I’m not totally sure. I think the limitation is that Photoshop CS4 doesn’t have the same level of support for FXG that Photoshop CS5 will

4. Will there be a way to import FB-Projects back into FC after some development work is done? For example, when the components are set up for databinding(form generation in FB) and can now be styled in FC.

Nope, in Catalyst 1.0 we’ve only got a 1-way trip. Once you open it in Flash Builder you can’t bring it back to Catalyst.

5. Will there by Fireworks import to FC ? Because the Pages and Stage model in Fw makes it a great UI design tool compared to Ps and Ai.
most probably will have better support in CS5

Mathias am 13. July 2009 um 11:19 am

Der Kommentarbereich ist geschlossen.