You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
while porting it might be an easy task i would like to reiterate what i said on #56
i dont have the time to suppor colorcoder on any editor but the one i use myself daily. While is find bugs and places for improvement in Colorcoder by actually using it daily, having a port on Atom or basically any other editor would require me to have a dedicated testing setups and consume more time—and, shame over my head, atm i dont even have time to work on Colorcoder for Sublime, just look at the timestamps of the open issues.
I recieved numerous enquires (partially via email) about porting Colorcoder to other editors, Atom beeing most prominent suggestion. I always answer by encouraging the porting, i would love to see Colorcoder being accessible to more developers as accessibility of coding to people with dysgraphia and the like should not be bound to a particular editor and i hate being the bottleneck on this.
To answer your actual Q: yes, i consider to port it but only when i am sure to have time to actually support it and fix bugs promptly, not leaving the user with unusable plugin for month
I would like to ask whether you would consider implementing Colorcoder also for Github's Atom?
The text was updated successfully, but these errors were encountered: