Comments on: Custom Project Builder Templates

By: Eric Blair

Eric Blair — Wed, 12 Nov 2003 05:00:30 +0000

But if the file name is NSSString-EBExtensions.h, that doesn’t help me separate the “NSString” and “EBExtensions” strings.

By: Martin Parretti

Martin Parretti — Tue, 11 Nov 2003 14:39:32 +0000

In PB try using the macro

FILEBASENAMEASIDENTIFIER

which uses the filename minus extension, and ensures that it is a legal C identifier.

By: Michael Tsai

Michael Tsai — Fri, 26 Sep 2003 05:43:24 +0000

I was thinking that the glossary entry could use AppleScript to do the parsing. I think you’re right about adding the files to the project, though.

By: Eric Blair

Eric Blair — Thu, 25 Sep 2003 09:53:27 +0000

How so? When I write categories, my files are usually named ObjCClass-ExtName.(c|h). I think the BBEdit Glossary would have the same problem as the Project Builder templates --- the glossary can't parse the file name to separate the class and extension names.

Of course, you could create a glossary entry that created a took text in the format of "ObjCClass (ExtName)" and populate the file from that, but then you'd need two variations (.h and .m files) and you'd have to add the file to your project by hand.

I just don't see a way to automate the process as nicely as can be done for Objective-C classes.

Maybe I should just create a template that leaves space for me to enter the class and extension names by hand...

By: Michael Tsai

Michael Tsai — Thu, 25 Sep 2003 05:59:12 +0000

Sounds like a job for a BBEdit glossary item.