I am new to codenameone and I am thinking about moving a large project from our current environment to it. So, I wanted to run a few tests but I already failed by setting up a project, since I do not find the place where to set it up :)
So I used Google and found a Video "HOW DO I - CREATE A BASIC HELLO WORLD APPLICATION & SEND IT TO MY DEVICE USING INTELLIJ/IDEA" and thought "Yeah, exactly what I need!". But when you start the video, one of the first sentences is "We are going to use Eclipse....", so I guess someone has published the wrong video.
Nevertheless, can someone tell me, where I can make the proper project settings (like in the mentioned video on 07:50) in IDEA ?
Type CTRL + ALT + SHIFT + S to open the Project Settings dialog box.
You can read more about it here.
I guess your answer fits for Windows Systems.
Nevertheless, on OSX you have to go to the preferences and there to "Other Settings" and there you can do all adjustments.
Personally, I hoped that they included the possibility to create multiple apps from one project (like e.g. Adobe AIR) :(
Related
Every time I open a new project in IntelliJ IDEA, the first time I open a particular tool window, for example 'Maven Projects', it appears in 'pinned' mode and remains visible until either I close it, or I go to the view settings for the window (the little cog) and deselect "Pinned Mode". I don't want any of my tool windows to be pinned so this gets a little annoying.
Do you know of a way to change the default behaviour of new project / tool windows?
As far as IJ 2016.2 I don't know about a dedicated setting for this. However I used an approach which allows you to define a default layout for all projects. Although the window-pinning works, which is what this question is about, some may not be persisted, such as Group Modules setting in the maven tool-window.
Nonetheless, to configure the pinning, you need to do 2 simple things, which you can also see in the GIF below:
1) Manually go and unpin all desired windows
2) Open the Windows menu and select Store current layout as default
P.S. If you'll be using tool-windows that you've never opened before, or install new plugins which add their own tool-windows, just follow these steps again.
I have 2 simple questions that I cannot find answer to.
First is in NetBeans when I type . operator behind a variable or method or whatever, small window with documentation will show up like on the picture. On the other hand I can't achieve the same result in IntelliJ. I followed steps on official website and this is what I get in IntelliJ after I press CTRL+Q. All I want is full documentation so for a begginer like me it would be easier to use and learn stuff.
[EDIT]: I tried it once again and I saw little yellow message "download missing driver" and it is working just fine.. this one is solved.
Second question is about MySQL database driver (or connector). In NetBeans, I just press right click on project and add the library I want. But I can't find solution for this in IntelliJ.
Thanks for every advice!
For the first question, I'm thinking what you mean is the suggestions after you type a '.'. In IntelliJ, the suggestions show only if you have config a right dependency in the File > Project Structure, and the Libraries tab.
And for the second question, also you should find File > Project Structure, in the Modules tab, Add new Database support(Hibernate such as) for you project.
Hope it helps you.
Ok, so I finally found the solution.
I went to Project Structure -> SDKs -> Documentation Paths and I added https://docs.oracle.com/javase/8/docs/api/ in there so now when I press CTRL+Q for quick documentation it shows exactly what I needed.
I have a real problem with making Play2.0 work with IntelliJ EAP version (120.152).
I create an empty project without module in IntelliJ
I create a new application using the play command, and using play idea at the end
I then add this module from IntelliJ, using "Import from existing module"
Now, I have two folders too chose from when importing the module.
1. .idea
2. .idea_modules
After seeing some different ways on the internet,
I chose .idea_modules -> moduleName.iml
(I have tried all the others just to check)
Here is what bothers me the most
Anyone had anything similar? I am not sure why this is, every other screenshot I have seen from this, have a path behind the red text (making it work!), which I do not.
Any suggestions what I can do from here to hopefully make this work?
My Scala facet looks like this in the IDE, but I have not seen any Play documentation that goes into modifying the facet, so I just leaved it as is
In IntelliJ 12 - the same as in IntelliJ 11 you can open the Play's project since version 2.0.2, just by using option 'Open project' in the start window view.
You don't need to create blank project first in IDE.
play new test-leda + all required steps by play console
cd test-leda
play idea + wait for bash prompt which indicates finalization
Open Leda and choose Open project
Find the folder test-leda and just click Choose
That's all
I have a noob Perforce question. I got my perforce plug-in on Eclipse working(for both Java and C).
I have no problems "opening" my perforce stored projects on Eclipse.
Scenario 1:
Whenever I want to change code, I open the project on Eclipse and right-click on it and go to "team" and check out, make changes and then submit. Works fine. But even after that I see a tick mark(indicating check-out) on my perforce screen.
Scenario 2:
I just open perforce code as Eclipse project and make changes(If read only, it prompts and asks if i have to allow write and I say yes). I make changes and save. It doesnt ask for submit. Also if I now open the code on Perforce screen, I already see the new changes made.
Scenario 3:
Just on a Perforce screen, if I check a file out and don't make any changes, I obviously dont want to submit as there are no changes. In this case, how can i "disable" check-out so that my fellow programmers dont think i'm working on it??
Scenario3:
So here are 2 ways i consider a good usage of the plugin:
Use Revert Unchanged Files:
Before you begin development of a feature, checkout the entire tree/branch that your changes will be concentrated around in future. You can do this by right-click the relevant package in package explorer. Once you want to submit, Project->Right-click->Team->Revert Unchanged Files. Now, you can submit your changelist.
This approach stands very useful if you know you will be editing a lot of files or replacing files.
Ofcourse, others can see that you have checked out the files.
Enable Auto checkout:
Incase you are going to make few changes, you should enable autocheckout. This will checkout the file when you begin to make edits. Eclipse->Preferences->Team->Perforce->Enable support for workbench edit..
detailed explainations here. Its a good idea to have this enabled always as it checks out on demand.
However, this does not monitor the filesystem so and code/libs you replace outside of eclipse are not checked out.
For Scenario 3, you can change a workspace option to prevent submitting unchanged files:
SubmitOptions: reverttunchanged
If you have a file checked out (open for edit), others will be able to see that. I guess I'm not clear on why you check a file out if you don't intend to modify it?
If you are going to setup this way and are also using the desktop client, I recommend the following steps in the desktop client:
1.) Open your desktop Perforce client
2.) Click “Connection” on the global menu
3.) Select “Edit Current Workspace…”
4.) Under the “Advanced” tab select “allwrite”
5.) Click Apply, then OK
How to do so?
What URL is the documentation of version editor?
If I click version editor toolbutton I just see an empty screen to the right
The quasi-answer (workaround) to your question (I think) is that.. there IS NO such thing as a "turn on" for this feature. If it isn't showing up right - which I've seen many times - means Xcode is having a debatably-temporary mental lapse. Chances are - it (Xcode) is about to crash… but if you just want to be done with it / seal the deal / put the horse out of it's misery, etc..
quit Xcode.
reopen Xcode.
and you should be able to browse your versions, á la Time Machine, as usual.
EDIT Ripley's believe it or not ® I think I'm wrong!
More likely is that your git "arrangement" has become "f-ed up", somehow-or-other.
For me no amount of committing in the GitHub client for Mac would remedy the situation (for some files)… However, thanks to this hint, i guess forcing Xcode to "take a good, long look at itself in the mirror" via the "actual" Xcode File -> Source control => commit command does seem to bring back the version-editing functionality of problematic source files.