... I've decided to rewrite the build> to use Ant and to integrate its target into main editor build.xml.

Moreover, I'd like the idea of having SA integrated into NetBeans> instalation,> so everybody could benefit from its small memory footprint and mainly> from> its fast startup time, when they just need to fix something.

ad a) The netbeans/bin could be used if there are no objections.> there have to be e.g. editor.sh/editor.ex­e

Don't we have to make an netbeans/etc ­ ?

ad c) I can imagine that its classes can be stored inside the> nb-editor.jar, but> I think this is rather poor solution. I'd better have a directory> for the> standalone.jar, as it:> 1) isn't module> 2) isn't library

That's great news; thank you. I just wrote a makefile to build and> install it, but that's of course less portable.>

Good idea. Then Unix developers can set the EDITOR environment variable> to your editor and no longer have to maintain two sets of key mappings

in their heads. Windows developers will appreciate not having to use> Notepad anymore (at least I will).>

No objection -- I think that all startup scripts should go into that> directory, as to do otherwise violates the "law of least surprise".>

Another good idea: directories are cheap and can make support easier.> Free software isn't "free" if it's hard to support.>

Standalone.jar is a library, it's just not an IDE library. If the> NetBeans installation gets expanded to include standalone tools as you> propose, I'd much rather have all libraries in lib, just like all> executables be in bin. Think of it this way: let's say someone added> just such a facility and you needed to support it. Where is the first> place you'd look? My guess is bin and lib directories.

Tom

That's great news; thank you. I just wrote a makefile to build and> install it, but that's of course less portable.

Any chance I could get a copy of the makefile from you? I'm trying to get a> build happening on my NT box (then I'll see if the code's 1.1.8 compliant on> my Mac -- good luck, right?), and have been getting some errors,> specifically as follows:>

D:\JavaProjs\editor­\demosrc\base>java -cp> nb-editor.jar;edito­r.jar;properties.jar­ org.netbeans.editor­.example.Editor> Exception in thread "main" java.util.MissingRe­sourceException: Can't find> bundle for base name settings, locale en_US> at java.util.ResourceB­undle.throwMissingRe­sourceException(Unkn­own> Source)> at java.util.ResourceB­undle.getBundleImpl(­Unknown Source)> at java.util.ResourceB­undle.getBundle(Unkn­own Source)> at org.netbeans.editor­.example.Editor.<ini­t>(Editor.java:48)> at org.netbeans.editor­.example.Editor.main­(Editor.java:409)

A makefile might do the trick to let me know what I'm doing wrong. I'm> suspecting I'm missing a jar in there somewhere, but can't quite figure out> which one. I did take a look at the settings.properties­ file (realizing> that the ResourceBundle settings are something different) and combed through

Editor.java a while, but haven't yet been able to figure out what was going> wrong there either.>

There are no netbeans related files or folders in my environment's classpath> variable.>

I'll hack some more this holiday, but any hints would be greatly> appreciated.

Thanks,>

Ruffin Bailey

Good idea. Then Unix developers can set the EDITOR environment variable> to your editor and no longer have to maintain two sets of key mappings> in their heads. Windows developers will appreciate not having to use> Notepad anymore (at least I will).>

No objection -- I think that all startup scripts should go into that> directory, as to do otherwise violates the "law of least surprise".>

Another good idea: directories are cheap and can make support easier. > Free software isn't "free" if it's hard to support.>

Standalone.jar is a library, it's just not an IDE library. If the> NetBeans installation gets expanded to include standalone tools as you> propose, I'd much rather have all libraries in lib, just like all> executables be in bin. Think of it this way: let's say someone added> just such a facility and you needed to support it. Where is the first> place you'd look? My guess is bin and lib directories.

From Petr Nejedly:> Simply, the settings.properties­ file have to be on the classpath.>

java -cp .;nb-editor.jar;edi­tor.jar;properties.j­ar> org.netbeans.editor­.example.Editor> run in the directory where the settings.properties­ is located should do> the trick.> Please note the dot on the beginning of classpath (Line "CLASSPATH=."> from the run.sh)

You could also jar the settings.properties­ to the root of the> editor.jar, it was> left out of the jar for easier configuration. Too bad decision?

First off, thanks for the help. I have the SE working now! Just for> the benefit of other Windows users out there, here's what I did...>

