I trust that you had a merry Christmas and a Happy New Year...

Supporting phones is a very good idea: "";
The article mentions: "Of the 6 billion cell phones in use, only around 1.1
billion of them are mobile-broadband devices."

I wonder what market size Mozilla is expecting for Firefox OS. Prior to you
mentioning: "";; I had not thought of the browser
supporting some of the same features as Firefox OS.

I have mixed feelings about: "this would break the fundamental rule that
the GUI should also work in an environment without JavaScript"

It seems contrary to what most companies are pursuing, e.g.: "";

Anyway, have you looked at: "";
and "";? I suppose that PicoLisp could run in the
browser; and, act as an offline cache for the server, etc....

Some of the same code could also be used in nodeJS; for OS interop, etc...

Under Windows I have used nodeJS so that localhost can query PicoLisp, in a
psuedo RESTful manner (i.e., no app session...)



On Wed, Dec 25, 2013 at 7:35 AM, Alexander Burger <>wrote:

> Hi Jon,
> thanks for the input!
> > Numerical input elements can/should be given pattern attributes that
> > trigger the numerical keypad on iPhones/iPads, like this:
> > <input pattern="[0-9]*" type="text" value="55667788" />
> > As far as I know, this pattern makes no difference on Android. ;-)
> This could be easily done using the '<style>' function or the '+Style'
> prefix class, e.g. by replacing the field definition
>    (gui '(+Var +NumField) '*DemoNum 10)
> with
>    (<style> '(pattern . "[0-9]*")
>       (gui '(+Var +NumField) '*DemoNum 10) )
> or with
>    (gui '(+Style +Var +NumField)
>       '(cons 'pattern "[0-9]*")
>       '*DemoNum 10 )
> For the '+FixField' the pattern should probably extended for the decimal
> point, and a '-' for negative numbers might also be necessary.
> Note that '<style>' could be used for a whole bunch of fields
>    (<style> '(pattern . "[0-9]*")
>       (gui '(+NumField) 10)
>       ...
>       (gui '(+NumField) 10)
>       ... )
> > When I tap/click on a menu and the menu drops down, I would like the menu
> > to go away if I tap/click outside the menu, on "neutral ground".
> This is difficult, if not impossible. The menu is implemented as anchor
> elements in an unordered list. Clicking outside it doesn't generate an
> event.
> Perhaps it could be solved with some JavaScript trick, but this would
> break the fundamental rule that the GUI should also work in an
> environment without JavaScript (e.g. on text browsers).
> ♪♫ Alex
> --

Reply via email to