-
Notifications
You must be signed in to change notification settings - Fork 10
Coderay support #6
Comments
What's necessary to advance this? |
Are you asking for advice on how to implement it? |
Yes! |
Should support for coderay be added here, or to the coderay project? Also, any idea how coderay deals with i18n? |
How does that sound? |
I think it makes more sense to add the coderay support in this project, especially since one parser is required per i18n language. |
What are the Gemfile and gemspec files for? Where do the tests go? |
How familiar are you with Ruby? These are pretty basic things in Ruby. |
My problem is how the various pieces fit together. The idea is to create a gem with an extension to coderay? |
Yes, I think that's the way to go. A |
One would have to require the new gem, right? Can you see any way for the new gem to add Gherkin support to Coderay in a transparent way, so that installing the new gem would be enough? |
Perhaps CodeRay could be changed to use the new gem. By the way, do you think it is really necessary to have one parser per language? One might have a single parser and recognize the # language: iso directive. |
What do you mean when you say CodeRay should be changed to use the new gem. Do you mean the CodeRay project should have a dependency on It would be possible to make the CodeRay parser use the |
How can one add support for Gherkin to, say, Redmine, without changing any of its code, just updating its gems? As to the runtime dependency, that would be good, right? |
That's a question for the RedMine maintainers. In theory it would be ok to let All of this can be avoided if RedMine provides a mechanism for registering 3rd party CodeRay scanners. |
I talked with Kornelius Kalnbach, the developer of CodeRay, and he suggested that gherkin-coderay could be a CodeRay plugin (gem). I think it is a good idea. |
Hi MMSequeira, have you found a solution for implementing gherkin syntax highlighting in Redmine? |
Grab this one: https://gist.github.com/1076987
The text was updated successfully, but these errors were encountered: