From: Henri Menke <henrimenke@gmail.com>
To: "ntg-context@ntg.nl >> mailing list for ConTeXt users"
<ntg-context@ntg.nl>
Subject: Re: roadmap
Date: Wed, 16 May 2018 17:38:40 +1200 [thread overview]
Message-ID: <63d9d108-e7b2-4aab-0783-8734cd394853@gmail.com> (raw)
In-Reply-To: <b0398c57-5731-9c8b-eeb4-74a703db35c0@xs4all.nl>
I just thought of another thing.
Could you expose _all_ the subtypes of _all_ the different node types
similar to node.id? (currently this is only enabled for whatsits) As of
now I always have to go to texnodes.w, find the array and count to find
out which number a subtype has. It would be much easier if we could
node.new("noad", "bin")
instead of
node.new("noad", 4)
and I would also like to see
node.subtype("noad", "bin") -- return 4
On 15/05/18 11:34, Hans Hagen wrote:
> On 5/15/2018 12:52 AM, Henri Menke wrote:
>
>> Math typesetting is really crappy in ConTeXt, but I get that this is
>> beyond your priorities. I plan to develop a module which resembles
>> the features and syntax of the amsmath LaTeX package for my PhD
>> thesis. I'm not sure how well this will integrate with the existing
>> mechanisms.
>
> hm. i have no clue what you refer to ... afaik most is configureable
>
>> - columnsets, the new ones have considerably fewer features than the
>> old ones.
>
> like ... but adding some is no problem (only predictable stuff) .. no
> column handler suits all (we now also have page columns btw)
>
>> - rowwise setups in xtables and maybe columnwise, but that is
>> computationally expensive.
>
> indeed so that's why we have categories instead
>
>>> - We can add more trickery for fonts and scripts. There are some
>>> pending extensions.
>>>
>>> - Maybe we should provide a few more general styles.
>>
>> What does that mean? Things like the TUGboat style?
>
> no, e.g. some basic educational stuff
>
>> More callbacks. I'm missing callbacks into error handling (i.e.
>> intercept errors) not just into error reporting like show_error_hook.
>
> if you want to intercept errors then that has to happen at the macro
> level, because once tex starts expanding the error can be anywhere
>
> (so, in a macro package one can set at the tex level flags that one can
> act upon in the error callback)
>
> (the eror messages themselves might become a layer but that's for later)
>
>> Throw out all non-Lua-related primitives and ntg-context@ntg.nlreplace
>> them with Lua functions. People can then define those primitives
>> themselves, e.g.
>
> way too slow ... in that case i'd drop tex completely (i.e. do all in lua)
>
> also, you can right now (re)define primitives if you like (depending on
> the definition of primitive)
>
>> \suppressoutererror
>>
>> becomes
>>
>> \protected\def\suppressoutererror{%
>> \directlua{errors.suppressoutererror()}}
>>
>> This makes it much easier to access that stuff from Lua. Also
>> interface all the \pdfvariable and \pdfextension stuff to Lua.
>
> all pdf stuff is already doable in lua (context doesn't even use \pdf*
> for quite a while)
>
>> This should have maybe been done before 1.0 but I guess with 2.0 you
>> can introduce “breaking” features.
>
> well, a 2.0 (if ever) will probably only be useable for context ...
>
>> LuaJIT will always be 5.1 compatible. That is one of the declared
>> goals of the project. However there exist compatibility layers for
>> Lua which implement recent features for older interpreters.
>> https://github.com/keplerproject/lua-compat-5.3
>
> in that case in the end it will be dropped ...
>
>> I would rather not see LuaJIT support being dropped. The VM by itself
>> (without JIT) is already a lot faster than regular Lua and I feel that
>> the ConTeXt runs benefit from that quite a lot. I use contextjit as
>> my daily driver.
>
> hm, at most 20% which is also what i get when i buy a new laptop
>
> keep in mind that luajit has some limitations (stack and such)
>
> (and the last few years i managed to squeeze out a lot from lua, and
> with lua 5.3 the gaps became narrower)
> Hans
>
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
> -----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2018-05-16 5:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 15:17 roadmap Hans Hagen
2018-05-14 19:36 ` roadmap Henning Hraban Ramm
2018-05-14 21:26 ` roadmap Hans Hagen
2018-05-15 9:01 ` roadmap MF
2018-05-14 22:52 ` roadmap Henri Menke
2018-05-14 23:34 ` roadmap Hans Hagen
2018-05-16 5:38 ` Henri Menke [this message]
2018-05-16 6:24 ` roadmap Joseph Canedo
2018-05-16 7:28 ` roadmap Hans Hagen
2018-05-14 23:41 ` roadmap luigi scarso
2018-05-15 19:17 ` roadmap Pablo Rodriguez
2018-05-15 21:26 ` roadmap Hans Hagen
2018-05-16 15:18 ` roadmap Pablo Rodriguez
2018-05-16 19:14 ` roadmap Fabrice L
2018-05-17 13:06 ` roadmap Hans Hagen
2018-05-17 14:24 ` roadmap Mohammad Hossein Bateni
2018-05-17 15:47 ` roadmap Otared Kavian
2018-05-17 16:50 ` roadmap Hans Hagen
2018-05-15 6:15 roadmap Christoph Reller
2018-05-15 6:23 ` roadmap luigi scarso
2018-05-15 6:36 ` roadmap Hans Hagen
2018-05-15 14:46 roadmap Christoph Reller
2018-05-15 14:51 ` roadmap luigi scarso
2018-05-18 9:54 roadmap Christoph Reller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=63d9d108-e7b2-4aab-0783-8734cd394853@gmail.com \
--to=henrimenke@gmail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).