Hi
100% agree but a litle reference on netbeans home about recent changes
on
plugin can help to take more users and even developers… Its hard to
get
some info…
El 06/11/2012 19:41, “Sbastien Le Callonnec” [email protected] escribi:
Last week I decided I would spend 1 full day a week working on this
until we can get it back onto the plugins catalog by default. The
lack of Netbeans domain knowledge and purely-spare-time nature has not
been cutting it. I have too many other hobby projects and nb ruby
support is too important.
I have done some work already (like updating to build to bundle jruby
1.7.0 – last week). I will send to our mailing list and the netbeans
one when I have something a little bit better. Also Rocko Requin has
been helping to find a indexing hang which can occur.
The first order goal is to get the test green and cleaned up. The
newer indexing libs in nb are causing issues and we have some process
launching issues (mostly on Windows).
The next goal will be updating nb to use latest release of
jruby-parser. It has lots of 1.9 parser fixes and ultimately should
be the kernel of all AST-related activities.
The goal after that is to update for Rails 4 (Rails 3 probably as well
since it is not working correctly).
The long-term goal will be to start replacing large swaths of Java UI
code with Ruby scripted code. The maintenance of this code is pretty
ugly. Lots of String handling which would be trivial in Ruby (and
this code is not performance sensitive).
If anyone wants to help then send me an email. I will get you up to
speed on building things.
On Wed, Nov 7, 2012 at 10:22 AM, Thomas E Enebo [email protected]
wrote:
Last week I decided I would spend 1 full day a week working on this
until we can get it back onto the plugins catalog by default. The
lack of Netbeans domain knowledge and purely-spare-time nature has not
been cutting it. I have too many other hobby projects and nb ruby
support is too important.
I have done some work already (like updating to build to bundle jruby
1.7.0 – last week). I will send to our mailing list and the netbeans
one when I have something a little bit better. Also Rocko Requin has
been helping to find a indexing hang which can occur.
[…]
The reason for this being the normative repo (I will setup a shallow
git mirror soon) is that it directly is connected through QA +
deadlock (hudson ci). The CI alone makes this fairly neccesary since
the unit and functional testing is pretty crazy.
To build a checkout:
ant nbms
To install you can add a local update center in Plugins/Settings to
your:
${nbruby_dir}/build/updates/updates.xml
-Tom
On Tue, Nov 6, 2012 at 12:41 PM, Sbastien Le Callonnec [email protected]
wrote:
Here is my current plan. I had no idea that I had the ability to
update the binaries in the netbeans.org website for eash release of
netbeans (I think QA staff put up 7.0 and 7.1 versions once I
submitted them for inclusion in catalog). As soon at NB 7.3 is out I
will upload the most stable version I have so people can then always
have something which somewhat works. For those who want to be more
cutting edge they can add this to their plugin sites:
This is the continuous integration servers storage of the last
completed test-run. The current version should not lock up during
completion and the debugger also works again. This build will only
work in NB 7.3Beta2 or higher though.
fixed. Also it would be easier to give the dev team (all two of you
lack of Netbeans domain knowledge and purely-spare-time nature has not
launching issues (mostly on Windows).
ugly. Lots of String handling which would be trivial in Ruby (and
I want to let you know that I appreciate all the work you are doing to
try to keep the ROR netbeans plugin project going. I have been
depending on it for 6 years as my primary dev environment for rails.
I have seen some of the posts with regard to bug fixes around the web.
Especially the auto-completion bug (Makes it nearly unusable on my mac).
Is there anyway you can make the “dev” version available in a repo so we
can just add it to the netbeans plugin sources and grab it when bugs are
fixed. Also it would be easier to give the dev team (all two of you
) feedback when a bug is encountered.
OMT, there are apparently two plugins in the netbeans plugin site, which
should be combined into one page.
Last week I decided I would spend 1 full day a week working on this
until we can get it back onto the plugins catalog by default. The
lack of Netbeans domain knowledge and purely-spare-time nature has not
been cutting it. I have too many other hobby projects and nb ruby
support is too important.
I have done some work already (like updating to build to bundle jruby
1.7.0 – last week). I will send to our mailing list and the netbeans
one when I have something a little bit better. Also Rocko Requin has
been helping to find a indexing hang which can occur.
The first order goal is to get the test green and cleaned up. The
newer indexing libs in nb are causing issues and we have some process
launching issues (mostly on Windows).
The next goal will be updating nb to use latest release of
jruby-parser. It has lots of 1.9 parser fixes and ultimately should
be the kernel of all AST-related activities.
The goal after that is to update for Rails 4 (Rails 3 probably as well
since it is not working correctly).
The long-term goal will be to start replacing large swaths of Java UI
code with Ruby scripted code. The maintenance of this code is pretty
ugly. Lots of String handling which would be trivial in Ruby (and
this code is not performance sensitive).
If anyone wants to help then send me an email. I will get you up to
speed on building things.
@Thomas E Enebo: I’ve installed the plugin into NB 7.3Beta2, seems that
the code completion now works but if I open my Rails 3.x Project the
plugin thinks that it was a Rails 2.x style project: no bundler menu,
when I run it says that script/server has not been not found… (the
same project into Netbeans 7.2 runs well…)
How can I run and debug my rails 3 projects into the IDE ?
Using NB 7.3Beta2 with the Rails plugin I’ve lost about 8 hours of
work…
After that an error was detected into autocompletion my source file was
truncated by the ide (0 bytes !), no history no ctrl-z available, the
source was simply lost…
I’ve load the source backed up yesterday, try to put again the code
updates and again:
the autocompletion try to lock the ide, some routine checking is
fired by the ide tell me that a process is working for too much time
the ide cannot save the updates (no error, simply ctrs-s or button
do’to do anything)
the source file is empty: 0 bytes
ctrl-z does’nt work
history are empty
In 30 years of programming this is the first time that I’ve lost the
whole source file (and about 8 hours of work) !
If you don’t want to lost your source files do not use NB7.3 beta 2
with the ror plugin !!!
Nella citazione in data lun 21 gen 2013 11:04:23 CET, Gianluca
Tessarolo (Tex) ha scritto:
Wow. I am super sorry to hear that. There was a deadlock in
auto-completion with some changes between 7.2 and 7.3 and we thought
we fixed but it (should have been prevented with a mutex), but it
appears it is not fixed. I am unclear how this lead to truncation of
your file.
Even though I am working on this plugin I don’t know how or if the IDE
saved a copy of the file between saves. Most editors and IDEs have a
working copy and a last written copy. I am really hoping NB does
this…I will see some googling…
-Tom
On Mon, Jan 21, 2013 at 2:23 PM, Gianluca T. (Tex) [email protected] wrote:
Tessarolo (Tex) ha scritto:
Especially the auto-completion bug (Makes it nearly unusable on my
should be combined into one page.
Rob Little.
support is too important.
launching issues (mostly on Windows).
code with Ruby scripted code. The maintenance of this code is pretty
I am running 7.2.1 on both mac and ubuntu. I have had luck by turning
off the auto completion in the preference.
Editor:Code Completion
turn off
Auto Popup Completion Window
Display Documentation Next to Completion
Insert Single Proposal Automatically
Case Sensitive Code Completion.
This is only a work around… the Control-Space still seems to work and
not cause a freeze up.
It has allowed me to use 7.2.1 on my mac. Before NB kept locking up and
I would have to force quit. After a force quit it would sometime require
the prefs to be removed and totally reset. (a real pain)
Thanks,
Rob Little.
Gianluca T. (Tex) wrote in post #1093096:
…
No problems on NB 7.2 (but autocompletion continues to freeze the IDE)