![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
(no subject)
May. 27th, 2006 08:26 pmSo, a while back I mentioned that I'd had to set aside all my clever LJ layout hacks because the dev team had broken something in handling new inline voice posts. I just today got around to merging my layout with the newest version of Tabular Indent, which had a variety of useful changes.* Right after I figured out what the original problem was, I discovered that a how-to page had been put up in the mean time, which would have saved me some, though not all, of the merge work. Basically, they broke the preferred method for printing entry content, so that a mysterious Entry::print_text() method now handles more complex inline content.
That's not so bad unless you, as I do, want to manipulate the text before printing it. Luckily there's a workaround as long as there's no inline media, and I don't really need to edit the text if there is, but the removal of that level of control irritates me.
Oh well, at last I get auto-cutting and quiz-blocking back.
*If proper encapsulation and inheritance were used here, it would have been substantially less work for me to keep up with new feature handling, but even I will concede that that would be a fairly advanced trait for this system.
That's not so bad unless you, as I do, want to manipulate the text before printing it. Luckily there's a workaround as long as there's no inline media, and I don't really need to edit the text if there is, but the removal of that level of control irritates me.
Oh well, at last I get auto-cutting and quiz-blocking back.
*If proper encapsulation and inheritance were used here, it would have been substantially less work for me to keep up with new feature handling, but even I will concede that that would be a fairly advanced trait for this system.
