|
|
|
Thanks for the answer, unfortunately it's on my work computer, so I'll only post it on monday
thanks I can see in my log when I open Aptana several of these errors:
!ENTRY org.rubypeople.rdt.core 1 0 2008-12-08 10:42:57.049 And strangely, now code assist works on models and helpers. I'm attaching the entire log I removed the log, then I started Aptana and tried to use code assist on a rhtml file. Aptana froze and I killed it with 'kill -KILL $process_id'
Ok, I corrected these "resolve path" errors by manually editing the file ".loadpath" on my project directory (for some reason that Project->Properties->Ruby Load Path really don't work)
Now autocomplete works well (kind of) on controllers, helpers and models, but it keeps hanging on .rhtml files Have newer versions of RadRails, specifically 1.1.0+ fixed the issue? I know that I had a huge performance fix in 1.1.0 for RHTML code completion...
I updated to this new versions and the problem continues.
What's your system? Do you think is there any way to fix my problem changing my setup? Well to be honest, I have no idea what would be causing this. There's no errors in your logs that's related so I don't really have anything to go by. The only way something would hang is if it's blocking forever on something, or its looping infinitely. Typically in the second case it'd be recursive and eventually throw a stack overflow or out of memory error.
I can try to add some logging in the ERB/RHTML content assist to at least give details on what's happening - how far it gets before it hangs. But I'd have to work something out so there's some hard to find pref to turn this on or off, as everyone else won't want that stuff filling up their logs. In this case you could send me an updated .jar with these logging, so this wouldn't mess up with everybody's setup
Well it isn't easy for me to build a custom JAR for you that would just work. I'm adding in a pref setting on the ERB/RHTML editor pref page that turns this debug level logging on and off for content assist. When radRails 1.1.2 is released, please change this pref checkbox and then try ERB/RHTML code assist. Your log (http://www.aptana.com/docs/index.php/Accessing_your_Aptana_log
I'm going to mark the target fix version for 1.2.0 since I can't get your feedback until 1.1.2 is released.
I'm also going to mark this as "request user response" pending your feedback on the 1.1.2 release, so please respond when you have this extra logging data I'm attaching the new log file with that extra option enabled, thanks
By the way, as the log says the content assist is freezing while "trying completions for methods in helper", I deleted all my helper methods on application_helper.rb and the helper of the view I was editing, but the problem continues.
Oh, I forgot to mention, I let it running for 6minutes before killing java. At night I will try again and let the thing running while I'm at home OK, well this definitely narrows our scope a lot here.
The code here is trying to grab the plural model name and then check the helpers/<model_name>_helper.rb file and search for all method declarations. I see a few spots where it could fall on its face, but it'd be best to get more info to narrow it down more. It'd be helpful to know a few things about the layout of your project (it may be easiest to expand out the project and take a screenshot): Is the project root also the RAILS_ROOT (i.e. the "apps" folder is a direct child of the project)? What is the project relative path of the ERB/RHTML file you're invoking code assist from? Is there an equivalent helper file for that controller? I'm attaching a screenshot with my project tree. See that the only exceptional thing here is that we separate system modules in namespaces. An example:
Resource: Projects Model: app/models/extra/project.rb -> Extra::Project Hope it helps, thanks I wasn't able to reproduce this on trunk using the same layout, so I'm a little concerned. I made some fixes to the ERB/RHTML code assist that might help fix this issue. I'm going to tentatively mark this as Fixed for 1.2.0, but obviously if it's not please re-open.
Only tie things resolved in 1.1.2 and 1.2.0 to 1.1.2 as fixed version (since it's assumed that 1.2.0 as a later release will contain all the previous release's bugfixes).
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Does it crash, or just freeze up entirely?