BlueGriffonTM

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

24Nov

Mac

We just built BlueGriffon for the first time on a Mac, only to discover we have a lot to do on the theme's side for that platform. But thanks to Laurent, we now have a cool build process on all platforms that will allow us to push fresh meat to this web site more often than before.

05Nov

Table layout dialog #3

A screenshot-based demo of table layouts. Create a basic table, open the layout dialog, find or create the one you want, click OK, done...

Create a table Select a layout Enjoy !

04Nov

Table layout dialog #2

A lot of progress on the table layout side. It's near completion. It's now possible to create new table layouts and modify existing ones. Only remain on the radar horizontal and vertical alignment controls.

Table layout dialog

03Nov

Language management

I've just added a context menu to the structure bar. The first menu item there is to manage the element's language.

Language management

08Oct

Zoom #2

Already working fine, only remain a few minor details to iron.

zoom statusbarpanel

07Oct

Zoom

Currently adding a UI element to control the zoom factor. This is an important accessibility tool that is so simple to add to a Gecko>1.8-based app that BlueGriffon should not exist without. Will be ready in a few hours from now I guess, if my dying Vaio laptop does not collapse before...

06Oct

Changes on the web site

Here are the last changes on the web site:

  • I configured our blog manager in order to have better urls. You should change the address of the atom/rss2 content in your feed reader.
  • Comments are now allowed !
  • The forum has been moved to /forum
  • I worked on the design of the forum. It's better, isn't it ? :-)

06Oct

Table layout dialog

It's only a beginning but it already works beautifully...

table layout dialog

02Oct

CSS rules only... #2

Tables are much nicer when the only attribute they carry is a class or an ID, aren't they?

bluegriffon table insertion dlg 1 table insertion dlg 2 table created source view

01Oct

CSS rules only...

One thing that has always puzzled me in existing HTML+CSS wysiwyg editors is the impossibility to create a table in a really strict markup context. I mean a table with no presentational attributes at all, no inline styles at all and only a class and/or ID or the table itself. Although almost nobody writes such tables, it's fairly simple for the most common attributes. I suspect it's for three reasons only : first, web sites use a lot of borderless tables ; second, existing editors don't let you do that ; third, most people don't understand CSS well enough. Let's suppose our table has ID mytable. Then we have the following equivalences:

  • for the border attribute on the <table> element if the value if not "0".
    #mytable {
    border: outset <value_of_the_attribute>px;
    }

    #mytable > * > tr > td,
    #mytable > * > tr > th {
    border: inset 1px;
    }
  • for the cellspacing attribute on the <table> element
    #mytable {
    border-spacing: <value_of_the_attribute>px;
    }
  • for the cellpadding attribute on the <table> element
    #mytable > * > tr > td,
    #mytable > * > tr > th {
    padding: <value_of_the_attribute>px;
    }
  • the rules and frame attributes on the table element is only a little bit more complex but it's a non-issue to map such an attribute to CSS rules.
  • the width, align and valign attributes on <table> and descendants of <table> are also a non-issue with a trivial mapping to their CSS counterparts
  • for the deprecated align attribute on <table>, a combination of 'margin-left: auto' and/or 'margin-right: auto'

In other terms, it's not a problem implementing an editor that provides a user wishing to insert a table with the following choice : "HTML attributes only", "Inline styles when possible", "Style rules or inline styles when possible". As a matter of fact, it's already implemented in BlueGriffon. Please don't focus on the UI since it's absolutely not final, it's even sure it's going to evolve a lot for instance to let the user reuse existing CSS style rules instead of creating new ones.

CSS policy

page 3 of 3 -