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.
Progress
03Nov
Language management
17:32 - By BlueGriffon - Progress
I've just added a context menu to the structure bar. The first menu item there is to manage the element's language.

08Oct
Zoom #2
12:31 - By BlueGriffon - Progress
Already working fine, only remain a few minor details to iron.

07Oct
Zoom
20:12 - By BlueGriffon - Progress - one comment
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
16:56 - By LaurentJ - Progress - 2 comments
Here are the last changes on the web site:
06Oct
Table layout dialog
16:08 - By BlueGriffon - Progress - 3 comments
It's only a beginning but it already works beautifully...

01Oct
CSS rules only...
10:20 - By BlueGriffon - Progress
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
borderattribute 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
cellspacingattribute on the<table>element#mytable {
border-spacing: <value_of_the_attribute>px;
} - for the
cellpaddingattribute on the<table>element#mytable > * > tr > td,
#mytable > * > tr > th {
padding: <value_of_the_attribute>px;
} - the
rulesandframeattributes on thetableelement is only a little bit more complex but it's a non-issue to map such an attribute to CSS rules. - the
width,alignandvalignattributes on<table>and descendants of<table>are also a non-issue with a trivial mapping to their CSS counterparts - for the deprecated
alignattribute 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.
page 3 of 3 - next entries »












