> > Well, if someone wants to do more work for the sake of argument, then I
> > guess we live in a free world. But still, the fonts are such a fringe
> > part of wine that I just can't see any extra work to be worth it. For a
> > while one can just consider fontforge to be a "proprietary" tool, and
"Kuba Ober" <[EMAIL PROTECTED]> wrote:
> That's lunacy! Just ship the damn prebuilt files until the time is ripe
> to take them out. Of course the sources should be kept there all the time
> as well.
So if a version of gcc got released that didn't produce correct
libraries then we should add al
> > 1. You never mentioned what you want this "front-end" to do. I think
> > that's pretty important to whatever you're talking about. Seems to me
> > it might fit in with winecfg or something else that already exists.
> >
> > 2. Did you read the thread(s) about rewriting WineTools that occurre
> >If fontforge"made a mess", that's not just because it's an extra
> > dependency. It's because someone, instead of making the right choice and
> > shipping whatever files fontforge is building, shipped only the sources.
> > The right thing to do would be to ship the prebuilt stuff at least until
Brian Vincent wrote:
On 4/16/06, Rich Gilson
<[EMAIL PROTECTED]>
wrote:
I
must say, the turn this conversation has taken is interesting. In
response
to what was written above, it does seem to me a curious precedent
Alexandre
has set. After all, wasn't Wine developed to allow people to ge
On 4/16/06, Rich Gilson <[EMAIL PROTECTED]> wrote:
I must say, the turn this conversation has taken is interesting. In responseto what was written above, it does seem to me a curious precedent Alexandrehas set. After all, wasn't Wine developed to allow people to get AWAY from
Windows? Yet, when
On Saturday 15 April 2006 14:57, Kuba Ober wrote:
> On Saturday 15 April 2006 10:48, n0dalus wrote:
> I think that this discussion has really degenerated into a long advocacy
> *against* everything that open source is good for.
>
> Alexandre's take seems to be that one should simply ignore what's o
Hi,
On Sat, Apr 15, 2006 at 07:54:12PM -0400, Dimi Paun wrote:
> On Sat, 2006-04-15 at 16:17 +0100, Karl Lattimer wrote:
> >
> > I seriously doubt that as far as users are concerned that dependencies
> > would be an issue, the user in general just wants something that
> > works, and they don't ca
On Sat, 15 Apr 2006 22:51:13 +0100, Robert Shearman wrote:
> So if a version of gcc got released that didn't produce correct
> libraries then we should add all of the .so files to the Wine tree? What
> a good idea!
That ignores the costs/benefits of each individual case. I think it's
completely
Karl Lattimer wrote:
The point here is that if someone is willing to install wine, chances
are they will have all the libraries required for it on a unix system,
Isn't this how we are running into the font problems by requiring
fontforge? Just because it is available and a user can and wan
On Sat, 2006-04-15 at 19:54 -0400, Dimi Paun wrote:
> On Sat, 2006-04-15 at 16:17 +0100, Karl Lattimer wrote:
> >
> > I seriously doubt that as far as users are concerned that dependencies
> > would be an issue, the user in general just wants something that
> > works, and they don't care that 4 ex
On Sat, 2006-04-15 at 16:17 +0100, Karl Lattimer wrote:
>
> I seriously doubt that as far as users are concerned that dependencies
> would be an issue, the user in general just wants something that
> works, and they don't care that 4 extra dependancies are required
> (python, gtk, pygtk, pygtk-gla
Kuba Ober wrote:
If fontforge"made a mess", that's not just because it's an extra dependency.
It's because someone, instead of making the right choice and shipping
whatever files fontforge is building, shipped only the sources. The right
thing to do would be to ship the prebuilt stuff at least
> [. . .]
>
> I think that this discussion has really degenerated into a long advocacy
> *against* everything that open source is good for.
>
> Alexandre's take seems to be that one should simply ignore what's out there
> and program like in Win 2.x days. In the meantime, software has moved for
On Saturday 15 April 2006 10:48, n0dalus wrote:
> On 4/15/06, Karl Lattimer <[EMAIL PROTECTED]> wrote:
> > If this http://wiki.winehq.org/ThemingSupport is to become a part of
> > wine (RE: GTK support for themes), I don't see what the problem with
> > using GTK is. GTK is available on all distribu
On Sun, 2006-04-16 at 00:46 +0900, Mike McCormack wrote:
> Karl Lattimer wrote:
>
> > requirements around this wouldn't be a great issue. With the current
> > complexity of linux desktops I believe that restricting the language and
> > dependencies is silly and uncalled for. Maybe Alexandre's view
Karl Lattimer wrote:
requirements around this wouldn't be a great issue. With the current
complexity of linux desktops I believe that restricting the language and
dependencies is silly and uncalled for. Maybe Alexandre's views may have
changed this far on?
I doubt that Alexandre's views have
> Note however, that being a good C programmer
> can be harder than being a good python programmer.
Oh how very true ;), but doesn't this statement in itself answer the
question. python == easy to write, easy to maintain, fun and featureful.
>
> I see many python developers get into the habit of
On 4/15/06, Karl Lattimer <[EMAIL PROTECTED]> wrote:
>
> If this http://wiki.winehq.org/ThemingSupport is to become a part of
> wine (RE: GTK support for themes), I don't see what the problem with
> using GTK is. GTK is available on all distributions that I know of, and
> definitely all popular dis
> When winecfg was originally proposed I wanted to do it in GTK, and whinged
> loudly when Alexandre said it had to be done using Win32 to keep
> dependencies small. I guess his reasoning hasn't changed, so, for GUIs
> you'd have to do it using Win32 and C :(
>
> Of course if you aren't bothered
On Sat, 15 Apr 2006 03:02:22 -0400, Rich Gilson wrote:
> If somebody were writing a Wine GUI front-end for uses with the hope that it
> might possibly make it into the Wine distribution one day, what language(s)
> and toolkit(s) would be acceptable to the Wine developers for that person to
> use
On Sat, 2006-04-15 at 03:02 -0400, Rich Gilson wrote:
> I was wondering...
>
> If somebody were writing a Wine GUI front-end for uses with the hope that it
> might possibly make it into the Wine distribution one day, what language(s)
> and toolkit(s) would be acceptable to the Wine developers fo
Rich Gilson wrote:
If somebody were writing a Wine GUI front-end for uses with the hope that it
might possibly make it into the Wine distribution one day, what language(s)
and toolkit(s) would be acceptable to the Wine developers for that person to
use? Or, of course, do you not forsee that
I was wondering...
If somebody were writing a Wine GUI front-end for uses with the hope that it
might possibly make it into the Wine distribution one day, what language(s)
and toolkit(s) would be acceptable to the Wine developers for that person to
use? Or, of course, do you not forsee that ha
24 matches
Mail list logo
