| 00:34.54 | JeffM | none of the others really make sense |
| 01:15.21 | *** join/#bzflag Nitroxis|Off (~pro@wtwrp.de) |
| 01:15.50 | *** join/#bzflag Nidhoggr_ (cj@jormungandr.dragon.org) |
| 01:15.51 | *** join/#bzflag Thot|offline (~Thot@wtwrp.de) |
| 01:40.01 | *** join/#bzflag jeffm (~jeffm@cl211143.wl.callutheran.edu) |
| 01:40.01 | *** join/#bzflag jeffm (~jeffm@unaffiliated/jeffm2501) |
| 01:40.01 | *** mode/#bzflag [+v jeffm] by ChanServ |
| 02:04.40 | *** join/#bzflag spldart (~spldart2@c-98-199-190-28.hsd1.tx.comcast.net) |
| 02:04.40 | *** join/#bzflag spldart (~spldart2@bzflag/contributor/spldart) |
| 02:04.40 | *** mode/#bzflag [+v spldart] by ChanServ |
| 03:12.26 | *** join/#bzflag Gabe_G23_ (uid557@gateway/web/irccloud.com/x-cxusgyslzyvfhotb) |
| 06:02.50 | brlcad | blast007: it's been discussed before in various places -- that "restriction" doesn't impose any new restriction on the freedoms that free software guarantees |
| 06:03.38 | brlcad | free software licenses are a positive set of granted rights on top of copyright restrictions |
| 06:04.13 | brlcad | but you're not actually ever granted the right to sell a work piecemeal |
| 06:04.34 | brlcad | so that clause is effectively moot |
| 06:05.46 | brlcad | the fsf licenses do allow sale, but they refer to the work as a whole |
| 06:06.56 | brlcad | that's why it passes dfsg muster and that of others |
| 06:14.11 | brlcad | I believe I've even heard that argument applied to source code as well, that an author is allowed to require a work retain its authorship integrity |
| 06:14.41 | BulletCatcher | The LGPL license under which BZFlag is distributed says "you have the freedom to distribute copies of free software (and charge for this service if you wish); that you receive source code or can get it if you want it; that you can change the software and use pieces of it in new free programs." |
| 06:14.54 | brlcad | meaning that you could prevent redistribution of portions, it's all or nothing |
| 06:15.02 | BulletCatcher | That seems to pretty clearly allow selling parts of it. |
| 06:16.05 | brlcad | but that's the point -- it doesn't actually |
| 06:16.48 | brlcad | that's two separate rights discussed |
| 06:17.19 | brlcad | redistribution right (which only refers to "the work") and a use right (which allows piecewise use) |
| 06:21.45 | BulletCatcher | Are you saying the LGPL grants the right to "use" parts of a work but not the right to redistribute just those parts? |
| 06:22.54 | brlcad | so in the case of lgpl, it gets a little interesting but basically yes |
| 06:23.11 | brlcad | in the case of lgpl, it also grants fairly liberal derivative works |
| 06:23.42 | brlcad | so you can create a derivative work that's a subset and that work (that you licensed) could be sold as the work |
| 06:24.17 | brlcad | fairly specific to gpl/lgpl, but not specific to the free software criteria |
| 06:25.22 | brlcad | there's several threads with more in-depth legal discussion on the distinction |
| 06:26.24 | brlcad | but (my claim) it mostly boils down to the free software principles allowing authorship integrity -- doesn't require it, but allows it |
| 06:28.24 | brlcad | GFDL is a good case study since it's been one of the more fringe cases that involve authorship integrity |
| 06:29.59 | brlcad | if I write a book, my name is on the cover -- just because I grant you the right to redistribute the book doesn't mean that I'm necessarily okay with you turning it into a porno rag with my name still on the cover |
| 06:30.55 | brlcad | free software guidelines say I gotta allow derivative works and redistribution, but that doesn't mean I can't impose some integrity criteria |
| 06:31.05 | BulletCatcher | I promise it will be done tastefully. :-) |
| 06:31.27 | brlcad | :) |
| 06:31.33 | brlcad | send me copies |
| 06:32.06 | BulletCatcher | I charge a fee for that! |
| 06:34.56 | brlcad | it's okay, I have a patent so I expect royalties |
| 06:39.35 | BulletCatcher | makes sure the actions described in the deritivate work fall outside the scope of the patent |
| 07:20.45 | *** join/#bzflag jeffm (~jeffm@cpe-76-167-236-199.socal.res.rr.com) |
| 07:20.46 | *** join/#bzflag jeffm (~jeffm@unaffiliated/jeffm2501) |
| 07:20.46 | *** mode/#bzflag [+v jeffm] by ChanServ |
| 08:53.24 | *** join/#bzflag PrezKennedy (~DarkCalf@2002:ade7:2862::ade7:2862) |
| 08:54.42 | *** join/#bzflag meeba_ (~lamer@c-75-71-180-64.hsd1.co.comcast.net) |
| 08:56.46 | *** join/#bzflag alezakosz (~kongr45gp@helit.org) |
| 09:00.41 | *** join/#bzflag bier (~bier@helixnetworks.de) |
| 10:40.44 | *** join/#bzflag I_Died_Once (~I_Died_On@unaffiliated/idiedonce/x-1828535) |
| 11:17.30 | *** join/#bzflag I_Died_Once (~I_Died_On@unaffiliated/idiedonce/x-1828535) |
| 15:46.59 | *** join/#bzflag TD-Linux (~thomas@about/essy/indecisive/TD-Linux) |
| 15:50.22 | blast007 | alezakosz_away: I plan to experiment with Mootools' own form validator stuff as well |
| 15:50.25 | blast007 | http://mootools.net/docs/more/Forms/Form.Validator |
| 16:45.37 | *** join/#bzflag meeba (~lamer@c-75-71-180-64.hsd1.co.comcast.net) |
| 16:58.24 | *** join/#bzflag JeffM (~JeffM@69.36.85.131) |
| 16:58.24 | *** join/#bzflag JeffM (~JeffM@unaffiliated/jeffm2501) |
| 16:58.24 | *** mode/#bzflag [+v JeffM] by ChanServ |
| 17:03.39 | *** join/#bzflag allejo (~allejo@pool-108-0-61-94.lsanca.fios.verizon.net) |
| 17:32.02 | *** join/#bzflag alezakos (~kongr45gp@unaffiliated/alezakos) |
| 18:45.38 | *** join/#bzflag Pimpinella (~frank@gondolin.pimpi.org) |
| 20:18.59 | *** join/#bzflag TD-Linux (~thomas@2607:ea00:104:1000:2677:3ff:fe83:7814) |
| 20:18.59 | *** join/#bzflag TD-Linux (~thomas@about/essy/indecisive/TD-Linux) |
| 20:19.38 | *** join/#bzflag allejo (~allejo@pool-108-0-61-94.lsanca.fios.verizon.net) |
| 20:20.46 | *** join/#bzflag TD--Linux (~thomas@x-160-94-87-31.uofm-secure.wireless.umn.edu) |
| 20:33.46 | *** join/#bzflag rodgort` (~rodgort@li125-242.members.linode.com) |
| 20:41.59 | *** join/#bzflag sirquine` (~quine@c-76-120-71-113.hsd1.co.comcast.net) |
| 20:43.49 | *** join/#bzflag Scrumpy (~Scrumpy@smurfnet.xs4all.nl) |
| 20:44.12 | *** join/#bzflag Nidhoggr (cj@jormungandr.dragon.org) |
| 20:44.21 | *** join/#bzflag JeffM (~JeffM@76-218-80-21.lightspeed.irvnca.sbcglobal.net) |
| 20:44.21 | *** join/#bzflag JeffM (~JeffM@unaffiliated/jeffm2501) |
| 20:44.21 | *** mode/#bzflag [+v JeffM] by ChanServ |
| 20:45.22 | *** join/#bzflag sam__ (~sam@poulet.zoy.org) |
| 20:47.44 | *** join/#bzflag Admirarch (~Athelthra@mrush.mth.abdn.ac.uk) |
| 20:49.37 | *** join/#bzflag TD--Linux (~thomas@x-160-94-87-31.uofm-secure.wireless.umn.edu) |
| 20:55.06 | *** join/#bzflag McYukon (~McYukon@64.31.53.34) |
| 21:13.14 | *** join/#bzflag ThePurplePanzer (~bentz@c-67-186-178-98.hsd1.ct.comcast.net) |
| 21:16.04 | ThePurplePanzer | A quick question, I'm hoping someone knows the answer. When I run BZFS with -d (1 or more), I'll get warnings about problems in the world file at certain lines - but when I go to those line numbers, the text there is completely unrelated to the warning/error. Maybe the line numbers mentioned by BZFS don't count whitespace or something; is there any way to find out what textural line number |
| 21:16.05 | ThePurplePanzer | in the .bzw file is equivalent to a BZFS reported line? |
| 21:16.26 | blast007 | or the problem is higher up |
| 21:17.03 | ThePurplePanzer | that's a thought; |
| 21:17.39 | ThePurplePanzer | one problem was 'unknown object parameter "color", and the line number was in a list of vertices; I'll scan up (though color didn't occur in that object at all). |
| 21:17.44 | blast007 | like, for instance, if you miss an end somewhere, it might not get caught right where it should have been, but it would complain when a new object is added |
| 21:18.12 | JeffM | it would be the call to color that is above that line |
| 21:18.15 | ThePurplePanzer | Sure, that makes sense. |
| 21:18.20 | ThePurplePanzer | ok, thx |
| 21:18.29 | JeffM | it stored that you had a color then tried to add a vertex with the color atribute, and verts don't have color ;) |
| 21:18.42 | JeffM | the parser is a bit of a state machine |
| 21:19.44 | ThePurplePanzer | The first previous 'color' reference was a few objects back, in a material that had no texture; that may be the problem. |
| 21:20.02 | JeffM | probalby missing an end somewhere in there |
| 21:20.26 | JeffM | what generated the mesh? |
| 21:21.27 | ThePurplePanzer | An included file, I think for shrubbery. Origin I don't recall now, maybe from Louman |
| 21:22.40 | JeffM | some files have atributes that 2.4 dosn't support, like if they wer emade for 2.99 |
| 21:23.35 | ThePurplePanzer | This is pretty old I think. Not sure why there's a new error, likely some new material or something. If I have to I will test by eliminating things until the error goes away. |
| 21:24.16 | JeffM | 2.99 is pretty old ;) |
| 21:24.54 | *** join/#bzflag TD--Linux (~thomas@x-160-94-176-39.uofm-secure.wireless.umn.edu) |
| 21:26.41 | blast007 | things can get wonky if you have the wrong number of attributes for an option as well |
| 22:32.35 | *** join/#bzflag TD---Linux (~thomas@x-160-94-176-39.uofm-secure.wireless.umn.edu) |
| 22:54.04 | *** join/#bzflag Delusional (~delusiona@pool-108-17-117-49.pitbpa.fios.verizon.net) |
| 22:54.05 | *** join/#bzflag Delusional (~delusiona@unaffiliated/delusional) |
| 23:15.36 | *** join/#bzflag allejo (~allejo@pool-108-0-61-94.lsanca.fios.verizon.net) |
| 23:34.11 | *** join/#bzflag TD---Linux (~thomas@x-134-84-67-164.uofm-secure.wireless.umn.edu) |
| 23:49.32 | ThePurplePanzer | It turns out my color problem involved the use of a named color (e.g., " color blue") in a sphere. Not sure why this causes a problem, but it does. It was convenient to use names for random color selection; guess I'll have to use rgb values. |
| 23:57.18 | Delusional | i've been getting thr "floating point bug" where you cant drive across two equal-height boxes when I apply a material to one of them |
| 23:57.34 | JeffM | yeah that changes one to a mesh |
| 23:59.28 | Delusional | now i wish i could apply a material to a base |