Argos theme

[Argos]

Guys,

just to let you know: I'm working on a new version of my backend theme. I did some error fixing and right now I'm working on a jQuery tabbed interface for the (loooooong) Settings page. Actually I just finished the mechanics, and it works like a charm. I have created 5 tabs, and within each tab you can switch between basic and advanced settings. I have to fix some styling and layout errors, but the technical stuff works. I'll attach some screenshots to show where it's going.

After that I'll see what other improvements I could do. Maybe some more tabbed stuff if it's useful, I don't know.

Any requests?

[gelöscht durch Administrator]

[Waldschwein]

Hello!

Suggestions:
- As I think to improve anything with user/group management you need to change Core / need a module I let that out.
- A good thing would be the implementation of a context-based help of the whole backend, perhaps with redirect to help site or language files. But I also think that's something bigger.
- Tabbed interface is great for settings!
- For the add-on detail site: Would it be possible to realize that also with jQuery, the page doesn't load new but just a "info-box" pops out on the same site? I use the details quite often to control which version the module / templates have...
- The argos_theme/images/up_folder_16.png in media doesn't look that nice (even if I colored it some time ago for 2.7 backend   ).
- As I think moving folders & files in media folder is Core based but not realizable with a theme like the resize function, I just mention it...
- I hope they will adjust the footer to WebsiteBaker, and the link to www.websitebaker2.o rg... I will write a ticket.
- There should be a new icon for the new add_child_page in 2.8.1, but I think that's an usability error of the Core...
- Backend preview with integrated browser, real frontend editing and a new access system.... Just kidding.  

Yours Michael

[Argos]

- As I think to improve anything with user/group management you need to change Core / need a module I let that out.

Yep, that's core stuff. I won't touch that.

- A good thing would be the implementation of a context-based help of the whole backend, perhaps with redirect to help site or language files. But I also think that's something bigger.

Sorry, not for now...

- Tabbed interface is great for settings!

Yes, I think so too. I'll see if I can modernize other sections as well.

- For the add-on detail site: Would it be possible to realize that also with jQuery, the page doesn't load new but just a "info-box" pops out on the same site? I use the details quite often to control which version the module / templates have...

Hm... I really don't know, but I will have a look if I have time.

- The argos_theme/images/up_folder_16.png in media doesn't look that nice (even if I colored it some time ago for 2.7 backend   ).

I'll check that!

- As I think moving folders & files in media folder is Core based but not realizable with a theme like the resize function, I just mention it...

Well, the resize function needed some admin coding changes, but I'm not doing that now. What do you have in mind with "moving files and folders" exactly?

- I hope they will adjust the footer to WebsiteBaker, and the link to www.websitebaker2.o rg... I will write a ticket.

I will have to check that with the developers.

- There should be a new icon for the new add_child_page in 2.8.1, but I think that's an usability error of the Core...

I agree, two plusses on a line is not ideal.

- Backend preview with integrated browser, real frontend editing and a new access system.... Just kidding.  

We have to keep our dreams, haven't we? LOL

[doc]

Hi Argos,

again a great step forward. Not only but especially on large screen resolutions, your template fits much better than the "default" one. From my point of view, the Argos theme should become the default "backend" theme, as this has really a "modern" look and feel and is some other improvements (e.g. the media stuff), which makes working much easier.

The idea of having the jQuery tabbed stuff is great. Hope your solution also works if Javascript is disabled (at least as long this is not a requirement of the WB core). Beside the DOM handling, the ability of writting unobtrusive Javascript solutions is one of the biggest benefits of the jQuery.

Hope your improvements will find its way into the WB 2.8.1 release. At usual, best things comes last
Keep up your great work.

I hope they will adjust the footer to WebsiteBaker, and the link to www.websitebaker2.o rg... I will write a ticket.

Solved in Changeset 1264

Doc

P.S.: If you have something to test, please post it and for sure you will get some more feedback

[YoJoe]

I got 1 request.
After creating page, adding to it couple wysiwyg sections, it would be nice not to have them all being loaded at start, but rather rolling/unrolling wysiwyg textareas indiwidually.

Having 5-6 wysiwyg windows takes too much time to load them.


edit: I see u base on default wb backend template.
Any chance you are going to improve gfx by creating own css ?

[Waldschwein]

I got 1 request.
After creating page, adding to it couple wysiwyg sections, it would be nice not to have them all being loaded at start, but rather rolling/unrolling wysiwyg textareas indiwidually.

Having 5-6 wysiwyg windows takes too much time to load them.

Hello!

With WB 2.8.1 under "managing sections" you can access each section individually without loading the others.
But it would be nice.

