Recommend an IDE setup for CouchDB? - couchdb

I tried experimenting with CouchDB but I find that without syntax highlighting, code completion, auto indenting, and other basic IDE features, I can't even code a Hello World.
What's the most common IDE set up, preferably integrated with eclipse?

Apache CouchDB is made up of simple components: HTTP and JSON. There are plugins for Eclipse for both of these. The largest "helper" tool you'll benefit from having is a "couchapp" publishing tool.
The "couchapp" tools take a file system directory and serialize it into a JSON "design document" for Apache CouchDB (or Cloudant) databases to use for MapReduce, _show, _list, validate_doc_update, rewrites, etc.
The best one available at this time is erica: https://github.com/benoitc/erica
You can then build your design documents with any IDE or editor, and publish them from the command line using erica.
Hope that helps, Alex.

erica is a useful tool but it's not an IDE.
I finally settled on KanapesIDE as the closest thing to what I was looking for.
It is still very basic, a far cry from something like Eclipse, but good enough for quick experiments while learning CouchDB.

Related

PProPanel JSX - Basic guide to get started?

I know you can extend Adobe Premiere Pro with some simple JavaScript. The problem with that link (which I got to through the official Adobe website), is that all of sample code links are outdated (they point to the wrong location of the file, to lines that aren't correct anymore).
The second paragraph instructs you to install a bunch of things, none of which seem like things you "install", and they mention ExtendScript, which I don't understand whether is already installed with my Premiere or not (it's not available on Creative Cloud, and also the links I found on Adobe's website for it are, again, dead). I keep searching online and finding dead links to tutorials that no longer exist. Really, dead links everywhere.
I'm an experienced developer with good JS background, I just want know what I need, some simple examples of basic usage to get me started and maybe working links to some cheat-sheet I can use when I'm looking for available functions.
Extendscript is the name of the old API for automating Premiere and other Adobe apps. It's built-in and can basically do anything that you can do with the GUI, and it's javascript-based.
There is an IDE for Extendscript, the Extendscript Toolkit (ESTK) which has a debugger and allows you to inspect data etc. It's perplexingly hard to find on the Adobe website; I found it by a duckduckgo search here, I installed it through the creative cloud desktop manager, though I'm not sure how you do that with the current version.
As far as documentation goes, you're right, it's dead link city. There is a Javascript Tools Guide included with the Extendscript Toolkit, on windows it's in C:\Program Files (x86)\Adobe\Adobe ExtendScript Toolkit CC\SDK\. That covers creating UI elements, but doesn't explain Premiere's object model. AFAIK there is no official documentation for this, you have to use the ESTK data browser to look for yourself.
The CEP extensions are a new development and allow for easier integration with the host. I think you already have all the documentation there is for it. I'd advise that you pester Adobe to make it easier for developers like yourself to create tools for their users.
Here is for anyone else who gets here from a Google search: You can also go to this link to download the ESTK: https://helpx.adobe.com/download-install/kb/creative-cloud-apps-download.html

Resharpening from the command line

I would like to use the ReSharper Adjust Namespaces feature on a number of solutions. I would like to automate this process by creating a command line application that uses the ReSharper API.
I looked at the ReSharper OpenAPI, but it seems to be geared towards using the ReSharper API from within an active Visual Studio session. I want to be able to use the ReSharper API from the command line.
Is this possible?
You are right: the open API is generally geared towards use within VS. While using it outside of VS is theoretically possible, it is technically challenging and may or may not work depending on your usage scenario.
There's no reason, however, why you shouldn't be able to adjust namespaces across several solutions right from within Visual Studio - of course, this would require to actually load each solution into the shell before performing manipulations. As things stand, this approach is your best bet.

NodeJS Skinning

Is there a module or similar things that support skinning in NodeJS? I want to build a NodeJS website, and want to be able to re-skin the website as I like without much efforts, like in Wordpress.
Is skinning supported in NodeJS?
If you're interested in building a website in Node.js and don't need a wordpress-style cms behind it, there are few projects that can help you out.
Have you looked into Bootstrap? It's built with less which you can easily plug in to your Express setup (see the guide here, using the command line executable to set up a new project you can specify less like this: express --css less myapp and it will do all the work for you)
In the bootstrap less file are several variables you can use to change the colours, fonts, sizes, etc, and it's also got a lot of helpers for grid layouts and responsive designs.
It even includes a few useful javascript plugins too which make the ui nicer with less work.
There are also a lot of sites with themes and theme generators around which then work on top of bootstrap, and may achieve what you want.
Plugging in this sort of solution (whether bootstrap or other) is about as close as you can come to getting skinning for node; As otherwise suggested if you're looking for a CMS out of the box as well, probably best to look for another platform like Wordpress.
Node.js is not a content management system. It is a platform on top of which you could built a web server with a content management system. To answer your question you need to be looking for node.js based content management systems that support themes.
The only node.js CMS that I am aware of is Calipso. It's still pretty alpha-stage. It may have some theming support, but it is nowhere near as polished as Wordpress.
Also is there a reason why you want to use node.js? I mean there is nothing wrong in using Wordpress for creating a themeable website - it is just awesome for that.
If you just want another OnlineShop, or maybe a blog, i think nodejs is maybe not your right choose as Jed Watson told.
If your requirements are more complicated, and you want a quick and easy implementation of a nice web interface, and you have html, javascript, and css knowledge... I strongly recommend you just trying to work with MEAN.js
It puts together MongoDB Expressjs, AngularJs, and NodeJs.
Use this, for example with a yeoman fullstack constructor and you will have a powerful webapp, with user autentication, and much more in a few minutes.
After that, the use of jade, less, scss, and similar languages of modelling the front, and the easy way you can also model collections in the back, is for me the best combination you´ll find for creating a website today.
Hope it´ll help you
King Regards

How can Aptana help with Netsuite Client Suitescript development?

I found my way here from the 3-years-out-of-date page at http://suitesource.netsuite.com/s.nl/it.A/id.82/.f . I have the latest eclipse, with the Aptana plugin and the NetSuiteEclipse plugin.
Just exactly what does Aptana do for me? It's not altogether clear, and it seems Netsuite may have abandoned their end of it.
By far the best environment I have found lately with regards to developing scripts for NetSuite is to just bag the instructions given by NetSuite and go with Aptana Studio 3 (not Eclipse with the Aptana plugin) and then include the NetSuite plugin to allow for direct upload into NS as Jeff mentioned. Aptana Studio is basically just Eclipse for JS and some additional cool features, like built in color themes.
The only other step you need to do (and this is not mentioned in the NS help) is to place SuiteScriptApi.js (and maybe nlapihandler.nl.js) in the root of your main project folder. The above configuration will give you code completion/definition for JavaScript in general and SuiteScript. I forget where I got the files but you can search on SuiteAnswers for them.
The help really needs to be updated to include the changes in IDE's.
The aptana plugin is not Netsuite specific it is a plugin for javascript development and provides code completion for javascript. The code completion of the netsuite objects is limited.
The netsuite plugin to Eclipse allows you to upload your suitescripts to netsuite directly from eclipse. However there are some limitations as to the path of the uploaded files that I can't remember at the moment. It did not allow me to set the paths the way I wanted so I stopped using it.
Use Suitecloud IDE.
Created from Eclipse but customized for Netsuite API.
http://elibeltran.com/suitecloud-ide/
About once a year I try Aptana and I end up uninstalling it each time- recently I tried again for my third time and uninstalled it. In my experience the code completion isn't very good, it doesn't handle complicated inheritance situations, doesn't play well with object literal notation, etc. I don't have proof and I've uninstalled it so if anyone asks me for specific examples I can't produce them.
I always end up back with Eclipse classic (3.7 I think) and JS Eclipse (which is an abandoned plugin that Adobe bought from Interakt but it still works) It's fast and has decent code completion. Is it better than Aptana? I don't think so, but it's snappier and seems to require less restarts.
I wish I had better experience with Aptana, it makes me nervous that JS Eclipse is a ghost that will disapear here at some point. I maintain over 48k lines of SuiteScript in our installation, I REALLY could use a better tool! ;)
Try Visual Studio 11.
It has much better intellisense in my opinion (as long as you configure it with any libraries such as the SuiteScript API.js). It also works well if you are already used to Visual Studio from .NET development (including SuiteTalk web services).
Not really an IDE but here is some suggestion.
Use a Google Chrome debugger. When you are in Edit mode in a record (example: customer), you can use the suitescript API to get the object-tree, very helpful in developing client-side script in Netsuite and understanding how their API works.

