Hi -

I'm new to fantom.

I'm able to do command line builds and executes of simple fantom files (using fantom-1.0.52) on both Windows 7 and Ubuntu 10.04 beta1.

Unfortunately, I can't get it to work on netbeans, and can only get it to work on eclipse if I edit the auto generated build.fan (which is no big deal). The bigger problem is with netbeans which can't seem to find fan stuff. I've defined FAN_HOME.

1. When I use the standalone fantom Netbeans IDE, it generates the following main.fan which fails to compile because it says "Unresolved type: Void"

class Main {

**
** Main method
**
static Void main()
{
    // TODO
}

}

In addition, it generates the following build.fan which fails to compile basically because of "unresolved pod: build". It also says: "unresolved type:Void"

using build

class Build : BuildPod {

override Void setup()
{
  podName     = "netbeanstest"
}

}

1. When I use the Eclipse plugin, it generates the following build.fan, which fails to compile because it claims there is no setup() that can be overridden: > using build class Build : build::BuildPod { override Void setup() {

   podName = "eclipsetest"

   } }"

If I change it to:

class Build : build::BuildPod {

new make()
{
  podName = "eclipsetest"
  summary = "eclipsetest pod"
  srcDirs = [`fan/`]
}

}

It compiles, debugs, and executes fine.

Any suggestions would be appreciated. Thanks.

My netbeans IDE is quite a bit behind (fantom 1.0.48) which was before the pod.fan changes.

I've been working on a major rewrite for a while now.

I'm going to try and release a new version in next few days.

Thanks for the quick reply...

On further testing, even on 1.0.52, it actually does compile and debug after you edit the build.fan.

It's just that it flags the source lines with errors.

Also, when it does hit a breakpoint, it says:

"Variable information not available, source compiled without -g option

Debug should work thought it's a bit buggy (I fixed it since, yet to be released)

You should get the debug variables for YOUR fantom code, however if you are debugging/stepping in the fantom source code itself, it is compiled and distributed without the local variables. (You could recompile your own with debugging enabled)

Nope - I'm just debugging my code.

On further examination, instance variables are displayed along with their values, but not local variables

I'll wait for the update...

Just wanted to update on the NebeansIDE situation.

I've been working on a major rewrite, now using a new parser (parboiled instead of ant). I've also completely reworked the code so it now resolve the type of every element in a source file, which will allow for real completion (previously was a bit of a hack and only allow a few Elements to complete correctly).

This type resolution task is kind of a beast but it's almost complete and will allow for many other features as well (semantic analysis, tips/hints, automatic imports, thing like that).

Also Bryan Headley has joined me as commiter to the project a couple weeks ago and has already done a lot off good work, such as lots of new file/project wizzards, runtime options window, improved function/closure completion and so on.

Anyhow I'm unit testing and fixing the last few odd parsing issues that are left, and waiting for a new version of the parsing library to be released, because the current one as a serious performance issue (fixed already but not released yet).

I expect to post a first beta this week, possibly around mid-week.

waiting with bated breath (what the hell is bated breath?)...

There where 3 things left:

• Me resolving a few parsing issues .. I'm down to a couple minor ones, should be done tonight.
• Bryan Headley fixing some issues with the "new project" wizards (he just commited that.)
• Was waiting on the parboiled library to be fixed (major performance bug)

They just release the a new parboiled library a couple hours ago and it fixed the performance issue ... however there is a new issue .... so I might have to compile my own with only the changes I need and not the other changes.

So I'm gonna say a first release will probably be tomorrow.

OK, i just posted a 1.6.0 alpha 1

A few important notes:

• If you had a previous version, please delete completely the old preference/cache folder , because of major changes in the indexing/database formats.

Ex: For the standalone version: rm -rf /home/you/.fantomide/

For the plugin, something like: rm -rf /home/you/.netbeans/6.8/var/cache/fantom/

It is such as major rewrite (new parser and new type resolution) it's likely there are bugs, please do report them, in particular provide the stack trace if you get one.

Also You might get some case where the IDE tell you code is invalid when it actually is, in this case please let me know as well and provide the code sample.

tcolar-fantomide AT colar DOT net

Note: after installing edit etc/fantomide.conf and adjust the memory, the default of 64MB is way too low, will try to fix that for next release.

default_options="--branding fantomide -J-Xms24m -J-Xmx512m"

Note: For local variable debugging to work you need to enable

debug=true in fantomHome/etc/sys/config.props

I am having a hell of a time responding to you because I keep getting fandoc errors. Isn't there some way to turn the friggin fandoc parser off?

All I can say is under Windows 7, and with all the changes to config files you've specified, I can't build or debug. I can build once (successfully), then it won't build (no errors - just does nothing). If I try to debug it does nothing. The actual editor and parser seem to work fine.

The default_usedir line doesn't work under Windows. It causes the ide to hang

this good hu ?

Not sure what the fandoc thing is about, the only time i do anyhtingwith fandoc is on completion request, can you send me a screenshot of the error.

not sure what your refer to with default_usedir

please send me the log file called jot.log

it should be in your user dir/fantom/log

Thanks

i don't have windows on hand, so might be windows only.

I'll try this on Ubuntu tomorrow and let you know. Got to go to bed now. Will also send you the log file tomorrow.

@lel4866

What the hell is bated breath?

From dictionary.com:

bate

