Bugs item #1263139, was opened at 2005-08-18 17:28 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1263139...
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: zexy Group: None Status: Open Resolution: None Priority: 1 Submitted By: Frank Barknecht (fbar) Assigned to: IOhannes m zmölnig (zmoelnig) Summary: Startup messages too verbose
Initial Comment: Hi Iohannes,
this is a wishlist bug: Since Zexy2 single Zexy externals in the path spit out a lot of messages like:
[a2l] part of zexy-2.1 Copyright (l) IOhannes m zmölnig, 1999-2005 forum::für::umläute IEM compiled: Aug 5 2005 ...
when Pd is started. This makes it hard to read anything important that came before zexy is loaded, for example, if Midi devices were found etc.
My wish would be to follow the "no news is good news" approach and not print these messages or make them a lot shorter.
Thanks, Frank
----------------------------------------------------------------------
You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1263139...
SourceForge.net wrote:
Initial Comment: Hi Iohannes,
this is a wishlist bug: Since Zexy2 single Zexy externals in the path spit out a lot of messages like:
[a2l] part of zexy-2.1 Copyright (l) IOhannes m zmölnig, 1999-2005 forum::für::umläute IEM compiled: Aug 5 2005 ...
when Pd is started. This makes it hard to read anything important that came before zexy is loaded, for example, if Midi devices were found etc.
My wish would be to follow the "no news is good news" approach and not print these messages or make them a lot shorter.
hmmmm there was a bug in zexy-2.0 that displayed this verbosity for each object even when zexy was compiled as a single monolithic library.
the only thing i can (read: want to) offer, is that the verbosity could be stripped down to 2 lines instead of 7, like
[a2l] part of zexy-2.1 (Aug 5 2005) Copyright (l) IOhannes m zmölnig, forum::für::umläute, IEM 1999-2005
i admit that i am not really willing to give up the individual splash-screens for each external to be loaded. (this is partly due to the way i read the GPL; but it is likely that i will stay stubborn even if you can prove that i am misunderstanding the GPL)
mfg.ads.r IOhannes
Hallo, IOhannes m zmoelnig hat gesagt: // IOhannes m zmoelnig wrote:
[a2l] part of zexy-2.1 (Aug 5 2005) Copyright (l) IOhannes m zmölnig, forum::fÌr::umlÀute, IEM 1999-2005
i admit that i am not really willing to give up the individual splash-screens for each external to be loaded. (this is partly due to the way i read the GPL; but it is likely that i will stay stubborn even if you can prove that i am misunderstanding the GPL)
Personally I will just edit the verbosity out anyway in my version of Zexy. But maybe it's a more general problem: Zexy is one of the bigger libraries, and it alone produces 337 lines of output on startup (yes, I counted). But other externals also send their messages along on load (mine do, too) so with a growing number of externals the startup message overload will be even bigger. I'm not really sure, what to do about this, but it can get annoying, don't you think?
Ciao
Frank Barknecht wrote:
Personally I will just edit the verbosity out anyway in my version of Zexy. But maybe it's a more general problem: Zexy is one of the bigger libraries, and it alone produces 337 lines of output on startup (yes, I counted). But other externals also send their messages along on load (mine do, too) so with a growing number of externals the startup message overload will be even bigger. I'm not really sure, what to do about this, but it can get annoying, don't you think?
well yes, naturally.
so i see 2 options: the dumb one: use monolithic zexy ;-) the clever one: only load those objects/libraries you really need.
again: zexy should not produce 337 lines of verbosity on startup. if used in a monolithic way, it will produce 10 lines of a splashscreen (no, i have not counted ;-)); if you are using the broken up version you will get as much lines as you need ;-) i cannot imagine that you are using 43 distinct zexy object-classes in your patch.
mfg.ad.sr IOhannes
On Thu, 18 Aug 2005, Frank Barknecht wrote:
Personally I will just edit the verbosity out anyway in my version of Zexy. But maybe it's a more general problem: Zexy is one of the bigger libraries, and it alone produces 337 lines of output on startup (yes, I counted). But other externals also send their messages along on load (mine do, too) so with a growing number of externals the startup message overload will be even bigger. I'm not really sure, what to do about this, but it can get annoying, don't you think?
Perhaps Zexy's externals could be combined to form one big library. Then we wouldn't have this problem and it would take many less filehandles (one or two per loaded external) and also less RAM as there wouldn't be as nearly as much fragmentation in the code segment. (think of the PDA's!)
Ok, I'm kidding / trolling / etc: What I'm saying is true but the RAM savings aren't too significant given the ridiculously high amounts of RAM we have nowadays. :-)
____________________________________________________________________ Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju Freelance Digital Arts Engineer, Montréal QC Canada
Frank Barknecht wrote:
Hallo, IOhannes m zmoelnig hat gesagt: // IOhannes m zmoelnig wrote:
[a2l] part of zexy-2.1 (Aug 5 2005) Copyright (l) IOhannes m zmölnig, forum::für::umläute, IEM 1999-2005
i admit that i am not really willing to give up the individual splash-screens for each external to be loaded. (this is partly due to the way i read the GPL; but it is likely that i will stay stubborn even if you can prove that i am misunderstanding the GPL)
Personally I will just edit the verbosity out anyway in my version of Zexy. But maybe it's a more general problem: Zexy is one of the bigger libraries, and it alone produces 337 lines of output on startup (yes, I counted). But other externals also send their messages along on load (mine do, too) so with a growing number of externals the startup message overload will be even bigger. I'm not really sure, what to do about this, but it can get annoying, don't you think?
I would prefer that all this output go into a log file e.g. 'pd_log.txt' that would be overwritten each time pd runs. This way if something goes wrong there will be lots of evidence to sift through even if the terminal window disappeared or its contents scrolled out of the buffer, and if nothing is amiss the user need not worry about the drive filling up with timestamped logfiles.
Martin
Hallo, IOhannes m zmoelnig hat gesagt: // IOhannes m zmoelnig wrote:
hmmmm there was a bug in zexy-2.0 that displayed this verbosity for each object even when zexy was compiled as a single monolithic library.
I checked again on respective machine and indeed it is, when loading zexy as a *library* that I get 337 lines of announcement. Maybe I'm just still running a too old version of zexy then, the one with this bug?
I'll check a really fresh CVS checkout later.
Ciao
-
Frank Barknecht -
IOhannes m zmoelnig -
Martin Peach -
Mathieu Bouchard -
SourceForge.net