• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Tip on Troubleshooting Code Sense
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Tip on Troubleshooting Code Sense


  • Subject: Re: Tip on Troubleshooting Code Sense
  • From: Rob Lockstone <email@hidden>
  • Date: Wed, 18 Aug 2004 16:06:03 -0700

Fwiw, I've found Code Sense for Java in Xcode 1.5 to be extremely fragile. I'm not talking about WO-related Code Sense. Just Code Sense (for Java) in general. It works great with small'ish projects. But as soon as you cross some threshold measured either in the number of files or the number of bytes, it breaks for me, reverting back to vanilla 1.2-style Code Sense (or maybe it's related to something else about the files I add to my project, which are not weird in any way as far as I know). What's odd is that it will (often) continue to work for some of the files in the project (the ones added earlier on), but doesn't work in the newer files.

Anyway, I spent many, many hours fiddling around with it and could never get it to work correctly/consistently with projects containing more than several dozen (a few hundred?) files. "Correctly" being defined as displaying real method names and arguments, not just lists of words in the index. That is NOT Code Sense, that's "displaying lists of words from the index". I gave up and filed a bug. I hope there's a 1.5.1 release that addresses the issue because when it works, it's really nice. Oh well.

Rob

On Aug 18, 2004, at 12:43 PM, Kieran Kelleher wrote:

This is for people who are still trying to get code sense working.

I had one dev machine that worked fine on code sense and the other was
stubborn, so here is a tip for those who still do not have code sense
working:

The bottom line is that a USER default must be set and a pre-cooked
index must exist in the correct USER directory for each collection of
jars that you want in code sense.

Using the standard index templates scripts and even using xcodeindex
-destPath from the command line just would not create the index in the
home folder of the stubborn dev machine.

The fix was to simply open the Index Template project for WebObjects,
allow it to index (watch Activity Viewer window until complete) and
then to copy the built index to the appropriate dir in the user's
Library folder.

WITHOUT the fully built index in the right place, code sense simply
will not work because the symbols are not present for it to populate
the code sense prompt list.

See the headings (article even has screen shots!)
	Prepare Java Classes for Code Sense and
	Turn On CodeSense
in this blog entry for more details:
http://homepage.mac.com/kelleherk/iblog/C1216817469/E517633567/
index.html

By the way, you will notice that aswell as the documented methods, many
methods beginning in "_" (underscore) show up in the code sense prompt
list. I guess these are the "undocumented" methods that I recall Chuck
Hill or somebody mentioning last year!

Regards, Kieran


________________________________________________________________
Dev Config = OS X 10.3.4 / Java 1.4.2_03 / WO 5.2.3 / XCode v1.5 /
MySQL 4.0.20 / Connector-J 3.0.11
Deploy Config = OS X 10.3.4 Server / Java 1.4.2_03 / WO 5.2.3 / MySQL
4.0.20 / Connector-J 3.0.11
My Blog: http://webobjects.webhop.org/
Meet other WO Developers at http://webobjects.meetup.com
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.


  • Follow-Ups:
    • Re: Tip on Troubleshooting Code Sense
      • From: Kieran Kelleher <email@hidden>
References: 
 >Tip on Troubleshooting Code Sense (From: Kieran Kelleher <email@hidden>)

  • Prev by Date: Re: Javamonitor =- no images
  • Next by Date: WOXMLCoder / NSXMLOutputStream
  • Previous by thread: Tip on Troubleshooting Code Sense
  • Next by thread: Re: Tip on Troubleshooting Code Sense
  • Index(es):
    • Date
    • Thread