Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Kyle P. Johnson
    @kylepjohnson
    I am eagerly awaiting v1!
    About the CODEX -- looks awesome. You guys out there should present for us! I can share my a recent slidedeck and/or teleconference in. Luke, we could do 50/50, half on core, half UI
    Luke Hollis
    @lukehollis
    okay, most recent updates from this last dev cycle out at http://api.cltk.org
    new routes include single pages like http://api.cltk.org/about (not much there yet)
    As well as routes for book-chapter-section (http://api.cltk.org/works/histories/1) and book-line (http://api.cltk.org/works/aeneid/1)
    The definitions panel has a little example data in it
    working on getting the demo data in the commentary/translation modal currently
    Kyle P. Johnson
    @kylepjohnson
    Spectacular. Is the API design working OK for you? Eg, the chunk1=4&chunk2=22 ?
    Luke Hollis
    @lukehollis
    Still on the backlog... :/ but I was hoping to have that together during this last sprint. I think it looks good though! As soon as more of the big pieces are together I want to work on getting the manifest of authors from the api and implementing the text api. I think we're almost there.
    Kyle P. Johnson
    @kylepjohnson
    Remember our POstgres conversation a while back? Just saw this and it looks terrific. https://github.com/begriffs/postgrest
    Seems a lot of people vouch for it. It's thought through the JSON-SQL stuff for us, while apparently abstracting away the hard parts. Who knows, maybe too good to be true, but worth consideration once we are ready
    Luke Hollis
    @lukehollis
    This looks really good!
    I've never worked with haskell before--but it seems like this is exactly the sort of thing we'd need to build
    Kyle P. Johnson
    @kylepjohnson
    Me neither. I hope this involves little to no knowledge of Haskell! I think my API could just take to the postgres API. That way, we can keep the URL logic you're building off
    Luke Hollis
    @lukehollis
    oh sure, that sounds great
    Kyle P. Johnson
    @kylepjohnson
    Hi everybody! I have added a few more texts to the API, or rather to the json dir of the latin_text_perseus repo.
    Kyle P. Johnson
    @kylepjohnson
    Actually, GW wasn't totally parsed. I'll add that to the list
    Luke Hollis
    @lukehollis
    looks great!
    I'll try to get ovid next
    Luke Hollis
    @lukehollis
    after these articles about how meteor is switching its preference from blaze or angular to meteor (https://www.discovermeteor.com/blog/the-state-of-meteor-part-2-what-happens-next/ https://www.discovermeteor.com/blog/the-state-of-meteor-part-3-aftermath/), I've been trying to move the frontend materials to react.
    though i don't want to follow blindly after whatever is the next new thing, I think that this represents a larger shift in the js community and it'll be easier to find other good react devs to contribute in the future than folks familiar / happy with angular 1 or blaze
    Luke Hollis
    @lukehollis
    Otherwise, I thought that this was a really interesting article about reading on the web from the shop that worked on the Atlantic: https://medium.com/truth-labs/re-thinking-reading-on-the-web-158e789eddd7#.j0fr3anhk
    Luke Hollis
    @lukehollis
    One other challenge thinking about the data model that I haven't thought of before: is there any way that we can store line/paragraph numbers that are strings?
    e.g. Iliad 1.85b
    this is what i'm considering with the comments in the commentary:
    text_n : {
              from : {
                   i : 85,
                   s : "85b"
              },
              to : {
                   i : null, 
                   s : null
              }
            },
    or somesuch?
    (ran into this problem on a different project recently)
    Luke Hollis
    @lukehollis
    structure.gif
    kk got some basic structure ideas on the page
    this is definitions, commentary, and translations
    entities might be some sort of highlighting?
    likewise for user notes and annotation
    unsure about the best method for related passages--@pickering-paul has been working on some ideas there
    Luke Hollis
    @lukehollis
    Hrmm... It looks like redux (https://github.com/reactjs/redux) would be useful for managing user reading state across feature components.
    Luke Hollis
    @lukehollis
    Build from most recent commits up at http://api.cltk.org
    Kyle P. Johnson
    @kylepjohnson
    So cool.
    Md. Sabbir Alam
    @InsomniacSabbir
    hello
    Rob Jenson
    @ferthalangur
    All the texts are pointing to Herodotus right now. Is that OK?
    Luke Hollis
    @lukehollis
    Yep.. Just working out the frontend templates. I think there's still a lot of improvements to be made there but that we have enough to build with for now
    I think that the module that accesses the API can perform it's operation very simply in a manner similar to the meteor spreadsheets package:https://github.com/ongoworks/meteor-google-spreadsheets
    Md. Sabbir Alam
    @InsomniacSabbir
    Hello, I have a question.

    Can we use the following type of text as a corpora for sanskrit ?

    कृष्णचन्द्रः नाम कश्चित् आसीत्।

    Kyle P. Johnson
    @kylepjohnson
    @InsomniacSabbir Do you mean whether we wantto serve texts in the Devanagari alphabet? Yes :)
    Md. Sabbir Alam
    @InsomniacSabbir
    So, if i import these type of text as sanskrit corpora there is no problem ?
    Kyle P. Johnson
    @kylepjohnson
    No, not a problem at all. I personally prefer Devangari, so long as it is utf-8
    Md. Sabbir Alam
    @InsomniacSabbir
    Thank you very much, sir.