Hi Erik,
> our very positive revenue perspective (we have already exceeded our
> fundraising targets for the fiscal year, and received the additional
> $2M from Google) allows us to do something we've hoped to be able to
> do: make our investment in user experience work permanent, as opposed
> to
Hello all,
our very positive revenue perspective (we have already exceeded our
fundraising targets for the fiscal year, and received the additional
$2M from Google) allows us to do something we've hoped to be able to
do: make our investment in user experience work permanent, as opposed
to releasin
On Mon, Mar 1, 2010 at 3:26 PM, Daniel Kinzler wrote:
> Marco Schuster schrieb:
>> The point of $IP is that you can use multisite environments by just
>> having index.php and Localsettings.php (and skin crap) in the
>> per-vhost directory, and have extensions and other stuff centralized
>> so you
> -Original Message-
> From: wikitech-l-boun...@lists.wikimedia.org
> [mailto:wikitech-l-boun...@lists.wikimedia.org] On Behalf Of
> Ævar Arnfjörð Bjarmason
> Sent: 01 March 2010 13:34
> To: Wikimedia developers
> Subject: Re: [Wikitech-l] hiphop progress
>
> On Mon, Mar 1, 2010 at 10
Marco Schuster schrieb:
> The point of $IP is that you can use multisite environments by just
> having index.php and Localsettings.php (and skin crap) in the
> per-vhost directory, and have extensions and other stuff centralized
> so you can update the extension once and all the wikis automatically
The point of $IP is that you can use multisite environments by just
having index.php and Localsettings.php (and skin crap) in the
per-vhost directory, and have extensions and other stuff centralized
so you can update the extension once and all the wikis automatically
have it.
However, the Installer
On Mon, Mar 1, 2010 at 13:35, Domas Mituzas wrote:
> Still, the decision to merge certain changes into MediaWiki codebase (e.g.
> relative includes, rather than $IP-based absolute ones) would be quite
> invasive.
> Also, we'd have to enforce stricter policy on how some of the dynamic PHP
> feat
Howdy,
> Looks like a loot of fun :-)
Fun enough to have my evenings and weekends on it :)
> this smell like something that can benefict from metadata.
> /* [return integer] */ function getApparatusId($obj){
> //body
> }
Indeed - type hints can be quite useful, though hiphop is smart enough
On Mon, Mar 1, 2010 at 10:10, Domas Mituzas wrote:
> Howdy,
>
>> Most of the code in MediaWiki works just fine with it (since most of
>> it is mundane) but things like dynamically including certain files,
>> declaring classes, eval() and so on are all out.
>
> There're two types of includes in Med
Looks like a loot of fun :-)
On 1 March 2010 11:10, Domas Mituzas wrote:
...
>> Even if it wasn't hotspots like the parser could still be compiled
>> with hiphop and turned into a PECL extension.
>
> hiphop provides major boost for actual mediawiki initialization too - while
> Zend has to reinit
Howdy,
> Most of the code in MediaWiki works just fine with it (since most of
> it is mundane) but things like dynamically including certain files,
> declaring classes, eval() and so on are all out.
There're two types of includes in MediaWiki, ones I fixed for AutoLoader and
ones I didn't - HPHP
11 matches
Mail list logo
