-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 By the way, I just saw that we are already in code freeze. So when you can't do the documentation part until tomorrow evening I will try to find some free time tomorrow. ................................... : ___ _ ___ ___ ___ _ ___ : : | \ /_\ / __| _ \ _ (_) \ : : | |) / _ \\__ \ _/ / | |) | : : |___/_/:\_\___/_| |_|_\_|___/ : :........:........................: : Web : http://www.dasprids.de : : E-mail : [EMAIL PROTECTED] : : Jabber : [EMAIL PROTECTED] : : ICQ : 105677955 : :........:........................:
Ben Scholzen 'DASPRiD' schrieb: > Alright, all modifications are done and comitted with regarding tests to > SVN. Tho I didn't had time yet to update the documentation, could you > maybe take that part, Matt? > > Ben > > PS: If you like, you can include the auto-sizing stuff. > ................................... > : ___ _ ___ ___ ___ _ ___ : > : | \ /_\ / __| _ \ _ (_) \ : > : | |) / _ \\__ \ _/ / | |) | : > : |___/_/:\_\___/_| |_|_\_|___/ : > :........:........................: > : Web : http://www.dasprids.de : > : E-mail : [EMAIL PROTECTED] : > : Jabber : [EMAIL PROTECTED] : > : ICQ : 105677955 : > :........:........................: > > > Matthew Ratzloff schrieb: >> Well, the idea is you can add this improvement in the next release >> (1.7.1 perhaps) without breaking BC. Otherwise, it breaks BC. For now, >> you could just throw an exception if that value is not present. > >> So if the columnWidths field is not present, use auto-sizing; if a null >> value is present in the columnWidths array, use auto-sizing for that >> field. This way, field sizes can act as maximum width, used as you said >> with word wrap. > >> -Matt > >> On Mon, Nov 10, 2008 at 12:05 PM, Ben Scholzen 'DASPRiD' >> <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: > >> Hey again, > >>> Actually, you could do the column values in the options hash as well: >>> $options = array( >>> 'columnWidths' => array(9, 8), >>> 'separation' => 'header', >>> 'decorator' => 'Ascii', >>> 'padding' => 1 >>> ); >>> $table = new Zend_Text_Table($options); >> Well I'm really no fan of putting required arguments into an optional >> config array. When Zend once will create a standard about that, I will >> vote for required arguments staying as arguments, and only all the other >> stuff should move to an options array than. > >>> By the way, in the future you should be able to auto-size the table >>> around the data it contains. >> Well, auto-sizing would take the ability of auto-word-wrap, but yeah, >> that's a possible idea. > >> Ben >> ................................... >> : ___ _ ___ ___ ___ _ ___ : >> : | \ /_\ / __| _ \ _ (_) \ : >> : | |) / _ \\__ \ _/ / | |) | : >> : |___/_/:\_\___/_| |_|_\_|___/ : >> :........:........................: >> : Web : http://www.dasprids.de : >> : E-mail : [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> : >> : Jabber : [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> : >> : ICQ : 105677955 : >> :........:........................: -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkkYsnIACgkQ0HfT5Ws789BX1ACeM4zOuVRdwLF0w1YqNhc+32/i bZwAoMPOigpJ1ea4sXEUKrrQvwUt2Thf =5RAC -----END PGP SIGNATURE-----