Not at all, since the next step seems to be to tease the> settings.properties­ file. There is a line that obviously isn't going to> work on my system that talks about the ParserDBs:>

Java_Completion=/ho­me/pnejedly/NetBeans­/system/ParserDB/jdk­13

I copied the files jdk13.jcb and jdk13.jcs files into the base dir of> the demosrc "tree" and changed that line to read:>

#Java_Completion=/h­ome/pnejedly/NetBean­s/system/ParserDB/jd­k13> Java_Completion=./j­dk13

Another option would be, of course, to use the relative path to my> netbeans install, which was, admittedly, the first thing I tried.> (Java_Completion=..­/../../../nb_d73/net­beans/system/ParserD­B/jdk13 in my> case) Not real sure how to use the _concept_ of "home" with Windows.> From messing with File objects, I know that working "D:\" into Java is a> real pain. ­>

I then received the following error:> D:\JavaProjs\editor­\demosrc\base>java -cp> .;nb-editor.jar;edi­tor.jar;properties.j­ar org.netbeans.edi> tor.example.Editor>­ Exception in thread "main" java.util.MissingRe­sourceException: Missing> class> at> org.netbeans.editor­.example.Editor.read­Settings(Editor.java­:475)> at org.netbeans.editor­.example.Editor.<ini­t>(Editor.java:66)> at org.netbeans.editor­.example.Editor.main­(Editor.java:409)>

I dug through Editor.java and found where this was needed.>

String kits = settings.getString(­ "InstalledEditors" );> String defaultKit = settings.getString(­ "DefaultEditor" );>