Yours Michael

[YoJoe]

Well, that's quite a method. But this isn't the thingy.
I would like to open page for editing couple wysiwyg sections at once.
But everytime I open a page with 5-6 sections it take ages to load all fckeditor instances.
Thats why it would be nice to load them using jquery, after unrolling a section I want to edit.

But you gave me an idea. But I doubt it would be doable without messing in core files.
You said about managing sections. Would it be possible to edit them using jquery, not to edit every section individually by entering it, which cause the reloading the page ?

[Stefek]

Well, that's quite a method. But this isn't the thingy.
I would like to open page for editing couple wysiwyg sections at once.
But everytime I open a page with 5-6 sections it take ages to load all fckeditor instances.

The loading time will be reduced once the CKEditor ist out.

Regards,
Stefek

[YoJoe]

The loading time will be reduced once the CKEditor ist out.

what do you mean ?
WB is going to get rid of fcke ?
What else wysiwyg editor is going to be used then ?

[Stefek]

The loading time will be reduced once the CKEditor ist out.

what do you mean ?
WB is going to get rid of fcke ?
What else wysiwyg editor is going to be used then ?

No, but there is a new Version of "fck" called CKEditor.
This version is faster than any other feature rich WYSIWYG editor on the os market.

Regards,
Stefek

[Stefek]

Not only but especially on large screen resolutions, your template fits much better than the "default" one. From my point of view, the Argos theme should become the default "backend" theme, as this has really a "modern" look and feel and is some other improvements (e.g. the media stuff), which makes working much easier.

I agree, that Jurgens Theme is better in many points as the default WB Theme.

However, to be the "default one" it should fit more to the WB like design to represent it well.
I also think a WB Logo should be part of the default theme - that's not at least important for screenshots of the backend for marketing purposes. 

Jurgen, I hope you don't get me wrong.
As many people know I have also created a Theme for WB Backend by myself which is very modern, but unfortunatly I don't have the time (not yet) to make the needed fine tuning, which is needed before I present it to the community.
However, my work started a long time ago and was never meant to be a "battle" with your work    (as some people do like to suggest).

I think the default Theme should be representative for WB as CMS in any aspect - and still modern and attractive.
It may be that I am alone with this considerations... wouldn't be the first time.
But besides functionality, there should be somthing representative for WB to become "standard".

Stefek

[Argos]

The idea of having the jQuery tabbed stuff is great. Hope your solution also works if Javascript is disabled (at least as long this is not a requirement of the WB core). Beside the DOM handling, the ability of writting unobtrusive Javascript solutions is one of the biggest benefits of the jQuery.

Hi Doc,

thanks for the thumbs up! No, the tabbed interface and Basic/Advanced switch doesn't work without javascript. But the regular admin themes need JS as well. For exampe the old style Basic/Advance switch also needs JS, and so does the page tree opening/closing, etc. I don't think there are many people who expect to operate a CMS with JS disabled... And if they do, they are not of this world.

[Waldschwein]

However, to be the "default one" it should fit more to the WB like design to represent it well.

You haven't seen the new "WB like" CI.  Because there argos_theme would fit best from the three ones... About 60%, the others only 40%. 

Yours Michael

[Stefek]

However, to be the "default one" it should fit more to the WB like design to represent it well.

You haven't seen the new "WB like" CI.  

Sure?

[Argos]

Stefek,

I have absolutely no problem with you or others making backend themes, on the contrary. I look forward to your version once you have found the time to finish it. Contributing to WB has nothing to do with battles whatsoever  

I would love to see my theme become the default, but that's not my intention. But if the developers like to have my theme as a basis for a new default one, I'll be more than glad to give it a more "WB compliant" design in new versions. But that won't be for WB2.8.1 I'm afraid.

I'm reworking the Settings section from tables to DIV's now. Almost finished. Much cleaner and better!

[Stefek]

Stefek,

I have absolutely no problem with you or others making backend themes, on the contrary. I look forward to your version once you have found the time to finish it. Contributing to WB has nothing to do with battles whatsoever 

I would love to see my theme become the default, but that's not my intention.

I'm reworking the Settings section from tables to DIV's now. Almost finished. Much cleaner and better!

Sounds great Jurgen.

Good Luck with it.

I really wished I had the time, but unfortunatly (or luckily) I have a lot of things to do customer wise.

I like the special functions of your theme and it would be a great Idea to have ONE standard Backend theme delivered/shiped with WebsiteBaker.
Why not yours?
At this time you are making the most on this and I think it where a good thing (also for core devs) to concentrate on ONE theme.

