Hi all, I'm using Evil last couple of months quite actively and is got very stable (congrats to developers!). Is there any plans for official 1.0 release soon? At least with this, we will have option to choose between bleeding edge and something we can always return to if something breaks with the latest code. Also it can be useful for cases (like mine) where we have installed Evil on several computers and from time to time versions got out of sync. Not to say about increased interest for Evil after some official news got spread :) Regards, Sanel
On Thu, May 31, 2012 at 05:11:37PM +0200, Sanel Zukan wrote:
Hi all,
I'm using Evil last couple of months quite actively and is got very stable (congrats to developers!). Is there any plans for official 1.0 release soon?
In principle it's probably time for a 1.0 release. There are still a few bugs I want to fix but this should not be a big problem (I hope). The main missing issue is the documentation which is still quite sparse. I've planned to improve the documentation for some time now, but ... well, as always never found the time to do it. And I would really like to have a more or less complete documentation especially of the API (how to define own commands, operators, motions, text-objects, key-bindings, interactive codes, ex-completion, ..., which helper functions can be used). I think this is important to nail down what the interface for 1.0 should look like. Users should then be able to rely on that interface for their own extensions or customizations. So the doc would be for both, the users and the developers to know which functions/variables must not be changed. But writing a good documentation is quite time intensive, at least in the beginning ... Frank
On Thu, May 31, 2012 at 5:54 PM, Frank Fischer <[email protected]> wrote: (...)
But writing a good documentation is quite time intensive, at least in the beginning ... (...)
Why don't you write an outline and send it to the list? I'm pretty sure some Evil users would gladly lend you a hand with at least some parts of the documentation. I would -- I haven't tried to hack evil yet, but I can read the code. Cheers, -- José A. Romero L. [email protected] "We who cut mere stones must always be envisioning cathedrals." (Quarry worker's creed)
On Thu, May 31, 2012 at 09:09:30PM +0200, José A. Romero L. wrote:
On Thu, May 31, 2012 at 5:54 PM, Frank Fischer <[email protected]> wrote: (...)
But writing a good documentation is quite time intensive, at least in the beginning ... (...)
Why don't you write an outline and send it to the list? I'm pretty sure some Evil users would gladly lend you a hand with at least some parts of the documentation. I would -- I haven't tried to hack evil yet, but I can read the code.
That's good suggestion. There's already some basic documentation in texinfo format in the doc branch. I'll see if I can add the outline of missing parts that I think should go in the doc in the next days. Bye, Frank
+1 ...besides, if something gets undocumented in 1.0, IMHO there is always next version to do that ;) Regards, Sanel On Fri, Jun 1, 2012 at 8:25 AM, Frank Fischer <[email protected]> wrote:
On Thu, May 31, 2012 at 09:09:30PM +0200, José A. Romero L. wrote:
On Thu, May 31, 2012 at 5:54 PM, Frank Fischer <[email protected]> wrote: (...)
But writing a good documentation is quite time intensive, at least in the beginning ... (...)
Why don't you write an outline and send it to the list? I'm pretty sure some Evil users would gladly lend you a hand with at least some parts of the documentation. I would -- I haven't tried to hack evil yet, but I can read the code.
That's good suggestion. There's already some basic documentation in texinfo format in the doc branch. I'll see if I can add the outline of missing parts that I think should go in the doc in the next days.
Bye, Frank
_______________________________________________ implementations-list mailing list [email protected] https://lists.ourproject.org/cgi-bin/mailman/listinfo/implementations-list
participants (3)
-
Frank Fischer -
José A. Romero L. -
Sanel Zukan