Hi,
On 24 May 2010 21:09, David Gerard dger...@gmail.com wrote:
On 24 May 2010 20:04, David Gerard dger...@gmail.com wrote:
Do we have a known graceful-degradation path when a browser is just
too crappy to deal with l33t skins like Vector? I'm thinking of the
PS3 users here, noisy as they
Extension access only:
* Liangent: CategoryMultisort extension
* Andrew Whitworth (whiteknight): EmbedVideo and EmbedVideoPlus
* Garrett Brown (gbruin): FBConnect
* Hampton Catlin (hcatlin): webstatscollector
-- Tim Starling
___
Wikitech-l mailing
On Wed, 26 May 2010 17:11:33 -0700, Michelle Knight wrote:
Hi Dan,
There is a list of browsers compatible with Selenium (See
http://seleniumhq.org/about/platforms.html#browsers ). The page states
that Selenium works with Firefox 2+ when a Linux OS is used (I think
Ubuntu would fall under
Hoi,
Selenium is not compatible with Ubuntu..
Thanks,
GerardM
On 27 May 2010 02:11, Michelle Knight mknight113...@gmail.com wrote:
Hi Dan,
There is a list of browsers compatible with Selenium (See
http://seleniumhq.org/about/platforms.html#browsers ). The page states
that
Selenium
Gerard Meijssen schrieb:
Hoi,
Selenium is not compatible with Ubuntu..
Thanks,
GerardM
works fine for me
-- daniel
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Hoi,
I read some more about this.. It turns out that even though I asked for an
update, the software did not update. I just upgraded from release 1.02 to
1.07 and now it works. The documentation states that from 1.05 updates are
pushed.
Thanks,
GerardM
On 27 May 2010 21:21, Daniel Kinzler
Here's the last post I could find on the subject:
For my part, I'm firmly against joining the provider but not
consumer camp. It's of no benefit to anyone . . .
I just thought of a great benefit, however. Consider this true
scenario: I want to write a MediaWiki API client for editors;
On Thu, May 27, 2010 at 6:13 PM, Robb Shecter r...@weblaws.org wrote:
Here's the last post I could find on the subject:
For my part, I'm firmly against joining the provider but not
consumer camp. It's of no benefit to anyone . . .
Not totally sure who wrote that. It may have been a while
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 37-01--10 03:59 PM, Robb Shecter wrote:
But there's one problem: people would need to log in to Wikipedia
*through my app*. They'd have to enter their username and password to
my app, which would turn around an authenticate via the MediaWiki
I could see some real use cases for OAuth. Especially with regards to the
cases mentioned above. People could potentially build apps like AWB and
Huggle using OAuth. In general I think this would be a cool thing to have
for all MediaWiki installs.
As for being an OpenID provider... only one
On Thu, May 27, 2010 at 7:08 PM, Jon Davis w...@konsoletek.com wrote:
I could see some real use cases for OAuth. Especially with regards to the
cases mentioned above. People could potentially build apps like AWB and
Huggle using OAuth. In general I think this would be a cool thing to have
Hi everyone,
One thing we're struggling with right now is getting a chunk of the Flagged
Revs UI to look right. None of us working on Flagged Revs right now are CSS
gurus, and the people that we have at Wikimedia Foundation that are really
good with CSS are buried in other work, so we could
Robb Shecter wrote:
Consider this true
scenario: I want to write a MediaWiki API client for editors;
something like the Wordpress Dashboard. Really give editors a modern
web experience. I'd want to do this as a Rails app: I could build it
quickly and find lots of collaborators via
Not to derail the open-id idea I think we should support oAuth 100%
and it certainly would help with persistent applications and scalability...
I don't think that's a derail at all. I don't know OAuth that well, but it
seems to provide the same benefits of OpenID Provider.
Now... going to
Not to derail the open-id idea I think we should support oAuth 100%
and it certainly would help with persistent applications and scalability...
But ...for the most part you can build these types of applications in
pure javascript. Anytime you need to run an api action that requires
you to
On Fri, May 28, 2010 at 12:11 AM, Robb Shecter r...@weblaws.org wrote:
Not to derail the open-id idea I think we should support oAuth 100%
and it certainly would help with persistent applications and scalability...
I don't think that's a derail at all. I don't know OAuth that well, but it
16 matches
Mail list logo
