Re: LyX Coding Rules and Recommendations

2010-10-27 Thread Pavel Sanda
Vincent van Ravesteijn wrote: > I'm not yet sure whether we should make one document of both the > Rules/Language Advice/Style and the implementation/design issues. i would prefer one doc. pavel

Re: LyX Coding Rules and Recommendations

2010-10-27 Thread Vincent van Ravesteijn
> perhaps kill the old ascii file (or move it to attic) so there is unambiguous > location. Yes, I will. I wanted to wait until this new document is somewhat decent (I'm not sure why though). >also you nice log about casts could be saved somewhere. It's already in there, but I hide it in the app

Re: LyX Coding Rules and Recommendations

2010-10-27 Thread Pavel Sanda
Stephan Witt wrote: > > Maybe we can create another document on the design principles and > > major structure in the LyX code. There are already some pieces, but we > > have to get them up to date and to put them in one place. > > > > Comments ? perhaps kill the old ascii file (or move it to atti

Re: LyX Coding Rules and Recommendations

2010-10-26 Thread Stephan Witt
Am 27.10.2010 um 07:04 schrieb Vincent van Ravesteijn: > Hi All, > > I converted the two files about Rules and Recommendation into a LyX > document. You might want to have a look at it, and put your two cents > in there about coding principle, style and so forth. It is still a bit > a mess, but I

LyX Coding Rules and Recommendations

2010-10-26 Thread Vincent van Ravesteijn
Hi All, I converted the two files about Rules and Recommendation into a LyX document. You might want to have a look at it, and put your two cents in there about coding principle, style and so forth. It is still a bit a mess, but I hope it will get better. Everyone is invited to edit. Please turn

Re: Changes to coding rules

2007-09-30 Thread Jean-Marc Lasgouttes
Andre Poenitz <[EMAIL PROTECTED]> writes: > So reformulate "short"? Thanks. JMarc

Re: Changes to coding rules

2007-09-30 Thread Andre Poenitz
On Sun, Sep 30, 2007 at 05:42:51PM +0200, Jean-Marc Lasgouttes wrote: > Andre Poenitz <[EMAIL PROTECTED]> writes: > > > -We also require you to provide a ChangeLog entry with every patch, this > > -describes shortly what the patch is doing. The ChangeLog entry follows > > -this syntax: > > +We als

Re: Changes to coding rules

2007-09-30 Thread Jean-Marc Lasgouttes
Andre Poenitz <[EMAIL PROTECTED]> writes: > -We also require you to provide a ChangeLog entry with every patch, this > -describes shortly what the patch is doing. The ChangeLog entry follows > -this syntax: > +We also require you to provide a commit message entry with every patch, > +this describe

Changes to coding rules

2007-09-30 Thread Andre Poenitz
Should be uncontroversial, but I'll wait for a nod. I have a few more controversial ones up my sleeve... Andre' Index: Rules === --- Rules (revision 20603) +++ Rules (working copy) @@ -12,6 +12,7 @@ but still, we don't

Re: coding rules

2000-03-07 Thread Lars Gullik Bjønnes
Andre Poenitz <[EMAIL PROTECTED]> writes: | I'd like to use development/Code_rules in some modified version for | internal (more or less educational) purposes. I would of course include a | small header concerning the origin of the document. | | Does anybody feel that this is not a good thing

RE: coding rules

2000-03-07 Thread Juergen Vigna
On 07-Mar-2000 Andre Poenitz wrote: > > I'd like to use development/Code_rules in some modified version for > internal (more or less educational) purposes. I would of course include a > small header concerning the origin of the document. > > Does anybody feel that this is not a good thing do?

coding rules

2000-03-07 Thread Andre Poenitz
I'd like to use development/Code_rules in some modified version for internal (more or less educational) purposes. I would of course include a small header concerning the origin of the document. Does anybody feel that this is not a good thing do? Andre' -- It'll take a long time to eat 63.00