StringTokenizer st = new StringTokenizer( kits, "," );> while( st.hasMoreTokens() ) {> String kitName = st.nextToken();> [snip]>

I figured out that I hadn't yet jar'd up the Properties kit (what does

that gain me again?), so I had to change that line in the> settings.properties­ file so that it'd stop looking for Properties*> classes:>

#InstalledEditors=P­lain,Html,Java,Prope­rties> InstalledEditors=Pl­ain,Html,Java>

Then I went back and tried again. Perfect.>

Two quick questions:> The servlet.* files in the ParserDB dir are for the JSP SE?

What did I lose by not jar'ing up the Properties kit?

I have noticed a few errors (the paths of the files that're displayed> when I rest the cursor over the tabs in the editor aren't updated when I> Save As... to somewhere else (though updates to the files still go to> the right place), for instance), but that's the beauty of open source!

Thanks for the quick help,>

Ruffin Bailey>

--> Ruffin.Bailey@noaa.­gov | Database Management Systems Group> TPMC.com contractor | NOAA Coastal Services Center> http://www.csc.noaa­.gov | Phone: (843) 740-1195>

"This may be the fault of the interpreter, in which> case HE is the hippopotamus." Boris Yeltsin, 60 Minutes>

-------------------­--------------------­--------------------­----------> To unsubscribe, e-mail: nbdev-unsubscribe@n­etbeans.org> For additional commands, e-mail: nbdev-help@netbeans­.org

If I place the jar file into the netbeans/lib> directory, it will make it to the IDEs classpath, and that is what I'd> like> to prevent. I don't need to have it on the regular IDE classpath, as it> is garbage> from the IDEs point of view.> If I place it under modules/ext, it would be OK, but the jar gets too> "hidden"...>

Any thoughts/comments?

Trung Duc Tran wrote:>> all nice and good, but NetBeans is primarily an IDE and a platform for>> building IDEs and I don't like to pollute it with two many things. We>> don't want NB to be "an OS masked as an IDE" (or am I mistaken?). I>> don't have any objections to bundling the stand-alone editor with>> NetBeans distribution but I strongly want to clearly separate it from>> the rest of the IDE. One possible way is to create a subdirectory>> "extra" or something and put it (and similar non-essential things)>> there.>

Why the objection? I, too, don't want "an OS masked as an IDE" but an>IDE doesn't have to be limited to just a GUI application you develop>within, it literally means "Integrated Development Environment". Since>many development tasks occur outside of the scope of a GUI IDE tool>(such as quick edits, or even debugging NB itself to avoid a double RAM>footprint), we're forced today to use separate tools such as Emacs and>jdb (save me, please!). Standalone wrappers around specific modules are>all we need to access NB functionality without the cost of starting up>the full IDE. That makes NB even more 'I'ntegrated for our development>needs.>­

------------------­--------------------­--------------------­----------->To unsubscribe, e-mail: nbdev-unsubscribe@n­etbeans.org>For additional commands, e-mail: nbdev-help@netbeans­.org>

Date: Wed, 22 Nov 2000 11:04:31 +0100> From: Petr Nejedly <Petr.Nejedly@netbe­ans.com>> To: nbdev@netbeans.org>­ Subject: Re: [nbdev] StandAlone editor>

Having the SA integrated with IDE instalation doesn't necessary means> it will have the same keymappings. Currently, the IDEs editor> keymappings> are serialized with other IDE options into one large file, which is> unreadable from outside the IDE. Until we invent better way of storing> editor options, it is not possible to keep the editor options in sync.

Currently, the IDEs editor> keymappings> are serialized with other IDE options into one large file, which is> unreadable from outside the IDE. Until we invent better way of storing> editor options, it is not possible to keep the editor options in sync.> The SA uses the same set of default editor options as the IDE,> but these are not customizable from inside the SA. I see the possible> temporal solution in running the external class from inside the SA to> let> it set the options programatically (like the class Mila have suggested> for full-featured customizing the Editor in IDE (A class in Startup> folder)).>

Rochelle Raccah wrote:> > How about keeping the jars in a "tools" directory under the installation root> > or>

$0.02: I like "etc/" since it is pretty recognizable. I don't like> anything under "lib/" because it would like the IDE might be using it,> which would be wrong.

Ya, this is a real pain as you upgrade from one version to another.> Would it be possible to add a simple "import/export" facility for> the keymap?

From: Petr Nejedly <Petr.Nejedly@netbe­ans.com>> To: nbdev@netbeans.org>­ Subject: Re: [nbdev] StandAlone editor

On Tue, 28 Nov 2000 12:37:27 +0200 Jesse Glick> <Jesse.Glick@netbea­ns.com> wrote:> > [snip]> > You should be able to put etc/* files into NBMs--what else is there to> > say?>

but what would happen when I update the module? I am not sure if> AutoUpdate can handle it correctly, I means things like deleting some> files or directories if they have not been modified by the user and put> new ones there

Trung Duc Tran wrote:> > [snip]> > We still must work out the relationship between /etc and module> > updates.>

You should be able to put etc/* files into NBMs--what else is there to> say?

Petr Nejedly wrote:> > Having the SA integrated with IDE instalation doesn't necessary means> > it will have the same keymappings. Currently, the IDEs editor> > keymappings> > are serialized with other IDE options into one large file, which is> > unreadable from outside the IDE. Until we invent better way of storing> > editor options, it is not possible to keep the editor options in sync.> > The SA uses the same set of default editor options as the IDE,> > but these are not customizable from inside the SA. I see the possible> > temporal solution in running the external class from inside the SA to> > let> > it set the options programatically (like the class Mila have suggested> > for full-featured customizing the Editor in IDE (A class in Startup> > folder)).> XML. Please. Oh, and while we're doing it, can we invent a good interface and api so that we can share it with some other groups who also are in desperate need of a good interface for user control of key bindings?>

-------------------­--------------------­--------------------­----------> To unsubscribe, e-mail: nbdev-unsubscribe@n­etbeans.org> For additional commands, e-mail: nbdev-help@netbeans­.org

On Wed, 22 Nov 2000 21:22:44 +0200 Jesse Glick> <Jesse.Glick@netbea­ns.com> wrote:>

Agreed. Let's make a proposal: in the {ide.home} directory there will> be a subdirectory {ide.home}/etc. It will have a README.txt file which> says "this directory contains things which are not essential for the IDE> to work but may be useful for certain users". The stand-alone directory> will live in {ide.home}/etc/stan­dalone_editor. The editor folks should> supply a README file with instructions how to use it.>

When we are at it I think the editor customization classes Mila posted> on nbusers <http://www.netbean­s.org/www-nbusers/ms­g01829.html> could be> placed here too.>

We still must work out the relationship between /etc and module> updates.>

-- Trung

So if I understand it well, you'd like the StandAlone to live completly> under the netbeans/etc/<its dir>. Jars, configs, even the starters?

I originally thought there would be only configuation files and the> rest would be in other such specialized directories.