Am 19.11.2009 um 02:26 schrieb hansfba...@googlemail.com:
2009/11/19 Gregory Casamento :
Hans,
The only thing I'm wondering is why "pear" in particular? I think
it's good, because it's imaginative. Additionally, I wouldn't have
wanted the tool to be called gsxcodebuild or gspbxbuild or e
1) Separate out the code which does the actual conversion. It would
be useful to have this as a library in case it could be used by other
tools or apps, such as ProjectCenter.
That would be appealing to me. I could envision an event-based API
like for SAX, but I have to look at the code to s
ah! cool, then. :)
On Wed, Nov 18, 2009 at 8:26 PM, wrote:
>
>
> 2009/11/19 Gregory Casamento :
>>
>> Hans,
>>
>> The only thing I'm wondering is why "pear" in particular? I think
>> it's good, because it's imaginative. Additionally, I wouldn't have
>> wanted the tool to be called gsxcodebuil
2009/11/19 Gregory Casamento :
Hans,
The only thing I'm wondering is why "pear" in particular? I think
it's good, because it's imaginative. Additionally, I wouldn't have
wanted the tool to be called gsxcodebuild or gspbxbuild or even
gsbuild as I have a distinct allergy to things being pref
A few more comments about pbxbuild since we're on the subject. I
have a few suggestions regarding the code:
1) Separate out the code which does the actual conversion. It would
be useful to have this as a library in case it could be used by other
tools or apps, such as ProjectCenter.
2) Refacto
Hans,
The only thing I'm wondering is why "pear" in particular? I think
it's good, because it's imaginative. Additionally, I wouldn't have
wanted the tool to be called gsxcodebuild or gspbxbuild or even
gsbuild as I have a distinct allergy to things being prefixed with GS
simply because they ca
I recently I had an idea for a new name of the tool:
pearbuild.
I really like it and it would even preserve the namespace prefixes.
What do you think?
Hans
___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnuste
