ConTeXt wiki:Wishlist (old)

From ConTeXt wiki

Here's an old wish list for the gardner :)


... a place to collect ideas to make the garden even better ...


  • Q: I have been playing a bit with the <context> rendering. What do you think of [1] instead of [2]? --pg
A: I'm not sure yet; it looks sharper, but the sharpening seems a bit uneven compared to the old version. So I don't know whether I prefer "sharper" or "more even". ... After looking at this some more, I think I slightly favor the old version, because it does look more even. On the other hand, the images are a lot smaller on the new version, which is a definite boon on a modem connection! --Brooks
  • Q: adding <xmlcode> (code highlighter is already written) or, if not too complicated, something more general like <code type="xml">, <code type="mp">, ...
A: This is quite hard I'd guess. Addition: in the new wiki software which I will eventually install (I am currently testing a lot -- MW sofware doesn't behave as expected) will be able to handle those parameters (note for myself: instructions here)
  • Q: adding <latex> counterpart to <context>; mostly in order to be able to compare LaTeX and ConTeXt results or to be able to describe the desired result in Category:From LaTeX
A: [update] I didn't remember what <context> does... Would we need a multiple pass solution? --pg
A2: Brooks seems to like LaTeX, perhaps he can tell more; I don't really remember how many time one needs to run it. I guess that we won't need BibTeX, but perhaps some proper indexing/cross referencing would be handy. Is running it two times enough? More than three times is probably already to much. --Mojca
A3:In most cases, LaTeX really only needs one run. It needs two runs to resolve any references that are referenced before they are created -- which, for Wiki examples (which don't have floats floating to later pages) is probably likely to be so infrequent as to be unnecessary. It occasionally needs more than two runs, but only in really rare cases, and we definitely won't see those on the Wiki. So, my answer would be to do two-pass (call "latex filename" twice) if it's easy to do, otherwise one-pass is probably sufficient. --Brooks 06:10, 9 Sep 2005 (UTC)
  • Q: We now have the the {{{cmd|command}} template and the <cmd>command</cmd> tag. The template works beautifully, although it prints the command in proportional text instead of the rather nice fixed-width font used on this wiki. The latter doesn't work. Would it be possible for the maintainer to do a wiki-wide find-and-replace of s_<cmd>_{{cmd|_g and s_</cmd>_}}_ ? It will make every single page on this wiki hugely more useful in an instant.


  • Q: Is it possible to download attachments? A: I have 'disabled' (by removing the link) downloading attachments. Lurker offers part of the message as an attachment for download. This might include email addresses and I don't want to reveal them without changing. I fear that I would also change the integrity of the attachments with my perlscript. So: they are there but not linked. I'll write this down on my todo list.
  • Q: I vaguely remember you were talking about using some other program for the html-ization (instead of / next to Lurker). Is that likely to happen any time soon? A: Not in the next two months. But I think around that time: yes. It will not use lurker as a backend


  • there's no "download this article" for MyWay and there's no link to user webpages listed under user pages
    • I get (half of) the word back: only this page and only some Ways have missing links
  • a form to submit proposals for new entries
  • sort by author/magazine number/title
  • maybe: adding talks in conferences (EuroTeX, ...)
  • support for documents in other languages: there are some French, German, Vietnamese ... (well and Dutch, of course!) articles & slides around; TODO: an additional field to note the language & add some documents (less work if a form for submitting proposals for articles is added)
    • word taken back again: language field is already supported, it's only that no documents in other languages are there (yet)
  • unimportant: exporting bibtex entries about the magazine (in plain and Taco's format)



  • selector to choose the ConTeXt version



  • Would it be sensible to add an extremely short description of what a module does on the first page? --Mojca


  • adding <a name="line xxx"> at the beginning of every line in the source code as to be able to reference to a certain line in hyperlinks (on the other hand: it may be a bad idea to be able to point to a certain line since the files are a subject to change)
  • perhaps adding <a name="ccedilla"> to places where \definecharacter stands in a similar way as the alt name= are added in front of \def\somecommand (on the other hand: a bad idea since there may be more than two definitions of a single named character in one file)
  • serching/highlighting more that one word
  • if the user comes from google, parse the URL for &q=somequery and add ?search=somequery at the end of the new URL
Example: if someone searches for hack in google and follows the link to supp-vis.tex, the site would open instead


The first two are implemented, see the help page. The third, well, needs some thinking and the link to the mailarchive will have to wait until I implement the new mailarchive. --pg
  • What about different tulip colors on icons for different modules? (so that one sees the difference between wiki/source browser/texshow and others already from the color; I would perphaps leave three colors for wiki and make the rest "mono"chromatic: blue for source browser, red for live, ...). Maybe a stupid suggestion, but I usually have approximately 10-15 tabs per browser opened and this makes a difference ;) --Mojca

/code>; mostly in order to be able to compare LaTeX and ConTeXt results or to be able to describe the desired result in Category:From LaTeX

A: [update] I didn't remember what