AutoWikiBrowser is open source but Windows-only, being written to the .NET 2 framework. Mono isn't up to .NET 2, and .NET 2 doesn't install under Wine on Linux. But I've opened a Wine bug for it:
http://bugs.winehq.org/show_bug.cgi?id=8499
Others are invited to give their stacktraces, relay traces, etc. Be sure to be using the current Wine, the .NET issue is being actively worked on and two weeks can make a difference.
(Darn, a reason to keep Winders around. AWB is just unbelievably cool, and is a much nicer browser to *edit* Wikipedia in. See [[WP:AWB]].)
The related .NET 2 on Wine bug is http://bugs.winehq.org/show_bug.cgi?id=3972 .
If you have other useful .NET programs you would like to run under Wine, give them a try on the current version and let wine-users know and possibly file a bug.
- d.
Erm, this list is not anything to do with AutoWikiBrowser. You might be better off posting to this to an AWB related place.
On 27/05/07, David Gerard dgerard@gmail.com wrote:
AutoWikiBrowser is open source but Windows-only, being written to the .NET 2 framework. Mono isn't up to .NET 2, and .NET 2 doesn't install under Wine on Linux. But I've opened a Wine bug for it:
http://bugs.winehq.org/show_bug.cgi?id=8499
Others are invited to give their stacktraces, relay traces, etc. Be sure to be using the current Wine, the .NET issue is being actively worked on and two weeks can make a difference.
(Darn, a reason to keep Winders around. AWB is just unbelievably cool, and is a much nicer browser to *edit* Wikipedia in. See [[WP:AWB]].)
The related .NET 2 on Wine bug is http://bugs.winehq.org/show_bug.cgi?id=3972 .
If you have other useful .NET programs you would like to run under Wine, give them a try on the current version and let wine-users know and possibly file a bug.
- d.
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/wikitech-l
On 27/05/07, Robert Leverington lcarsdata@googlemail.com wrote:
Erm, this list is not anything to do with AutoWikiBrowser. You might be better off posting to this to an AWB related place.
There are a lot of AWB users here, though, so it's quite a good place to come if you need more data points to fix a bug.
On 27/05/07, Thomas Dalton thomas.dalton@gmail.com wrote:
On 27/05/07, Robert Leverington lcarsdata@googlemail.com wrote:
Erm, this list is not anything to do with AutoWikiBrowser. You might be better off posting to this to an AWB related place.
There are a lot of AWB users here, though, so it's quite a good place to come if you need more data points to fix a bug.
It was on the notion that the general idea of automation applied to Wikipedia was plausibly on-topic. I must say I'm quite excited by the possibilities of such things as api.php and wikipediafs for more of the same. As was noted in this thread on wikien-l, a MediaWiki-specific browser would be a fine thing - and we certainly have the back end for such a creature.
- d.
On 5/28/07, David Gerard dgerard@gmail.com wrote:
the same. As was noted in this thread on wikien-l, a MediaWiki-specific browser would be a fine thing - and we certainly have the back end for such a creature.
What a surprising situation. I'm quite astonished that no one has created such a beast, given the thousands of technically competent users we have. Perhaps we should put out a public request? Would this not also be a really good summer of code project?
Steve
the same. As was noted in this thread on wikien-l, a MediaWiki-specific browser would be a fine thing - and we certainly have the back end for such a creature.
What a surprising situation. I'm quite astonished that no one has created such a beast, given the thousands of technically competent users we have. Perhaps we should put out a public request? Would this not also be a really good summer of code project?
There are many things that could be a good Summer of Code project. However, the limiting factor does not seem to be lack of things to do (there are at least 12 ideas on http://meta.wikimedia.org/wiki/Summer_of_Code_2007 plus more at http://meta.wikimedia.org/wiki/Summer_of_Code_2007/proposals ). I suspect the critical path has more to do with number of suitable student developers who are willing to participate, the number of projects that Google are prepared to sponsor, and the possibly the number of mentor developers available. In other words, it is an absolutely fantastic bonus when it happens, but the healthiest approach is probably that we need to collectively try to solve our problems for ourselves rather than expecting some external entity to help make it happen.
-- All the best, Nick.
On 28/05/07, Nick Jenkins nickpj@gmail.com wrote:
[on making a MediaWiki-specific browser]
available. In other words, it is an absolutely fantastic bonus when it happens, but the healthiest approach is probably that we need to collectively try to solve our problems for ourselves rather than expecting some external entity to help make it happen.
And people do it already, e.g. AWB. It's just annoying they do so only for Windows!
- d.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Moin,
On Monday 28 May 2007 05:10:42 David Gerard wrote:
On 28/05/07, Nick Jenkins nickpj@gmail.com wrote:
[on making a MediaWiki-specific browser]
available. In other words, it is an absolutely fantastic bonus when it happens, but the healthiest approach is probably that we need to collectively try to solve our problems for ourselves rather than expecting some external entity to help make it happen.
And people do it already, e.g. AWB. It's just annoying they do so only for Windows!
Exactly. Teach them to not write their software for some system so that the result is vendor-locked in into an OS, and a platform at the same time.
Trying to fix their broken software development model by using wine is counterproductive.
All the best,
Tels
- -- Signed on Mon May 28 07:55:12 2007 with key 0x93B84C15. View my photo gallery: http://bloodgate.com/photos PGP key on http://bloodgate.com/tels.asc or per email.
"In a closed society where everybody's guilty, the only crime is getting caught. In a world of thieves, the only final sin is stupidity."
-- Hunter S. Thompson
On 28/05/07, Tels nospam-abuse@bloodgate.com wrote:
On Monday 28 May 2007 05:10:42 David Gerard wrote:
On 28/05/07, Nick Jenkins nickpj@gmail.com wrote:
[on making a MediaWiki-specific browser]
available. In other words, it is an absolutely fantastic bonus when it happens, but the healthiest approach is probably that we need to collectively try to solve our problems for ourselves rather than expecting some external entity to help make it happen.
And people do it already, e.g. AWB. It's just annoying they do so only for Windows!
Exactly. Teach them to not write their software for some system so that the result is vendor-locked in into an OS, and a platform at the same time. Trying to fix their broken software development model by using wine is counterproductive.
I'm not a coder (or I'd be fixing it myself) so lecturing them on software development is unlikely to be listened to. I wonder why that is.
ps: setting the default reply on your email to "nospam-abuse" is one level of obnoxious below setting it to one that does whitelisting.
- d.
Once mono is available for .NET 2.0 this should be fixed, not?
On 5/28/07, Tels nospam-abuse@bloodgate.com wrote:
And people do it already, e.g. AWB. It's just annoying they do so only for Windows!
Exactly. Teach them to not write their software for some system so that the result is vendor-locked in into an OS, and a platform at the same time.
Trying to fix their broken software development model by using wine is counterproductive.
On 5/28/07, Tels nospam-abuse@bloodgate.com wrote:
Exactly. Teach them to not write their software for some system so that the result is vendor-locked in into an OS, and a platform at the same time.
I've developed a few things for Windows over the years. That advice just isn't helpful. If you develop using MS Visual Studio or Borland Delphi, there is no trivial habit you can suddenly kick which would make your wish come true. Windows developers don't write software that only works on Windows out of spite. They do so because they have access to the tools, their knowledge is of Windows (as opposed to the often scary world of *nix) and, in many cases, 95%+ of their potential clients are using Windows.
Make a compelling reason for people to write stuff for multiple platforms, or make it trivially easy for them to do so, and they will.
Anyway, about AWB: it's not the solution here. AWB is a hack. Let's get a real *client* happening, not a toolbox of different solutions to particular problems.
Steve
Steve Bennett wrote:
On 5/28/07, Tels nospam-abuse@bloodgate.com wrote:
Exactly. Teach them to not write their software for some system so that the result is vendor-locked in into an OS, and a platform at the same time.
I've developed a few things for Windows over the years. That advice just isn't helpful. If you develop using MS Visual Studio or Borland Delphi, there is no trivial habit you can suddenly kick which would make your wish come true. Windows developers don't write software that only works on Windows out of spite. They do so because they have access to the tools, their knowledge is of Windows (as opposed to the often scary world of *nix) and, in many cases, 95%+ of their potential clients are using Windows.
Make a compelling reason for people to write stuff for multiple platforms, or make it trivially easy for them to do so, and they will.
Anyway, about AWB: it's not the solution here. AWB is a hack. Let's get a real *client* happening, not a toolbox of different solutions to particular problems.
Steve
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/wikitech-l
ِis it possible to modify awb to use any mozilla browser or it heavily depends on ie that it cannot be separated from it?
if it is possible.. wouldn't it be easy to rewrite awb in platform-neutral thing like wxWidgets or GTK+ ?
10%alnokta
On 28/05/07, Mohamed Magdy mohamed.m.k@gmail.com wrote:
ِis it possible to modify awb to use any mozilla browser or it heavily depends on ie that it cannot be separated from it?
It's .NET embedding IE, so it would be possible to use the Mozilla ActiveX wrapper. Main trouble is that it uses lots of bits of .NET that aren't in Mono yet.
if it is possible.. wouldn't it be easy to rewrite awb in platform-neutral thing like wxWidgets or GTK+ ?
I presume the logic parts are simple enough. (Haven't looked at the code myself.)
- d.
On 5/28/07, David Gerard dgerard@gmail.com wrote:
It's .NET embedding IE, so it would be possible to use the Mozilla ActiveX wrapper. Main trouble is that it uses lots of bits of .NET that aren't in Mono yet.
No, no, no -- I don't know why everyone has this in their heads that the Mozilla ActiveX wrapper can simply be interchanged with IE. The Mozilla component has a horribly, horribly immature DOM interface that allows you to do pretty much nothing. Additionally, it's bug-ridden as all hell, crashing frequently and without provocation. Believe me, *everyone* would rather use Mozilla in their apps, but it's simply not do-able. This is the primary set-back to porting windows-based MediaWiki clients to *nix; it's not that developers think "unix is scary," it's that much of the Linux world is quite rocky and unstable at this point, and much of the functionality offered in the way of development in Windows is completely unavailable in *nix.
Instead of screaming at the Windows developers, it's likely much more productive to scream at the developers of Mono and Wine, although if you really want things to get done, you shouldn't scream but offer a hand ;).
Additionally, Wine is actually a shockingly stable interface, and anyone with enough patience can get just about any Windows application to run under it. I've gotten three of my Windows tools to run under a Wine (all three of which were dependent upon IE, I might add), and I'm currently working on a way to deploy my most recent app for seamless install on Wine--we'll see how that goes. I would personally find development in the way of Windows emulators to be much more prone to success than attempts to port current software. I would also bet there are likely many ways to hack AWB to run under wine, it's just a question of if anyone has the patience to do so.
wikitech-l@lists.wikimedia.org