<![CDATA[Novalys Help Desk]]> <![CDATA[Appeon Mobile - Windows controls transposed into the Mobile world]]> 1:  The Windows/PB controls are transposed into the iPad/iPhone world by implementing the appropriate iOS controls. Will this process be fully automated by Appeon Mobile? 

Yes, this process will be fully automated by Appeon Mobile.  


2: For some complex PB controls that have no equivalent within iOS, how does Appeon Mobile transpose the Windows/PB controls into iPad/iPhone world?  

Appeon Mobile can transpose automatically all of supported PB controls. For the complex PB controls that have no equivalent within iOS, Appeon will design a set of cross-platform controls that will be run on iOS, Android, Windows Phone and other platforms.

 

3: Are there any properties/functions that Appeon Mobile cannot transpose automatically for some reason? 

  Only some properties/functions related with Mouse-move, Keyboard, etc. 

]]> <![CDATA[Appeon Mobile - Our PB UI is too big for mobile. How to migrate i...]]> We automatically map PB UI controls to corresponding native mobile UI controls.
In some cases, like PB menu, toolbar, etc. we have adapted them to be usable in the mobile form factor.
Also, your application will automatically benefit from a modern mobile UI look and feel.
However, if leveraging windows from an existing PB application designed for a desktop client,
you will need to make some adjustments to the size of the window, size of the controls, placement of the controls, and possibly the navigation.
The Appeon Emulator will allow you to view what the app would look like on the targeted Mobile device.
Also, we provide APIs so you can programatically retrieve the exact dimensions of the target device and dynamically resize your UI to fit virtually any type of screen. ]]> <![CDATA[Appeon Mobile - How do you transform Mouse scrolling in the Mobil...]]> In the Mobile device the DataWindow can be scrolled by just using hand gestures on the DataWindow itself.
When doing so a scrollbar will appear to indicate how far the data has been scrolled.
This is consistent with how Mobile devices with touchscreens handle scrolling.]]> <![CDATA[Appeon Mobile - Can I change the look & feel of the autogenerate...]]> Yes, you can change any control/object properties in PB, and the changes will fully reflect on the mobile UI.
You can even develop your own PB/Mobile framework, to ensure consistency across several applications and jumpstart new projects
In the later versions, we will increase the developer flexibility to make even more radical changes to the UI.]]> <![CDATA[Appeon Mobile - Can you create mobile controls like Carousels?]]> We automatically map PB UI controls to corresponding native mobile UI controls. 
In some cases, like PB menu, toolbar, etc. we have adapted them to be usable in the mobile form factor (i.e. looks quite different from the PB version). 
Also, all PB controls will automatically benefit from a modern mobile UI look n' feel that the native mobile OS provides. 
After Appeon Mobile 1.x, we will expand controls that can be used in PB design time to include more exotic mobile controls.]]> <![CDATA[Appeon Mobile - Can I deploy existing PB apps to mobile (Like App...]]> Yes you can deploy existing PB apps to Mobile but please take into account the following information:

Besides modifying the unsupported features, we also recommend adjusting the PB app UI, navigation and possibly the functionality to best suit tablets and smartphones. 
At a minimum, we suggest adjusting the window size, control size, row height, font size, etc. so they are easy to operate on the targeted device.
Appeon Mobile provides an emulator to simulate your app on a given Mobile OS and identify necessary modifications to fit the device's UI.
Appeon Mobile 2.5 will also provide templates in the form of a PB Framework that will jumpstart new apps targeting a given Mobile device.

]]> <![CDATA[Appeon Mobile - UI resize: can we use the same CODE for tablet & ...]]> Appeon Mobile provides a function to automatically resize the UI, so one code can be used for both targets.  However, if the customer’s window has too many DataWindows and controls, then when Appeon resizes it to iPhone it will be too small for the user to work effectively and efficiently.  So the point is if a customer really wants to target both devices with 1 code they should design their app so it works well on iPhone. 

If a customer is targeting both devices, he would need to create different PB windows for phones vs. for tablets. The best strategy is to include 2 sets of PB windows in a single PB application. The application would select the proper windows depending on the user device. Appeon provides a function to detect whether app is running on tablet or phone. So the customer would need to do a little coding to call the Appeon function and depending on the device type open the appropriate window.

If a customer only wants to target tablets and desktops, it should be possible for the desktop and tablets to share the same PB windows since tablets have fairly decent screen size.  It may not be necessary to do such switching or develop 2 sets of PB windows. 1 set of PB windows should be enough

]]>