Simple Developer Questions

[kenneth2k1]

Hey, all!

I just have some simple questions that Im sure you guys can answer. I made a solution using FM Pro 5.5. However, I wanted to disable many features (such as view mode) so that the users cannot tamper with the layouts and such. I heard that FM Developer is what I needed. I was just looking for some general information that makes Developer different than regular FileMaker.

In addition, I was wondering if there was a way that one can disable the big FileMaker window that comes up when you start the program. Or, to be even more inquisitive, is there a way to put my own customized window up when the program starts? I suppose I should ask this question in one of the other forums.

I really do appreciate all your help.

Ken

[Vaughan]

Access to modes and file editing (value lists, define fields and scripts) can be stopped using passwords -- the plain client can do it. Create two passwords, an admin with full rights and a user that's limited. In the document preferences, set the file to enter the user password at startup. Now the file will automatically open with the limited access privileges.

Regarding the splash screen: developer might be able to do this through a bound file, but I dunno I've never used it.

[Steven H. Blackwell]

FileMaker Developer 5.5 is a full copy of FleMaker Pro 5.5 with 2 additional features built directly into the application: THe Script Debugger and the Database Documentation Report (DDR).

Additionally, FileMaker Developer 5.5 has the Developer Tool that performs a variety of functions on files, including inducing kiosk mode, creating standalone runtime engines, renaming certain menus, renaming files and updating internal links, and renaming suffixes.

The Developer Tool does not remove the splash scrren per se. If you create a runtime engine, the standard FileMaker Pro splash scrren is replaced by one that says "made with FileMaker Pro" or words to that effect.

Additionally, FileMaker Developer 5.5 contains the API's needed for plug-ins, Java classes, etc.

From time to time lads have been tempted to tinker with the splash screen using a Resource tool of one type or another. This is a prescription for trouble. It will almost certainly cause damage both to your application and to your files.

Make youself a splash scrren on a blank layout.

HTH

Old Advance Man

[Steven H. Blackwell]

quote:

---

Originally posted by kenneth2k1:

Thanks for your replies.

Forgive my ignorance, but what are kiosks and runtimes?? They sound pretty in-depth to explain here, so do you know of any good resources that I can look up to find more information?

---

A kiosk is a user interface without any menus or keyboard commands. Every action--and I do mean every action--must be scripted.

A runtime is a standalone application created by the FileMaker Developer Tool that allows you to open and to use FileMaker Pro files without having the FIleMAker Pro application itself. Runtimes are best used for demo purposes.

Old Advance Man

[SteveB]

While I haven't looked on the 5.5 disk, there was an example of a kiosk on the 5.0 CD (I assume it still is on the 5.5 CD).

If you want to really control the user environment, kiosk is the way to go...users would be hard-pressed to know that your app was made with FM (there are only a few error msgs and the closing screen which can be hacked that would still say Filemaker). But as OAM points out, because all the normal FM menus are removed, you must provide all the navigation.

You'll need the runtime if your users don't have copies of FM on their disks. Basically the Developer tool binds the database engine to your solution so that you can distribute standalone copies.

By the way, there is very much in the way of documentation around, except for the FM dev guide.

[ December 03, 2001: Message edited by: Steveinvegas ]

[kenneth2k1]

Ooooh...I see

Thanks for the reply, Steve.

Its starting to make more sense. But one question: I thought that once you develop a solution, it is considered a third-party item, and could not be sold along with a FileMaker product unless you bought certain legal licenses. So that's not true? Is there a way to move my solution into the runtime, or would I have to start from scratch?

Thanks!!

Ken

[Steven H. Blackwell]

FileMaker Developer runtime carries a license allowing you certain rights of distribution. I believe there is a copy of this lciense on the FMI website.

Old Advance Man

[SteveB]

You can sell as many copies of the single-user solution you want at no charge...that's part of the developer license. You don't have do do anything to create a runtime...certainly not starting over. However, if you go with the kiosk method, you'll need to provide your own navigation.

