With each new build...

Given the choice between this versus very frequent/responsive EAP builds, I'd opt for the regular builds.

Wish I could be as productive as you: Code samples, screen shots, 2 pages of text in 30 minutes - amazing ;)

But there's some truth in it - what good is a sophisticated open api if I cannot figure out how to use it?

At least of language API there's a plenty of samples. Whole JavascriptPlugin.
Documentation yet to follow.
-

Maxim Shafirov
http://www.jetbrains.com
"Develop with pleasure!"

IDEA brings new features, and openAPI changes, and all we get to learn
about them is a dry 3-6 line summary. I wouldn't hurt if, once per
build, JB would spend 30 minutes writing down a 1 or 2 page summary,
with some code sample, and a few screen copies.

Currently, we can only guess from the visible interface. For the
details, we'll have to wait 6 months - ? - for the official release,
and read the updated help file.

1/
For example, I'm not sure I'm using fully the new Move features.
2/ The openAPI:
---------------
I'm pleased to see that 3212 brings us :
. OpenApi. Custom language API
. OpenApi. Class Chooser API
. OpenApi. API for productivity hints registry
, but a few code samples wouldn't hurt either.

I think we deserve those 30 minutes, once a build.

Alain

Hi,

Code samples for new Open API are available in JavaScriptLanguage plugin

Stephen Kelvin wrote:

Wish I could be as productive as you: Code samples, screen shots, 2 pages of text in 30 minutes - amazing ;)

But there's some truth in it - what good is a sophisticated open api if I cannot figure out how to use it?

--
Maxim Mossienko
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Stephen

>Wish I could be as productive as you: Code samples, screen shots, 2 pages of text in 30 minutes - amazing ;)
>

>

30 minutes is enough to take a few screencopies, before and after the
actions, crop them to isolate the useful areas, copy and paste them
into a document and add a few words.


For the openAPI, it's true, it wouldn't be that easy, but compared to
what we have now - NOTHING -, anything, even 10 lines of pseudo-code per
entry, would be an incredible improvment.


Alain

Maxim,

At least of language API there's a plenty of samples. Whole
JavascriptPlugin. Documentation yet to follow.

Of course, we can reverse engineer the existing plugin - we've been
doing that for years: a shame -,
but you can save us hours of trial an errors by just
- giving us a few code snippets,
- telling us about what's important to know
- showing US the right way to use the system YOU designed.

I'm sure 1 or 2 page, per build, would have people send you flowers, for
the saved nights of sleep, and pulled hairs.


Alain

Hi,

What's important to know (v 0.1 for 3112)

If you have downloaded the sources
(http://www.intellij.net/eap/products/idea/redirect.jsp?filename=idea3212-dev.zip)
then start from JavascriptLanguage class, overall language facilities
support is straightforward.

Alain Ravet wrote:

Maxim,

>> At least of language API there's a plenty of samples. Whole
>> JavascriptPlugin. Documentation yet to follow.

Of course, we can reverse engineer the existing plugin - we've been
doing that for years: a shame -,
but you can save us hours of trial an errors by just
- giving us a few code snippets,
- telling us about what's important to know
- showing US the right way to use the system YOU designed.

I'm sure 1 or 2 page, per build, would have people send you flowers, for
the saved nights of sleep, and pulled hairs.


Alain

--
Maxim Mossienko
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Alain Ravet wrote:

Currently, we can only guess from the visible interface. For the
details, we'll have to wait 6 months - ? - for the official release, and
read the updated help file.

Goitta make those freebee plugin-author IDEA users work for their
licence don't we :)