Everyone seen our new demos?
Hello everyone,
We've recently released two demos showing the new features of IntelliJ IDEA
5.1. The first of them demonstrates our i18n support:
http://www.jetbrains.com/idea/training/demos/i18n.html
The second one demonstrates using IntelliJ IDEA to develop an AJAX application
in five minutes:
http://www.jetbrains.com/idea/training/demos/AJAX_demo.html
If you have any feedback on these demos, feel free to post it in this thread.
Also, any suggestions on other areas of IDEA functionality that should be
covered by demos are very much welcome.
Happy watching. :)
--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com
"Develop with pleasure!"
Please sign in to leave a comment.
Nice..
However the example could have been better. I mean when you open a new tab to dynamically update, the entire point of the demo is lost.
You could have just shown perhaps the clock updation, may be per 10 secs without leaving the page.
Real world examples, may be like an auto suggest would have been better.
Ah well.. good to see some solid AJAX support in IDEA.
nice !
I'll really have no excuse for not internationalizing my applications any more
IMHO you should detail the Javascript functionality in another demo that is just javascript oriented.
1. What about some videos to make IntelliJ plug-ins? For Netbeans there are quite a few and they
animated many people to start making Netbeans plug-ins (or using the platform).
2. Since refactorings are the biggest advantage of IntelliJ, why not dedicate many but short
animations to each of the refactoring. This would be interesting for many of not so obvious one like
"rename" :). Let's say, one every week, and post it to Javalobby too :).
3. IMHO there's need for more webapplication demos. Since there are so many aspects of the webapp
dev, more demos ordered by functionality would be better than one big monolithic demo.
Ahmed.
Hello Ahmed,
Interesting ideas, thank you.
be interesting for
and post it to Javalobby too :).
There are some demos about refactoring (made for 3.0, but still valid).
They are here: http://www.jetbrains.com/idea/training/refactoring.html
Is that what you mean?
As for creating one demo once a week... Well, that's why we ask for feedback.
It takes time to create a demo (and it is much faster to write some tip).
Are demos indeed much better than let's say articles and tips&tricks?
Best regards,
Alexandra Rusina
-
JetBrains, Inc
http://www.intellij.com
"Develop with pleasure!"
>> 2. Since refactorings are the biggest advantage of IntelliJ, why not
>> dedicate many but short animations to each of the refactoring. This would
>> many of not so obvious one like "rename" :). Let's say, one every week,
Yes, I know them, but IntelliJ has much more refactorings. Why not to make this really visible?
IMHO both are good. The best solution is to use both: a video(short) and a short text with the
tip/trick. The video is the reason to go there and make people curious. Some short text with a "more
info" link will direct the interested people to details.
The idea with "once a week" was to keep the news head in javalobby and other sites with something
really useful. Eclipse people do the same, but with mostly useless news. Netbeans is presenting
interesting information however, hence the rapid growth of their user base.
Ahmed.
Hello Ahmed,
Yes, at Javalobby we actually do this now. As for "other sites" - again,
any ideas are welcome.
Best regards,
Alexandra Rusina
-
JetBrains, Inc
http://www.intellij.com
"Develop with pleasure!"
Yes, I saw this, but immediately as you post an article, several "spam" like Eclipse news show up
and shift the article from the list or to the end of the list. I observed this several times based
on the publication interval :). That's not very fair play from the other side :).
A blog dedicated to IntelliJ's "cool feature of the week".
Also these short articles/messages could be than reused for the "Tip of the Day".
However, one should update it (and all the other jetrains blogs), not like the Onboard magazine.
Just see here how often get interesting updates:
http://blogs.sun.com/roller/page/roumen
and here
http://blogs.sun.com/roller/page/geertjan
Except this one:
http://blogs.jetbrains.com/ait/
none of the other jetbrains blogs get frequent updates. IMHO this is a big problem. Maybe the
solution is to merge more blogs into one, so that at least it "get's updated" by combining the
messages from many.
Ahmed.
I was just trying the Ajax demo and I'm not getting the same results in my
js code completion as the demo. When I create the Ajax object and try to
code complete the PeriodicalUpdater I don't see it in the drop-down. See
attachment of my results (MyResult.jpg) compared to the screenshot of the
demo (Demo.jpg).
"Dmitry Jemerov (JetBrains)" <yole@jetbrains.com> wrote in message
news:83ca25fd2672468c809afecb63580@news.intellij.net...
>
>
>
>
>
>
Attachment(s):
Demo.jpg
MyResult.jpg
I should mention that after typing new and hitting ctrl+space, I see the
Ajax object in the drop-down, so apparently I have the js file included
correctly.
"Brad L" <no@no.no> wrote in message news:dtvldi$jrj$1@is.intellij.net...
>I was just trying the Ajax demo and I'm not getting the same results in my
>js code completion as the demo. When I create the Ajax object and try to
>code complete the PeriodicalUpdater I don't see it in the drop-down. See
>attachment of my results (MyResult.jpg) compared to the screenshot of the
>demo (Demo.jpg).
>
>
>> Hello everyone,
>>
>> We've recently released two demos showing the new features of IntelliJ
>> IDEA
>> 5.1. The first of them demonstrates our i18n support:
>> http://www.jetbrains.com/idea/training/demos/i18n.html
>>
>> The second one demonstrates using IntelliJ IDEA to develop an AJAX
>> application
>> in five minutes:
>> http://www.jetbrains.com/idea/training/demos/AJAX_demo.html
>>
>> If you have any feedback on these demos, feel free to post it in this
>> thread.
>> Also, any suggestions on other areas of IDEA functionality that should be
>> covered by demos are very much welcome.
>>
>> Happy watching. :)
>>
>> --
>> Dmitry Jemerov
>> Software Developer
>> JetBrains, Inc.
>> http://www.jetbrains.com
>> "Develop with pleasure!"
>>
>>
>
>
Hello Brad,
It's just a bug that quite rarely reproduces. I had it once while shooting
a demo. Just reopen the project or restart IDEA. In my case that helped.
Best regards,
Alexandra Rusina
-
JetBrains, Inc
http://www.intellij.com
"Develop with pleasure!"
Thibaut wrote on 28/02/06 00:47:
Other than not speaking other languages ;)
Is that bug going to be fixed? Is there a Jira issue filed?
"Alexandra Rusina (JetBrains)" <Alexandra.Rusina@jetbrains.com> wrote in
message news:c8a8a1b796b58c80a7902456c44@news.intellij.net...
>
>
>
Hi,
You may need manually invoke file sync.
If the problem is steadily reproduced then, please, file JIRA request.
Brad L wrote:
>>Hello Brad,
>>
>>It's just a bug that quite rarely reproduces. I had it once while shooting
>>a demo. Just reopen the project or restart IDEA. In my case that helped.
>>
>>Best regards,
>>Alexandra Rusina
>>----
>>JetBrains, Inc
>>http://www.intellij.com
>>"Develop with pleasure!"
>>
>>
--
Best regards,
Maxim Mossienko
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"
Hey,
Nice ajax demo...but there is one thing I really don't like / wish it could be improved upon.
Why doesn't the PeriodicalUpdater show up in FileStructure view? Can we get this to show up?
Thx,
Steve
Hi,
I don't think that demos are better than written tips and documentation, although your demos are nice. I prefer to have something, which I can handle "offline" that is printing it and reading it when I am not at the computer.
By the way, when is JetBrains willing to provide a documentation, which ready for printing - i.e. in PDF-Format? Since years I am asking for that. I you lokk at your help system it is not on par with that of other IDEs, notably MyEclipse IDE. The IntelliJ help is not formatted to be printed on A4 size, the help window does not provide a print button, and you do not provide user's guides in PDF format.
I would prefer, if you would spend your efforts on improving the documentation shipped with IDEA instead of producing isolated fancy demos for the web, which I may not be aware of and which I cannot access while I am offline (for example sitting in a train).
So although the demos are nice, I feel they are more targeted to new customers while you neglect the need of existing customers, who are working with the product. Please to us a favor and provide documentation ready to print, preferable in PDF format. Or you could make the Manning publication IDEA in Action a PDF eBook, which will be maintained as IDEA changes and ship it with IDEA for buying customers.
Kind regards
Thomas Gülden
Munich, Germany
Hello Thomas,
We do plan to improve the help and I hope a lot will be done for IntelliJ
IDEA 6.0 Release.
As for "written" tips you can check the new IntelliJ IDEA blog (http://blogs.jetbrains.com/idea/).
Yes, that's also not very "offline", but at least these tips are easier to
print than the original help.
We also publish some articles and how-to's at http://www.jetbrains.com/idea/documentation/documentation.html.
These articles can be printed without problems. Also, if you do need some
how-to, feel free to ask.
I can't say that demos are for new customers only. Some of the demos (like
i18n support) show you how to use new IntelliJ IDEA features or how you can
use IntelliJ IDEA for new technologies (like AJAX).
As for PDF... I can't even imagine how many pages the printed version will
contain. Our help now is really big. And it contains a lot of screenshots
and external links. Yes, we are working now on its restructuring, but I'm
really not sure that the printed version will be something you will read
in a train. Again, I hope the situation will change for 6.0 Release.
Best regards,
Alexandra Rusina
-
JetBrains, Inc
http://www.intellij.com
"Develop with pleasure!"
My best recommendation is to focus on application task project.
I realized that Intellij is very powerful but most of its power go under utilized because features is too many and overwhelming and most user do not bother to go beyond the basics.
In fact, only after purchasing the book "Intellij in action" that I realized how much I have "under utilized" Intellij. The book is important however, the best is to come out any series that is more task orientated on a project. The book should highlight the actual development in different platform
1. J2ME
2. Web application
3. J2SE => Swing desktop application
4. Integrating open-source to intellij
For example, a full-feature expense j2me covering full application using Intellij, and taking advantage of it ...
I believe this is the best approach. I often realized that the help file is not useful.
and Intellij in action make a better help file actually.
thank
Okay, to continue from last message, what I like to convey is that the company to focus on concentrating on the feature rather than tell what Intellij can do. Intellij can do many "interesting" stuff, what we needed is actually teaching us how to understand and use the "features" in a detail way. Most of the help file actually tell what it do but do little to demostrate how to use it .
For example, the condition in debugging feature say what it do , but neglect what to put in.
I guess this does not give justice to the amount of effort the Intellij developers put in developing the features. A features that is unknown and did not communicate well is as good as feature not there, but for marketing reason.
I do suggest that Jetbrain put more effort in focusing on the feature know how rather than keep innovating without properly conveying the value and usage of those features.
In this way, Intellij will continue to be the best IDE there is... Hope that this is priority for next version of Intellij....
From what I know from Manchester Business School, the material guide is structured
like from MBA course,
1. Understand the customer
2. Create the value
3. Communicate the value
4. Deliver the value
I guess Intellij is lacking in communicating the value.
thank
I don't think communicating the value should be bound to some particular version, and should be a replacement for creating new one.
hi Eugene,
that's true, it should not. but since the team are so focus on delivering the next version, it is better use that the new version to better communicate its value. The team may not fix it in current release, putting it into next release might re-enforce it. A better communcation and documentation of features might one of a winning point for next version,