04:58 AM, emw wrote:
Hi all,
For a MediaWiki extension I'm working on (see
http://lists.wikimedia.org/**pipermail/wikitech-l/2012-**
April/060254.htmlhttp://lists.wikimedia.org/pipermail/wikitech-l/2012-April/060254.html),
an
effectively plain-text file will need to be converted into a static
Hi all,
For a MediaWiki extension I'm working on (see
http://lists.wikimedia.org/pipermail/wikitech-l/2012-April/060254.html), an
effectively plain-text file will need to be converted into a static image.
I've got a set of scripts that does that, but it takes my medium-grade
consumer laptop about
Thanks for the feedback Platonides.
Would requiring Python, GIMP and PyMOL to be installed on the server be
workable for a WMF MediaWiki deployment?
Not ideal, but is probably workable. Still much better than relying (and
potentially DDOSing) on a third party.
If you could drop GIMP
suma...@wikimedia.org
wrote:
On 04/21/2012 08:07 AM, emw wrote:
Hi all,
I'm in the process of developing a media handling extension for MediaWiki
that will allow users with WebGL-enabled browsers to manipulate 3D models
of large biological molecules, like proteins and DNA. I'm new
Hi all,
I'm in the process of developing a media handling extension for MediaWiki
that will allow users with WebGL-enabled browsers to manipulate 3D models
of large biological molecules, like proteins and DNA. I'm new to MediaWiki
development, and I've got some questions about how I should go
Anyway, I don't say that the project is impossible or unnecessary, but
there're lots of tradeoffs to be made
- what kind of real time querying workloads are to be expected, what kind of
pre-filtering do people expect, etc.
I could be biased here, but I think the canonical use case for someone
I'd be willing to work on this on a volunteer basis.
I developed http://toolserver.org/~emw/wikistats/, a page view analysis tool
that incorporates lots of features that have been requested of Henrik's tool.
The main bottleneck has been that, like MZMcBride mentions, an underlying
database
