Search options (Page 147 of 152)

Someone please correct me if I'm wrong, but I don't believe this site will host images, apart from author photos and covers.

That might be a problem for the authors of illustrated children's books.

I'm assuming it was after Charm was Charm'd?  I can't imagine Brekin and Slash seeing much in each other?  At least not much that would keep them together.

Why did Horror-Charm allow Brekin to stay with Slash?  Clearly she feels something about him, even if it's only that he can protect her.

I'm not sure now if I'm confusing different versions.  I remember Jaylene telling Sulder that Alda >destroyed< a Horror, but now the Horror resides in that mustard pot, ready to come out when Jaylene jumps in the river.  (AAaarrghhh!)

Not that it relates to anything here but I've just been reminded of some words John Dickson Carr put into the mouth of Henri Bencolin:

.

Well, then I have to rush and get it in!

Minor  nit: in the Settings / email page, you spell 'below' as 'bellow'.  I suggest also that the 'email' menu item and page be titled 'email notifications'.

Another possible future chapter here.

These occur as I see how characters' paths have to cross and what sort of plot things events have to unfold, and how.  Most 'what' at this time.  It also helps me see what I have to develop in the first volume as I rework it.

A classic version control question.  After you version-control the components, how do you create/manage a unified version for the whole product?  The software world has tried a number of different models.  Some work well, some are clunky, and some seem slick but are fraught with problems, often because the descriptions contradict the user's mental model.

Anyhow, there is a fair amount of prior art, in the working model, in the interface functions, and in the back end.  The back end part is probably less useful because many systems store changes as deltas.  That presumes certain ratios of storage and storage access to computation power.  Unless you are running a truly massive--and effective--RAID system, the cost of storage access--disk transactions and head movement--has gone up relative to the cost of storage and computation.

If you're going to work on it at some point I encourage you to open the dicussion to users and to emphasise walking through scenarios to see whether it works as expected--and provides the benefits expected to the user.

If you're going to take this version control step, you might deepen the hierarchy to multi-volume works and multi-section multi-volume works.  The step from three to four is usually easier than from three to four, and that is much easier than the step from two to three.

It's a sketch.  Do the plot/milieu questions hit you like a big pizza pie?

That's the flasher portion, about 1/3 of the parts and nodes.  An astable multivibrator to time the flashes, a monostable m.v. to set their duration, and another astable to fire narrow pulses directly off the power rails for max brightness in each flash, pulse width widening as the batteries run down. The pulses run from 140 usec at low voltage to 75 or 80 usec at max, and you need bells, whistle, and a gong or two to make the mutlivibrator run cleanly at those narrow duty cycles.  The first astable, on the other hand, needs a bell (but not a whistle) to avoid the lockup that ASMVs are prone to.  I'd hoped to use a shared emitter resistor--it's worked for me before--but it didn't work here.

Oh, 630 to 640 usec between the pulses, varying slightly with the pulse width, and about 7.4 msec for each flash.

Communication is feasible on the phone.  Reviewing is harder.  I would attempt only the most minor of story edits because I don't thinkthe Android's physical interface is up to the challenge.

But I've just copy/pasted from a 'source' window, and I'm using that as my referrence for correction.