Possible Backlog for 0.2.0 release

0 views
Skip to first unread message

h3raLd

unread,
Apr 11, 2010, 2:59:26 PM4/11/10
to Glyph
Now that the first preview release of Glyph is released, it's time to
start thinking about 0.2.0 :-)

I prepared a possible backlog containing the features and bugfixes I'd
like to include in the next release:

http://github.com/h3rald/glyph/issues/labels/0.2.0

The top priority is obviously better diagnostics: at the moment, if
you forget a square bracket that's it, your glyph project won't
compile, and there's no way to understand where the error is.
Fortunately there's a failure_reason method in Treetop which is
supposed to help when a parsing error occurs... I'll investigate and
I'll try to use it with Glyph.

Then, I'd like to add the possibility of compiling single .glyph
files, without having to create a project at all. This would be handy
for writing articles and integrating glyph with other programs as a
filter of some kind (Static Site Generators like Nanoc and Jekyll come
to mind). In order to do this, it would be nice to be able to define
snippets and configuration settings *directly* in a Glyph file: that's
fairly easy to do by adding the appropriate macros.

Then I'd like to add a condition macro, which basically allows the
execution of any macros within it only if a condition is satisfied. To
be honest, I'm a bit unsure on this: Glyph does not aim to become a
programming language! On the other hand, conditional compilations are
used in many document authoring tools, so...

If everything goes well, I *may* add Textile and Markdown as output
targets. This would mean rewriting some of the macros (now HTML-
specific) for Textile and Markdown as well... Kinda tedious, but it
may be worth it. Of course, it would also be nice to have a fallback
mechanism to fallback to HTML in case a macro is not defined.

Finally, I'd like to tidy up the code macro. It works for now (more or
less), but I'd like to add syntax highlighting to it.

If you'd like any feature to be implemented or any particular bug to
be fixed, just ask :-)

Reply all
Reply to author
Forward
0 new messages