How to make ODOO application responsive to any kind of device? - odoo-10

I have created the odoo 10 application. I need to make that one responsive.When the resolution changes the alignments are changed. How can I make that one responsive to any device?

Try this theme, it makes odoo more responsive and more like the enterprise edition
https://www.odoo.com/apps/themes/10.0/backend_theme_v10/

In tables you have to use width and height in pixels
In forms, labels and fields you can use percentage for width and height

Related

Does a system metric or parameter exist for margins of icons on the desktop?

I find on Win7, when Align Icons to Grid is enabled, my desktop icons have a left margin of 13 and a top margin of 2. Are there any system metric or parameters that report that? Or even via IFolderView2 or anything else?
TIA!!
I would imagine you want SPI_GETICONMETRICS because MSDN says that SM_CXICONSPACING/SPI_ICONHORIZONTALSPACING is the grid size.

Adaptive Layout in Xcode 7.0.1

I have an app that displays properly in portrait view but truncates in landscape view:
From the research I have done it looks like I need to understand Size Classes and Adaptive Layout. However, I am only concerned with layout on iPhone 6, not across different devices (eg iPad).
Before jumping into Adaptive Layout and Size Classes, which seems quite a complex topic, I just wanted to ask if there is a simple way to make this app display properly in both portrait and landscape for iPhone 6.
Thanks in advance!
Yes, you can do it without size classes, but it requires a reasonable modification to your UI.
If you think about it then having a picker always visible makes no sense for you. Looking at your image I am puzzled as to which date is currently being adjusted.
What you want to do instead, is to make your picker appear after user clicks on one of the dates. You can make it slide up from the bottom. In addition, you can add a label above it which will clearly indicate which date the user is currently modifying. That label can be placed in the toolbar to make it easy to add "Done" and "Cancel" buttons to the left and to the right.
In my view it would make much more sense and would also solve your problem. The rest of the UI can be put in the scroll view if you don't have enough space on old devices (e.g. 3.5 inch iPhones)

Autolayout needed if only support one orientation?

Is Autolayout needed to setup for any subview, if my application only support one orientation (e.g., landscape right), applied for all UIViewControllers?
Yes, of course in the case of using animation I agree. But for the normal case, do I need AutoLayout?
Note: I am using XCode7, Swift, ios9
Understanding Auto Layout
Auto Layout dynamically calculates the size and position of all the
views in your view hierarchy, based on constraints placed on those
views. For example, you can constrain a button so that it is
horizontally centered with an Image view and so that the button’s top
edge always remains 8 points below the image’s bottom. If the image
view’s size or position changes, the button’s position automatically
adjusts to match.
This constraint-based approach to design allows you to build user
interfaces that dynamically respond to both internal and external
changes.
Unless you are making an app for one specific screen size, you will want to
use Auto Layout.
Use cases:
You want to support different size classes.
You want to support different screen sizes.
The content displayed by the app changes.
The app supports internationalization.
The app supports Dynamic Type (iOS).
Most of these changes can occur at runtime, and they require a dynamic
response from your app. Others, like support for different screen
sizes, represent the app adapting to different environments. Even
through the screen size won’t typically change at runtime, creating an
adaptive interface lets your app run equally well on an iPhone 4S, an
iPhone 6 Plus, or even an iPad. Auto Layout is also a key component
for supporting Slide Over and Split Views on the iPad.
Auto layout is not required at all. Even for multiple orientations.
However, If you don't use it, you'll have to manage placement for all the different sized devices yourself. So you might as well use it.

Managing image renditions on CQ5 / AEM DAM upload for responsive pages

Basic Challenge is as follows...please help if you can:
AEM 6 DAM - we want the DAM to automatically create various image renditions for each of mobile, tablet and desktop breakpoints. We want to preserve aspect ratio. We do not want to mandate the size/aspect ration of images that are uploaded to the DAM or used on the site.
There don't seem to be many sizing options apart from assigning both exact Width and Height for each rendition in pixels.
Will this mean that images are stretched or cropped if they don't fit the size exactly? Or, hopefully, does AEM give precedence to the WIDTH and allow the height to flow to maintain aspect ratio?
Your help on this, and on how best to execute this simply using the workflow so that the renditions are created automatically on upload, would be much appreciated.
Thanks,
Sentry1
UPDATE:::::: It appears that editing the 'Thumbnail' step of the out of the box Workflow for "DAM Update Asset" with [height,width] of the rendition in question actually preserves the aspect ratio whatever the initial height and width and creates a rendition based on whichever of the H or W is the smaller. Does anyone agree?
This is correct - as per the RenditionMaker interface in DAM API:
The aspect ratio of the assets base image will be preserved. Depending on orientation, either width or height of the target size will be smaller.
http://docs.adobe.com/content/docs/en/aem/6-0/develop/ref/javadoc/com/day/cq/dam/api/renditions/RenditionMaker.html
Another option could be to use ootb adaptive image component instead of creating renditions on upload.
http://blogs.adobe.com/experiencedelivers/experience-management/cq_5_6_and_responsivedesign0/
https://docs.adobe.com/docs/en/cq/5-6-1/developing/mobile/responsive.html
That way you don't fill your DAM with such renditions.

Standard margins between controls and standard control sizes

For example, Windows Forms Designer offers to place my controls on the form the way there are 12 pixels between form border and control border. It seems too much to me. Is it standard value? Also, as I understand standard button height should be 23 pixels. Am I right? Is there any documents that state all this? And can I setup this default values in Visual Studio (for example what if want default margin between control and form borders, when the snap appears, to be 6 pixels instead of 12)?
You can always refer to the Windows User Experience Guidelines. It comes with a handy table of recommended control sizes. There are drawbacks in using pixel sizes, however.
I don't know of a way to control the snapping behaviour in Visual Studio, though. Apparently it can't be done. You can set a grid size, but it won't affect the dynamic snapping lines.
To change the snapping options, go to Tools > Options > Windows Forms Designer. There is a 'Layout Settings' category that include a setting called 'GridSize'.
As far as standards are concerned, I see them fading away with the arrival of technologies that focus on the user experience (WPF/Silverlight). Look at Expression Blend for instance. Not very standard, right? I think delivering a great user experience in each app is much more important than having a common GUI style across all apps.

Resources