We shouldn't show tags. It has to be graphically resolved. Campfire
currently makes them red and italicized.... You may want to do the same for
starters, if possible... Any graphical solution is preferable to tags. We
don't want to scare off people.

Sava



Paul Baranowski
ski.org> cc:
Subject: [campsite-dev] Subheads
10/05/04 04:05 PM
Please respond to
campsite-dev






I'm working on subheads for HTMLArea. What I know of subheads is this:
they let you break your article into multiple pages.

The way it works is: you highlight a word, then click the "subhead"
button. The question is: do we give some sort of indication that a
section of text is a subhead? Initially, Mugur and I decided that we
shouldnt, but after thinking about it, it seems like we should.

If we dont give an indication of the subhead, then the person editing
the article may highlight a word and make it a subhead multiple times.
(I'm not sure what the parser would do in this case).

I suggest that we put template-like tags around the subhead, like this:
{{PageTitle}}Page 2: A New Beginning{{/PageTitle}}

Even though this opens up the possiblity to people mucking with the
tags, I think it is a better solution than keeping them hidden. Another
solution would be to put some sort of icon next to the word, and have a
dotted underline underneath the selected words. I'm not sure my
HTMLArea skills are up to this level yet, however.

Comments?

- Paul

------------------------------------------
Posted to Phorum via PhorumMail

My suggestion is: do not display campsite specific tags. And I'm sure Sava
agrees with me: he is the one who wanted a true online WISYWIG editor in the
times when it was not possible

There is another option: display the subtitles with different character format:
bold, italic, size +2. I think this would be a much better solution for the
journalist. When one sees some text that looks totaly different than the other
content one immediatelly thinks it may be a chapter, subtitle etc. But when one
sees some tags he/she (not a programmer) doesn't know what that is and even if
he/she figures it out he/she will shurely not know that it has to respect a
strict syntax:
{{PageTitle}}
not
{{Page Title}}

So the latter one needs training

What if I (a journalist) think that I am smart and I should delete the / in
{{/PageTitle}}? Also, they don't care about functionality tags, they only care
about the text and it's natural and I think we shouldn't force them to deal
with programming like formatting.

There is another reason why we shouldn't display the subtitle tag: I would have
to modify the parser to accept two kind of tags:
- the old ones
and
{{ }} - the new ones

I can easily make it accept one of them but not both of them at the same time.

Then, another reason: we agreed we don't want to spend more time on yet another
upgrade script.

Mugur

--- Paul Baranowski wrote:

> I'm working on subheads for HTMLArea. What I know of subheads is this:
> they let you break your article into multiple pages.
>
> The way it works is: you highlight a word, then click the "subhead"
> button. The question is: do we give some sort of indication that a
> section of text is a subhead? Initially, Mugur and I decided that we
> shouldnt, but after thinking about it, it seems like we should.
>
> If we dont give an indication of the subhead, then the person editing
> the article may highlight a word and make it a subhead multiple times.
> (I'm not sure what the parser would do in this case).
>
> I suggest that we put template-like tags around the subhead, like this:
> {{PageTitle}}Page 2: A New Beginning{{/PageTitle}}
>
> Even though this opens up the possiblity to people mucking with the
> tags, I think it is a better solution than keeping them hidden. Another
> solution would be to put some sort of icon next to the word, and have a
> dotted underline underneath the selected words. I'm not sure my
> HTMLArea skills are up to this level yet, however.
>
> Comments?
>
> - Paul
>
>




__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail

------------------------------------------
Posted to Phorum via PhorumMail