Jump to content

Chrome/Android OS Compatibility - for GO


This topic is 2461 days old. Please don't post here. Open a new topic instead.

Recommended Posts

I would like to have 20 simultaneous users inputting data on tablets.  $200/tablet for Android, $600/iPad - hmmm.  Android compatibility would open up a world of possibilities.

Link to post
Share on other sites

We asked about this when Go was first showcased at DevCon a few years ago. I asked FMI again last year. They dont have any plans to do it.

Link to post
Share on other sites

With the direction we see in FM 12, I think we all see hope that there will be an easier, more powerful platform to open up development.  IWP would be great, were it more powerful...and HTML5. hehe But maybe that is asking too much?!

Link to post
Share on other sites
  • 5 months later...

Just to follow up on this thread - IWP solution worked great using Chrome.  I picked up 30 Trio Tables for $130 each.  Still I would like to see Go for Android :-)

Link to post
Share on other sites

This topic is 2461 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Similar Content

    • By jaboda
      Hi,
      This is a peculiar bug which seems to have appeared with a recent Chrome update.
      Create a Web Viewer control with the following content:
      "data:text/html,<html><body bgcolor=\"#EEEEEE\">HELLO</body></html>" Then view the layout in WebDirect in Chrome. You'll notice it doesn't display anything. Remove the bgcolor and it works as expected. It also works in FileMaker.
      There are numerous workarounds but I can't find out how to fix it.
       
      Anyone else experienced this?
    • By Jonathan Ackerman
      Hello,
      I am developing an app where users may login with Android or IOS via Webdirect.
      On IOS (safari) via Webdirect-- everything is fine.
      With Android(chrome)-- anytime the script refreshes the screen or switches panels-- all uncommitted data is lost.
      any ideas or workarounds?-- 
      my script checks validation and i really need to refresh to trigger conditional formatting
      also hoping to have a multi-panel entry so the user does not have to scroll to the bottom (layout has about 100 fields)
      thanks!
    • By Jonathan Ackerman
      When using WebDirect on an Android phone- sometimes when switching to a newlayout (via a scripted button)--
      all formatting disappears-
      see attached images.
      (also noticed that it also happens on webdirect via a desktop browser)
      anyone have ideas?
      thank you!
       
      with correct formatting:

       
       
      all formatting suddenly missing:

       
    • By CRexen
      Hi everyone,
      We have a newly deployed OS X 10.10.5 Server with FMS14 installed with only 3 databases hosted, all accessible via Web Direct.
      Now some of our customers are experiencing difficulties with even accessing our solutions, which we have narrowed down to local network problems at our customers.
      The problem is, the login window is not showing, and therefore they can't access the databases.
      Now, the problem is somehow browser based.. I went through the login process with a customer, which was sitting with Windows 8.1 / IE.. Now when trying to connect to the database the customer gets the following message "Failed to load the bootstrap javascript ./VAADIN/vaardinBootstrap.js"
      I then tried to connect to the database through Chrome, which worked perfectly fine!
      Is there something I can do for the customer or on our Server, to prevent this message for future customers?
      Best regards
      Christoffer 
    • By Jesper Søholm Biberkopf
      First a disclaimer. I'm well aware that WebDirect (FM13) is not build or supported for iOS or Android tablets. I've read the specifications. And yes, things should probably be done in PHP instead. Which is no doubt, what will happen eventually. But for a number of reasons, I'm involved in a couple of projects, where we have decided to examine the borders of WebDirects compatibilty first. 
      So I would like to hear any concrete findings from other crazy persons who have been experimenting on the wild side with WebDirect. What kind of functions and design methods work for you. What should we avoid in striving for a solution to best survive in e.g. Chrome on an Android tablet? Any experiences with Raspberry?
      Why is this interesting? Well, unless you publish your WebDirect solution on an intranet or another very controlled environment, there will always be users who will try to use whatever browser is at hand. So we might as well prepare and try to recognize and understand the things that can and will go wrong in those situations. Maybe we might even collect some useful feedback for the good developers at FMI. ;-)
  • Who Viewed the Topic


×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.