In relation to: https://bugzilla.wikimedia.org/show_bug.cgi?id=25124 - I
am considering removing $wgStyleDirectory rather than further depending
on it.
It seems that it's only partially used right now, and making the style
directory variable but not other directories is inconsistent as well.
There was some point about this being a feature that makes MediaWiki
more flexible, but I'm unsure this is actually adding flexibility, it
seems more like unnecessary complexity.
I'm considering just removing it - any points to the contrary would help
me make this decision.
- Trevor
Hey,
I'm doing some effort to use the Resource Loader in the Maps extension. A
problem I've run into is that I apparently cannot use things defined in
another module that already loaded. What I'm doing is loading the OpenLayers
library, and then another JS file that uses the OpenLayers library to create
the actual maps on the page. After looking at this with Firebug, I guess
it's a scope issue, as each module's contents is getting put in a function.
Are there currently ways to correctly load such libraries? And if not, what
would be a good way of creating this? Making a new class that derives from
ResourceLoaderModule?
Cheers
--
Jeroen De Dauw
* http://blog.bn2vs.com
* http://wiki.bn2vs.com
Don't panic. Don't be evil. 50 72 6F 67 72 61 6D 6D 69 6E 67 20 34 20 6C 69
66 65!
--
Hi,
FTP external link CSS looks like that:
#bodyContent a.external[href ^="ftp://"],
.link-ftp {
background: url(file_icon.gif) center right no-repeat;
padding: 0 18px;
}
The padding is 18px on the left AND on the right and 0px otherwise.
This is though I guess to reserve space for the small icon placed on the
right of the link.
I have two questions:
* Why we have defined a padding also on the left (and not set padding: 0
18px 0 0;)?
* Why on the online site we do not see the padding on the left?
I ask these questions, because after using the dumpHTML extension, I have
this issue:
I see the 18px big padding on the left with the static html files.
See this old bug report
https://bugzilla.wikimedia.org/show_bug.cgi?id=20828
Thanks for your help
Emmanuel
Hi All,
More Test Cases could be add to the existing Selenium Test framework. The
idea should be to test the main Wiki Editor functionalities and Page
view/preview functionalities in a smoke test suite.
The detailed administrative functionalities as User Preferences (more
advanced features as Managing Watch-list, Advanced options in Editing,
E-mail options) should be covered in a separate detailed test suite if
necessary.
Wiki Editor functionalities can be tested by automating "Content Addition"
in a new wiki page. All the basic text editing can be performed and should
be verified in page preview and saved page view.
The same page can be tested for "Content Editing" by performing same editing
functionalities in the previously saved page. The content changes can be
verified in page preview and saved page view.
Set Basic preferences can be tested separately and basic settings as Basic
Information, Signature, Date Format, Skin can be tested. The applied
preferences can be verified against the saved page.
The other utility functionalities as Search for Pages, Move Page, My
Watch-list, My Contributions, Delete Pages can be tested at the end of the
test suite. Delete Page functionality can be used to delete all the newly
created pages.
So the smoke test suite can be of 4 main test suites;
Add content to new Page (Wiki Editor for new page)
Edit content (Edit content in existing page)
Basic user preferences (Basic Information, Signature, Date
Format, Skin)
Extra features (search, move, delete, watch-list,
contribution)
All the above can be supported by some common functionalities as;
User Login
Search for Pages
Search and copy Text
Select applied skin
Get Page Name and other attributes (Page Headings/Titles
etc.)
Get text atttributes (bold, italic, font size etc.)
Regards,
Jinesh De Silva
Calcey Technologies - <http://www.calcey.com/> www.calcey.com
Voice: +94 11 2827560
Fax : +94 11 2827561
One week ago, I requested that LiquidThreads would be
activated on sv.wiktionary. Nothing happened.
https://bugzilla.wikimedia.org/show_bug.cgi?id=25761
The background is that sv.wikisource requested this
in April, finally got it activated on August 28, and
has been very happy with using it. It took four months
because the software wasn't ready for launch, but
that excuse is not valid anymore.
Pt.wikipedia is also waiting, since Augusti 28,
https://bugzilla.wikimedia.org/show_bug.cgi?id=24971
What's up? Anybody home?
--
Lars Aronsson (lars(a)aronsson.se)
Aronsson Datateknik - http://aronsson.se
Hi,
I'd like to add a hook to the getPoweredBy() function in
/includes/Skin.php - the function that sets the "Powered by MediaWiki"
button - so that other extensions or systems could add their own
buttons. I'm thinking to call it "SkinGetPoweredBy". Any objections?
-Yaron