Hi all - when the decision was leaning to W9-10 I was going to join, but today 2:30 is already booked. apologies, but happy to try and work with things or test. --elli [Elli Mylonas Senior Digital Humanities Librarian and Center for Digital Scholarship University Library Brown University library.brown.edu/cds] On Tue, Oct 3, 2017 at 10:28 AM, Raffaele Viglianti < raffaeleviglianti@gmail.com> wrote:
Thanks James,
Sorry to hear that -- the disruption in the email delivery and the short notice made this process messy. I think we'll go ahead with the 2:30 meeting today and schedule more efficiently for next time.
Raff
On Tue, Oct 3, 2017 at 10:22 AM, James Cummings < James.Cummings@newcastle.ac.uk> wrote:
Hi all,
It turns out I'm not going to be able to make 2:30pm EDT. (Which I think is 7:30pm here?)
I'm happy to help try and break what Raff (and others) produce, test it with weird ODDs, etc. Or just feed back usability comments if that is helpful.
Best wishes,
James
--
Dr James Cummings, James.Cummings@newcastle.ac.uk
School of English Literature, Language, and Linguistics, Newcastle University
________________________________ From: tei-council-bounces@lists.tei-c.org
on behalf of Raffaele Viglianti Sent: 03 October 2017 14:34:44 To: tei-council@lists.tei-c.org Subject: Re: [tei-council] RomaJS meetings We're meeting today at 2:30 pm EDT.
On Oct 3, 2017 09:02, "Peter Stadler"
wrote: I could only do Wed. 9–10, sorry.
Cheers Peter
Am 30.09.2017 um 01:34 schrieb Hugh Cayless
: I can do Tuesday, either time. Wednesday 9-10 is possible, but I'll be waiting on a plane, so will probably have to leave early.
Hugh
Sent from my phone.
On Sep 29, 2017, at 18:52, Elisa Beshero-Bondar
Hi Raff― I might be dispensable, but I’m glad to help if I can. I’m
only available next week on Tues. Oct. 3, but probably anytime between 2-5pm, so long as it’s just an hour. My sense is that 3-4 pm is
―Elisa
-- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text | Associate Professor of
English
University of Pittsburgh at Greensburg | Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: ebb8@pitt.edu mailto:ebb8@pitt.edu Development site: http://newtfire.org http://newtfire.org/
On Sep 29, 2017, at 5:11 PM, Raffaele Viglianti < raffaeleviglianti@gmail.com> wrote:
Hello,
I would like to set a 1-hour call for sometime next week to kick
off. I said Fridays would be good, but actually I'll be in Charlottesville at the end of this week, so these are times that would work for me (all times are in EDT):
Tuesday 3 Oct 9am - 10am Tuesday 3 Oct between 2pm - 5pm Wednesday 4 Oct between 9am - 12pm
Please let me know if you're interest in attending, your time
or if you're interested but cannot make those times.
While it's true that you'll need to know some Javascript to help,
a fair bit of conceptual work that wouldn't require you to code. For example: what operations should one be able to do with elements? What about defining their content model? What parts of the ODD (and its JSON counterpart) should be queried and how? Coming up with algorithms / strategies together can be as useful as writing the real thing.
Also, based on my email from yesterday about p5subset.json, it's now
that there will be some XSLT work required as well, which most of you can help with. We still need to discuss what changes are needed and why, and I'm hoping we can focus on this during the call.
If you want to try helping with JS coding and are not familiar with React/Redux, you could start form these short pieces to get a
wrote: probably best. things preference, there is likely summary idea:
https://reactjs.org/tutorial/tutorial.html#what-is-react http://redux.js.org/docs/introduction/Motivation.html http://redux.js.org/docs/introduction/CoreConcepts.html
Because development is underway, there is already a lot of boilerplate code that can be copied to create new places where to hold data, new operations, and new UI components. But you'll still need to figure out how to connect everything together. I am happy to do code walkthroughs.
Thanks, Raff -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived
-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived
-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived
-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived
-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived