Does Anyone Use FileMaker Pro to Build iPhone Apps? [closed] - objective-c

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
My company has an app built using FileMaker Pro, and it is not a great app. It's not user friendly and it is hard to use. It also doesn't do everything that we need it to do. I don't know anything about Filemaker Pro, but it seems like it's an older system. Most people building iPhone apps are coding in objective C and swift right?
Does anyone have any input on Filemaker Pro? Anything you share would help. Is it old? Does it have a lot of limitations? Is it popular to use when building apps? Does anyone still use it or are most apps built in Objective C and Swift with a text editor?
Thanks for the input!

Your question is really off-topic for StackOverflow, but I will provide a couple of pointers:
FileMaker is not old - it's very current.
FileMaker is not a tool for building iOS apps. FileMaker is a tool (or set of tools) for developing and deploying cross-platform database solutions. One of these tools is FileMaker Go - an iOS app that will run a solution developed in FileMaker. This appears to the user as a native iOS app.
If the solution does not fit your needs, the fault is more likely to lie with the developer than with the platform.
If you're not running FileMaker as part of your business, then FileMaker Go is probably not the best choice for you.

Related

Karate - Robot for Java Based Desktop application. Unable to identify controls using Inspect.exe [duplicate]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 1 year ago.
Improve this question
For those that have used Karate robot for automating desktop applications in Windows written in Swing I'm curious to know what your experience was like? i.e. were the test runs reliable or flaky?
What was the best spy object tool you used to help identify Swing components and feed that to Karate scripts?
Also I see that https://github.com/intuit/karate/projects/3 MacOS support is in the backlog, is there any update on whether this update will support Swing apps on MacOS?
Appreciate your support, thanks.
Developer of Karate Robot here. Most known users are targeting Windows MFC / C++ / .NET or Delphi so there are no reports of Swing yet, but my guess is that it should work at least on Windows. "inspect.exe" works well to introspect the component tree. And we are looking for contributions for Mac, but there doesn't seem to be much interest - yet.
To summarize, I think your best bet is to contribute code to Karate, and you can make that decision based on your comfort with Java and your evaluation of how good Karate is in its current state and if it will "stay around", mature into a good desktop testing tool etc.

React Native - why is so few apps in AppStore? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I am learning React Native and considering developing IOS apps for my clients in it. I'd like to see some sample apps in AppStore, but there is just one. Why is that?
I see so much hype about this technology, but it looks like almost nobody uses it. Or is there any other reason for it? I'm already working with React and would like to add React Native to my skills, but don't know, if it's worth it. There are some interesting tutorials on the web, but no real samples in AppStore.
Actually there is already an app in the app store according to this blog post.
And as far as I know two of facebook's apps have been built using react-native (maybe not completely ): Groups and Paper.
So if you have any concerns, whether react-native is production ready: I think if Facebook can use it in their production apps it's probably good enough for you too ... ( no offense ) :D
People are still bootstrapping their knowledge and building applications.
Also, the technology is still in its infancy.

How to run Clipper Application [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I have a legacy code base written in CLIPPER. I don't have any idea of CLIPPER programming language.
How do I get started with it and deploy this application? Is it a scripting language OR some sort of OOPS language any study reference will be helpful
Thanks in Advance
Kaushik
Clipper is 16-bit compiler for character-based (not GUI) applications running on MS-DOS platform. There are, however, 3rd-party tools that will allow to produce 16-bit Windows GUI applications.
It's still owned by Computer Associates but all future development and support was delegated to GrafX long time ago.
The last released version was 5.3 but many developers stayed with 5.2e. The last update was around Y2K.
There are Harbour and xHarbour open source projects that developed their own compilers for this language (which in the beginning was similar to dBase III).
You can find information about the language and some 3-rd party libs in a Clipper section of this web-site.
Native Clipper compiles all its code into a single executable that runs on user desktops. Its data and index files are usually placed on a network share. Executable itself can also be placed on a share with user desktops having a short-cut to it.
Native Clipper applications (16-bit) will not run under 64-bit Windows. There are emulators (like DosBox) that allow to overcome such limitation.
Clipper related questions can be asked on comp.lang.clipper newsgroup.
If you have more questions add them as comments here.
Another good resource is Norton Guides for Windows, you can download it from a great site with lot of information about Clipper:
Download NGW from www.the-oasis.net.
I was unable to find the .NG files on that site, but you can see them online here if you want or try to found the files googling them.

Windows version of Mac App [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
I have a Mac App that uses the NSKeyedArchiver to save persistent data and it all works fine, but thinking ahead ideally I would like to be able to create a windows version. The current App is all in objective-c using cocoa as I did not think of portability when I first started writing it. I would be happy to make a windows version from scratch but obviously the two need to share data. I am a complete beginner when it come to cross-platform apps. What should I do?
Thanks in advance.
You either need to find (or write) code/a library to read NSKeyedArchiver plists on Windows, or you need to release an update to your Mac app that converts the keyed archives to something more generic, like a JSON- or XML-based format.

How to know that, the system you are building is a better as Desktop Application than an Web Application? [closed]

Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 4 years ago.
Improve this question
How to know that, the system you are building is a better as Desktop Application than an Web Application?
My top 3:
I need to use/control the hardware directly (printer, graphic card...).
I don't care if my project is platform dependant.
Need complex user interface (OK Web 2.0 is better than ever, but it's still hell to make advanced specialized stuff to work in all Web browsers).
Interesting question. in practice the answer hinges primarily on the deployment requirements:
If you want very broad and "instant" deployment - then use HTML and HTTP.
if you or your organization have administrative control over the computers on which the app will be deployed, making it a "desktop app" is acceptable.
Most apps lie between those extremes.
It depends on your target audience, desired features, and what delivery method makes the most sense.
It might help to answer these questions:
1) Who will use this?
2) What will they do with it? (think about thinks like media operations, data storage,..)
3) How will they best be able to get this app?
4) What operating system(s) will it support?