Re : New member

2 messages Options
Embed this post
Permalink
guillaume.dreux

Re : New member

Reply Threaded More More options
Print post
Permalink
Hi Kent,

Thank you for the link to your wiki, I think this will be a great help for me.

Too bad that the links I referred to are a little bit ancient ( I don't think I will try to work on a plugin for FMP6 ) but that is a kind of approch for me.
Well, I have a lot of work to understand all of this ( and that's quite a long time I have not play with C++ ).

By the way, I have an another question. I read that a code is needed to write FileMaker Plugins ( registered for mac and for FileMaker ).
Is it absolutely needed to write a plugin to test or is it just for the selling ?

Thank you an other time.

Bye,

Guillaume.



----- Message d'origine ----
De : kent <[hidden email]>
À : [hidden email]
Envoyé le : Dimanche, 17 Août 2008, 22h50mn 58s
Objet : Re: [fmplug-prog-list] New member


Hi Guillaume,

Both the links you gave are referring to the old FM6< plugin API
functionality.

There is very little in the way of documentation for the FileMaker
API.  you just need to read the header files and plug away.

When I was doing this,  I started to put together a wiki,  which you
are most welcome to have a read of.  All I've done is given examples
of some functions as I worked out how to use them.

http://fmplugins. idma.co.nz/

cheers,

Kent.

On 18/08/2008, at 12:21 AM, guillaume.dreux wrote:

> Hello everybody,
>
> I am a new member of the group.
> I have search for some documentation on writting FileMaker plugins but
> i didn't find a lot of sources.
> I found that link :
> http://www.murrayc. com/learning/ filemaker/ fmplugins. shtml and that
> link :
> http://www.mactech. com/articles/ mactech/Vol. 15/15.01/ FileMakerProPlug -
> Ins/ . I also have the file included in the developper package of
> filemaker.
> I have read the text of the two links and they were well done but a
> little more explanation coul be good.
> So I request you all the link, documentation and books you can
> recommend me.
> I hope I don't bore you with my noobie questions.
>
> Guillaume.
>
>
> ------------ --------- --------- ------
>
> Yahoo! Groups Links
>
>
>

   


      _____________________________________________________________________________
Envoyez avec Yahoo! Mail. Une boite mail plus intelligente http://mail.yahoo.fr
Kent Lendrum

Server Side Plugins / Registration dialogs

Reply Threaded More More options
Print post
Permalink
Hi All,

I recently experienced an issue (my fault entirely) where a plugin was  
locking up a server side client (SSC) on  FileMaker 9 server due to  
the not registered dialog showing, and expecting the user to click 'OK'

I couldn't disconnect the SSC.  When stopping FMS9,  the files were  
reported as closed, but the SSC still had them open.  (Admin Console  
showed the file as closed, but still had 1 connected user)

The only way out was to stop the FileMaker Server completely.

End result, the files the SSC had open, we not closed properly and on  
restart were reported as such, and potentially damaged.


I have notified the developer of the plugin I was using, and have  
suggested that the 'Not Registered' dialog NOT show when the plugin is  
called unless it is running from within FM or FMA.  (ie. Don't show  
when on the server)

I have also notified FM, and requested better handling of a 'locked' SSC


I've written to you all, as this issue potentially affects all plugin  
developers, who show 'dialog' windows in their plugins requiring user  
interaction, and where the plugin may be used on the server  and/or  
web publishing engine.

Can I suggest all plugin developers, who show dialogs the user doesn't  
instigate  (such as a not-registered dialog), first check to make sure  
they are running on a Client, before showing.



I've since tested with another plugin, that shows a not-registered  
dialog, but times out after 30 seconds.  In this case, while it caused  
a 30 second 'delay',  it didn't lock the SSC.  (of cause,  being a  
SSC, no one actually saw the dialog)



In my case, the issue was cause because I'd updated to a new version  
of the plugin, requiring a new registration key, but had failed to  
update the SSC registration to the new registration key.


regards

Kent Lendrum
KAMAR Limited
Mount Maunganui
New Zealand