Please see our comment below to Ketan regarding this topic.

Thanks,
Josh van Tonder
Product Marketing Manager, Adobe

Please see our comment to Ketan regarding this topic.

Thanks,
Josh van Tonder
Product Marketing Manager, Adobe

To be clear, Adobe is still investing in LiveCycle and its business process related modules such as LiveCycle Process Management. Together with our partners, LiveCycle will continue to be sold in all industries, not just financial services and government. We believe LiveCycle will continue to be one of the leading business process technologies for automating forms related workflows and specific process-based use cases. We are currently in conversation with Gartner about the published report you referenced.

Thanks,
Josh van Tonder
Product Marketing Manager, Adobe

I have been doing some research also on Clientlibs lately and I think they work great for making your components more modular as you can include JavaScript and maybe some generic required CSS with the component instead of with the full design of the app.

@Linda: The Channels allow you to have conditional CSS and JavaScript includes…

This one will only be included if the user visits the page using Internet Explorer 6:
/etc/designs/geometrixx/clientlibs/ie6/themes/default: channels=”[ie6]”

This one will NOT be included if the user visits the page using a mobile phone:
/etc/clientlibs/foundation/swfobject: channels=”[!touch]”

Although I haven’t implemented the Channels myself yet, I probably will be soon… and I would really appreciate an addition to this article with a more elaborate overview of the possibilities of the Channels…

I’ve noticed some cq:ClientLibraryFolder nodes have a channels (String[]) property; I can’t find any documentation about these, any idea what they do?
/etc/designs/geometrixx/clientlibs/ie6/themes/default: channels=”[ie6]”
/etc/clientlibs/foundation/swfobject: channels=”[!touch]”

Suppose my “project.main” clientlib embeds “project.components” and similarly the “projects.components” clientlibs have a dependency for “project.main”. That way, the code can either include “project.main” (embedding all component JS in the one file) or include “project.main.components” (automatically including “project.main”). Does this make sense or will this cause conflicts/duplicates?

Linda