more stable API

[GoogleCodeExporter]

This is more of a feature request, so feel free to modify this issue to match 
that.

I am a Vim plugin author and utterly excited about Conque and it's 
capabilities. I have started to 
use the API to use Conque whenever it is available for a user.

And this works perfectly.

But I am feeling nervous in releasing a newer plugin version of my own that 
supports Conque if the API 
is listed as BETA.

What does this mean? Will it change constantly? 

When can we see an API that is a bit more stable? or stable enough to be used 
by other plugins?

Original issue reported on code.google.com by alfredodeza on 5 May 2011 at 3:08

[GoogleCodeExporter]

This is kind of a chicken and egg problem. I still have the API labelled as 
beta because I don't think it's been used enough to know if the functionality 
makes sense, or if it has any bugs. I don't personally use it for anything.

I'll take a look at it again soon to see if anything needs to be changed. But 
at the moment I have no reason to think the currently defined functions will 
change before I lock the prototypes.

If you have any suggestions for simple ways to improve it, let me know. I'd be 
curious to see some code where it's being used.

Thanks.

Original comment by nicora...@gmail.com on 5 May 2011 at 9:13

[GoogleCodeExporter]

Thanks for the reply. I have just started adding support for it in a plugin 
that lets you use
py.test with Vim.

The need for Conque is to be able to run pdb with a nicer interface, other than 
the dumb terminal from
Vim.

It is just a couple of lines to make sure Conque is there, otherwise it falls 
back to regular dumb terminal.

So far, I feel pretty good about it.

See: 
https://github.com/alfredodeza/pytest.vim/blob/master/plugin/pytest.vim#L599-L60
6

Original comment by alfredodeza on 5 May 2011 at 9:17

[GoogleCodeExporter]

Took the api out of beta in 2.3.

Original comment by nicora...@gmail.com on 3 Sep 2011 at 7:16

• Changed state: Fixed