About 2.8.1 RC 2

[instantflorian]

Hi,

thanks for improving WB 2.8.

I don't know if this is the right place for it, but I've got some annotations about the backend of 2.8.1 RC 2:

- on a wide screen, the positions of the WB logo, the function buttons and the revision information look a little bit strange, because the width of table in the header ist still only 900 pixel
- the space for entering the short text of news is too small (due to the lots of functions of FCKE)
- the new added function for selecting the parent page directly in the list of pages is quite usable, but the "+"-icon on the right side should be replaced. It's not very usable to use the same icon for different functions.
There are several nice icons in the famfamfam icon set which could be used instead

Other icons and the screenshots see http://test.meerwinck.com/wb281/pages/screenshots.php


FCKE features:
- at the modifyed "Image options" dialogue of the FCK Editor (image link) the input field for the link target should be bigger; if you add a css class, this will not occur in the frontend
- the icon for "image button" (form) and "add image" are the same, this is not very usable 

Regards

-instantflorian.

[Waldschwein]

Hello!

Yes, I can absolutely say the FCKEditor is in this "static" height not very comfortable usable. Due to the 9x0 px width the height is not really fitting to the width.
Suggestion: Either adjust the static height in the template or (better one...) use the JQuery script (Bianca spoke about it...) in Core and default you can adjust the position of FCKeditor as you want.

Another thing: I open yet a ticket some weeks ago http://project.websitebaker2.org/ticket/888 but the YUI is still the same outdated version, and you get very, very nasty errors in IE8 when using Drag&Drop. The YUI package yui_280r4_wb281_new readme.zip there is really usable as it is and at least gets rid of the error with making the whole IE8 unusable...

Yours Michael

[Luisehahne]

call the initialize.php in framwork folder, and set the constant EDITOR_WIDTH to 0, to get the width settings by modules. May be later to set it in backend settings

Dietmar

[Argos]

Not really a solution to the problems mentioned, but you could use the argos_theme backend for better usability. Although IE8 does some weird stuff with the column width of the settings page there. I'm working on an update for RC3 (or Final?), that has bug fixes and other improvements.

[tiggerific]

Ahh... I was just thinking about you well, not you in particular.

I use your Argos back-end theme for all new client sites since you have made it available (thank-you). It's clean and professional, and the media section is great.

I have just now submitted a feature request regarding the display of the Menu Name or number in the Page Tree. Perhaps this can be done with just template changes? Here's my feature request:

http://project.websitebaker2.org/ticket/929

[kweitzel]

Hi,

thanks for this, is ist by any chance possible to get the sample code you used in your implementation?

You should be able to post it inline (use the Code Block feature) or attach it to this ticket.

cheers

Klaus

[Argos]

@tiggerific : that's a nice idea, I will have a look if I can create that (thanks for the compliment, by the way!).
@kweitzel : I'm not sure what you mean and who you are talking to  

[kweitzel]

@kweitzel : I'm not sure what you mean and who you are talking to  

it was a direct reply to the post above mine ... also copied in the ticket

cheers

Klaus

[Argos]

Ah! I overlooked the "made the modification myself" part in his request ticket... Yes, that part is not that difficult to show I guess. Dividing the menus is harder, but would be cool.

[instantflorian]

Hm... this kind of ordering reminds me very strong to Joomla.
I would prefer not to change the default core of WB in that way.
Maybe this could be a special backend template or addon, sth. in that way.

[Argos]

Hm... this kind of ordering reminds me very strong to Joomla.
I would prefer not to change the default core of WB in that way.
Maybe this could be a special backend template or addon, sth. in that way.

The Joomla menu setup is much more complex than WB. WB cannot link a page to more than 1 menu, so that poses a problem I didn't think of before. What to do with child pages that belong to another menu than their parent? Now they are shown in the tree under their parent, but if a backend tree is not the same as a site menu, you would have a problem. Do you show the "technical" tree, or the menu tree? Hm... it may be more complex than it looked at first sight. I think we should leave it at showing the menu name or menu ID, and not visually divide the tree into menus.