How do I enable auto-complete/code completion feature of IntelliJ IDEA to work with ExtJS javascript library?
Thanks
This could probably be closed as a dup of this question:
Add ExtJS code assist to IntellijIDEA
The answer is here:
http://blogs.jetbrains.com/webide/2010/11/working-with-javascript-libraries-in-phpstorm-webstorm/
do you have the extjs javascript files in your project? I find that when I do Intellij is somewhat good at getting methods, but it doesn't always get all the available methods. I thinks its just a gotcha of dynamic languages -- an IDE can't know all the methods available because some are available only at runtime...
Related
I am reading Selenium documentation (eg http://www.seleniumhq.org/docs/04_webdriver_advanced.jsp) and notice that some examples are not available in JavaScript. Is it due to incomplete documentation or is certain functionality not implemented in JavaScript binding? Shall I learn Selenium using Java binding or would any binding be OK?
I think they do support same functionality. I remember that I was trying to figure out what to do from vs options on our mvc project. Just a great product with bad documentation :)
You can find the Selenium JavaScript documentation in below link:-
https://seleniumhq.github.io/selenium/docs/api/javascript/index.html
The above link contains all modules cover.
Additionally, they have put up all details regarding changes they have done version to version.
I am using grails2.3.7 and hibernate4.
However, the default database-migration plugin is not working with hibernate4.
Is there any other plugin that can do the same thing but support hibernate4?
Thanks.
Depending on what functionality you can do without, you may be able to use straight Liquibase in your project. It is fairly simple to setup. You could use the manual or a presentation I gave to get yourself started.
You can always look at the source of the database-migration plugin to give you clues about how to set it up if you get stuck.
The plugin is updated to support hibernate4 now.
database-migration
I am having trouble with ABCalendarPicker. Can someone please explain why the below screenshot is coming out this way? I have added the bundle and the .a library as build resources. I have also built the ABCalendarPicker project prior to running.
ABCalendarPicker component does not support Autolayout. Just disable Autolayout or help to improve component...
Does anybody know of an ExtJS editor (like HTMLEditor) with syntax highlighting or does someone has some experience integrating Bespin or other Scripts into it?
There is no specific editor for ExtJS code highlighting, however, you can use CodeMirror for Javascript code highlighting. Even I integrated it with my ExtJS application to write Javascript as well as ExtJS codes and it is working perfectly.
If you want to get this feature for highlighting codes in IDE then you can use Spket Update : "http://www.spket.com/update/" in Eclipse (Help->Software Updates->Find and Install->Search for new feeatures) for ExtJS code highlighting.
you could use ace-extjs
In the ExtJs Forum someone published a syntax file for vim, which I use daily.
There is also this (older) blog post : IDEs, Plugins and tool for ExtJs.
Finally, you have a lot of forums thread abouts IDE.
PHP Storm and Webstorm are great
Can anyone please tell me how I can "enable" CakePHP's Helper auto-completion in CakePHP? Essentially so when, for instance, I type $form-> it gives me a list of $form's methods and variables.
I have read http://bakery.cakephp.org/articles/view/model-based-code-insight-and-completion-in-netbeans and also tried to implement comment #3. When I try that it still fails to auto complete in either a Controller or View.
Do any Netbeans & CakePHP users out there have any tips, tricks, or hacks that can get this working? Thanks!
You can enable almost full support for CakePHP in NetBeans 6.8 just try this http://www.tiplite.com/cakephp-support-in-netbeans/
In Netbeans 6.8 there is a confirmed bug that makes the "comment #3"-method not working.
http://netbeans.org/bugzilla/show_bug.cgi?id=180239
It seems to be resolved in version 6.9. Haven't confirmed it myself, though.