I like using Flux for simple script development... But I think it is missing hew key nice features without asking for the full blown IDE...
As I am learning the language, I don't know about every pod, types and slots... So it will be nice to have a kind of navbar displaying the type DB as a tree, list of pods, then their types and then their slots... And documentation can be displayed when hovering over elements... Will allow to no have to always go back to website to browse the doc
This is the 1st step...
The next one, will be to have the list of available slots when typing . like in IDEs...
With that, I think that will be a very neat tool for beginners coming to Fantom - no need of a full blown IDE to just try stuff in scripts.
brianSat 6 Mar 2010
Flux will probably eventually get those features, but probably not for a while. Getting the context sensitive help while you type is immensely complicated and is what makes tools like NetBeans, Eclipse, etc what they are. We built flux as the simplest "IDE" we could mostly as test application for FWT. Now that we have several real IDE projects underway, I hope that will allow Andy and I to focus on the non-IDE stuff that matters for a 1.0 release.
BTW, I believe KevinKelley has some Flux sidebar plugins for navigating pod/types/slots.
lbertrandSat 6 Mar 2010
No problem...
I may tackle the Flux sidebar for types... I think as a 1st step that will be great and quite helpful for me when playing with Fantom...
I already have created a quick command tool to run a script directly with Flux... Regarding this, at the moment, I use the compileScript slot of Env to compile the file which allows me to know if it is a script or not... Is there a better way to decide if a file is a script or not without compiling it?
brianSat 6 Mar 2010
Is there a better way to decide if a file is a script or not without compiling it?
Probably the best way to distinguish b/w a fan script file and a fan source file within a pod is to look for a "build.fan" file up the directory hierarchy.
If you annotate all our scripts with the Unix shebang, that might be another way.
That would be nice thing to have in Flux built-in. The killer problem has always been that Java doesn't give you a way to kill a process.
KevinKelleySat 6 Mar 2010
Flux sidebar plugins for navigating pod/types/slots.
I do have; but I hadn't got around to the last few rounds of Fantom changes with it. (I was moving more toward a separate tool, and kind of let the Flux plugin get dusty)
lbertrand Sat 6 Mar 2010
I like using Flux for simple script development... But I think it is missing hew key nice features without asking for the full blown IDE...
As I am learning the language, I don't know about every pod, types and slots... So it will be nice to have a kind of navbar displaying the type DB as a tree, list of pods, then their types and then their slots... And documentation can be displayed when hovering over elements... Will allow to no have to always go back to website to browse the doc
This is the 1st step...
The next one, will be to have the list of available slots when typing
.like in IDEs...With that, I think that will be a very neat tool for beginners coming to Fantom - no need of a full blown IDE to just try stuff in scripts.
brian Sat 6 Mar 2010
Flux will probably eventually get those features, but probably not for a while. Getting the context sensitive help while you type is immensely complicated and is what makes tools like NetBeans, Eclipse, etc what they are. We built flux as the simplest "IDE" we could mostly as test application for FWT. Now that we have several real IDE projects underway, I hope that will allow Andy and I to focus on the non-IDE stuff that matters for a 1.0 release.
BTW, I believe KevinKelley has some Flux sidebar plugins for navigating pod/types/slots.
lbertrand Sat 6 Mar 2010
No problem...
I may tackle the Flux sidebar for types... I think as a 1st step that will be great and quite helpful for me when playing with Fantom...
I already have created a quick command tool to run a script directly with Flux... Regarding this, at the moment, I use the compileScript slot of Env to compile the file which allows me to know if it is a script or not... Is there a better way to decide if a file is a script or not without compiling it?
brian Sat 6 Mar 2010
Probably the best way to distinguish b/w a fan script file and a fan source file within a pod is to look for a "build.fan" file up the directory hierarchy.
If you annotate all our scripts with the Unix shebang, that might be another way.
That would be nice thing to have in Flux built-in. The killer problem has always been that Java doesn't give you a way to kill a process.
KevinKelley Sat 6 Mar 2010
I do have; but I hadn't got around to the last few rounds of Fantom changes with it. (I was moving more toward a separate tool, and kind of let the Flux plugin get dusty)
I'll clean it off and put it back up, shortly.