"to reduce, to lessen in intensity," c.1300, aphetic of abate (q.v.). Now only in phrase bated breath, which was used by Shakespeare in "The Merchant of Venice" (1596).

</end of diversion>

Back to fantom...

OK, i installed and tested in a win2K image in virtualbox. I think i fixed that fandoc thingy (pathing issue)

I can see build/debug doesn't work seem to not like the parameters i'm passing to java executable, will have to find why tomorrow.

Also seems like logging does not happen which sucks, might be because i was using a folder starting with a "."

Will try to fix those tomorrow.

Under OXS/Linux you should not have those issues.

The fandoc thing was not your problem. It's a problem with this fantom website discussion software. Sometimes when I try to enter anything code-like into a reply, and click Submit, it returns with a "Fandoc error" that I can't get rid of, and therefore can't reply properly to you. As I write this (and hope that this response doesn't get the error - it does have parens and quotes in it), I'm thinking maybe it's a firefox under Wndows thing.

That's what I meant when I said I wanted to turn off the fandoc parser

If you ever have some problem formatting your text on the website, just indent it 2 spaces it will all appear as a code section.

Although it should not be an error that prevents you from posting - that is a bug.

I tried to run the alpha 2 version, but after adding my first project my cpu keeps doing 100% and response becomes very slow. I do not know whether i did correctly deleted the old H database of the previous version.

I was in the woods all weekend, so sorry for the late response.

Couple things:

@lel4866 did you get a chance to try on ubuntu, did that work well ?

@jessevdam It is normal to do that once(first start) for about 15mn, or does it saty at 100% at all a times ? is that on windows ?

To "reset" everything(delete the db), you can remove:

• linux: /home/[user]/.fantomide/
• OSX: /Users/[user]/.fantomide/
• Windows: C:\Documents and Settings\[youruser]\Application Data\.fantomide\

Also if you get errors or it does not work, send me the log (in the same folder under dev/fantom/log/jot.log)

for example: C:\Documents and Settings\[youruser]\Application Data\.fantomide\dev\fantom\log\jot.log

Alright, just released FantomIDE 1.6.0 beta 1

http://fanide.colar.net/home

Changes (fixes):

• Many Windows fixes: Spent some painful time with windows in VirtualBox and found out there was lots of problems and fixed them (mostly paths issues, dealing with backslashes and spaces in paths)
• Debugger Fixes: Also fixed a lot of issues with the debugger (in particular under windows) and improved a few features.
• Build/Run/Debug actions: Those where a bit finicky (project node had to be selected for it to work right), it's now smarter at finding the right project.
• Bug fixes: Various bug fixes.

Hopefully it runs well under windows now and the debugger is more useful.

Let me know how it goes.

OK! Great work! I really appreciate it.

Now it works on Windows 7 on an initial test project. Can build, debug, break, single step, look at variables.

However, the stand alone ide (didn't try the plugin) hangs when you try to start it in Windows 7 until you change the 2nd line of fantomide.conf from:

default_userdir="${HOME}/.${APPNAME}/dev"

to:

default_userdir="C:\Users\larry\devdir"

Secondly, when I stepped into the closing brace of static void Main(), it went to line 536 of method.java. Not really a killer, but strange.

Thirdly, when I reloaded a completely trivial project, I get and exclamation point which says when you hover over it: "Unresolved Type: Void" on the first line of static Void Main(), even though it builds and debugs just fine

Thanks for the feedback.

FYI: I'm back at working on one of my fantom code project, so I'm using the IDE and fixing issues as I find them (fixed a bunch of NPE/errors today)

The default userdir thing sounds odd, that file is generated by Netbeans and its suppose to replace the path during installation with the correct thing(ie: windows path)). It seem to work fine on XP so I'm guess it's an issue with Netbeans & windows 7, will see if they have a bug report.

For the debugger stepping, I'll check but it could be "normal" behavior for the java VM to call Fantom's main that way (through method.java)

For the unresolved type .... i still have a few issues like that (fixed a couple today), so keep reporting them (with actual variable type/definition if possible) and I'll fix what's left.

Thanks.

FYI, I've moved FantomIDE to bitbucket so you can track releases there: Currently 1.6.0 beta 2

http://bitbucket.org/tcolar/fantomide/downloads

I tried the beta 2, but on my project it seems to failing on the parsing of docs. It keeps using 100% power and eventually their is no more response.

I created a new project and that works fine. It would be fine when there would be an option for the autocompletion, so I do not have to prese crtl+space all the time.

Could you send me the project that causes the issue ... I've had that happen to me a few time but not reproducible enough to debug (seem to be an issue in the parser library recursing forever and causing an OOM)

If you cant send the project, can you let it run/crash and then send me the log file

Linux/OSX: user home/.fantomide/dev/fantom/log/jot.log

Windows: C:\Documents and Settings\youruser\Application Data\.fantomide\dev\fantom\log\jot.log

Thanks.

Beta 2 looks really good.

The problem with user_default in fantomide.conf appears fixed, as well as the Unresolved Type problems.

One more minor thing - when I say "New Project", it always defaults to the fantomide directory. I thought this was what user_default was for, but it doesn't seem to use that.

Released 1.6.1. Se chnagelog for more infos:

http://fantomide.colar.net/changelog

Released version 1.6.3

Several fixes, main one is a fix for a large memory leak sometime during parsing which was causing OOM / crashes / slow performance.

http://bit.ly/cheLTS