Because BoltWire has natural spacing you can cut and pasted tabbed date,
like an outline from a document and it will display it by using a bunch of
markups. Similarly, you can put a long string of spaces and it will
do the same. I do find myself taking advantage of this rather than going
with bullets sometimes to do something like this (I'm using spaces to
indent):
line1
line2
line3
It shows up like that in BoltWire (5 and 10 spaces respectively)
But I just get lazy typing all the spaces. So I was thinking the following
would generate the same output...
line1
,line2
,,line3
Maybe it's not worth putting in the core. Just seems I do this quite a bit.
Esp considering the fact your are right, we would be smarter to do for
output, otherwise long lines that wrap will look really ugly. Guess I need
to think about this some more...
line1
<div style=padding-left:20px>line2</div>
<div style=padding-left:40px>line4</div>
Always appreciate your insights Martin...
Cheers,
Dan
On Tue, Feb 18, 2014 at 2:14 AM, mz <[email protected]> wrote:
> I may be wrong but I never saw tabbed data on a website.
> I always thought you need some kind of <span> or <div> or at least a table
> for this.
> But who knows: a less tech-savvy user would use tabs.
>
> I would go with commas, too.
>
> Greetings, Martin
>
> Am Sonntag, 16. Februar 2014 20:01:18 UTC+1 schrieb Dan:
>
>> Hi all, another quick question...
>>
>> BoltWire already converts tabs (when cutting and pasting from another
>> document) into 5 spaces/tab.
>>
>> Yet you can't enter tabs directly, because the browser just shifts you
>> out of the edit box and to the submit button (or whatever is next in line).
>> If you want to manually create your own tabs (say an outline) you have to
>> add a lot of spacing. I'm thinking about using one of the following and
>> soliciting feedback:
>>
>> ===word (three tabs)
>> ---word
>> ,,,word
>> +++word
>>
>> I like the first but it conflicts with bullets a bit and many wikis use =
>> for headers (rather than !) The second option is good but it might conflict
>> with natural input from a user. The commas look a little clunky but might
>> be best. The +'s require a shift to enter, but it almost looks like a t for
>> tab.
>>
>> Any thoughts? Is this even a feature people would use?
>>
>> Cheers,
>> Dan
>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "BoltWire" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/boltwire.
> For more options, visit https://groups.google.com/groups/opt_out.
>
--
You received this message because you are subscribed to the Google Groups
"BoltWire" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/boltwire.
For more options, visit https://groups.google.com/groups/opt_out.
