Coder Social home page Coder Social logo

Back/Forward - general solidity about lyt HOT 2 CLOSED

notalib avatar notalib commented on August 20, 2024
Back/Forward - general solidity

from lyt.

Comments (2)

simmoe avatar simmoe commented on August 20, 2024

BTW jumping subsections reminds - aspiring to assimilates - jumping by clicking on the audio statusbar. Which seems to work seamlessly. If we want to implement it easily (for no other reason than knowing it works if we need it), why not fake a timeswitch?

from lyt.

Flambino avatar Flambino commented on August 20, 2024

I'm not sure I completely understand what you mean. As you say, it's difficult unless we're using the same terms.

Here's what I've been calling things so far (and this is what it's called in the code, too):

  1. Section refers to anything with its own heading (regardless of level) in the NCC file. Sections map 1:1 to SMIL files, and thus 1:1 to MP3s. Sections can be nested, but they are still played back separately.
  2. Segment refers to a time-slice in a section's MP3 file. This is the smallest "unit" in the system.

It's confusing to call something a "chapter" because we can't tell from the structure of an NCC if something's literally a chapter or not. E.g. the back cover of the book isn't a chapter, but it is a section.

Right now the back/forward buttons skip through segments, until it reaches the start/end of the current section. At the point it'll skip to the previous/next section, and then skip through that section's segments.

Things get confusing/hard to code because books are divided in different ways. Sometimes several time-slices will refer to the same piece of text or the same panel in a comic book; sometimes it's 1:1. Sometimes the whole book is divided neatly into "1 section per chapter", and other times it's divided into "everything in 1 section".

None of this is a problem if you're reading the book, and just want to play something as audio (and everything is a local file with zero download time). If you're just reading, you can alway drill down to the piece(s) of audio that belongs to a given piece of text.
But we're doing the opposite: Playing back audio, and showing the text. And that's makes everything about the Daisy system maddening.

Anyway, let's talk more about this on Monday

from lyt.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.