Search options (Page 147 of 151)

Say, why did Charm/Breckin take to Slash, anyway?  And before or after Tazar had his balls?

So go read the future stuff in Vol 2 while you wait.

I have a draft of the new version of CH3.  I'm hoping to get it out in the next 36 hours.  Amy, you'll beat me up on description.  I think this new version will have a litttle more room to insert it after the thrashing.

In the damaged, supperating noggin.  Actually, I'm sorry I suggested 'noggin', since it's not your voice.

Alda has to avoid Slash's renewed injuries and his mangled mug, his damaged dial, his disfigured phiz.

I was afraid the spears had gone into into HammerSpace

If we're determined to keep the inline review system, and if reviewers are convinced that it's a better way to enter reviews, then I'll ask for a couple of things.  First, the option to display the whole set, with whatever replies, in a format suitable for printing.  Second, for relief from the length-of-reply limit on the individual 'tweet'.

But I still think a way to link a single-body review into the text, with at least two display options, would be better.

I also found some things that won't work between the timer and the flasher.  The timer turns the flasher on by supplying power to it via a MOSFET.  I forgot that the timer output is totem-pole, not open collector/drain.  Fixable, but at this point I need to rearrange some things and find the most economical way to do it.  I don't have much room left for parts and connections.  I just had a thought on simplicating it.  Write it, think it, then get to reviews.

It's up now.  I suspect TNBW hasn't got their caches right.

Thanks..  Will check it out.

---It looks good!  Sorry for the delay in getting back to it.

I'm not seeing it.  Are you sure you uttered all the right magic?

I have to get to bed now.  I spent the last few hours trying to fix a design problem, and before that I put the sketch of the far future chapter up.

Can't find the old 'Future Wishlist', so I'll write here.

Minor but irritating thing that could be improved:  When I go to publish, I get a 'Warning: Are you sure you want to do this' on the point cost.  'Warning: are you sure you want to do this' I associate with file deletion and such.  Perhaps you could make this particular message a little more like a bank transfer or phone payment: 'Confirm: 3.25 points will be deducted from your account to pay for this transaction' or similar words.  It would be just as effective and less jarring.  I don't know if there are other places where this could apply.

When it comes time to get the email notifications working, I suggest multi-level options on the creation or publishing of work.

1. An alert on an author.

2. An alert on an entire group.

3. An alert on an author IN a group, thus Mrs. Plum, but only for posts in Medieval Fantasy and Magic, but not for postings in Literary Fiction (unless it's also in the other group)

And then a further distinction:

1. Creating/first publishing of a work by the author/group, as above

2. Updates/publishing a chapter in said work

3. Updates/publishing a chapter of a =selected= work

so that I'm notified when Mrs. Plum has a new work, but I have chosen not to get subsequent chapter updates on her work--unless I mark that specific work for chapter updates.  (And I should be able to mark such any work that I can read, even if I'm not following the authors or groups.)

Yeah, a few more columns in the database, but I suspect that many of us writers here will want these capabilities sooner or later.

=Postscript=: Attempting to do this list with bullets instead of numbers didn't work.  I'm going to play with the posting a bit and see if I can get some clues.

Okay.  The BBCode document says that (open-square-bracket)list(close-square-bracket) is the correct syntax, but when I go back in to edit it's been changed to (open-square-bracket)list=*(close-square-bracket).  In any case, the HTML is <ul> <li>...</ul>  ......  with no indication of what the bulleting character is.  I don't have my HTML references with me so I can't check them at the momement.

As an aside, can someone tell me, as the BBCode article does not, how to escape square brackets when I mean to use them to indicate the BBCode itself?
Let me know if you can use the screencap.

Which is why some threads belong to stories.  Ideally, reviews would flow right into the story's thread.  (Or one of the story's threads.)

There's a story, supposedly true, about an architect who designed part of a  campus without paving paths between buildings.  He waited until the students wore paths, then paved where they walked.

This may be related to a problem I had.  I did some investigating into the generated HTML and sent a screencap to Sol.  There's a definite bug--at least one--in the code that turns review text into HMTL.  In my case, the angle brackets were left untranslated and the browser is left to try to interpret their content as an HTML tag.  If you know how to use the 'developer tools' on your brower, you might take a look to see if that's the problem.  If not, more detail would probably help the developers investigate.  Or PM me the work and chapter and I'll take a look.  (Use the connection request for the info; I'll decline the connections afterwards.)

You might add to your report the work/chapter you were reviewing.

For now you might use double parens instead of brokets to quote things.