OK, thanks - I'll take a look!
Dawn
On 29/12/2017 14:36, Geertjan Wielenga wrote:
Here's a plugin that might help, would be interesting to hear if it
does what you're looking for:
https://github.com/geertjanw/FullMavenProjectFilesNode
https://github.com/geertjanw/FullMavenProjectFilesNode/releases
Thanks,
Gj
On Fri, Dec 29, 2017 at 1:40 PM, Geertjan Wielenga
<[email protected]> wrote:
Interesting feedback and great to hear this combination works well for
you. Your "would be nice if" would be quite trivial to add, i.e., the
"Project Files" node would contain all the files found in the Maven
root node, not just pom.xml and nb-configuration.xml, as is currently
the case. I.e., a simple plugin could remove the current Project Files
node and replace it with one that contains all those files and we
could also change the definition of the Project Files node within the
Apache NetBeans Git to allow this, so that no plugin at all would be
needed and that this would be the default behavior. In either case,
would be good if you'd add an issue for this so that we can discuss it
further there and implement it together:
https://issues.apache.org/jira/projects/NETBEANS/issues
Gj
On Fri, Dec 29, 2017 at 1:32 PM, Dawn Raison <[email protected]> wrote:
FWIW, I'm using it solely for development of a complex JS application, which
I am slowly migrating over to an Angular paradigm using typescript.
The "project" is maven based, and I use the exec-maven-plugin to fire off
the JS compilation tasks - currently by invoking gulp which has tasks to
package the legacy JS, and compile/webpack the typescript (via
webpack-stream).
There are a number of niceties that I've noticed pop up, for example an npm
node appears once you have a package.json with tools to tell you what
updates are available, and gulp tasks are recognised and are available on
the relevant context menus.
One "would be nice if" would be the ability to get recognised config files -
such as tsconfig.json, package.json, gulpfile.js, webpack.config.js, etc
could be shown in the "project files" node of the project viewer, rather
than having to use the file tree ;)
Dawn
On 28/12/2017 19:05, Geertjan Wielenga wrote:
Definitely NetBeans is relevant for JavaScript usage. Best of all, any
roadblocks you encounter can be fixed by your own pull requests to Apache
NetBeans on Apache Git.
Gj
On Thursday, December 28, 2017, Thomas Hubschman <[email protected]>
wrote:
Hi all,
As an old time NB user (started sometime between 2000 and 2004) I have
been quite devout in my use of NB for all things Java.Â
As much as I'd like to have seen a Swing-dominate world, it was
JS/HTML/CSS that prevailed. ;) ;) ;)
20 years later I find that most of my UI work is in Angular, React, or
Ember.
I have tried on several occasions to use NB for this work, but it doesn't
quite seem designed for it. I keep hitting roadblocks.
My question is: Is it Practical to use NetBeans for a Modern "Compiled" JS
app?Â
e.g. ES7 ==> WebPack ==> Babel ==> etc. ==> etc.
I have used it when I included Angular libraries in the index.html header
directly to great success but since I started having WebPack run things I
have had less success. I love the Chrome integration.
Thanks,
Tom
P.S. As a side note I am looking to do some development work on NB. I D/L
the repo over the break and am starting to poke around.Â
--
Rgds.
Dawn Raison
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
--
Rgds.
*Dawn Raison*
Lemur Software Ltd.
E:[email protected] W:http://www.lemur.co.uk
M: 07956 609 618 T: 01428 729 431
Reg: 3097160, England & Wales
Heldan House, Tower Close, Liphook, Hampshire. GU30 7AS
This email and any attached files are for the exclusive use of the
addressee and may contain privileged and/or confidential information. If
you receive this email in error you should not disclose the contents to
any other person nor take copies but should delete it immediately. Lemur
Software Ltd makes no warranty as to the accuracy or completeness of
this email and accepts no liability for its contents or use. Any
opinions expressed in this email are those of the author and do not
necessarily reflect the opinions of Lemur Software Ltd.