[Steven H. Blackwell]

quote:

---

Originally posted by Steveinvegas:

You can sell as many copies of the single-user solution you want at no charge...that's part of the developer license. You don't have do do anything to create a runtime...certainly not starting over. However, if you go with the kiosk method, you'll need to provide your own navigation.

---

Let's be clear here about what the restrictions and limitations of the run-time engine are:

1. It is standalone. It does not work on a network.

2. It does not support companion plug-ins. THis mean the Web Companion and related items. Some third party plug-ins are supported.

3. FileMaker, Inc. does not provide Tech Support to customers using the runtime. That is your explicit responsibility as the developer.

4. Read the license that accompanies the product. It spells out additional restrictions and requirements, such as the information screen.

HTH

Old Advance Man

[garhop]

Ken,

To elaborate on OAM's #4

The "additional restrictions and requirements" are basic and clearly spelled out in the Developer Manual (There's not much clearly spelled out in this manual, but these items are). They are not complex... for example you are reqired to list FMI as a copyright holder on a screen (but doesn't specify how large the font must be). If you desire FMI not to unlock the solution at the request (and payment) of a solution user (because you password protected your solution and the user wants to get into it), then you must list some specific terminology on a screen specified by FMI. This screen tells FMI that you, the developer, have limited the user's access to only the password protected privileges that you assigned solution users. Nothing difficult.

After fulfilling these requirements, you have unlimited distribution rights of your "Runtime" without any royalty payments to FMI. As Steve mentioned, these rights come with the Developer edition and are spelled out in the License.

To create a Runtime solution (your solution runs on the user's computer without him having an actual copy of FMP) you utilize a program that comes with Developer, but not with FMP. With this "Binding Program' you create a "Runtime" version of your solution by specifying your solution "File Name", plus whether you want the solution to run in "Kiosk" mode, any custom file extension you want and a couple other choices that you're offered. After making the selections, you tell the program where to place the files, click the "Finish" button and it does it's thing. That's it.

It is not difficult but does require some experimenting to learn how the various selections (that you made during the bind) affect the solution.

Also many, if not most, third party Plug-ins work with the Runtime as well as FMP.

Kiosks present their own set of potential problems. Steve has seen and resolved most of them.

HTH

Gary

[kenneth2k1]

Thanks for your replies.

Forgive my ignorance, but what are kiosks and runtimes?? They sound pretty in-depth to explain here, so do you know of any good resources that I can look up to find more information?

[GibCo]

FYI: While the runtime version do not work as a networked system, e.g. using a server version of FMP, it is possible for runtime versions to be used on a server. It requires that each user have their own runtime software and that these runtime versions be placed WITHIN a folder on the server. If they are not inside folders, only one user will be able touse their runtime software at a time. The individual folders can have set access privileges so only the individul or the individual's supervisor or the BIG BOSS, can access the runtime version inside the folder.

A supervisor or Big Boss can have a Master Runtime in their folder and periodically import from all the other folders so the data of all the individual folders would be in the master folder.

It doesn't allow for real time access to all the data the way a FMP server does and it is much more bulky to handle but not impossible especially when working with customers with very limited budgets due to the current state of the economy. It works until customers can acquire enough money to purchase FMP server and set up their database.

Bev

[dynaflash]

For what its worth, I dont know about FM 5.5 but I use developer 4 and there is no Filemaker splash screen when you create a bound runtime. As well, you can disable the closing FM splash screen with a setting during binding. basically there is no indication to the end user of the runtime that FM has anything to do with it (other than the icon you click to start the runtime).

The only thing would be the credits screen you must make according to the developer agreement you folks mentioned above.

Am I to understand that in 5.5 you cannot disable an opening FileMaker splashscreen when creating a runtime?

[SteveB]

There is no opening screen, but there is a closing screen in 5.0 and 5.5.

There are also some messages that will say Filemaker instead of your solution name...as usual they've done things half way.

[ January 31, 2002: Message edited by: Steveinvegas ]