FreeConferenceCall – Sciter UI

August 28, 2015

Filed under: Sciter — Andrew @ 8:17 pm


FreeConferenceCall company has published new version of their video conferencing application that aims at one-presenter-thousands-viewers video conferences and screen sharing.

Their application works on Windows and OS X and uses solely Sciter based UI with extensive use of Sciter’s unique popup DOM elements. Even video is rendered by Sciter with custom native video frames providers.

It is probably hard to realize, but that bar on the top and popup from it is HTML/CSS in reality.

Colorizer has landed into Inspector

August 27, 2015

Filed under: Sciter — Andrew @ 9:41 pm
Inspector with source code highlighting module

Inspector with source code highlighting module

Tokenizer + ::mark() = syntax colorizer

August 25, 2015

Filed under: HTML and CSS,Sciter,Script,Source code — Andrew @ 9:45 pm

Here is selfie of syntax (tiscript) colorizer – the text below is a full source code of syntax highlighting routine.
The code has colorized itself:

syntax colorizer

syntax colorizer

Can your browser do that in 40 lines of code?

And here are styles that define style of tokens:

plaintext > text::mark(number) { color: brown; }
plaintext > text::mark(number-unit) { color: brown; }
plaintext > text::mark(string) { color: teal; }
plaintext > text::mark(keyword) { color: blue; }
plaintext > text::mark(symbol) { color: brown; }
plaintext > text::mark(literal) { color: brown; }
plaintext > text::mark(comment) { color: green; }

Easy, no?

And even shorter selfie, colorizer wrapped as an aspect component (referenced from colorizer.css):

::mark(…) feature is comming

August 22, 2015

Filed under: HTML and CSS,Sciter,Web Application Techologies — Andrew @ 10:04 pm

Please consider these tasks:

  1. Find all words in text on HTML page and highlight them
  2. Syntax highlighting: parse text of <pre> and mark all keywords by changing their color
  3. Find all misspelled words in <textarea> highlight them specifically.

Currently you can do #1 and #2 by wrapping each text found into <span>s with specific classes – thus to modify DOM structure of the document. Such modification by itself is a) not trivial to implement, b) is highly non-desirable (consider text editor with syntax highlighting) and c) even impossible in case of <textarea> for example.

Ideally we should have some facility that will allow us to a) mark text fragments, b) apply styling to such marked runs through CSS and c) do that without DOM tree modifications.

As a result upcoming Sciter will have:

  1. In CSS, support of ::mark([s]...) pseudo element.
  2. In script runtime, new methods of Selection class:
    • Selection.applyMark(start,end, ... mark names...); – to add marks to the range.
    • Selection.clearMark(start,end, ... mark names...); – to clear marks from the range.

Example, CSS:

div::mark(hilite) { background-color:lime; } 
div::mark(hilite2) { background-color:cyan; }
div::mark(literal,string) { font-style:italic; color: red; }

First rule will tell the engine to set background color on all text runs that are marked by “hilite” to “lime”.

And script code

      var text = $(div).firstNode;
      var start = [bookmark: text, 6, false];
      var end   = [bookmark: text, 11, false];

will apply mark “hilite” to the text node from 6th until 11th position and so you will have the following rendering:
marks in text nodes
Note: this will not change DOM structure but rather apply some meta information to characters in the text.

My interview to Russian “Hacker” magazine

Filed under: Sciter — Andrew @ 9:46 am

You can read it here (in Russian).


Adding “script eval” into inspector

August 14, 2015

Filed under: Sciter — Andrew @ 8:32 am
script eval input and its context menu

script eval input and its context menu

ENTER in that input triggers script evaluation: inspector asks the “inspectee” to execute that script in context of its selected element.

« Previous PageNext Page »