Migrate from VS2005 to VS 2010 directly

Our project is currently developed in C#2 , VS2005.
We were thinking of migrating to VS2008 and C#3.
Do you think it might be a better idea to move directly to VS2010 instead?
We do not plan to release the new version till the end of next year.
Is there any advantage in moving from vs05 to vs08 and then moving to vs10?
thanks!
Well this post implies you can, but certain features of certain projects might get broken:
When you upgrade certain solutions from VS2005 to VS2010, the solution explorer layout can become broken. Some files move up the filter hierarchy. In our large solution, a hundred or so files ended up in the root of solution explorer.
It only seems to affect solutions where the solution explorer filter nesting is more than one deep, the files are not compiled (like headers), and they're excluded from the build in some configs.
Though an answer indicates it was fixed:
We have verified that the header file now gets placed under subfolder rather than directly the header filter. The fix should be available in the next public release of VS2010 (Beta2).
To answer your other point. One advantage of going via VS 2008 is that you can make that migration now (assuming you don't want to risk beta software) and start using the features of C# 3 straight away.
Visual Studio 2010 Beta 2 comes with a "Go-Live" license, so if you are ok dealing with beta software, then why not? I have tried it at work myself, while the other developers continue on 2008, but I have to be careful with the project files, to not check in changes, etc.... I don't use it all the time, yet, because it's a memory hog, but other than that performance is a lot better.
There are also a lot of features that are worth the upgrade. The text editor is in WPF now and scales nicely with a ctrl-click and I find I use it a lot. There are a lot of new addins being built to integrate with the UI because the new framework for the code editor exposes a new addin model that is much easier to develop against.
Being able to split windows across multiple montiors in a more flexible way is great.
If you go for the "Ultimate" versions, there are a ton of new architecture and modeling tools and tools for exploring code. I love the ability to generate a sequence diagram from some method and use that while I am reading some unfamiliar code. Works great.
The list goes on really, I have barely scratched the surface, so yeah move on if you want to learn how to use the new stuff, and no one is stopping you, go for it.

Resources