This scenario with "updating all three themes every time something changed in the admin directory" is exactly what I was saying one year ago. But no one listened to a designer *L*

But if the developers like to have my theme as a basis for a new default one, I'll be more than glad to give it a more "WB compliant" design in new versions. But that won't be for WB2.8.1 I'm afraid.

This is a good Idea.

Best thing would be to finally get rid of three shipped Themes along with WB.
It costs too much time in developement in apdating them all again and again.

Kind Regards,
Stefek



 

[Argos]

I agree completely 

[doc]

Hi,

But the regular admin themes need JS as well. For exampe the old style Basic/Advance switch also needs JS, and so does the page tree opening/closing

Uups, thought this also worked without JS disabled. However, jQuery is very powerfull in introducing additional functionallity only if JS is enabled.

Regarding the themes. Yes I think one "finally worked out" backend theme would be enough to ship with WB, other themes should be available for download as normal templates once the "technical things behind" are sorted out and guidelines are established for creating themes.

As long as the Argos theme is part of the WB installation package and/or can be downloaded for free seperatly, I don´t care too much

Doc

[Stefek]

Regarding the themes. Yes I think one "finally worked out" backend theme would be enough to ship with WB, other themes should be available for download as normal templates once the "technical things behind" are sorted out and guidelines are established for creating themes.

I agree.

I think its important to have one working Theme which is easy to customize with a minimum of effort.
I also think that at the moment 3 shipped Themes pull to much attantion - attantion needed to make one really working an represenative Backend Theme.
I hope the devs (allthough this has more to do with marketing then with core) get this point, stop shipping three Themes and concentrate on one stable, working solution instead.
For this purpose there should /or could/ be started a own sub dev team, dedicated completely to the Usability and Workability of the Backend Theme (with some help core wise to figure out the core things needed to synchronise with the Themes).
Such a Sub Team would also be able to make guidelines (and recomendations) for use with Modules (Backend Templates for the modules).


If you get me right, you'll soon see how important this could be for a appropriate Marketing of WB and its Modules.
One important part of Marketing has to do with making a good product visible and real.
We should concentrate on the reality of 2010 and stop shipping 2004 Themes with this wonderfull product.

Such a Board (sub team) was a dream of mine about a year ago.
And I still find that this is one of the most important (and most neglected) things in order to rise websitebakers Quality (and beyond).

This is something where the dev team shouldn't be involved to much into.
The Dev Team doesn't "sell" the product, has no need to do so.
Only if new Features needs to be integrated into the backend, they would work along with the Theme Board to get it implemented. It should be handled as a separated activity but with help in both directions.

Stefek

[maverik]

please have a look at options with ie8

[gelöscht durch Administrator]

[Luisehahne]

If you give the setting_name and setting_value in the CSS file a percentage value, it will be fixed.

@Argos
Better check out the newest version, because some problems with validation were eliminated.

Dietmar

[Argos]

The IE8 error is fixed in the new version. You can try either Dietmars solution (I did something else, with the same effect) or switch to compatible mode in the mean time.

[Argos]

Houston, we have a problem!

I finished the Settings section, and it looks good for now. However, the very last bit in the Mailer Settings (the SMTP stuff) causes problems. The old style javascript there conflicts with the jQuery. Due to that a lot of menu selections in the complete Settings menu, don't show the right values anymore, but error warnings. See the screenshot. If I remove the old javascript, the complete Settings works fine fine again (apart from the very last Mailer settings bit).

The problem for me is that I'm not good enough to restyle the old style javascript into compatible jQuery. Simple hide/show stuff I can do, but that part is a bit more complex, because it shows/hides content based on user choices, and also stores values at the same time. That's over my head.... I need a helping hand here. Who is able and prepared to have a go at it?

You can check what happens if you open the settings.htt file, and look for the DIV <div class="settings_table2 showhide"> that begins at line 608. If you remove that DIV, the Settings section menus work fine, but with the DIV added you will see many menus don't show their values anymore.

[theme removed to prevent people actually using it]

[gelöscht durch Administrator]

[Luisehahne]

Now i could unzip, But i have to post it here, be carefull do use this wonderfull styled theme. Settings not working (Javascript errors), footertext not correct, something we fixed is buggy again, no validate code. Sorry Jurgen, but i think we have to talk per mail to fix the issues. I don't want to discuss here in the forum.

Only the users have to know, that new argos_theme will not be added to the actuell release.

Dietmar

[Argos]

Okay, I used RC2 to work on. I did some minor changes to / admin / pages / settings.php and the Dutch language file as well. Maybe that causes errors in your site. Let's discuss it further privately. I'll remove the theme from the post.