Open michael opened 11 years ago
Hi! Did you mean parsing that data and save it in our database?
Yep. Should be fairly simple since the eLife format already conforms to the substance doc format. So actually no parsing involved here ;)
Sorry, missed some changes. Could you point me to db API?
So we need something like button "load test data" to get all data from lens API?
And sorry - I'm not pretty familiar with document model. Is it true that type
object is something like schema for objects
? So http://elife-converter.herokuapp.com/documents is part of document model too?
So I see many properties in lens schema. Do we need to save them? Or we just need to use our schema which is described in schema.json
?
Don't worry about it for now.. we changed so much, it just takes a while until the code is consistent again. Will keep you posted. :)
Thx. Sorry.
I'm currently working on a big redesign... you could definitely help by creating design sketches. How much time will you be able to spend working on Substance in the coming 6 weeks ? Just for rough task planning. We'd like to get a solid release ready before end of summer.. so there's definitely a lot of stuff that we could need help with.
first mockup of the new vertical split layout..
Looks fascinatingly. Well, I think that I could spend about 6 hours per week. I can help with sketches/css/jade/local javascript.
On 25 June 2013 18:26, Michael Aufreiter notifications@github.com wrote:
first mockup of the new vertical split layout..
[image: screen shot 2013-06-25 at 4 24 56 pm]https://f.cloud.github.com/assets/2931/703077/1b9a7d62-dda3-11e2-8293-5d0328791428.png
— Reply to this email directly or view it on GitHubhttps://github.com/michael/hub/issues/72#issuecomment-19979648 .
Or with backbone if you have plans to use views like with lenses.
On 25 June 2013 18:32, beilinson@gmail.com beilinson@gmail.com wrote:
Looks fascinatingly. Well, I think that I could spend about 6 hours per week. I can help with sketches/css/jade/local javascript.
On 25 June 2013 18:26, Michael Aufreiter notifications@github.com wrote:
first mockup of the new vertical split layout..
[image: screen shot 2013-06-25 at 4 24 56 pm]https://f.cloud.github.com/assets/2931/703077/1b9a7d62-dda3-11e2-8293-5d0328791428.png
— Reply to this email directly or view it on GitHubhttps://github.com/michael/hub/issues/72#issuecomment-19979648 .
You're more than welcome. :) I'll think about suitable tasks that can be done independently. Will assign issues to you, and you can choose which ones you like to take. Just gimme some more time :)
Cool! I'll be waiting. But I'm sorry if I'll ask you a lot of questions :) And sorry for bumping this issue. Thanks!
On 25 June 2013 18:36, Michael Aufreiter notifications@github.com wrote:
You're more than welcome. :) I'll think about suitable tasks that can be done independently. Will assign issues to you, and you can choose which ones you like to take. Just gimme some more time :)
— Reply to this email directly or view it on GitHubhttps://github.com/michael/hub/issues/72#issuecomment-19980455 .
I hope we have working version of the stack by the end of the week. I'll give you instructions how to install. It's hard to keep in sync the documentation since we're changing so much.
For developing a proper UI of the composer we need some good example data. So a great basis to work with would be the current set of eLife documents.
Can we create a dynamic seeding mechanism for dev that would just pull in all the eLife docs from:
http://elife-converter.herokuapp.com/documents
and for each document:
http://elife-converter.herokuapp.com/documents/00048
?