00:00:40 it would be good to use sloccount. and something else than gnuplot, unless it can be made to show dates in human-readable format 00:01:24 yet another rewrite done :-) are there important parts missing? 00:01:39 sure! not done at all! :) 00:02:27 almost everything's commented out to make it compile... 00:03:45 everything under layout is to be rewritten? 00:04:00 y 00:04:23 and everything using it, updated 00:05:34 that's one third of libvob, 7500 physical SLOC 00:06:17 the re-implementation estimate being? 00:07:07 1.66 person-years, $224,452 00:07:20 right. so much for the basic COCOMO model 00:08:28 the new lob system only takes an estimated half person-year to implement 00:12:45 if we had versioned dependencies you would mark fenmm into requiring an older version of libvob 00:13:26 tuukkah: you mean instead of being forced to port it to the new version? :) 00:13:31 yes 00:14:08 perhaps you'd need to move it into another subproject as well 00:14:11 sounds like a misfeature :) 00:15:33 well, now I've moved them to basalt/ 00:15:44 s/them/it/ 00:16:13 the problem with package-level dependencies is that darcs doesn't operate on parts of a repo 00:16:23 mhm 00:18:53 or could it work so that when fenmm is compiled the classpath is set to another copy of libvob that has a good version from the repo 00:20:49 at the moment, you could branch libvob into libvob2, implement the new system there and port fenfire to use that 00:21:20 tuukkah: what's wrong with the way I'm doing it now? 00:21:45 I don't like it that you have to port fenmm 00:21:56 I don't, I punt by moving it to basalt/ 00:22:19 I don't like that you have to move it there either 00:22:36 seems easier than the alternatives you're pondering :) 00:23:38 hmm. what would be a good name for a class with lobsystem-related static methods dealing with rdf? 00:24:03 ah, FenLobs 00:46:57 pushing now 00:47:13 port isn't complete, but enough is ported that I feel it makes sense 00:48:27 ok 00:52:53 I really should try to sleep. cu 00:53:32 [feel free to port more while I sleep. heh heh ;-)] 00:55:30 rubberpaw has quit 00:58:19 I should sleep as well 02:24:07 rubberpaw has joined #fenfire 08:30:30 by the way, at the moment http://planet.debian.org/rss10.xml is valid enough for fenfeed 08:32:13 oh no 08:33:05 hmm 09:24:23 you say above that libvob has taught you to keep generated files in version control 09:24:27 why is that? 09:27:31 even to compile some of the java files, you need some parts of c++ build environment. and we're not interested in that, so we keep these generated files in the repo 09:32:47 rubberpaw has quit 09:33:03 * ibid declines to comment 09:33:04 :) 10:32:17 rubberpaw has joined #fenfire 11:58:07 http://liw.iki.fi/liw/texts/software-webpage.html :) 12:06:39 rubberpaw has quit 12:13:00 huomenta 12:32:27 rubberpaw has joined #fenfire 13:10:19 menta 13:18:51 rubberpaw has quit 14:07:31 I suppose we're doing ok on the checklist excluding that we don't have releases 14:11:27 benja_, do you know of other software than Fenfire that can find and read our DOAP? 14:25:44 tuukkah: no 14:26:23 to make it findable, we need to include a meta tag in index.html 14:26:43 not sure how to best do that, postprocessing like with navbars and textures I guess 14:27:11 to make it readable, need to offer an rdf/xml version for many tools out there 14:30:05 it's nice that the loggerbot actually works :-) 14:32:34 rubberpaw has joined #fenfire 16:11:40 benja_, the indexes aren't browsable in fenfire, because they talk about a blank node (AFAICT) 16:15:05 should the blank node be smushed with the http uri or something? 16:28:57 rubberpaw has quit 16:43:58 rubberpaw has joined #fenfire 17:40:58 b 17:41:05 hi 17:41:17 how was Easter? :-) 17:43:27 hi majukati 17:44:47 tuukkah: I don't understand, I can browse them 17:44:56 (after fixing some new-lob-system bugs :)) 17:51:43 so you can get http://fenfire.org/irc/fenfire/index.rdf with ctrl-g and see the entries? where? 17:52:13 tuukkah: I downloaded the .rdf for a particular day and loaded it from the command line 17:53:22 how's that "browsing the indexes"? 17:53:58 benja_: it was fine. no internet in 3 days 17:54:17 I thought you meant the logs 17:54:50 my point is I can get index.rdf but now I'd like to get to the entries by moving in the structure 17:56:05 we can look into it sometime 17:56:25 yes :-) 17:57:24 benja_: i see no commits in project repo, when are you going to start traveling? 17:57:34 tomorrow 17:57:55 what do you want in project repo? me translating your finnish texts?!? 17:58:10 rubberpaw has quit 18:01:20 benja_, perhaps you writing new texts for next time ?-) 18:01:30 benja_: some text for the lecture. 18:01:56 benja_: and i did translate the text.. 18:04:39 the code is still not ready, it doesn't make sense to write text when the code isn't there 18:06:12 you can still write the introduction. which the course is =) 18:06:19 ? 18:06:56 benja_: ok, how much do you think you take time with that and what else should be in the same lecture? 18:07:03 can't you give an introduction even before the code is ready? 18:09:26 benja_: for every 15-25 minutes we shall put Tux to go from one to another and ask questions or let participants make questions 18:10:43 tuukkah: perhaps i could have done that 18:11:10 majukati: what can you do tommorow & wednesday? 18:11:47 benja_, I didn't mean you should, just that you could 18:12:52 benja_: anything? 18:13:22 I think it would be best if you would work on porting the existing stuff 18:13:34 i.e. make work what I broke... :-] 18:14:00 I'll write lecture notes on wednesday 18:14:54 what have you broken?-) 18:15:16 majukati: I've changed ff to use the new lob system 18:15:52 I haven't worked on canvas & calendar views at all yet 18:16:09 also unique colors for properties aren't there 18:16:36 there's also a lot of speed fixing to be done, but it's probably better if I do that / we do it together when I'm in jkl 18:17:07 look at the stuff in libvob for "good" code, the stuff in fenfire is hacky 18:17:16 (i'm worried about the lecture material and the lecture not the code..) 18:17:58 majukati: imho if there's no lecture material that's a minor problem, if the code is broken the lecture is pointless 18:18:18 (i.e., we need to substitute another one or I don't know) 18:20:59 and using the old, working code makes it equally pointless if we then replace that code the next week 18:36:12 ok, here's another option. instead of a hands-on session, we make it about rdf, lobs, and the fenfire vision 18:36:20 it = the lecture 18:36:34 instead of coding, I make writing lecture notes the priority for the trip 18:36:39 sounds good 18:36:56 we bump the hands-on session for a week and have more time to get it ready 18:37:09 in this lecture, we show ff with the old lob system 18:37:17 majukati: would you prefer that? 18:42:42 definitely 18:44:14 i mean we can show something like two scenes and how to make animation between them 18:46:36 ok ... then I have to worry less, too :) 18:46:50 jvk has the third lecture 18:47:13 so we have even more time for this 18:47:20 mhm... 18:47:51 I'll be in Germany on 5.5 btw, but I think I told you already 18:48:20 yes. there is final session after that 18:48:23 perhaps some people weren't convinced after the first lecture that identity technologies and fenfire would be more than buzzwords. discussing our use of rdf (in contrast to semantic web, or xml, or ...) and vobs could benefit a lot 18:48:59 majukati: I'll be back for the final session 18:49:13 tuukkah: ok 18:50:10 tuukkah: they do not change their attitude even if we say something if we do not publish something real ;) 18:50:16 but if we had fenhaystack ready and had a programming session imho that would have benefited even more :) 18:51:13 ibid wrote a long one.. 18:51:38 benja_, perhaps 18:52:23 but it's probably best to do it like this given the situation now 18:54:11 majukati, you can ask him to sum up saying that long emails are not read ;-) 18:55:21 rubberpaw has joined #fenfire 18:55:30 benja_, of course you can promise that for the following week and perhaps even show some view changing as an introduction 19:00:55 benja_: hmm, could you write an email to me and summ up (with french lines) the lecture subjec(s) now? 19:01:39 could jvk lecture a week later or is the time fixed? 19:02:33 majukati: I can do that during the trip, yes 19:02:45 not today, I need to sleep 19:02:58 my train leaves at 10am 19:03:15 benja_: please do it now. i'm still out 19:13:03 tuukkah: i don't like if we keep changing the lecture times and subjects all the time :) 19:13:49 majukati, why not? if you don't give a hands-on session this week, wouldn't it be natural to move each lecture one week later? 19:14:30 tuukkah: how many has already marked jvk's lecture to their calendar? 19:15:12 why would they have? have you given us a definite schedule? 19:15:44 http://himalia.it.jyu.fi/darcs/project/teaching/TIE363/www/ 19:16:02 majukati: is it a bad thing?:) 19:16:28 majukati, doesn't sound very definite :-) lots of "..." 19:16:33 ibid: a long one, not really :) 19:17:04 tuukkah: yeah yeah.. i should add "pidättää oikeudet tehdä muutoksia..." 19:23:16 majukati: I don't know how to say this in a good way, sorry, but I need to say something, so. ok, I'll stay sometime longer. but please don't do this too often (telling me 'please work more' when I tell you I can't). 19:23:33 yes, I know, I haven't had ready today what I should have had ready 19:24:57 but you've been busy coding the new system to the point where majukati can continue 19:25:01 but you know, I've worked really hard. I did what I could. and when I say, here's the point where I can't do more, I don't want to be told, do it anyway. I'm ok with being asked "could you perhaps," but not with "please do." 19:25:04 (sorry, you asked me to have the lecture with you and you are leaving tomorrow - and i nee time to process things) 19:26:39 majukati: yes, I understand, and I'll do it, I just want to tell you that I don't want to be *told* to do it, and that this is upsetting me 19:28:16 I want to have the option to say no without saying "fuck you" 19:28:36 as I said, I don't know a good way of saying this 19:29:23 benja_: i want to do my best for my part for the lecture - currently i feel unsure 19:31:01 benja_: you have wrote a lot of code for the lecture. i do admire that! 19:31:52 but, if we had a funding proposal due the next day and I didn't know if I could do it alone or something like that, and you told me you need to be with aapo and heidi or something, I hope I wouldn't tell you "please don't" -- although I might say, here's the problem, it's a real problem, you decide whether you can work on the proposal today 19:31:57 okay, anyway 19:32:29 I had to say that because I felt really upset. sorry, I know you didn't mean it in a bad way or anything 19:32:46 *takes a deep breath* 19:34:00 majukati: is it ok if I say points here instead of writing e-mail, and you reply if you don't understand something? 19:34:09 (can collect in e-mail later if needed) 19:34:29 benja_: 5 lines is enough for french lines but just something 19:34:44 rdf is easiest, I suppose 19:34:50 so let's start with that :-) 19:35:24 - introduction: URIs, triples, literals (have you done this in the last lecture?) 19:35:46 can we start with this ultimate "ok, we need to teach you something about ideas.." "we got an idea for this lecture but it needed some work which we didn't get enough time.. " =)) 19:35:58 - example: foaf, e-mail, blogs (these are just ideas) 19:36:17 majukati: sure :-) 19:36:36 majukati: (note: I don't necessarily want to start with RDF, just starting the french-line-producing with it :)) 19:36:46 yes 19:37:07 re the fenfire vision, there's http://fenfire.org/manuscripts/2004/hyperstructure/ 19:37:48 hm, should give a demo first 19:37:49 fenfire vision -> fenfire browsing 19:38:03 or while browsing perhaps 19:38:31 we can start demo with demo.turtle, bring in danny's foaf, then his blog 19:38:47 and show the calendar 19:39:07 probably should start with that, then explain RDF with the examples seen there 19:39:50 i tried to explain rdf with triples of subject predicate and object but please do it again 19:40:07 yeah 19:40:29 it's probably easier with real examples 19:40:33 ah 19:40:50 when explaining, also need to explain the theoretical concept of resources 19:41:02 and that there's a one-to-many relationship between resources and URIs 19:41:44 what you mean with that? 19:42:34 then, I think for "fenfire vision" we could follow the scenario, two people communicate by blog and mail, decide to start some project together, set up milestones, track ideas and their relationships to milestones and deliverables 19:43:24 majukati: the rdf thing -- a 'resource' is some real-world thing, and there is a 1:n relationship between resources and RDF nodes -- one node represents one thing, one thing is represented by zero to arbitrarily many nodes 19:43:36 in Fenfire, we merge two nodes when we know they represent the same thing 19:44:11 the 'many nodes represent the same thing' is necessary because real-world things cannot normally be given a unique URI (there's no authority for that) 19:44:49 'one node represents only a single thing' keeps things sane :-) 19:45:12 ok 19:45:30 even if they aren't bnodes? 19:45:32 well, mainly, it means that you can do logical inferences to convert between two vocabularies representing similar concepts 19:45:36 majukati: yes 19:46:40 re fenfire vision, the scenario: 19:47:14 step 1: two people talk on their blogs; through RDF links, you can browse their 'dialog' as structure (this post replies to that post, etc.) 19:47:58 step 2: they decide to do a project together. they start discussing goals and make rdf nodes for them (which the blog posts discussing the goals refer to) 19:48:30 step 3: they start planning milestones and connecting them to the goals 19:48:44 oh well, it's kinda boring 19:49:22 :) 19:49:41 ok, demo, vision, rdf - something else? 19:49:46 (step 4: when they blog or send e-mails with versions of the deliverables, they connect them to the goals; when they discover issues, they create nodes for them and connect blog posts and stuff to it) 19:49:52 majukati: yes, lobs 19:50:29 ok, - need: UI components for Fenfire 19:50:53 - (need for flexibility, because we want to try out different things) 19:50:59 (or easier ui components) 19:51:04 majukati: true 19:51:30 - the basic ideas in Fresco: basic lobs do only one thing 19:51:56 you compose basic lobs to get components 19:52:15 - the basic lobs 19:52:49 is there anything for me?-) i mean this all sounds very much like your special area :) 19:52:52 - making components from basic lobs: example 19:53:22 majukati: let me finish the french lines first, just a moment :) 19:54:38 - the idea of key lobs -> we give parts of the screen a 'key' and use that for interpolation and decoration and state management and other things 19:54:50 do you know the game of 3x3 table and there is one black hole. would it suffice to create that with vobs and lobs? 19:54:55 (reference to libvob lecture coming later) 19:55:30 majukati: no, I don't know the game or don't recognize it 19:55:35 there are other rectangles like a,b,c; d,e,f; g and h. 19:55:37 majukati, and the animation would come for free! 19:55:45 oh, the boss puzzle 19:55:46 ok 19:55:55 4x4? 19:55:56 it's usually 4x4 though :-) 19:56:07 hm, sounds like a good thing to include 19:56:33 well isn't that just NxN :) 19:57:17 - the 'recursive hierarchies' idea. argh, I don't even have a reasonable french line for that 19:57:19 would you have a grid or table lob for 4x4 and move the pieces from cell to another? 19:57:38 tuukkah: yeah 19:58:13 that could be done without rdf or such 19:58:18 oh, and need to introduce javolution also 19:58:24 tuukkah: yup, could 19:58:39 (the above sounds like a full program :-)) 19:58:52 javolution introduction maybe only brief 19:59:01 but the important thing in libvob animation is animation between views? 19:59:05 [depending on time, probably there isn't enough] 19:59:17 tuukkah: well, it's not a libvob lecture 19:59:35 but yeah, we can have animation between views 20:00:06 the other view can be a two-column table, first column: puzzle piece, second column: position 20:00:16 can also include third column: times you have moved it 20:00:20 or why else do you do lobs in libvob instead of using awt 20:00:47 tuukkah: well, since it's not a lecture about libvob, that isn't so much the point 20:01:21 but, need to stress the role that identities play in the lob system 20:02:06 demo, vision, rdf, lobs(why?, what are those?, javolution) 20:02:24 majukati: rdf before vision 20:02:40 because it's connected to demo 20:02:53 but, yes 20:02:56 demo, rdf, vision, lobs(why?, what are those?, javolution) 20:03:00 y 20:03:12 I think I need to give the last part of the lobs part 20:04:26 do you want to talk in the demo part and I'm at the keyboard? 20:05:10 not really :/ 20:05:17 hum 20:05:32 ok, other way around then 20:05:46 but please don't stay silent then :) 20:06:15 vision: we need to work out a good scenario 20:06:26 something fun :-) 20:06:37 benja_: i think it's not clear if there are two lecturers at the same time speaking or doing something 20:07:23 majukati: if it's two people who present one thing together, I believe it's usually good 20:07:35 if it's two people talking about different things, not, of course :) 20:08:50 for a vision - two is ok but we need to be sharp ;) 20:09:01 good :) 20:10:11 my headache is getting worse, what do we still need to do today? 20:10:42 b=benja, mudyc; b:demo, b:rdf, b&m:vision, m&b:lobs(why?, what are those?, javolution) 20:11:04 benja_: go to sleep and have a nice trip tomorrow 20:11:12 travel day one... 20:11:15 thanks 20:11:38 and thanks for saying fuck you aloud i really needed that ;) 20:12:18 I'll have time online in Stockholm perhaps and definitely on the ship, both on Wednesday, tomorrow probably not :-( 20:12:24 majukati: :)