Netbeans


#netbeans #ide 

Comments


It is a nice IDE had used it a lot with Java . Still have it. Not easy to get updates. Lots of options to sort out.

Modern netbeans is much easier than it was even a few years ago … super easy to update.

I have 8.1 – nice for code jockeys perhaps.

i would expect that that here would be some integration between netbeans and the repositories … is there?

Several: here is a clip 

Another one is Eclipse. http://www.eclipse.org/  I have not played with either for a long time.  They are not online interactive but interact with the local copy on your machine. 


Look around both netbeans & eclipse both possibly have cloud interaction.

Netbeans requires a Java download first … or get them together maybe … http://www.oracle.com/technetwork/java/javase/downloads/index.html

well certain amount of synergy possible if nathan and i are using the same tools

I think you can get the integrated download. Look around maybe it will work without Java if you are not writing java code.

I have used both Netbeans and Eclipse for years. Netbeans is a ton easier and cleaner.  

You might say that Netbeans is more like an Apple product and Eclipse is more like a Microsoft product. That pretty much says it all.  

Yes. And sometimes I use the built in integration. I personally fought using the command line for years too. But finally, I gave in. The command line works the same everywhere, on every computer, and on every server. It is fast and reliable and gives consistent results. It is well documented and lots of help on stackoverflow for anything you want to do no matter how obscure. All the GUI’s out there are specific, tricky to use, and wobbly in results … even the ones built into the IDE’s like netbeans.

The built in ones are sometimes helpful for a few things, and could be used okay if you are locked into a tight development path … but when you are working with lots of people and/or lots of different flavors of code and a variety of different server destinations, the command line becomes your friend and the gui’s become tedious at best.

got #netbeans w/java from here … now installed on desktop and getting some plugins null

The netbeans project for the td repo is in projects/td/nbproject

But realize that if you use that project it will need to be git tracked and merged if you make any changes to the project files. You could also create your own project for it outside the repo and git will still track all changes to the actual repo files without changing the master project files.

Of course, if you do make changes to any files in the td repo itself, they will have to be merged with my changes on the master branch in order to propagate. You know, standard team code change stuff. Fork your own branch, make changes, push them, deploy them, test them, do code review diligence, then merge back to the master yourself or submit a pull request.


absolutely that is what i am swimming into null

My current project here, however, is more additive than changeative null.

Objectives to manifest just so you will know where i am going with this ...
  1. learn the SparkPost api and apply it to speaktomecatalog.com/newsletters #newsletters. This is the critical path for my business and i am under extreme pressure to restart sending them out.  The server switcheroo fucked up the way they used to work.
  2. integrate SparkPost in TD as a standard way to share a thought to an individual – as seen all over the web. 
    • one usecase would be to dispatch the welcome letter when a person registers
  3. create the ability for a group to copose and send a newsletter to all of it’s members – urgently needed for http://td.rentonfoodcoop.com/forum and other groups.

Well, for item #2. Maybe SparkPost would add tangible value to that process, or maybe it would be like using a bulldozer to dig a hole for a potted plant and there is an easier and more direct and efficient way to do what you are wanting to do, like that already existing garden spade over there. #IDK … would have to review what you are doing.  

I can see how it is useful for your newsletters though.

well after quite a bit of research i am confident that SparkPost will meet the requirements of #1 & #3.

#2 should be done via a API like everything else that happens through thinking.live domains.  Sparkpost does whatever it does through a great looking API.  

Sending out one letter is just a special case of sending out a bunch of them … all the same headers and reputations and sending domains need to be configured.  i see no reason to think of them differently and develop different facilities for each.  That way we get 2 birds knocked down with the same stone.

Maybe, maybe not. You are welding logic, and logic is not always the answer. But I can’t say without proper research and this is very low priority cart a mile before the horse stuff. By the time we actually need to send a newsletter, we will know much more and better be able to follow the real YES.

… and right now we can send single emails effortlessly with the existing library.

well obviously your priorities are quite different than mine.  i needed to send out newsletters and welcome letters for the CoOp months ago.   In fact that is one of the primary reasons that group project has stalled. 

That is a specific need of your own cooper project. You don’t have any other customers to know if it is a big need of general #TD owners … and there is plenty to do yet to make ready for real owners.

i.e. You are yet again treating this like your private thing and your needs drive it, not the needs of actual others.

all real groups want and need to communicate through email … that is one aspect of how they communicate and share.   it does needs to be a basic function of thinking.live … just like the other kinds of social network sharing … facebook, twitter, G+, instagram.   that is not just me.  it is the needs of real customers.   thinking.live would be a incomplete offering without state of the art social network sharing.

Well, I didn’t say no even though you are beginning to spin up crusade energy as if you perceived that someone is preventing you from something. I simply said #IDK and it doesn’t feel exciting to me at this time to research it.

I always tell everyone to follow their excitement. If this is exciting to you, do it. Do the energy work first of course. If you state of being is aligned, the actual physical details will be trivial.

i did not ask you to do anything here at all.   this is something that i am doing.  the only thing hampering me is the difficulty involved in learning the technology. 

and yes i do appreciate you answering  technical questions and sharing designs here just according to your own excitements  … #thanks → nathan for that.
 
i have no idea where you got the idea that “i perceived that someone is preventing me from something” … trust me when i tell you that no such thought even entered my mind or my feelings.    you just #MadeUpShit about that in a very insulting way.  I don’t know why you keep doing it.

Conversation forked to thought 23002

yeah but how do you integrate #netbeans with getting and editing a file at a website?
 
strange but i can’t seem to figure how to do that …
unless i just ftp it back and load it from my local computer as usual … which seems a bit regressive.

incidentally there is no git repository at speaktomecatalog.com yet. 

Several ways.
  1. Netbeans has built in FTP you can use to directly edit remote files as if they were local. This works fine for static sites, like FBI used to be and speak still is. It does not work well for deployed sites, and not at all for cloud sites with static code files like gcloud.
  2. You can directly attach Netbeans to a remote git repository.
  3. The way I do it is use a local git repo, git commit and then git push the code and then use a cloud shell to td update fbi. Three simple shell steps I can almost do blind in a quick second using shell history. Because only the changed code is transferred, it is very quick.
  4. You can run a local webserver and do all your dev locally, with local or remote SQL server access, and then use any of the above 3 to push the code up when you have it cherry.

i expected it, but can not find the “built in FTP”.

I used it several years ago and it worked nicely. Have not used it lately, so I simply googled “netbeans ftp” and came up with this.

https://netbeans.org/kb/docs/php/remote-hosting-and-ftp-account.html 

… also there are likely lots of FTP plugins available. check out the netbeans plugin libraries.


#thanks

here is  youtube to descirbe it …