Help
Add this page to your book
Show book (0 pages)
Suggest pagesUser talk:Sergey Chernyshev
Contents
| Thread title | Replies | Last modified |
|---|---|---|
| Extension: Google Presentations | 0 | 18:33, 27 February 2012 |
| talk back | 0 | 00:40, 16 December 2011 |
| Extension:Header Tabs | 2 | 05:26, 3 December 2011 |
| New Orleans developers' get-together | 0 | 23:48, 24 August 2011 |
| Template:Maintainer sought-after | 1 | 20:10, 17 May 2010 |
| Extension:OpenID | 2 | 22:17, 16 May 2010 |
Hi, Sergey! Thanks for your work! Can I ask you whether there are plans to make the widget compatible with new google presentations?
You can remove this notice at any time by removing the {{Talkback}} or template.
Could you answer any of the questions there? thanks for your hard work!
Hello Sergey, I am currently working on some feature additions to Header Tabs for a private wiki and thought that maybe I could contribute back. You can see my development version running Sandbox but be aware it's not the final version, I'm still playing around with various UI elements. I hope to have the code publicly reviewable soon.
All features were added to the 1.17 jquery branch only:
- hash tag with tab or heading id now open the correct tab automatically on page-load
- $htTabNameInURI=true: If you click on a tab, it appends the hash for it to the URL so that bookmarks load to the correct tab
- $htAlwaysOn=false: If no <headertabs/> is found, inserts it at the end of the article. You can still use the tag to end tabs earlier
- $htRenderSingleTab=false: If only one tab is found, should we show tabs? Default is no. (change from current behaviour)
- $htDefaultFirstTab=false: If set to a string like 'General', automatically puts everything 'above' the first specified tab into this tab.
- $htDisableDefaultToc=true: The default TOC now works properly because the anchors load the right tab, however in most cases you still do not want to show a huge TOC above the tabs (maybe only if your skin puts them beside?). This disables the TOC only if tabs are being shown, if they aren't, then the TOC remains wherever it was inserted.
- $htGenerateTabTocs=true: Generates a TOC for each tab, but only if standard MW would usually generate a TOC for the headers found in the tab.
- $htEditTabLink=true: Adds a 'edit tab' link, I am currently playing with two ways of doing this, either in the top far right MW vector tabs, or by putting a section-style 'edit' link on the far right of the Tabs.
- $htAddTabLink=false: Adds a 'new' link, I am currently playing with 3 ways of doing this, either in the top far right MW vector tabs, using a '+' tab like browsers do, or by putting a section-style edit 'new' link on the far right of the tabs.
- $htStyle=false: A new style interface for tabs, the most popular from Extension:Header_Tabs/JQueryStyles could become standardized named styles you can use here. For now I've just added 'bare'.
- $htDisableInNamespaces=array(MAIN_TALK, USER_TALK): List of TALK namespaces where tabs will not be displayed if using the $htAlways on flag. This is to facilitate people using $htAddTabLink
- New magic words to match similar article-wide actions. __NOTABTOC__, , __NOTABEDITLINKS__, __NOTABNEWLINK__, __NOTABS__ will be added (next on my list)
I've done a bit of cleaning up of some of the code:
- ResourceLoader is now used properly and javascript is in
HeaderTabs/skins-jquery/ext.headertabs.core.jsand css in modules, for example,HeaderTabs/skins-jquery/ext.headertabs.bare.css - Support for Extension:Configure
- the 'skins' folder has been renamed 'skins-yui' so people stop changing those files on MW 1.17 thinking it will affect jquery
Of course as it currently stands I have a few problems:
- $htRenderSingleTab and $htDefaultFirstTab cannot both be true, it puts tabs in things like the 'last edited at' line because more then article text is fed into the Parser.
- $htAddTabLink only works if you change MediaWiki:Newsectionheaderdefaultlevel to insert level-1 headers instead of level-2 headers. This change of course affects talk pages, which now become tab-heavens with $htAlwaysOn hence the use of $htDisableInNamespaces
- Some of my implementations may have better solutions, for example I hope to find nicer ways to generate the tab TOCS, and fix how the browser snaps down when viewing a tab with a TOC.
I hope to establish a new 'default' state that is not it's current state:
- $htAlwaysOn=true, $htDefaultFirstTab='General', $htStyle='bare' -- I believe this is a much better experience out of the box, however large wikis who for some reason use level 1 headers extensively will want to disable the alwayson, and wikis already using the tabs heavily for forms who want more of a visual cue may want to keep style at false.
While I could keep maintaining my version, I have SVN access and I was hoping that you would be open my collaborating with you and Yaron on Header Tabs. I'm committed to continuing to improve the features, and generally supporting the extension. I hope we can merge the changes outlined above with the main Header Tabs and continue to improve the extension. I'm very open to your feedback on these features as well.
Olivier,
It's great to see that you invested the time to maintain what I started! More over almost everything you're mentioning was requested already by users and is not there only because of lack of time on my end.
I'm definitely open to the idea and I think Yaron will be happy to see your contributions go into the code.
Unfortunately, can't work on the extension myself - too much other stuff in my life now, but don't see why it should stop such an awesome tool (if I say so myself) from continue to be developed.
Since Yaron (and Jeroen) are taking over most my extensions, I would suggest contacting them and going ahead!
I'd like to invite you to come to the New Orleans Hackathon 2011. We're getting together folks like you -- template, script, tool, extension, and gadget writers -- to participate, give feedback, test, and hack with us.
At the event, MediaWiki developers and Wikimedia operations engineers will be working on Wikimedia's gadgets/extensions/tools support, authorization/authentication strategy, dev-ops virtualization, and general training and hacking. And we'll improve and discuss the Wikimedia Labs projects infrastructure and other stuff that makes it easier for anyone to supercharge Wikimedia with awesomeness.
The event is open to anyone who wants to come and contribute, and is an opportunity to spend time with senior MediaWiki developers & ops engineers, write beautiful code, and learn about the latest developments. We'll write code together, discuss the software, and hold little workshops.
If you can make it to New Orleans, Louisiana, USA, 14-16 October 2011, we'd love to have you. Please add your name to the attendees list. Thanks! Sumanah 23:48, 24 August 2011 (UTC) (Volunteer Development Coordinator, Wikimedia Foundation)
Hi Sergey, please do not feel offended by my edit today. Usually sections like these get manhandled by link spam. I did not expect this list to be moderated. Cheers --kgh 21:28, 16 May 2010 (UTC)
