BlueFish is a free and open source text editor supporting a wide range of languages, multiple document interface, powerful search tools, in-line checking and auto-recovery, and other features.
N/A
SharePoint Designer (discontinued)
Score 6.0 out of 10
N/A
Microsoft's SharePoint Designer was a tool for developing SharePoint applications that has been discontinued.
BBEdit is fantastic but it costs money. Frankly, BBEdit is not worth paying for. All you are doing is paying old software and I have a problem asking people to do that. Also, BBEdit is limited to the small Mac Universe. Likewise, Notepadd++ is only found on Windows but I much …
Compare it to what I'd call its WYSIWYG editor, BlueGriffon. Again, the two are fundamentally different solutions. Use them together. Don't waste your money on Adobe or any other proprietary alternative.
I haven't used anything else like this. I use different products for workflows and forms, but they aren't listed in the listings for this page. Instead of using it for workflows or forms (deprecated 2 years ago), I use Nintex. For everything else, I have what I need in the …
These products are very good alternatives to SharePoint Designer but SharePoint Designer stacks up when you are using it for on-premise SharePoint environment.
I prefer InfoPath for designing forms for use in SharePoint over SharePoint Designer. I have not used SharePoint Designer for designing pages in SharePoint. I have found it easier to work directly in SharePoint. Granted I have only had the product for a little over a year.
I'd say that Nintex is a lot easier to configure and identifying errors is less complex than SharePoint Designer. In addition, an alternative that developers may prefer using is Adobe Dreamweaver which is also a web development tool. A third option is Coda, a text editor that …
SharePoint Designer is somewhat inferior when compared to a purpose-built third-party tool like Nintex. Even though Nintex leverages built-in workflow engines (SP2010 and SP2013 depending on platform), it builds on top of that and adds many useful features.
Nintex Forms and Workflow are both very robust tools, but cost for some clients can be prohibitive. Nintex does not provide tools to manage SharePoint sites, lists and libraries.
Both K2 and Nintex provide a powerful platform to build and run business applications that integrate seamlessly with SharePoint; business apps typically consist of workflow, forms, data and reports. The type of business apps range from simple document approval workflows to …
Both Nintex and K2 Blackpearl are great products in their own way, but they are expensive. The pricing models for the SharePoint Online environment is very expensive for how Holiday uses workflows. Nintex's pricing model is by the number of workflows in your tenant, and I …
There really isn't a holistic, complete SharePoint Designer replacement currently. You can utilize several different tools and piece together the functionality of Designer. No one really "selects" SharePoint Designer, it is just a necessary evil. For O365 subscribers, Flow …
SharePoint Designer is the only tool of its kind that I feel 100% comfortable using. Compared to the Nintex workflows/forms, SharePoint Designer has much more increased functionality and ease for an IT-type user like myself. I think it has a much better and easier to navigate …
As I said before, I didn't select SharePoint Designer per se, but I did (and will continue to) elect to sometimes use Designer rather than create deployable solutions in Visual Studio.
Designer could be called the lazy person's tool for modifying SharePoint. Solutions created in …
It is perfectly suited for most markup and programming languages, much better than Text docs, but it is not ideal for anyone who'd like a visual editor.
Well Suited - WORKFLOWS! To a SharePoint Developer, workflows are like a hammer to a carpenter. If there is a business process that needs automation, the first thing I look to is what are we automating? What/where is the data? How can we minimize the number of keystrokes by end-users to get from the start to finish? The answer to all of these is "build a workflow". With the introduction of "Call HTTP Web Service" action, you can now access data anywhere in a site collection and consume it in any site, on any list, for any form. SharePoint Designer Workflows makes the SharePoint world go round. Less Appropriate - Building SharePoint Pages I have attempted to use SharePoint Designer to build custom pages, but it just is the worst tool to use. There are many other tools to use to develop customized pages. The techniques of designing custom page layouts, CSS files to populate in pages, JavaScript Snippets for pages have changed so much over the years, and SharePoint Designer did not change with them. In fact, it is my opinion the 2013 version made it 100 times more difficult than the 2010 Version.
Easily found and downloaded. If I need someone to go to the web and grab it I can tell them the URL. It is easily installed and one can be edited in minutes.
BlueFish is easy to use. It can have a non-technical user use it to edit config files or text documents and not have them frustrated. It has a friendly straight forward user interface.
BlueFish does a really good job editing HTML documents specifically. Probably one of the best HTML editors left out there.
SharePoint Designer offers more granularity of customizing a workflow that is more sophisticated solution that can effectively delegate tasks to responsible parties and reflects status updates of task status.
SharePoint Designer allows SharePoint professionals the ability to customize a SharePoint site with HTML5, CSS3, and JavaScript that can be integrated in .ASPX pages.
SharePoint Designer offers form customization where Office products such as Word, Excel or PowerPoint cannot meet specific government requirements and or expectations.
There are WYSIWYG Open alternatives, some of which work perfectly as an Open version of Dreamweaver, but the only suggestion I would have is that Bluefish add a WYSIWYG tab, e.g. code/visual.
Navigation between sub-sites and beyond the entry point is not seamless. I find it difficult to get to the root of a directory structure if I have not started there.
Would love to be able to do WYSIWYG in some form. I have only used it for a year but I have not found anything fancy to do.
I would like to be able to work in a development site and easily move to the production site.
As with most GNU GPL products support is top-notch. Documentation is fantastic, all functions are documented. Also, this product has been around for more than a decade so there is lots of stuff on how to do this or that with this tool. The only thing holding you back from support is your own drive to find a solution. RTFM, my friend.
Support is good from Microsoft. They are quite responsive when we raise a ticket but SP Designer support will be ended by Microsoft in the near future as they have got new techs like PowerApps and Flow to achieve the same functionality SP Designer does and even more than that.
BBEdit is fantastic but it costs money. Frankly, BBEdit is not worth paying for. All you are doing is paying old software and I have a problem asking people to do that. Also, BBEdit is limited to the small Mac Universe. Likewise, Notepadd++ is only found on Windows but I much better than BBEdit. Finally, there is Atom. I like Atom a bunch because it has a lot more functionality than BlueFish. Atom is a better code editor than BlueFish. Also, the Atom interface is a bit confusing to the new user.
In order to simplify our internal workflows, we have installed additionnal tool for our SharePoint platforms : Nintex Workflow and forms. Compared to Nintex, SharePoint Designer is very far away. I am only talking here for 2 main features of SharePoint Designer : - Workflows - Forms But for these 2 features, Nintex is way above SharePoint Designer
With workflows alone we have had a positive ROI because it gives us increased functionality and value with a smaller amount of development time needed.
The testing of workflows or pages is more structured and we have less base cases than a ground-up customized development solution.
Occasionally, we will have a negative impact on our ROI based on the work-arounds needed to make SharePoint Designer work for a specific project, but overall there has been more positive impacts than negative.