This is my project http://www.mediawiki.org/wiki/User:Making-it-yours for GSOC - 2013, which I hope haven’t interested you.
Recently, I encountered with an analogy for my project which I wish to discuss with you so that I can persuade you. Head to this https://play.google.com/store/books and select a free book ( say Pride and Prejudice). Select some text and see how elegantly we can do operations I wish Wikipedia must have but not limited to. I can't get the technology they use for this. I wish you could figure out. Please help me with understanding it.
Hope it makes you love it.
Kind Regards
Vishal
Hi,
I have made prototype extensions for Firefox and Chrome related to this
project.
These extensions port jQuery.IME completely to the client side and can be
installed in the browser.
These extension would allow users to use multilingual input methods on any
website and not just on MediaWiki enabled websites.
Source code and installation instructions are available at:
https://github.com/pravee-n/prototype.jquery.ime
Let me know if you have any queries. I would love to get some suggestions
regarding how to improve these extensions.
Hi folks,
A few months back, we switched to updating the WMF Engineering Roadmap
in Google Docs[1], and deprecated the on-wiki version. This wasn't an
ideal solution, but the way that we were doing updates before also
wasn't working, so it was worth trying something else.
Now there's a script[2] to update this page, which we've used for a
couple of weeks now. The page is here:
https://www.mediawiki.org/wiki/Roadmap
The page is output as old-school subpage templates now, which isn't
perfect, but has the advantage that there's a lot of latitude to
reformat the page without altering the script. Feel free to play
around with the formatting.
The next step I'm planning to take is to output the page as something
that can be loaded via Scribunto's loadData call, which then will make
it pretty easy to include portions of the output in other pages.
This isn't in Gerrit yet, but that's only because I haven't quite
figured out where it should live. Suggestions welcome (offlist or on
my talk page[3] is probably best for that).
Rob
[1] Google Docs version:
https://docs.google.com/a/wikimedia.org/spreadsheet/ccc?key=0Aoizbfxc5g6KdE…
[2] Script: https://gist.github.com/robla/5416776
[3] My talk page: https://www.mediawiki.org/wiki/User_talk:RobLa-WMF
On Sun, May 12, 2013 at 10:56 AM, Dmitriy Sintsov <questpc(a)rambler.ru> wrote:
> On 12.05.2013 1:18, Tyler Romeo wrote:
>> FWIW, here is what I have so far: http://pastebin.com/hUQ92DfB
>
> Perhaps you should send the link to HipHop developers (or to their list, if
> there's any).
Unfortunately, they don't have a mailing list yet. We discussed that
with them in the meeting we had this past week, and we agreed it would
be a good idea to have one, hence this request:
https://bugzilla.wikimedia.org/show_bug.cgi?id=48391
In the meantime, there is a Facebook page you can post to:
https://www.facebook.com/hphp
Rob
Several people from the HipHop team at Facebook just met with several
people from WMF. Also, in the last couple of days, I've been doing
some research into what it would take to make MediaWiki support HipHop
VM. The answer is: not very much.
There's two features that we use, mostly in extensions, that the
Facebook people are not keen to implement due to their complexity:
ArrayObject and filter_var(). It seems that it would be much easier
for us to stop using them than for those features to be implemented in
HipHop.
So I'd like to suggest that we refuse new code submissions in Gerrit
that use these features, if they are targeted for WMF production, and
that we start work on migrating away from the existing uses of those
features.
There's a few other SPL features that we don't use at the moment and
we should avoid introducing if possible due to lack of support in HipHop:
* CachingIterator
* EmptyIterator
* GlobIterator
* InfiniteIterator
* LimitIterator
* MultipleIterator
* NoRewindIterator
* ParentIterator
* RecursiveArrayIterator
* RecursiveCachingIterator
* RecursiveFilterIterator
* RecursiveRegexIterator
* RecursiveTreeIterator
* RegexIterator
* SplDoublyLinkedList
* SplFixedArray
* SplHeap
* SplMaxHeap
* SplMinHeap
* SplPriorityQueue
* SplQueue
* SplStack
* SplTempFileObject
We are not yet promising that we are indeed going to start using
HipHop in WMF production, and we don't have any timetables. But HipHop
has evolved to the point where supporting it is almost trivial, at
least for test installations, so I think it makes sense to establish
policies which will avoid making migration to HipHop more difficult.
-- Tim Starling
Hi everyone,
I've just installed VisualEditor + parsoid for mediawiki. This is the my
configurator:
---> localsettings.js
exports.setup = function( parsoidConfig ) {
// The URL here is supposed to be your MediaWiki installation root
parsoidConfig.setInterwiki( 'localhost', '
http://www.startupperday.com/api.php' );
// Use the PHP preprocessor to expand templates via the MW API
(default true)
//parsoidConfig.usePHPPreProcessor = false;
// Use selective serialization (default false)
//parsoidConfig.useSelser = true;
// allow cross-domain requests to the API (default disallowed)
parsoidConfig.allowCORS = '*';
};
---> LocalSettings.php
require_once("$IP/extensions/VisualEditor/VisualEditor.php");
// Create VisualEditor namespace
define( 'NS_VISUALEDITOR', 2500 );
define( 'NS_VISUALEDITOR_TALK', 2501 );
$wgExtraNamespaces[NS_VISUALEDITOR] = 'VisualEditor';
$wgExtraNamespaces[NS_VISUALEDITOR_TALK] = 'VisualEditor_talk';
// Allow using VisualEditor in the main namespace only (default)
$wgVisualEditorNamespaces = array( NS_MAIN );
// Restrict VisualEditor to the VisualEditor namespace
#$wgVisualEditorNamespaces = array();
#$wgVisualEditorNamespaces[] = NS_VISUALEDITOR;
// Enable by default for everybody
$wgDefaultUserOptions['visualeditor-enable'] = 1;
// Don't allow users to disable it
$wgHiddenPrefs[] = 'visualeditor-enable';
$wgVisualEditorParsoidURL = 'http://www.startupperday.com:8000/';
---> but when I try to save everything in mediawiki I get:
TypeError: Object.keys called on non-object
at Function.keys (native)
at Object.WikiConfig (/srv/
www.startupperday.com/Parsoid/js/lib/mediawiki.WikiConfig.js:41:20)
at null.<anonymous> (/srv/
www.startupperday.com/Parsoid/js/lib/mediawiki.parser.environment.js:300:22)
at processSome (/srv/
www.startupperday.com/Parsoid/js/lib/mediawiki.ApiRequest.js:98:17)
at process._tickCallback (node.js:415:13)
Can you help me? :(((
--
*Marco De Nadai*
http://www.marcodena.it/<http://www.marcodena.it/?utm_source=email&utm_medium=email&utm_campaign=Ema…>
--
*Marco De Nadai*
http://www.marcodena.it/<http://www.marcodena.it/?utm_source=email&utm_medium=email&utm_campaign=Ema…>
Hi everyone!
What tools do you use for a small tasks in Google Summer of Code? I mean
the tasks like "prepare the working environment", "learn gerrit", "write a
blogpost", etc.? I thin that bugzilla is too heavy for this purpose.
Also can we use microblogging for reporting the current progress (in
addition to posts in a blog one in 2 weeks )? I tried that once and it was
very fun and efficient.
Cheers,
-----
Yury Katkov, WikiVote