Responsive design avec WebCenter Portal

http://www.oracle.com/technetwork/articles/enterprise2/zheng-responsive-portal-app-2190915.html

http://www.ateam-oracle.com/adf-webcenter-responsive-adaptive-design-beyond/

I’m not aware of guidance for using Zurb Foundation in ADF-based pagesHowever, given that any such JavaScript framework has to interact with ADF’s Rich Client Framework, the recommendations/pitfalls/best practices will follow what the ADF team or the A-Team recommend Here’s an article by A-Team–

http://www.ateam-oracle.com/adf-webcenter-responsive-adaptive-design-beyond/
Here's a video by ADF PM--

https://www.youtube.com/watch?v=9_6K4xJov88

http://www.slideshare.net/stevendavelaar/running-adf-faces-on-tablets-and-mobile-phones

Responsive design is possible. Adaptive design is very hard - for two reasons - because of JDev restrictions (Portal uses 11.1.1.7), and the client side is ugly (see slide 19 of the presentation).

My experience is that you have to hand roll this yourself. Any attempt to utilize additional responsive frameworks (bootstrap, etc., etc.) will fail

When it comes to adaptive design, there is a simple ADF JS trick that you need to implement to pass on additional data to the server-side.

Once this is done, adaptive design is rather straight forward.

Have a look at this article which explains the ADF JS part:

http://www.ateam-oracle.com/adf-webcenter-responsive-adaptive-design-beyond/

And in this article: http://www.ateam-oracle.com/building-a-hybrid-application-with-mobile-application-framework-and-webcenter-portal/

I explain how to use this technique to build a hybrid application with WebCenter and MAF.

When I did the Portal Framework Workshop, I experimented a lot with client side JS firing events into the portal app on the server, creating an adaptive application. As you have pointed out, you need to create that custom Java code in your application, and for me working in a framework app, it was, well, not simple, but straightforward.

In the new world where everything is now based off the PortalBuilder framework (i.e. Spaces), it’s difficult (at least for me) to understand where (in the context of uploading page templates, etc.) one defines the custom Java code, how one incorporates that into the PortalBuilder framework, and how you ensure it: a) works, b) does not have any unexpected side effects, and c) does not collide or conflict with any other client event handler. For example, can team A build an adaptive/responsive PortalA, while team B builds an adaptive/responsive PortalB on the same instance? Or, do you design a common adaptive/responsive layer that both must use?

Yannick