claris folder in runtime solution folder (mac)

[harryk]

The manual states that in the runtime solution folder a folder named 'claris' should be available. (start of Chapter 5).

The additional files delivered on the CD of Developer 5.5 and installed as

Filemaker Developer 5.5/Filemaker Developer Tool/Runtime Files

do not contain that folder.

Can any developer shine a light on this?

I expect the missing of certain claris files only can give problems importing graphics, but I'm not sure. I do not have a clean spare mac to try out..

Has somebody an idea where to get hold of those claris translators/graphic import filters to get a solution complete?

Harryk

[CobaltSky]

Hi Harry,

Which manual are you looking in - I can't find the reference in mine (might be a translation error?). Moreover chapter 5 in all the recent dev manuals I have here is about layout themes?!

A 'Claris' folder was installed with FM v4.x and earlier, but was not required for a runtime (may have been for earlier versions - I'm struggling to remember!) even that was renamed around the time when FMI took over management of the application.

[harryk]

Hello Ray,

My manual is the Developers Guide coming with Developer 5.5, the chapter is named Distributing Filemaker Pro Database Solutions.

It is so, that it is only the ILLUSTRATION mentioning the claris folder, not the text later in the chapter. That does not speak of that claris folder.

I remember that, when I installed my Developer 5.5 on my Imac, I had to fiddle around with some claris files in the system folder to make graphic import possible. I can imagine that similar problems might occur when people install a CD with a runtime.

On the other hand, graphic import is not needed in the solution and as I said, I don't expect those claris files necessary for something else than that.

I am in the fase of anticipating possible problems that might occur. One of the problems I read about in this developer-section of the site was that buttons did not work in a runtime solution, and as possible cause was given the fact that the solution was made under an early OS 9 version. As I work with OS 9.04..

But it seemes to me higly unlikely that an OS-version can cause such a problem. Do you have any ideas about that?

Thanks,

Harry

[CobaltSky]

I've not encountered such a problem - and my runtimes have been both bound on and bound for a broad cross section of system versions from 95 to XP and from 8.6 to 10.2.

I have a suspicion that such a problem would be more likely to be caused by corruption or a flaw in the solution than by the operating system.