Quote:
Originally Posted by ekaser
That's up to you. I'm just trying to provide a second point-of-view, one that may or may not mesh and/or differ from your own. Ultimately, you're writing the code, so you have to (get to) make the decisions about what will work best for what YOU are trying to accomplish.  It just seems to me like there are two primary things: structure and content, with content being further divided into images, text and text formatting. Structure (other than sentence and paragraph massaging) would remain pretty much unchanged, I'd think, and most of the changes your program would make would be to the content. Therefore, separating the two as much as possible, while maintaining the necessary links between structure and content, would be best. |
Well... yes. I think the reason I feel compelled to try to yield to your implied return to my earlier conception is because the more high-level and real-world I can make the structure (sentences referring to real/detected sentences, et cetera) the simpler I can make my text/content processing code... and, presumably, the less error prone they will be. (Though even in the best scenario, most of them would end up being pretty complex still... which is reason enough to simply where/as possible.)
Quote:
Originally Posted by ekaser
I guess I was seeing footnotes and hyperlinks as being pretty much the same thing. You're going to have to handle hyperlinks, so I figured why not treat the footnotes the same way (in terms of the link itself)? You have to write the code once (for hyperlinks), so if you fold the footnote link into the same mold, you're all done. But YOU'RE the one that has to hold all of this in your head until it's excreted as code, so whatever works best in YOUR head is key... |
That is a good point. I will have to give it more thought. Getting rid of the footnote-marks is definitely a useful thing (because it reduces the number of places where processing code needs to account for them or parse around them)... so unless there are any big benefits from simplifying links/footnotes to be handled via the same underlying mechanism, I will likely keep to the approach I described.
It's definitely going to be a monster of sorts... but hopefully with my ideas starting to become increasingly clear and granular, it will end up a tamable monster.
Quote:
Originally Posted by ekaser
It's sounding pretty good to me!
|
Thanks for the sanity checks!
I'll give you a shout when there is code!
- Ahi