[GEM-dev] using logpost(3) for version message

IOhannes m zmoelnig zmoelnig at iem.at
Tue Sep 27 09:05:48 CEST 2011


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2011-09-27 02:39, Hans-Christoph Steiner wrote:
> 
> I think that Pd should startup with a blank Pd window, just like a blank
> canvas.  The new log levels makes this easy to accomplish.  Gem is the
> last library in Pd-extended that still uses post() for its version
> message.  I propose using the new 0.43 logpost(NULL, 3, "Gem version);. 
> Then by default, the Pd window is blank, but people can easily see all
> the version posts if they want to.

i don't see a point in using logpost() as is, for two reasons:
- - logpost() is there since 0.43, i want the Gem binaries to work on 0.42
and possibly 0.41
this is not a big problem for PdX, where you ensure that the pd binary
is accompanied by "matching" externals, but it is a problem if you
distribute binary builds of the external.
- - logpost() is mainly there to post verbose information that is attached
to an object. the Gem version is not attached to any object.

apart from that, i don't see much harm done in seeing a 10 line
splashscreen.
on the contrary, i really think that people should be made aware that
they have loaded Gem.
and people could use a lower log level to suppress these messages.

but feel free to report a feature request.


fgmasdr
IOhannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk6BdcwACgkQkX2Xpv6ydvS4lQCfcbRm01KduUaeogLIQjLtKX+D
RcsAoM68eEGheDGDS9BTOu4NViKSIw0W
=CfRe
-----END PGP SIGNATURE-----

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3636 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.puredata.info/pipermail/gem-dev/attachments/20110927/c977d827/attachment.bin>


More information about the GEM-dev mailing list