| 01:07.06 | Notify | 03BRL-CAD:starseeker * 63565 brlcad/branches/qtged/src/qbrlcad/QAccordianWidget.cxx: Improve accordian open/close behavior. |
| 01:08.48 | *** join/#brlcad FreezingCold (~FreezingC@135.0.41.14) | |
| 01:10.24 | Notify | 03BRL-CAD:starseeker * 63566 brlcad/branches/qtged/src/qbrlcad/cadaccordian.cxx: Call it an 'object' rather than a 'primitive' |
| 01:29.06 | Notify | 03BRL-CAD:starseeker * 63567 (brlcad/branches/qtged/src/qbrlcad/QToolPalette.cxx brlcad/branches/qtged/src/qbrlcad/QToolPalette.h): Rework the QToolPalette slightly with an eye towards allowing a shared control panel between multiple tool palettes. |
| 01:49.19 | *** join/#brlcad gurwinder (3b5b7116@gateway/web/freenode/ip.59.91.113.22) | |
| 02:23.51 | *** join/#brlcad hdo (3b5b7116@gateway/web/freenode/ip.59.91.113.22) | |
| 02:24.00 | *** part/#brlcad hdo (3b5b7116@gateway/web/freenode/ip.59.91.113.22) | |
| 02:29.32 | Notify | 03BRL-CAD Wiki:MollyKauffmann * 0 /wiki/User:MollyKauffmann: |
| 02:33.50 | starseeker | grr - shared control panel space for multiple palettes will take a little more work than I thought |
| 02:36.45 | starseeker | probably warrants a slightly different version of the widget supporting 'groups' of buttons as part of a single palette |
| 02:38.45 | Notify | 03BRL-CAD:starseeker * 63568 (brlcad/branches/qtged/src/qbrlcad/QToolPalette.cxx brlcad/branches/qtged/src/qbrlcad/QToolPalette.h): Back out QToolPalette changes - need a different direction for what we've been considering, so there's little justification for the extra complexity here. |
| 04:24.14 | *** join/#brlcad kintel (~kintel@unaffiliated/kintel) | |
| 04:25.00 | *** join/#brlcad gurwinder (3b5b7116@gateway/web/freenode/ip.59.91.113.22) | |
| 04:36.39 | Notify | 03BRL-CAD Wiki:DarioTRDrxa * 0 /wiki/User:DarioTRDrxa: |
| 05:17.36 | Notify | 03BRL-CAD:brlcad * 63569 brlcad/trunk/NEWS: carl make pix-bw work like pix-png, writing to both a specified file and redirected output |
| 05:20.36 | Notify | 03BRL-CAD:brlcad * 63570 brlcad/trunk/src/util/pix-bw.c: comment formatting |
| 05:56.40 | *** join/#brlcad kintel (~kintel@unaffiliated/kintel) | |
| 06:32.04 | *** join/#brlcad kintel (~kintel@unaffiliated/kintel) | |
| 06:38.33 | brlcad | starseeker: could just disassociate the buttons from the palette -- just have the tools unhide/hide their palette so only one is visible at a time |
| 06:40.07 | brlcad | http://www.cise.ufl.edu/research/sparse/matrices/ |
| 08:37.39 | *** join/#brlcad teepee (~teepee@gateway/tor-sasl/teepee) | |
| 09:15.16 | *** join/#brlcad d_rossberg (~rossberg@66-118-151-70.static.sagonet.net) | |
| 11:35.02 | *** join/#brlcad teepee- (bc5c2133@gateway/web/freenode/ip.188.92.33.51) | |
| 12:33.15 | *** join/#brlcad ries (~ries@D979C47E.cm-3-2d.dynamic.ziggo.nl) | |
| 13:21.44 | *** join/#brlcad sofat (~sofat@202.164.45.208) | |
| 13:26.31 | *** join/#brlcad kanzure_ (~kanzure@131.252.130.248) | |
| 13:29.04 | *** join/#brlcad sofat (~sofat@202.164.45.208) | |
| 13:31.28 | *** join/#brlcad kanzure (~kanzure@131.252.130.248) | |
| 13:42.58 | *** join/#brlcad kanzure (~kanzure@131.252.130.248) | |
| 13:56.16 | *** join/#brlcad sofat (~sofat@202.164.45.204) | |
| 13:56.20 | *** join/#brlcad teepee- (bc5c2133@gateway/web/freenode/ip.188.92.33.51) | |
| 13:58.27 | *** join/#brlcad kanzure_ (~kanzure@131.252.130.248) | |
| 14:16.31 | *** join/#brlcad ankesh11 (uid8015@gateway/web/irccloud.com/x-qlpakwfvsdrrszqm) | |
| 14:20.43 | *** join/#brlcad sofat (~sofat@202.164.45.208) | |
| 14:55.09 | *** join/#brlcad sofat (~sofat@202.164.45.204) | |
| 15:17.47 | *** join/#brlcad albertcoder (~albertcod@202.164.45.204) | |
| 15:23.02 | albertcoder | Hi brlcad , had a great time at Reunion. :D |
| 15:23.11 | albertcoder | Have you had a look of materials database? |
| 15:23.25 | albertcoder | I have installed it on brlcad server here |
| 15:23.36 | albertcoder | http://brlcad.org/~albertcoder/mediawiki-1.22.7/index.php/Special:Materials_database |
| 15:23.57 | albertcoder | Just wanted some directions to improve my work further. |
| 15:29.13 | *** join/#brlcad kintel (~kintel@unaffiliated/kintel) | |
| 16:06.02 | sofat | maths22, hello |
| 16:06.11 | sofat | i want to ask one question |
| 16:07.33 | *** join/#brlcad teepee- (bc5c2133@gateway/web/freenode/ip.188.92.33.51) | |
| 16:08.04 | brlcad | wonders if the question will ever arrive |
| 16:08.16 | sofat | which theme you are working |
| 16:08.24 | sofat | in repo there are two themes |
| 16:09.41 | albertcoder | brlcad, ping |
| 16:09.49 | albertcoder | Just wanted to carry my work ahead |
| 16:10.00 | brlcad | albertcoder: yes, I know response in just a sec :) |
| 16:10.18 | albertcoder | yeah thanks :D |
| 16:10.35 | brlcad | sofat: since it may take minutes or hours to get a reply (should stay on IRC), I suggest working a separate bit ... I don't think his mailing list message indicated which was closest but the intent was to merge iirc |
| 16:10.52 | brlcad | albertcoder: so you tell me how this can be improved? |
| 16:11.22 | albertcoder | hmm there are quite some improvements in my mind |
| 16:11.52 | albertcoder | like adding the feature to add material types, trait types, and so on. |
| 16:12.15 | albertcoder | at present these things are kind of static |
| 16:12.27 | brlcad | static is actually probably good for a first cut |
| 16:12.35 | brlcad | so people will understand the scope |
| 16:12.43 | albertcoder | yeah thats fine |
| 16:12.44 | brlcad | and not try to extend with arbitrary metadata |
| 16:13.08 | brlcad | question is whether those five are a sufficient point is one question |
| 16:13.21 | brlcad | I worded that terribly :) |
| 16:13.41 | brlcad | meant that it's a good question whether those five traits are sufficient starting points |
| 16:13.54 | brlcad | or whether there are some other common fields (which I think there are |
| 16:14.16 | brlcad | did you ever get a copy of a material xls data sheet? |
| 16:14.25 | albertcoder | nopes |
| 16:14.26 | brlcad | it was a spreadsheet |
| 16:14.36 | brlcad | hm, don't know if I have a copy of that any where |
| 16:14.40 | brlcad | goes looking |
| 16:18.38 | sofat | brlcad, i want to ask one question regarding Benchmark performance database |
| 16:19.58 | sofat | i see there can be many improvements |
| 16:21.15 | sofat | now i just need to know infrastructure website if it is mediawiki then i have already mediawiki extension and if wordpress then i will make plugin for it |
| 16:25.18 | albertcoder | thinks brlcad go went gone ;-) |
| 16:27.49 | albertcoder | So far the ultimate goal of materials database extension is concerned I think we need to make it interact with brlcad software. |
| 16:29.27 | albertcoder | May be some tinkering with the brlcad source may be required to make the extension talk to the software. |
| 16:30.58 | Notify | 03BRL-CAD:starseeker * 63571 (brlcad/trunk/src/libbrep/CMakeLists.txt brlcad/trunk/src/librt/CMakeLists.txt): Set up some test code to see what the openNURBS shape identification routines can tell us. |
| 16:40.28 | brlcad | sofat: good question -- I don't see the benchmark being a solid fit with mw for some reason, maybe not even a solid fit with wordpress |
| 16:40.30 | brlcad | current is neither, right? |
| 16:41.17 | sofat | is confused |
| 16:42.00 | brlcad | feels like it's prime for being a cake or node or cappucino or similar framework |
| 16:42.17 | brlcad | sofat: don't be confused, I could be confused |
| 16:42.33 | brlcad | there are certainly merits with working with mw and/or wp |
| 16:42.50 | brlcad | wouldn't be opposed to either and leverage existing infrastructure is definitely a GOOD THING |
| 16:43.30 | Notify | 03BRL-CAD:carlmoore * 63572 brlcad/trunk/doc/docbook/system/man1/en/pix2asc.xml: touch up, as usual, of pix2asc man page |
| 16:43.37 | brlcad | I'm talking where are we waiting to go LONG long term and what will suite that application platform (the benchmark site is an application platform) the most |
| 16:43.55 | brlcad | what is the current implementation based on? I don't recall |
| 16:44.39 | brlcad | albertcoder: so I'm remembering a key feature needed for materials db |
| 16:44.41 | sofat | it is python |
| 16:45.14 | brlcad | albertcoder: support for composite material types, which implies changes on even those five values you already have |
| 16:45.24 | brlcad | sofat: pure python, no frameworks? |
| 16:45.44 | sofat | yes django framework |
| 16:45.57 | albertcoder | brlcad, do you mean materials composed of one or more materials? |
| 16:46.10 | brlcad | albertcoder: with composites, everything is a range ... min/max and default (which is basically the number you have now) |
| 16:46.26 | brlcad | so there's a minimum density, a maximum, and a default |
| 16:46.30 | brlcad | and min/max are optional |
| 16:46.38 | brlcad | unlike the default, which is required |
| 16:47.43 | albertcoder | sorry couldn't be so clear, an example can help me :) |
| 16:48.50 | albertcoder | I am not sure if a specific material can have min and max density at the same time |
| 16:49.00 | albertcoder | or I could not get you. |
| 16:49.34 | sofat | and i have made this in php for mediawiki extension |
| 16:50.24 | brlcad | other common fields (also with min/max/default fields) some you have, some you don't yet: name, alternate name(s), density, hardness, yield strength, ultimate strength, shear strength, youngs modulus, bulk modulus, and notes (free-form text) |
| 16:50.24 | sofat | because your current website running on mediawiki so did this |
| 16:51.19 | brlcad | albertcoder: a "pure" material like copper has a given density, but a copper alloy is going to have a range of density (probably a normal distribution) |
| 16:51.51 | brlcad | sofat: so we have a python framework based on django and now a mediawiki extension, yes? |
| 16:52.33 | sofat | yes ankesh made this in django and i made this in mediawiki |
| 16:53.25 | albertcoder | okay brlcad then the min and max densities point to the densities of alloys of copper right? |
| 16:56.28 | albertcoder | and we have to have the range shown once we see the details of copper. Do we? |
| 16:57.05 | albertcoder | And I will try adding the above traits you mentioned as soon as possible. |
| 17:10.53 | *** join/#brlcad sofat (~sofat@202.164.45.204) | |
| 17:17.19 | *** join/#brlcad albertcoder (~albertcod@202.164.45.204) | |
| 17:25.28 | brlcad | sofat: okay! sorry on the delay, had a convo going |
| 17:25.45 | brlcad | sofat: so how does your work now on mw compare with the django work? |
| 17:25.59 | brlcad | oof |
| 17:26.31 | brlcad | albertcoder: density, hardness, yield strength, ultimate strength, shear strength, youngs modulus, bulk modulus |
| 17:26.53 | brlcad | they should all have optional min/max ranges and a default value |
| 17:27.44 | brlcad | ugh |
| 17:29.01 | teepee | can see a pattern there ;) |
| 17:31.47 | *** join/#brlcad merzo (~merzo@user-94-45-58-138-1.skif.com.ua) | |
| 17:33.16 | brlcad | teepee: heh, yeah |
| 17:39.08 | *** join/#brlcad sofat (~sofat@202.164.45.204) | |
| 17:42.40 | brlcad | sofat: did you see my reply? |
| 17:55.35 | sofat | no |
| 17:55.41 | sofat | where is ? |
| 17:55.59 | *** join/#brlcad albertcoder (~albertcod@202.164.45.204) | |
| 18:07.38 | brlcad | sofat: how does your work now on mw compare with the django work? |
| 18:07.47 | brlcad | url/screenshots of both? |
| 18:08.19 | brlcad | we can and should certainly try to consolidate the efforts as two is inefficient (certainly don't want to waste your time!) |
| 18:09.04 | sofat | i can provide screen shots now and i put my project online tomorrow |
| 18:09.18 | sofat | wait i send you screen shots |
| 18:13.30 | brlcad | sofat: I can tell you that my immediate concern is that the site ankesh made LOOKS really nice, the polished design and appearance of the graphics is appealing |
| 18:13.44 | brlcad | that affects usability and is central to the benchmark database site |
| 18:14.06 | brlcad | that's why I suggested benchmark is a bit different than the rest in terms of needing to integrate with the rest of our infrastructure |
| 18:15.02 | brlcad | the project there is more independent and it's more important that it look nice and be downright TRIVIAL to navigate |
| 18:15.28 | brlcad | i.e. interface and usability are more important than features (the central feature is a simple performance number) |
| 18:20.29 | sofat | i sent you mail in this mail store the screen shots of my work please check |
| 18:25.30 | *** join/#brlcad albertcoder (~albertcod@202.164.45.204) | |
| 19:02.32 | brlcad | sofat: so you're going to make this very difficult I see :) |
| 19:02.42 | brlcad | the screenshots look a lot better than last time I saw them |
| 19:03.43 | sofat | :) |
| 19:03.54 | brlcad | sofat: basically, I'd like you and ankesh11 to sort it out ... |
| 19:04.10 | brlcad | if only one of you is active, that one would get to decide how to proceed |
| 19:04.22 | brlcad | my requirement will be on the usability and appearance |
| 19:04.51 | brlcad | ankesh11's interface style (the colors) still looks better, but that probably wouldn't be hard to adapt |
| 19:04.57 | brlcad | to yours |
| 19:05.10 | brlcad | so please discuss and let me know if there's a consensus |
| 19:05.32 | brlcad | if there's not a consensus on how to proceed, I can intervene or give further guidance |
| 19:05.33 | sofat | alright thanks |
| 19:06.14 | sofat | i will discuses with him |
| 19:06.23 | brlcad | basically, whomever is the most active will be the project lead for this |
| 19:07.03 | brlcad | I can say that I think the MW menu is completely distracting on this interface, so that would need to be hidden if it stays on MW |
| 19:07.13 | brlcad | the user shouldn't know or care what the underlying platform is |
| 19:07.25 | brlcad | it should just be a clean simple interfae that matches our style guide |
| 19:08.56 | sofat | ok i will change the menu style |
| 19:10.10 | brlcad | for style guide, see: http://www.google-melange.com/gci/task/view/google/gci2013/5844328496758784 <-- it's incomplete but a really decent start |
| 19:10.19 | brlcad | and see beta.brlcad.org |
| 19:10.46 | brlcad | rather beta.brlcad.org/wp/ |
| 19:10.59 | brlcad | waves |
| 19:11.59 | ``Erik | preparing the thunderdome just in case? ;) |
| 19:40.54 | ankesh11 | sofat: Hi, great that you are working on the Benchmark project too. |
| 19:41.22 | ankesh11 | Oh, he went offline! |
| 19:53.03 | *** join/#brlcad albertcoder (~albertcod@202.164.45.204) | |
| 20:11.32 | *** join/#brlcad kanzure (~kanzure@131.252.130.248) | |
| 20:17.14 | *** join/#brlcad YatharthROCK (~YatharthR@unaffiliated/yatharthrock) | |
| 20:25.02 | *** join/#brlcad LordOfBikes (~armin@dslb-088-065-178-252.088.065.pools.vodafone-ip.de) | |
| 21:42.16 | *** join/#brlcad merzo (~merzo@239-50-132-95.pool.ukrtel.net) | |
| 22:14.21 | starseeker | ``Erik: did you happen to come across this paper back when you were working on the mesh boolean problem? http://arxiv.org/pdf/1308.4434 |
| 22:14.34 | starseeker | was curious if you had an opinion about it |
| 22:30.34 | ``Erik | I believe so, um, "it's good stuff"... it was one in the chain that descended from the old siggraph paper that our nmg stuff was based off of |
| 22:31.10 | ``Erik | except it's on the path that went for simplification to improve robustness and performance, where nmg went towards complicating it for, uh, some ... reasons... I guess? O.o :D |
| 22:44.31 | ``Erik | wait, no, I couldn't have seen that one, but it sure does look familiar |
| 22:48.53 | ``Erik | meh, formulaic style, very similar images, :) no, I don't think I saw that one, it was after I was doing that stuff, I think I was shifted over to libwa by the time that came out. I'm guessing one of those referenced papers looks similar and is what I was thinking? *shrug* |
| 22:49.46 | ``Erik | well beyond gci work, but maybe a minimal impl that just splits out obj could be on the wishlist for next years gsoc |
| 22:55.36 | *** join/#brlcad merzo (~merzo@239-50-132-95.pool.ukrtel.net) | |