|
== Archives ==
[[/Archive 1]]
== Font conventions (again) ==
Another possible approach to handlign syntax conventions has become available. Wikipedia now supports GeSHi[http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi], which provides automated syntax highlighting by use of <nowiki><syntaxhighlight></nowiki> tags. This would eliminate the need to include formatting markup in the text of the page itself (which can be a little cumbersome). A downside is that the current support for syntax highlighting of Eiffel (yes, it has Eiffel support already) doesn't perfectly conform to the current syntax presentation guidelines:
For example we would get the following
<syntaxhighlight lang="eiffel">
class
HELLO_WORLD
create
make
feature
make
do
io.put_string ("Hello, world!")
io.put_new_line
end
end
</syntaxhighlight>
However, if we were to convert the page to using GeSHi <nowiki><syntaxhighlight></nowiki> tags then we could move the convention issues over to fixing Eiffel syntax highlighting in GeSHi (there are, apparently, files for each language which can be changed) and not have to mess with markup on this page anymore -- it would all propogate automatically. Thoughts? -- [[User:Leland McInnes|Leland McInnes]] 20:11, 16 May 2007 (UTC)
:I like this proposal. GeSHi seems to use CSS so it's reasonable to think users could pick how they want to view the code. For instance, I could imagine little buttons on every source snippet that would switch between formatted and unformatted views. Regardless, with GeSHi support, I think these <nowiki><syntaxhighlight></nowiki> tags are likely to become the standard way to present code, so this article should probably conform for that reason. --[[User:Doradus|Doradus]] 03:07, 19 May 2007 (UTC)
::It is done. Certainyl it makes maintainability of code samples much easier. It also has the bonus of actually taggin code as Eiffel code specifically. Unfortunately it doesn't work fo inline code. -- [[User:Leland McInnes|Leland McInnes]] 06:39, 19 May 2007 (UTC)
:::Why wouldn't it work for inline code? --[[User:Doradus|Doradus]] 21:55, 26 June 2007 (UTC)
::::Because GeSHi automatically renders into blocks, so putting <nowiki><syntaxhighlight></nowiki> tags on inline code only results in it no longer being inline. -- [[User:Leland McInnes|Leland McInnes]] 02:42, 5 July 2007 (UTC)
Nice to see the article has recovered from its brief bout of blue-font insanity. I think the way it's done now, with a "style conventions" section, is just right. --[[User:Doradus|Doradus]] 21:54, 26 June 2007 (UTC)
: there was a clear vote on how it should like, and the inventors proposal was voted for. i'd suggest you change your stylesheet so it conforms to the original, or you change it back to without stylesheet and it looks again like the original. --[[User:83.215.194.249|83.215.194.249]] 00:13, 5 July 2007 (UTC)
:: I would be happy if the GeSHi Eiffel stylesheet could be cleaned up to conform. It's actually reasonably close already (compare, for example, to code on the open source EiffelStudio wiki [http://eiffelsoftware.origo.ethz.ch/Catcall_checkpoints][http://eiffelsoftware.origo.ethz.ch/Usage-site_variance]). That, however, is in the hands of whoever maintains GeSHi for Wikipedia -- I really would not know how to make the change as an ordinary user. Ultimately this is the best solution, it just has pending stylesheet changes to be dealt with. -- [[User:Leland McInnes|Leland McInnes]] 02:42, 5 July 2007 (UTC)
::: It seems to be at [[MediaWiki:Geshi.css]], so make whatever change you want. --[[User:Doradus|Doradus]] 11:57, 11 July 2007 (UTC)
:::: That is what I suggested to do 4 years later, although the format has an <code>inline</code> option <syntaxhighlight lang=eiffel inline>class HELLO_WORLD create make feature ...</syntaxhighlight> if that makes sense.
:::: I don't know if you already had noticed that. This discussion is so long that I forgot what other point I wanted to write about.
== No instructions, advice, or how-to ==
| 