[AD] Re: Alleg-developers digest, Vol 1 #836 - 9 msgs

[Harsha <nharsha@xxxxxxxxxx>]

HI 

 I am new to this mail listing My name is Harsha I am from India I am
using allegro since fro m 1 year. can any one has a link so that I can
learn how to read the news of this new group. Presently I am using
google new group ulity for reading this

On Wed, 08 Dec 2004 20:00:44 -0800,
alleg-developers-request@xxxxxxxxxx
<alleg-developers-request@xxxxxxxxxx> wrote:
> Send Alleg-developers mailing list submissions to
>        alleg-developers@xxxxxxxxxx
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>        https://lists.sourceforge.net/lists/listinfo/alleg-developers
> or, via email, send a message with subject or body 'help' to
>        alleg-developers-request@xxxxxxxxxx
> 
> You can reach the person managing the list at
>        alleg-developers-admin@xxxxxxxxxx
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Alleg-developers digest..."
> 
> Today's Topics:
> 
>   1. Re: Documentation update (Elias Pschernig)
>   2. Re: Documentation update (Evert Glebbeek)
>   3. Re: Documentation update (Elias Pschernig)
>   4. Merged in 4.1.17 into new_api_branch (Peter Wang)
>   5. Re: Merged in 4.1.17 into new_api_branch (Elias Pschernig)
>   6. Re: Merged in 4.1.17 into new_api_branch (Elias Pschernig)
>   7. Re: Merged in 4.1.17 into new_api_branch (Evert Glebbeek)
>   8. Re: Merged in 4.1.17 into new_api_branch (Elias Pschernig)
>   9. Re: Merged in 4.1.17 into new_api_branch (Peter Wang)
> 
> --__--__--
> 
> Message: 1
> Subject: Re: [AD] Documentation update
> From: Elias Pschernig <elias@xxxxxxxxxx>
> To: alleg-developers@xxxxxxxxxx
> Date: Wed, 08 Dec 2004 12:58:24 +0100
> Reply-To: alleg-developers@xxxxxxxxxx
> 
> On Fri, 2004-12-03 at 22:13 +0000, Grzegorz Adam Hankiewicz wrote:
> > Normal words get tt-ised in HTML format with these `quotes'. It
> > looks damn ugly though.
> >
> 
> Yes, it does :| What should we do? Maybe just use normal ticks in the
> _tx, and then let the text output convert it to `', but not the HTML
> output. (Could do the other way around, but '' is easier to type I
> find.) As it looks, this is something for the new _tx, where all sorts
> of docs modifications *should* be very easy to do :)
> 
> --
> Elias Pschernig
> 
> --__--__--
> 
> Message: 2
> Date: Wed,  8 Dec 2004 13:21:03 +0100
> From: Evert Glebbeek <eglebbk@xxxxxxxxxx>
> To: alleg-developers@xxxxxxxxxx
> Subject: Re: [AD] Documentation update
> Reply-To: alleg-developers@xxxxxxxxxx
> 
> > Yes, it does :| What should we do? Maybe just use normal ticks in the
> > _tx, and then let the text output convert it to `', but not the HTML
> > output. (Could do the other way around, but '' is easier to type I
> > find.)
> 
> Well, I find the exact opposite - I'd be really annoyed if I suddenly hav=
> e
> to use '' instead of `'. ;)
> If the current docs have `', then I suppose it's also more convenient to
> do it this way, as it doesn't involve a lot of doc changes.
> 
> > As it looks, this is something for the new _tx, where all sorts
> > of docs modifications *should* be very easy to do :)
> 
> In that case, maybe consider a <begin quote>...<end quote> scheme
> (<q>...</q>?) in the new _tx documentation. This is neutral with respect =
> to
> `' or ''.
> 
> Evert
> 
> --__--__--
> 
> Message: 3
> Subject: Re: [AD] Documentation update
> From: Elias Pschernig <elias@xxxxxxxxxx>
> To: alleg-developers@xxxxxxxxxx
> Date: Wed, 08 Dec 2004 13:44:22 +0100
> Reply-To: alleg-developers@xxxxxxxxxx
> 
> On Wed, 2004-12-08 at 13:21 +0100, Evert Glebbeek wrote:
> > > Yes, it does :| What should we do? Maybe just use normal ticks in the
> > > _tx, and then let the text output convert it to `', but not the HTML
> > > output. (Could do the other way around, but '' is easier to type I
> > > find.)
> >
> > Well, I find the exact opposite - I'd be really annoyed if I suddenly have
> > to use '' instead of `'. ;)
> > If the current docs have `', then I suppose it's also more convenient to
> > do it this way, as it doesn't involve a lot of doc changes.
> >
> > > As it looks, this is something for the new _tx, where all sorts
> > > of docs modifications *should* be very easy to do :)
> >
> > In that case, maybe consider a <begin quote>...<end quote> scheme
> > (<q>...</q>?) in the new _tx documentation. This is neutral with respect to
> > `' or ''.
> >
> 
> Hm, I assume, English keyboard layouts have a ` key on them. Here, it's
> hard to type, requiring a mode switch.
> 
> Maybe we could just say that quoted parameter names should use *name*.
> That's already used in _tx at some places to emphasize words, and is
> easy to type, and looks better (IMHO) than `name', which is quite
> assymetrical, since the ` falls left, but the ' doesn't fall right as it
> should.
> 
> I really like the way wikipedia editing works
> (http://en.wikipedia.org/wiki/Wikipedia:How_to_edit_a_page) - maybe
> could also steal ideas from them.
> 
> But I'm ok with everything not involving a backtick :)
> 
> --
> Elias Pschernig
> 
> --__--__--
> 
> Message: 4
> Date: Thu, 09 Dec 2004 10:21:55 +1100
> From: Peter Wang <tjaden@xxxxxxxxxx>
> To:  alleg-developers@xxxxxxxxxx
> Subject: [AD] Merged in 4.1.17 into new_api_branch
> Reply-To: alleg-developers@xxxxxxxxxx
> 
> In case you don't subscribe to the cvs-commits list, I've merged the
> changes between 4.1.16 and 4.1.17 into the new_api_branch.  This
> includes a hackish port of Elias' new X keyboard driver.
> 
> Peter
> 
> --__--__--
> 
> Message: 5
> Subject: Re: [AD] Merged in 4.1.17 into new_api_branch
> From: Elias Pschernig <elias@xxxxxxxxxx>
> To: alleg-developers@xxxxxxxxxx
> Date: Thu, 09 Dec 2004 00:41:47 +0100
> Reply-To: alleg-developers@xxxxxxxxxx
> 
> On Thu, 2004-12-09 at 10:21 +1100, Peter Wang wrote:
> > In case you don't subscribe to the cvs-commits list, I've merged the
> > changes between 4.1.16 and 4.1.17 into the new_api_branch.  This
> 
> Ah, nice work. I'm really wondering how well the transition from 2.4.1
> to 2.4.3 will work out - it isn't too far away if all goes as planned.
> Ideally we'd just swap back the new_api_branch and continue with a
> single branch in 2.4.3. Another route would be to leave new_api_branch
> as the place for experimental stuff, and only extract back parts into
> the current WIP as needed - but I somehow feel that approach would
> require more maintenance. And personally, I would rather avoid having to
> do things like merging changes between branches with CVS :P
> 
> > includes a hackish port of Elias' new X keyboard driver.
> >
> 
> Not too hackish I hope :)
> 
> [Oh, and since you and Grzegorz both overlooked it in that other thread
> - could you temporarily give Tomasu access to CVS for the makedoc stuff?
> It's not a real problem since he's in #allegro most of the time and can
> dcc changes, but still might be useful..]
> 
> --
> Elias Pschernig
> 
> --__--__--
> 
> Message: 6
> Subject: Re: [AD] Merged in 4.1.17 into new_api_branch
> From: Elias Pschernig <elias@xxxxxxxxxx>
> To: alleg-developers@xxxxxxxxxx
> Date: Thu, 09 Dec 2004 00:45:54 +0100
> Reply-To: alleg-developers@xxxxxxxxxx
> 
> [edit, well, if email had it]
> 2.4.1 and 2.4.3 should be 4.1.x and 4.3.x of course.
> 
> --
> Elias Pschernig
> 
> --__--__--
> 
> Message: 7
> From: Evert Glebbeek <eglebbk@xxxxxxxxxx>
> To: alleg-developers@xxxxxxxxxx
> Subject: Re: [AD] Merged in 4.1.17 into new_api_branch
> Date: Thu, 9 Dec 2004 00:59:10 +0100
> Reply-To: alleg-developers@xxxxxxxxxx
> 
> On Thursday 09 December 2004 00:41, Elias Pschernig wrote:
> > Ah, nice work. I'm really wondering how well the transition from 4.1
> > to 4.3 will work out - it isn't too far away if all goes as planned.
> > Ideally we'd just swap back the new_api_branch and continue with a
> > single branch in 4.3. Another route would be to leave new_api_branch
> > as the place for experimental stuff, and only extract back parts into
> > the current WIP as needed - but I somehow feel that approach would
> > require more maintenance. And personally, I would rather avoid having to
> > do things like merging changes between branches with CVS :P
> 
> I think we should fork off 4.2 when it becomes stable, similar to how 4.0
> was forked off, then replace mainline with the contentx of new_api_branch
> and then close down (at least for now) new_api_branch.
> In fact, I was even contemplating wether or not it would be a good idea to
> do the flip before that time and split off 4.2 before its release date.
> The idea behind this that I'd like to get the stuff into mainline before
> Peter's time becomes too limited again (I think he said he would have a
> busier semester after Januari/Februari?). On the whole, I don't think this
> would be a good idea in general though.
> 
> > [Oh, and since you and Grzegorz both overlooked it in that other thread
> > - could you temporarily give Tomasu access to CVS for the makedoc stuff?
> > It's not a real problem since he's in #allegro most of the time and can
> > dcc changes, but still might be useful..]
> 
> What is the problem exactly...? I couldn't see any way to only grant acces
> for a specific module... besides, isn't Thomas already on the list of
> developers?
> 
> Evert
> 
> --__--__--
> 
> Message: 8
> Subject: Re: [AD] Merged in 4.1.17 into new_api_branch
> From: Elias Pschernig <elias@xxxxxxxxxx>
> To: alleg-developers@xxxxxxxxxx
> Date: Thu, 09 Dec 2004 01:08:25 +0100
> Reply-To: alleg-developers@xxxxxxxxxx
> 
> On Thu, 2004-12-09 at 00:59 +0100, Evert Glebbeek wrote:
> > What is the problem exactly...? I couldn't see any way to only grant acces
> > for a specific module... besides, isn't Thomas already on the list of
> > developers?
> 
> Ah, true, someone must have added him in the meantime :)
> 
> --
> Elias Pschernig
> 
> --__--__--
> 
> Message: 9
> Date: Thu, 09 Dec 2004 11:57:19 +1100
> From: Peter Wang <tjaden@xxxxxxxxxx>
> To:  alleg-developers@xxxxxxxxxx
> Subject: Re: [AD] Merged in 4.1.17 into new_api_branch
> Reply-To: alleg-developers@xxxxxxxxxx
> 
> Evert Glebbeek wrote:
> 
> >I think we should fork off 4.2 when it becomes stable, similar to how 4.0
> >was forked off, then replace mainline with the contentx of new_api_branch
> >and then close down (at least for now) new_api_branch.
> >
> >
> 
> That's what I think, too.
> 
> >In fact, I was even contemplating wether or not it would be a good idea to
> >do the flip before that time and split off 4.2 before its release date.
> >The idea behind this that I'd like to get the stuff into mainline before
> >Peter's time becomes too limited again (I think he said he would have a
> >busier semester after Januari/Februari?). On the whole, I don't think this
> >would be a good idea in general though.
> >
> >
> 
> It doesn't actually matter what is in which branch.  The switch would
> only be symbolic, I think.
> 
> >What is the problem exactly...? I couldn't see any way to only grant acces
> >for a specific module...
> >
> 
> That's not possible with CVS.
> 
> Peter
> 
> --__--__--
> 
> _______________________________________________
> Alleg-developers mailing list
> Alleg-developers@xxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/alleg-developers
> 
> End of Alleg-developers Digest
>