-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UI with tabs #153
UI with tabs #153
Conversation
Nice, thank you, Pedro! Do you have WP_DEBUG on in wp-config.php? If not, turn it on next time you develop. I got a few notices, like "Undefined variable: qtx_admin_section_4 in on line", on the first try of page http://w.marina.soutyrine.com/wp/wp-admin/options-general.php?page=qtranslate-x, right after the pull, but this is ok, I will clean it up. Is there a way to make tabs look a bit fancier, like maybe rounded a little bit? Some kind of 3D look? Also blue rectangle around active tab might look better if it has 3 sides only, without bottom? Just something to play with if you have time, otherwise it is not important. It is much more convenient and up-to-the-state-of-art this way. Thank you very much 👍 |
This was a start, some code can be deleted, but I've just commented it for further review and minimize commitdiffs. Some stuff that I would also like to remind you, of course I hope you already checked all this before merging.
|
Well, no. I'll check on this later. About that variable, I just replicated the code as you can see. Probably it's somehow related to it being on other file. One thing I must say, in one of my first attemps to clean the code before I started to implement the tabs, I did put the Import/Export section within the same file, without the need to use the include. It worked well, but it would be much difficult to understand the pull request. The code would benefit a bit with a parcial cleanup on that file.
I'm sure that there is a way to do that, I just did a simple mechanism, and for plugin settings and configuration I do prefer a perfectly integrated with it's native mother framework, usually it allows it to grow together with core WordPress. If it changes the native admin CSS, qTranslate-X will keep in perfect harmony with it, with no need to override stylesheets.
Much more comfortable to navigate and a lot less mouse scrolling :) |
Pedro, I cleaned it up and pushed. I added functionality:
The most difficult part for me would be to figure out the proper CSS for tabs, which you did perfectly - thank you again. I did not know that WP has some pre-arranged CSS for tabs. If so, indeed we should stick with their version, this is the safest and the simplest way. Pedro, @Grafcom, @Gunu, could you please try to test it now as much as you can, switching, pressing buttons, making sure it does what it is supposed to do? |
Hi
I found that in some plugins and I in some WordPress API info that I cannot find right now, but yes, it's the most safest/simplest version you can get. As far as I tested, it looks fine now. |
Thank you, Pedro! |
Here is one of the links on CSS of the WordPress backend. It's not in the oficial codex site, and the behaviour is not the same, as it pushes the form on each tab pressed, but the css is the same: |
Thanks! This is useful to know. |
Brand new PR to substitute the old #135 (comment) that was getting too long and intrincate so sync with changes from both sides.
This adds exactly the same simple code bits, and it's now on top of latest
master
branch.