Viewport problem

0
0

I have put the metatag

<meta name=”viewport” content=”width=device-width, initial-scale=1″>

in my default.html header but I am having trouble getting it to work.  I have an iPod5 / Safari that I am testing with.

Should I be using “Pages” or “Forms” when I am using a mobile device?

We will likely have iPods, iPads and normal displays using WiseJ applications.  I would like to get my apps to work with WiseJ and the viewport but so far haven’t had much luck.  I have looked in this support site and seen a number of articles about ClientProfiles and the viewport but no real examples that I can go off of.  They articles have some info in them, but I haven’t had much luck with getting that info to work yet….

 

Thanks,

Shawn

General
Share
  • You must to post comments
Filter
Sort by: Recently Active
0
0

The viewport meta tag is used by the browser, not by Wisej. Some browsers may implement it differently. For example, apple decided not to honor disabling the zoom feature.

The client profiles configuration in wisej is simply a set of properties that identify a profile that you can call with different names: “Large Monitor”, “Old Screen”, or “Samsung”, … Whenever a client profile is matched you get the Application.ResponsiveProfileChanged event and adapt the controls accordingly.

I’ll attach a sample that logs the client profiles later today.

HTH

/Luca

  • Shawn Ramirez
    Let me explain what I am trying to do and maybe someone can give me a suggestion. We are using an iPod5 / Keyboard stuffer / WiseJ application (on Safari). The user scans a barcode, that is stuffed to the keyboard of our WiseJ application. The screen has 1 text field (for the barcode) and a number of buttons. I was hoping to make the application so that the user didn’t have to worry about scrolling to see / “touch” things, but that all would appear on screen in a size that is touch appropriate. So, are forms or pages (within WiseJ) the best option for something like this? The user will be going back and forth between forms/pages, but they will have a back button or the submit button will close the current form taking them back a form/page. Do I have to make my buttons larger manually so it is better for touch? Lastly, if someone uses an iPad instead, can I detect that and perhaps give them a different form with more info? Or in another related question, will their screen show exactly the same (controls and sizes) as if they were on the iPod5. Hopefully, this made sense. This is our first time branching into the mobile screen factor so we have many questions. Thanks, Shawn
  • You must to post comments
Showing 1 result
Your Answer

Please first to submit.