Bug 207544

Hi, 

in project's context menu Code Assistance you can turn it OFF, then ON when you think it's ready.

The best way I know is:
- specify correct build and clean commands (which work for you from command line) and do clean&build 
=> magic behind the scene will figure out full set of compiled files and passed compiler options for each file given the best configured code assistance (which is almost impossible to make manually for Mozilla-like code bases)

mentioned build&clean command could be specified either in wizard "From Existing Sources" or in project properties in Build category

Btw, make sure you have NB enough memory (i.e. -J-Xmx2G) and use 32-bit jdk (--jdkhome /path/to/jdk32bits) to reduce almost twice peak memory

Hi Vladimir. I'm the same guy that filed bug 197297, so I was aware of these things since you helpfully told me about them there. :) I just think that the status bar's context menu should allow the Parsing step to be cancelled just like it normally allows other things to be cancelled. That would be quicker, more consistent, and simpler to explain on the wiki document that I'm writing about setting up NetBeans for Mozilla.

By the way, it's not clear to me whether the code assistance needs to be enabled for the Build step for the smart analyzer to collect information during the build, or if it matters if code assistance is left disabled during the build and only turned on afterwards to retrigger a Parsing step. Do you know?

Hi jwatt,

Btw, as you know about Mozialla, may be you know why
make -f client.mk clean 
invocation does something strange even from command line - it starts to create new processes till computer goes out of resources.
Does "clean" work for you?

The reason I ask whether code assistance needs to be enabled for the Build step is because I turned it off in exactly the way you describe, and forgot to turn it back on again. So you can add to the list of reasons for fixing this bug that it would be less error prone to cancel the Parsing step from the status bar that to turn off code assistance and potentially forget to turn it back on again.

Regarding comment 3, I'm not sure offhand, but I'm certainly willing to help. Can you mail me offline to we can have a conversation without cluttering this bug?

(In reply to comment #2)
> Hi Vladimir. I'm the same guy that filed bug 197297, so I was aware of these
> things since you helpfully told me about them there. :) I just think that the
> status bar's context menu should allow the Parsing step to be cancelled just
> like it normally allows other things to be cancelled. That would be quicker,
> more consistent, and simpler to explain on the wiki document that I'm writing
> about setting up NetBeans for Mozilla.
If you can share link to document, it would be great and I can review/comment if you'd like :-)

(In reply to comment #4)
> The reason I ask whether code assistance needs to be enabled for the Build step
> is because I turned it off in exactly the way you describe, and forgot to turn
> it back on again. So you can add to the list of reasons for fixing this bug
> that it would be less error prone to cancel the Parsing step from the status
> bar that to turn off code assistance and potentially forget to turn it back on
> again.
I'm sorry, can you clarify, please. I don't understand how "cancel" from progress bar can help here.

I think system should do the following itself:
- during Build (when magic of extracting compiler flags is ON) suspend on parsing/reparsing activity
- when Build is finished and compile flags are adjusted in project => let parser make up-to-date check to see if options were changed and reparse affected files

(In reply to comment #7)
> I'm sorry, can you clarify, please. I don't understand how "cancel" from
> progress bar can help here.

If it was possible to cancel the "Parsing" activity from the status bar, then I wouldn't have needed to temporarily disable code assistance since I'd have just canceled the parsing. If I hadn't canceled code assistance, then I wouldn't have been in the position of forgetting to turn it back on. Therefore being able to cancel parsing from the status bar would be less error prone. :)

(In reply to comment #8)
> (In reply to comment #7)
> > I'm sorry, can you clarify, please. I don't understand how "cancel" from
> > progress bar can help here.
> 
> If it was possible to cancel the "Parsing" activity from the status bar, then I
> wouldn't have needed to temporarily disable code assistance since I'd have just
> canceled the parsing. If I hadn't canceled code assistance, then I wouldn't
> have been in the position of forgetting to turn it back on. Therefore being
> able to cancel parsing from the status bar would be less error prone. :)
Ok. I can clean parser queue on scan cancel, but it not "disable", right?
Parser starts to work when some events have happened in system (i.e. new file created/remove/modified under source root) and it will trigger parser again, because it's not in "off" state.
Is it OK?

As long as the Parsing item in the status bar is changed to allow me to cancel it using its context menu, then I'm happy.

This bug is targeted for 7.2 but still in the new state.  Is it going to be retargeted?

jbentonAdc, what is your reason to stop parsing activity?

http://hg.netbeans.org/cnd-main/rev/a4f1310f1079
disable code assistance for project on Cancel

Integrated into 'main-golden', will be available in build *201208231248* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main-golden/rev/a4f1310f1079
User: Vladimir Voskresensky <vv159170@netbeans.org>
Log: fixed #207544 - The Parsing step can't be cancelled: disable Code Assistance when cancel parser

by default it is not cancellable, start NB with -J-Dcnd.cancellable.parse=true

http://hg.netbeans.org/cnd-main/rev/650cad17524f