=== sagaci__ is now known as sagaci [16:22] mhall119, quick question, in general, how much do you want to push to the views opposed to the models before it gets pushed into the database. Last night, I pushed in that quick change to deal with the line breaks within the doc string, but I did it before it was stored in the database. However, I wasn't sure how much you wanted to manipulate the content going into the db. [16:24] jvrbanac: in general, I'd like to disturb the data as little as possible between the GIR and the database [16:25] unless there's a good benefit to doing so [16:25] Got it. You want me to move that code into the view then? [16:26] what change are you making? [16:28] It was that linebreak clean up and replacement that I pushed up last night. I think it was merged into that pull that you merged into this master this morning. [16:29] oh, I didn't notice it, let me go back and look at it [16:30] jvrbanac: so I've been thinking about what to do with these docs [16:30] being in docbook is kind of a pain for embedding them within a page [16:30] also, if we're going to support Qt APIs and others, we can'd depend on them all being the same markup [16:31] I'm wondering if we should run an XML translation on the GIR docbook text, and convert it to something like Markdown [16:33] That would certainly make things easier on the rendering side. [16:34] I haven't found any simple python docbook library though, so we may have to work with the XML directly [16:35] ehh, it shouldn't be too hard... famous last words. [16:42] heh [16:48] mhall119, do you want me to put together a util to do that conversion or do you want to wait and mess with it later? [16:55] jvrbanac: if you can do that, it would certainly make everything else easier [16:58] mhall119, sure. I have written a few proprietary xml format readers for my day job over the past few years. Never in python, but it shouldn't be too much different. === davi_ is now known as davi [22:12] nope