Mario et al

We seem in different timezones, So a lot of water goes under the bridge 
while I am sleeping.

I like the look of your work and you are really extending it to meet all 
those fanciful ideas we discussed, so I am very impressed.

I am however getting a little confused because you are taking this so far, 
if you could make a summary of the state of play or more the current end 
game I would appreciate it. Then I can do through testing and review. If 
you can do this keep it short but list any inter dependencies if they exist 
(But I think you are avoiding those anyway)

*As an Author*
I have some real world demands to produce authored content right now so 
these "facilities" - Shortcuts, utility and custom CSS and new wiki text 
characters are not only fantastic but I can robustly test it as an author 
rather than a designer / hacker.

*Keyboard shortcuts*

I was looking at shortcut for tick and angle braces and Found some on the 
QWERTY keyboard that would suit me and every one


   - alt-> for angle braces (Actually alt-period)
   - alt-' for tick (alt single quote, In shift would be " quotes)


This highlights that such shortcuts may vary with keyboards and languages 
so although we may provide some defaults people should be encouraged to 
build there own.
Actually we build them and they can change the keystrokes.

These would be very quick to learn, the shortcuts only result in the 
special characters being entered at the cursor and need only be active in 
the editor. They can be documented in the Editor toolbar popups as well 
along with triggering the edit tool bar items.

*Defaults and extensibility*

Here is a quick description as I see users / authors may see it in future - 
intentionally leaving out the details

This solution provides the author of wiki text to use additional wiki text 
characters similar to the existing * # ! etc.. on any line in your wiki 
text, Editor toolbar buttons are provides to prefix one or more lines at a 
click with this additional wikitext symbols. To avoid clashes these 
characters are not available on all keyboards so and alt-keyname 
alternative is also provided to enter one of these new wikitext characters.
Depending on which new character you use, the line it prefixes will be 
transformed into a html div or p paragraph.


   - But now on any line, in your text, you can follow the "special 
   character" with .classname or even multiple .classname1.clasname2 (As with 
   any existing wiki text character) and the classnames CSS will be applied to 
   that line and than line only.
   - A small set of CSS classes have being provided to get you started but 
   to can delete, rename and add you own.


*What this means for the author*
As you type your content it is possible to quickly trigger the current 
line, or set of lines to be rendered as a HTML div or paragraph at render 
time, with one or more custom styles applied, for appearance of your 
layout. If you have a preferred style you wish to apply you can create your 
own class to apply. 

   - For example you may want the class "q" to represent quotes from 
   people. simply add a <tick>.q at the beginning or a line and at render it 
   could be rendered in Italics with large Quote icons, indented from the left 
   and right with the text justified and a grey background

For example on a given line, or range of lines, you could provide the class 
.i (indent) and .r (right-indent) ".i.r ", which would indent the line from 
the left and the right.

This means with the included examples or a little css knowledge, the Author 
can quickly create what is in effect custom markup for their text, all of 
which can be quickly entered at the keyboard. Who needs WYSIWYG?

*Now?*
Is it now complicated by defining your ow rule/special character?

Should we have a minimum viable product before we open tiddlywiki down 
another wonderful but infinite path?

Regards
Tony


On Thursday, 3 September 2020 05:18:04 UTC+10, PMario wrote:
>
> Hi,
>
> The keyboard definitions are definitely a problem. 
>
> I personally would like to get an E2 keyboard as described in 
> https://de.wikipedia.org/wiki/Tastaturbelegung#Tastaturbelegung_E2. That 
> would be cool. 
>
> I will try to create a configuration for windows 10 for my existing one, 
> but I'm not sure, how the new "level 2" chars (the red ones) will work. We 
> will see. 
>
> -mario
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/07358b89-3f8d-483a-918a-c1a509d00065o%40googlegroups.com.

Reply via email to