BlueGriffonTM

The next-generation Web Editor
based on the rendering engine of Firefox

Thinking at loud

Entries feed

22Mar

Help needed for BlueGriffon on Mac OS X

I am hitting a strange issue on Mac OS X: the OS X "Special Characters..." menu entry in the Edit menu is not always present in BlueGriffon:

  • launching BlueGriffon with the en-US locale, it's often present; not always. If it's not, opening the Keyboard Viewer and unchecking/rechecking "Show Keyboard & Character Viewer in menu bar" oftens helps
  • using another locale, the menu entry in Edit is never available and the little trick above does not help...

I'm lost here. Does anyone have a clue about what's going on? That would help a lot, thanks !

Note: Windows and Linux users have an extra XUL dialog for special characters...

10Oct

Toolkit Manager !

I just had the idea for the coolest add-on for BlueGriffon: a toolkit manager ! Thinks jQuery, KEYS.css, prototype, etc. As a web author, I want a way in BlueGriffon to declare a toolkit, declare all the relevant CSS and JS urls, have BlueGriffon download the files' contents and store them locally (in files or database), have BlueGriffon be able to update the files from their official web repository with one single click. I want a menu listing all the available toolkits and inserting ALL the necessary JS and CSS in my document, embedded or linked, with one SINGLE click. I want it, I love the simplicity of the idea, and I am of course going to code it. Stay tuned!

20Aug

Source view

The main problem with BlueGriffon's source view is the following one : tabs disappear in source view... In other words, to copy some markup from one document's source to another, you have to switch back to wisywig mode. That's an ooooold thing: Nvu and Mozilla Composer already had that very same restriction and that is caused by our nsPlaintextEditor.

But since Bespin is now used by BlueGriffon for the source view, I can probably work around that restriction. Let me think a bit about it :-)

25Jun

Adding presentation to HTML is hard

Attributes ? Inline Styles ? Context ? ID ? Class ? A mix ? *sigh*

I'm not happy with the CSS Policy Manager I implemented. It currently lets users of BlueGriffon decide in all dialogs how an action should be performed: through HTML attributes, through inline styles, or through embedded styles attached to an ID or a class. That's far too complex for many users and the resulting dialogs are so painful that I hate them myself. I am then going to revamp it entirely and remove the corresponding bits from the dialogs. I will probably also remove support for HTML presentational attributes... BlueGriffon will then rely 100% on CSS for presentation... That was not possible a few years ago because of the browsers' landscape but I think it's now a more - if not perfectly - reasonable target. The whole Table Layout dialog is already 100% CSS-based.

In summary, the Preferences panel will offer the following choices:

  • Let BlueGriffon decide by itself how it adds styles and let it pick IDs and classes for me when needed (enter a prefix below)
  • Let BlueGriffon decide by itself how it adds styles but prompt me when a new ID or class is needed
  • Let me decide

It's clearly (much) harder to implement but I am sure the whole CSS/HTML machinery should be hidden as much as it can. The average user - and that includes myself - does not want to know about the technical details as soon as the result is clean, standards-compliant and what he/she expects from a rendering point of view. Advanced users will still have the possibility to edit their stylesheets directly through the CSS Manager.

All in all and in my opinion, this proposal is good for both beginners and advanced users. Comments?

22Jun

T-shirt :-)

here...

12May

Image dialog

The new Image insertion dialog in BlueGriffon will allow to set a CSS box shadow and a CSS roll-over. Other suggestions?

02Mar

JSCSSP

Nvu had a strong limitation, because of Gecko. It could only edit CSS styles understandable by the embedded version of Gecko. This is something I don't want for BlueGriffon because I think it does not make sense to make a content editor for the Web that is restricted to Gecko-based browsers. I want users to be able to manipulate a UI that will create -moz-transform but also -webkit-transform. And I also want users to be able to edit stylesheets that include both properties while the -webkit-* are never present in Gecko's CSS OM (and that's normal). I don't need to cascade, I want to preserve all rules and all declarations even multiple declarations of the same property, I want to preserve comments as much as possible (ie between rules and between declarations), I want to preserve CSS parsing errors. The only extra thing I need is a resolver for shorthands.

So I just started my own CSS parser. It'll parse a string containing a stylesheet and will return CSSOM-like objects with the necessary extensions. It'll live inside the CSS Inspector sidebar of BlueGriffon but I will probably make it MPL.

01Mar

CSS 'font-weight' and UI

CSS is so cool. So cool. But not in terms of UI for a CSS editor...

  • let's suppose you can have your text 'bold' or 'normal'; one checkbox or checkboxButton is enough, and you can have this button live with other buttons like italic, underline and others
  • let's suppose now you can have your text 'bold', 'normal or unspecified ; a few options here:
    1. one checkbox to say the boldness is specified or not and a checkbox/checkboxButton for bold
    2. two checkboxes/checkboxButtons for 'bold' and 'normal'; property is unspecified when both are unchecked
    3. a menulist with three choices
  • let's suppose now, and that's the CSS real case that matters to me, boldness can take the values 'bold', 'normal', 'bolder', 'lighter', 'inherit', 'initial', 100, 200, 300, 400, 500, 600, 700, 800, 900 or can be unspecified... The two reasonable choices here are:
    1. one checkbox to say the boldness is specified or not and a menulist
    2. a menulist where 'unspecified' is one of the options

In other terms, offering the full power of the 'font-weight' CSS property to a CSS editor will necessarily suck in terms of UI (yeah, forcing a menulist when most users will only use the 'bold' choice just sucks)... I am even tempted to have two modes in the CSS editor, basic and advanced. Pffff....

Ideas, suggestions?

03Oct

Speaking of tables

One of the nice features of text editors is table formatting. Think MS Word and its Table Autoformat dialog. It's very easy to implement that in BlueGriffon... Hehe :-)