Peter Beutner wrote:
Dmitry Timoshkov schrieb:
"Peter Beutner" <[EMAIL PROTECTED]> wrote:
Wine is a very good way of testing the waters with a Linux market.
If a significant part of the market share starts coming from Linux
or other Unix operating systems then the company can start offerin
On 12/13/05, Dan Kegel <[EMAIL PROTECTED]> wrote:
> So I've been thinking about how to attract more Windows ISVs
> to test, support, and promote their apps on Linux with Wine.
>...
> I've made a start at the documentation (http://kegel.com/wine/isv) ...
> How about we create a new mailing list, win
Peter Beutner wrote:
Michael Jung schrieb:
On Friday 16 December 2005 10:49, Peter Beutner wrote:
Wine is _not_ just a different toolkit. Just look at all the "nasty"
stuff
wine has to do to emulate the windows process environment.
I guess in the long term a project like wine, if success
On Fri, 2005-12-16 at 23:45 -0700, Vitaliy Margolen wrote:
> Friday, December 16, 2005, 11:26:28 PM, Scott Ritchie wrote:
> > On Fri, 2005-12-16 at 19:48 +0100, Alexandre Julliard wrote:
> >> The goal is not to prevent regressions between every minor point
> >> release, it's to make releases freque
Markus Goemmel wrote:
> My partner and I are developing Windows applications
> (http://www.emtec.com). Seeing Wine some months ago fascinated
> me a lot, so since then I'm spending one or two hours a day
> trying to bring our applications to work under Wine, too...
>
> But it's clear that there are
Friday, December 16, 2005, 11:26:28 PM, Scott Ritchie wrote:
> On Fri, 2005-12-16 at 19:48 +0100, Alexandre Julliard wrote:
>> The goal is not to prevent regressions between every minor point
>> release, it's to make releases frequently enough that regressions can
>> be found and fixed quickly, so
On Fri, 2005-12-16 at 19:48 +0100, Alexandre Julliard wrote:
> The goal is not to prevent regressions between every minor point
> release, it's to make releases frequently enough that regressions can
> be found and fixed quickly, so that they don't creep into the next
> major release. Now, if you t
Tony Lambregts <[EMAIL PROTECTED]> writes:
> Perhaps it's partly a matter of perception then.
>
> If I understand you 0.9 was a major release then, and 0.9.1 and
> company are minor releases, with the next major release being 1.0. So
> I anticipate that we will have a major freeze before 1.0 jus
Am Freitag, 16. Dezember 2005 19:48 schrieb Alexandre Julliard:
> The idea is that people should test the releases. The point of the
> beta phase is to encourage end users to test, and for this to happen
> they need to be able to get binary packages, which is what the
> releases are about. This is
On 12/16/05, Alexandre Julliard <[EMAIL PROTECTED]> wrote:
> Tony Lambregts <[EMAIL PROTECTED]> writes:
>
> > Well that is a real sore spot with me. You know that I am a strong
> > supporter of wine but it really concerns me that we have gone beta and
> > not addressed preventing regessions from ge
> "Peter" == Peter Beutner <[EMAIL PROTECTED]> writes:
Peter> Michael Jung schrieb:
>> On Friday 16 December 2005 15:41, Peter Beutner wrote:
>>> Don't get me wrong I still think it is perfectly valid that wine is
>>> doing that sort of hack to get existing windows applications
Tony Lambregts <[EMAIL PROTECTED]> writes:
> Well that is a real sore spot with me. You know that I am a strong
> supporter of wine but it really concerns me that we have gone beta and
> not addressed preventing regessions from getting into our releases in
> any way. We currently have no freeze or
Michael Jung schrieb:
On Friday 16 December 2005 15:41, Peter Beutner wrote:
Don't get me wrong I still think it is perfectly valid that wine is doing
that sort of hack to get existing windows applications working but you
really shouldn't advertise it as a solution to platform independence and
e
Dmitry Timoshkov schrieb:
"Peter Beutner" <[EMAIL PROTECTED]> wrote:
Why? Wine is effectively just a different toolkit, like QT or GTK
(albeit much larger) that give applications a Windows, KDE and Gnome
look respectively. Take Notepad for example - with some slight
modifications you could eve
Jeremy White wrote:
>>Not that I mean to sound like a pessimist, but I'm really just calling
>>it as I see it. No offense to anyone intended. :)
>
>
> This, in a nutshell, is Wine's greatest challenge
> (stepping even outside ISV boundaries for a minute).
>
> I believe, either because I'm insane (t
On Friday 16 December 2005 15:41, Peter Beutner wrote:
> The point is that it won't be integrated in neither kernel or glibc.
Integration in the loader is just one possibility. Wine needs to load code at
fixed positions. Thus, there has to be a possibility to do it. Currently we
do it in a way
> The point is that it won't be integrated in neither kernel or glibc. At
> least I can't imagine that this will happen. Why should anybody integrate
> another binary loader/memory layout into the kernel/libc where there is
> already a fully working one?
> Just because some people don't want to
Michael Jung schrieb:
On Friday 16 December 2005 12:54, Peter Beutner wrote:
Let's just look at the problem with the memory layout. Wine relies on the
possibility to load certain codes at fixed addresses as this is how it
works under windows. Linux choose exact the opposite direction, i.e. try
"Peter Beutner" <[EMAIL PROTECTED]> wrote:
Why? Wine is effectively just a different toolkit, like QT or GTK
(albeit much larger) that give applications a Windows, KDE and Gnome
look respectively. Take Notepad for example - with some slight
modifications you could even modify the File Open dia
On Freitag 16 Dezember 2005 10:49, Peter Beutner wrote:
> Robert Shearman schrieb:
> > Peter Beutner wrote:
> >> Maybe it's just me but when reading all this I got the feeling that
> >> writing windows applications(which work with wine) is just *the* way
> >> to go.
> >
> > It is the cheapest way
On Friday 16 December 2005 12:54, Peter Beutner wrote:
> Let's just look at the problem with the memory layout. Wine relies on the
> possibility to load certain codes at fixed addresses as this is how it
> works under windows. Linux choose exact the opposite direction, i.e. try to
> ensure that lib
James Liggett schrieb:
I really fear that this will end up with vendors loudly advertising linux support and
proudly putting linux stickers on their products where everything you find inside are just
the same windows .exe files and a readme stating that these will work fine with wine.
Which at
Michael Jung schrieb:
On Friday 16 December 2005 10:49, Peter Beutner wrote:
Wine is _not_ just a different toolkit. Just look at all the "nasty" stuff
wine has to do to emulate the windows process environment.
I guess in the long term a project like wine, if successfull, doesn't have to
l
Hi,
> I'll vote against a wine-isv list. History has shown we're not
> responsible enough to have many mailing lists. Sure, if it takes
> off.. great. But more than likely we'll be having a discussion on
> wine-devel in 18 months about getting rid of the list because only a
> handful of people
On Friday 16 December 2005 10:49, Peter Beutner wrote:
> Wine is _not_ just a different toolkit. Just look at all the "nasty" stuff
> wine has to do to emulate the windows process environment.
I guess in the long term a project like wine, if successfull, doesn't have to
live with the restriction
Robert Shearman schrieb:
Peter Beutner wrote:
IMHO all this stuff goes a bit too much into the wrong direction.
I really fear that this will end up with vendors loudly advertising
linux support and proudly putting linux stickers on their products
where everything you find inside are just the
> Not that I mean to sound like a pessimist, but I'm really just calling
> it as I see it. No offense to anyone intended. :)
This, in a nutshell, is Wine's greatest challenge
(stepping even outside ISV boundaries for a minute).
I believe, either because I'm insane (the likely
explanation), or bec
Peter Beutner wrote:
IMHO all this stuff goes a bit too much into the wrong direction.
I really fear that this will end up with vendors loudly advertising
linux support and proudly putting linux stickers on their products
where everything you find inside are just the same windows .exe files
On 12/15/05, Peter Beutner <[EMAIL PROTECTED]> wrote:
> it's definitly a good thing when vendors care about their product running
> with wine or
> companies migrating to linux trying to get their highly-specialized-app to
> work with wine.
> But imho it _shouldn't_ be the long term solution.
We'
> I really fear that this will end up with vendors loudly advertising linux
> support and
> proudly putting linux stickers on their products where everything you find
> inside are just
> the same windows .exe files and a readme stating that these will work fine
> with wine.
> Which at least i
Scott Ritchie schrieb:
On Tue, 2005-12-13 at 22:33 -0800, Dan Kegel wrote:
I used to hate the term ISV (Independent Software Vendor) since
it sounded so acronymy compared to 'developer', but it's
very commonly used in the industry to refer to outfits which
are trying to write and sell off-the-s
On 12/15/05, Brian Vincent <[EMAIL PROTECTED]> wrote:
> You're secretly just trying to get me to finish the commercial page I
> promised, huh?
:-)
> I'll vote against a wine-isv list. History has shown we're not
> responsible enough to have many mailing lists. Sure, if it takes
> off.. great.
You're secretly just trying to get me to finish the commercial page I
promised, huh?
I'll vote against a wine-isv list. History has shown we're not
responsible enough to have many mailing lists. Sure, if it takes
off.. great. But more than likely we'll be having a discussion on
wine-devel in 18
On Mittwoch 14 Dezember 2005 07:33, Dan Kegel wrote:
> How about we create a new mailing list, wine-isv, aimed squarely
> at ISVs and the Wine community members who want to
> help them?
Sounds like a good idea to me ;)
David
pgpntIJmD7w1g.pgp
Description: PGP signature
Hi,
> How about we create a new mailing list, wine-isv, aimed squarely
> at ISVs and the Wine community members who want to
> help them?
I'd say go for it!
Stefan
pgp3gHbP0Ls0o.pgp
Description: PGP signature
On Tue, 2005-12-13 at 22:33 -0800, Dan Kegel wrote:
> I used to hate the term ISV (Independent Software Vendor) since
> it sounded so acronymy compared to 'developer', but it's
> very commonly used in the industry to refer to outfits which
> are trying to write and sell off-the-shelf software -- an
I used to hate the term ISV (Independent Software Vendor) since
it sounded so acronymy compared to 'developer', but it's
very commonly used in the industry to refer to outfits which
are trying to write and sell off-the-shelf software -- and
as monkey-boy said, Microsoft is where it is partly becaus
37 matches
Mail list logo
