Difference between revisions of "Wiki:Wishlist (old)"

From Wiki
Jump to navigation Jump to search
(minor edits now <i> instead of <strong> →‎[http://wiki.contextgarden.net wiki])
(transparency in inline context →‎[http://wiki.contextgarden.net wiki])
Line 6: Line 6:
  
 
=== [http://wiki.contextgarden.net wiki] ===
 
=== [http://wiki.contextgarden.net wiki] ===
* '''Q:''' Are the <code>&lt;context&gt;</code> images rendered using gs? In that case, could [http://www.cs.wisc.edu/~ghost/doc/cvs/Devices.htm#PNG <code>-sDEVICE=pngalpha</code>] be used to get transparent images? '''A''': Yes. The [http://sandbox.contextgarden.net sandbox] is setup to use the <code>-sDEVICE=pngalpha</code> But after that imagemagick is used. Could anybody try it or give me an example where the transparency could be used?
+
* '''Q:''' Are the <code>&lt;context&gt;</code> images rendered using gs? In that case, could [http://www.cs.wisc.edu/~ghost/doc/cvs/Devices.htm#PNG <code>-sDEVICE=pngalpha</code>] be used to get transparent images? '''A''': [update] Done. HowTo now transparent.
::Thanks, it looks OK. The first place where I noticed that it would be useful was here: [[:Template:Howto|Howto]] vs. [http://sandbox.contextgarden.net/Template:Howto Howto (sandbox)] or http://meta.wikimedia.org/wiki/Help:Formula. If someone needs white background, a box with white background can still be made.
 
 
* '''Q:''' adding <code>&lt;xmlcode&gt;</code> (code highlighter is already written) or, if not too complicated, something more general like <code>&lt;code type="xml"&gt;</code>, <code>&lt;code type="mp"&gt;</code>, ... '''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: [http://meta.wikimedia.org/wiki/MediaWiki_extensions_FAQ#How_can_I_pass_XML-style_parameters_in_my_extension_tag.3F instructions here])
 
* '''Q:''' adding <code>&lt;xmlcode&gt;</code> (code highlighter is already written) or, if not too complicated, something more general like <code>&lt;code type="xml"&gt;</code>, <code>&lt;code type="mp"&gt;</code>, ... '''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: [http://meta.wikimedia.org/wiki/MediaWiki_extensions_FAQ#How_can_I_pass_XML-style_parameters_in_my_extension_tag.3F instructions here])
 
* '''Q:''' adding <code>&lt;latex&gt;</code> counterpart to <code>&lt;context&gt;</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:''' no problem, would the layout (colors, etc.) change?
 
* '''Q:''' adding <code>&lt;latex&gt;</code> counterpart to <code>&lt;context&gt;</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:''' no problem, would the layout (colors, etc.) change?

Revision as of 10:46, 5 September 2005

Here's a wish list for the gardner :)

Ideas

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

wiki

  • Q: Are the <context> images rendered using gs? In that case, could -sDEVICE=pngalpha be used to get transparent images? A: [update] Done. HowTo now transparent.
  • 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: no problem, would the layout (colors, etc.) change?
I don't think that changing anything is needed, but I'm not sure if I understand the question.
  • Q: In the "recent changes" page, it's often hard to notice the "N" designations ("New page") in the midst of a long line of "M" ("Minor edit") changes. Would it be possible to highlight the "N" in red or something? --Brooks
    I agree with it. It is possible to hide minor edits, but it would really be better if M would become M or if the color of N would change. --Mojca A: Done --pg

archive

  • 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

articles

(Comment from the gardener: articles will be the first service which will change completely. I will try to use ruby on rails for that one. Thanks for the suggestions, I will implement them --pg )

  • archiving articles (if allowed) or at least adding direct URLs to them
  • sort by author/magazine number/title
  • a form to submit proposals for new entries
  • maybe: adding talks in conferences (EuroTeX, ...)
  • unimportant: exporting bibtex entries about the magazine (in plain and Taco's format)

dl

live

  • selector to choose the ConTeXt version

mirror

modules

source

  • 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 http://source.contextgarden.net/tex/context/base/supp-vis.tex?search=hack would open instead

texshow

general

<form method="get" action="http://www.google.com/search">
<table>
  <tr>
    <td><img src="http://www.google.com/logos/Logo_40wht.gif" alt="Google" border="0"></td>
    <td>
      <input name="q" size="31" maxlength="255" value="" type="text">
      <input name="btnG" value="Search" type="submit">
      <input name="domains" value="contextgarden.net;pragma-ade.com;ctan.org" type="hidden">
      <input name="sitesearch" value="contextgarden.net" type="hidden">
    </td>
  </tr>
</table>
</form>