quick pane. The quick pane is now divided into 4 sections: left, center, right and
additional. Additional items appear in the drop down box. Buttons are not sorted
within the groupings.
In addition, the quick pane will overflow onto the "additional" dropdown if there is not
enough room to display all the buttons.
The use case is the digibug printing module needed to add a button to the quick pane, and
I don't like putting code into core that says if module is active... That's another one
of those code smells :-)
Signed-off-by: Tim Almdal <tnalmdal@shaw.ca>
be smart about it. If we see a comma or a semicolon, expect the keywords to be separated
by that delimeter. Otherwise, use space as the delimiter.
Fixes ticket #446
only implementing schema version 1. This caused install.sql to be
populated from version 1 which meant that after install you'd have to
run the upgrader. No harm done, and the pattern is fixed for the
future.
Alphabetize the tables so it's easier to find stuff.
1) Put a "starting up..." message before there's any feedback from the server
2) show the title of the task in the dialog.
Signed-off-by: <unostar@danalan.info>
encoding issues resulting from embedded keywords in encodings we can't
decipher. This can lead to weird truncation issues which in turn can
lead to multiple tags getting truncated to the same value in MySQL
which leads to mysql complaining that we're adding a duplicate tag.
Signed-off-by: <unostar@danalan.info>
returns an error, and log them appropriately. This should fix a slew
of import failures from corrupt G2 installs.
Signed-off-by: <unostar@danalan.info>
encoding issues resulting from embedded keywords in encodings we can't
decipher. This can lead to weird truncation issues which in turn can
lead to multiple tags getting truncated to the same value in MySQL
which leads to mysql complaining that we're adding a duplicate tag.
Move the creation of the setting menu back to gallery_menu::admin, now that
there is a mechanism to remove empty menu items
Signed-off-by: <unostar@danalan.info>
1) Stored the menu element type in the menu element
2) Scanned the menu before display removing any empty sub menus.
Went with the removal approach because there will more users than developers
Signed-off-by: <unostar@danalan.info>
1) Stored the menu element type in the menu element
2) Scanned the menu before display removing any empty sub menus.
Went with the removal approach because there will more users than developers
Bharat Mediratta
Tim Almdal
Andy Staudacherand