Since BlueGriffon does not yet know which web browser you prefer to use, you will be rewarded with a dialog where you need to specify which one among e.g. Google Chrome, Microsoft Internet Explorer, Mozilla Firefox, Opera, Safari or whatever browsers are installed on your computer system. This chapter of the BlueGriffon tutorial shows you how you can insert such a navigation menu into your web page. Obligatory note: if you have arrived at this article from outside thesitewizard.com, you may want to start from chapter 1 of the BlueGriffon tutorial, since this guide assumes that you have done all the steps suggested earlier.
First there was Netscape Composer, a WYSIWYG for creating webpages that was part of the Netscape suite. It was never great, just OK. It faded into irrelevance.
Then it was followed by Nvu, an open fork of Composer that was slightly better but didn’t set the world on fire. It faded into irrelevance.
Then that was followed by KompoZer, a community-driven fork of Nvu that fixed a few things in Nvu but was still just fair to middling. It’s still around, but it’s not something I would recommend.
Now the latest on the scene is BlueGriffon, developed by the same guy who wrote Nvu. Like the others, it’s written with Mozilla & XUL. It, however, is the best of the bunch. That still doesn’t mean it’s great.
I know HTML & CSS quite well, so I don’t need a WYSIWYG, but I know WYSIWYGs for creating webpages—I have to in order to teach my courses at Washington University in St. Louis. The best WYSIWYG by far is Dreamweaver, which pains me to say since it is expensive & owned by Adobe, who like to exploit the users of their software to squeeze every penny. If, however, you just have no money at all, or you’ve a devotee of open source & refuse to use closed source software, or if you just need a WYSIWYG for a very specific purpose. In my case, I use BlueGriffon when I need to generate a big, confusing table. Sure, I could do it in HTML, but it’s a PITA, so instead I open BlueGriffon & use that.
I needed to create a table today, so I downloaded BlueGriffon. The software itself is free, as are several add-ons1, but the other add-ons cost money. Want to edit CSS? 9.99€. Like to see a word count? 2.49€. Need templates? 9.99€. And so on.
Now, I have absolutely no problem with BlueGriffon charging money for add-ons. Developers have the right to make money from their software, & charging money for add-ons is time-tested method to do so (although I think some of those costs are excessive & would never pay them2).
But today I noticed a new add-on: a User’s Manual. It’s described thusly: “The missing Users’s Manual for BlueGriffon… We finally have one!” Yes, there has never been a manual for the software. And now there is one. And it costs 5€.
That is ridiculous. It’s one thing to charge for add-ons, but making users pay for the manual is unfair, uncool, & user-unfriendly. A manual is a service you provide your users so they can better use your software. You don’t make them pay extra for it. The fact that the price is only 5€ has nothing to do with it. It’s still not a good thing for users, and BlueGriffon should immediately release the manual as a free add-on.
Like FireFTP (FTP/SFTP), and … well, heck, on looking again, it appears that FireFTP is the only free add-on. ↩
To mitigate the expense, you can buy the Silver Offer, which gives you 9 add-ons for $35. Maybe Apple’s App Store has ruined me, but that still seems like a lot for an HTML WYSIWYG editor. Granted, though, compared to the $375 that Dreamweaver charges, that’s a bargain. On the other hand, Dreamweaver is a lot better than BlueGriffon. On the other other hand, it ain’t $340 better. There is no third hand. ↩
BlueGriffon has serious problems on recent versions of macOS, the authors don't appear to react on bugreports. So we stopped making BlueGriffon available via the Self-Service.
The user manual is available online, only for CERN users, here
Fl studio 11 skins download. The Basic version add :
The Epub edition add all the necessary features to produce quality Epub contents: