[liblouis-liblouisxml] Re: New At This
- From: David Lalonde <david_lalonde@xxxxxxxxxx>
- To: liblouis-liblouisxml@xxxxxxxxxxxxx
- Date: Mon, 19 Aug 2013 14:27:44 -0400
A FileMaker Pro plug-in is not a library. It resembles a Photoshop plug-in. It
is a Mac OS X bundle that is only recognized by FileMaker Pro.
David Lalonde, CC
Business and database consultant / Consultant en affaire et en informatique
FileMaker Certified Developer / Développeur certifié FileMaker
D-Cogit
(519) 631-4646
(855) 631-4646 toll-free / sans frais
www.d-cogit.ca
Le 2013-08-19 à 13:59, Keith Creasy a écrit :
> I think so. I'm not sure. Is your plugin a library?
>
> Sure, you'd have to create functions ( methods) to let you avoid using a
> conflicting constant. There is also the possibility of using a namespace, it
> is what namespaces are for after all.
>
> I think if I were doing it I'd create a wrapper class for liblouis with a
> namespace declaration. Then, you could make your calls using
> namespace-specific constants. Your wrapper class would use those and call
> liblouis with what it expects.
>
> Your wrapper class could also handle any housekeeping tasks related to
> liblouis if there were any.
>
> It adds an extra layer but the cost, if done well, is inconsequential.
>
> -----Original Message-----
>
> Hello John and Keith,
>
> Your replies are greatly appreciated.
>
> Regarding Keith's post. Please let me know if my understanding is correct.
> You are suggesting I hide liblouis in a non-Cocoa library and then include
> the non-Cocoa library in my Cocoa code. Because the non-Cocoa library has its
> own header file, XCode would no longer see a conflict. I presume I would need
> to create equivalent non-conflicting constants in the non-Cocoa library if I
> needed to pass the constants (bold, italic, .) during runtime.
>
> Regarding John's post. The requirement that the plug-in be self-contained
> means I must use static libraries. XCode indicated it could not use the
> liblouis static library. The requirement that the plug-in be self-contained
> means the tables must be located inside the local package directory. As the
> plug-in installation location can vary from user to user, it must be a
> relative path. My preference would be to incorporate the tables directly in
> compiled code. Users expect to update the plug-in for updates, never the
> tables alone.
>
> David Lalonde, CC
> Business and database consultant / Consultant en affaire et en informatique
> FileMaker Certified Developer / Développeur certifié FileMaker D-Cogit
> (519) 631-4646
> (855) 631-4646 toll-free / sans frais
> www.d-cogit.ca
>
> Le 2013-08-19 à 13:16, John J. Boyer a écrit :
>
>> I think Keith is right. If you just unpack the tarball and then use
>> configure, make, make install it should compile with no problems. The dylib
>> will be in /usr/local/lib and the tables will be in
>> /usr/local/share/liblouis/tables I'm not sure what the path to the tables
>> might be in a static library, but you will probably need to emulate the
>> directory structure in share .
>>
>> John
>>
>> On Mon, Aug 19, 2013 at 04:43:55PM +0000, Keith Creasy wrote:
>>
>>> I do not work under OSX or COCOa but as for the constants you can probably
>>> just wrap the liblouis part in a file that does not include the COCOA
>>> headers and likewise not include the liblouis headers in your COCOA code.
>>> That should fix the conflicts.
>>>
>>> I'm sorry I can't be of more help than that.
>>>
>>> -----Original Message-----
>>>
>>> Hello,
>>>
>>> I am new at using liblouis and Apple's XCode and I need help.
>>>
>>> I am looking at making a plug-in for use in a software called FileMaker Pro
>>> on Mac OS X that will use the liblouis library. These are the requirements:
>>> the plug-in needs to be self-contained; the translation tables must be
>>> contained in the plug-in.
>>>
>>> Before starting off on this endeavour, I attempted to compile the liblouis
>>> code to familiarize myself with the code. I originally followed the
>>> instructions to make a static library. The library could not be used in a
>>> XCode project. I then attempted to compile the code in XCode. Two seemingly
>>> important errors came up: the path to the tables could not be resolved;
>>> some of the constants conflict with Cocoa constants (bold, italic, .).
>>>
>>> Can anyone help me by either giving me development advice or generously
>>> offering me a self-contained static library that functions in XCode?
>>>
>>> David Lalonde, CC
>>> Business and database consultant / Consultant en affaire et en
>>> informatique FileMaker Certified Developer / Développeur certifié
>>> FileMaker D-Cogit
>>> (519) 631-4646
>>> (855) 631-4646 toll-free / sans frais
>>> www.d-cogit.ca
For a description of the software, to download it and links to
project pages go to http://www.abilitiessoft.com
Other related posts:
