I actually prefer 4 spaces per tab instead of 8.. 8 takes so much more screen real-estate then it should IMHO. So if we'd adopt a modified mono standard, then that's the thing i'd prefer to change.. everything else doesn't matter too much to me personally.
As for the wiki, it needs a lot more stuff.. so if anyone feels like updating any part of the wiki: feel free! On Tue, Mar 18, 2008 at 9:01 AM, Darx Kies <[EMAIL PROTECTED]> wrote: > That is a very good idea. > > But providing screenshots is a difficult task as I don't know anymore > what i changed. :D > > But like I said let's start a a thread on voting about the changes. > > Now that the community is growing we should perhaps choose something > that suits all of > us and goes well with monodevelop and vs. > > Chriss. > > Phil Garcia wrote: > > A wiki is a good idea. If you could provide screenshots of the > > additional formatting options which must be set/unset, I'll put the > > page together. > > > > I actually like Mono's standards, except for the 1) space after the > > method name, and 2) instance fields should use underline as a > > separator. I noticed that not all the developers do this either > > (including myself), *especially* the naming of instance fields. From > > reviewing the existing code, we all seem to prefer camel casing for > > instance fields (without underlines). > > > > So maybe we would vote on adapting those two points of differentiation > > from the Mono standard? > > > > - Phil > > > > PS. For reference, I had to research this area before for another open > > source project, and here are three well documents standards: > > > > Design Guidelines for Class Library Developers from Microsoft > > http://msdn2.microsoft.com/en-us/library/czefa0ke(vs.71).aspx > > > > Coding Standards for .NET By Lance Hunt (Short version) > > http://weblogs.asp.net/lhunt/pages/CSharp-Coding-Standards-document.aspx > > > > Coding Standard: C# by Philips Medical Systems (Most complete) > > http://www.tiobe.com/content/paperinfo/gemrcsharpcs.pdf > > > > All the standards above are nearly identical. > > > > > > > > > On Tue, Mar 18, 2008 at 12:10 AM, Darx Kies <[EMAIL PROTECTED]> wrote: > > > >> There are more settings. > >> > >> Perhaps we can put the VS settings file into the wiki? > >> > >> Or perhaps we start to do a vote on that so that such issues won't come > >> up again? > >> > >> Chriss. > >> > >> > >> Phil Garcia wrote: > >> > >>> On Mon, Mar 17, 2008 at 11:37 PM, Ásgeir Halldórsson <[EMAIL PROTECTED]> > >>> wrote: > >>> > >>> > >>>> Hi, > >>>> > >>>> Why are we not just using TAB char instead of spaces? > >>>> > >>>> > >>>> > >>> I have been confused on that point as well. The coding standard, based > >>> on Mono, is to use "8-space tabs", which simply means that tabs should > >>> be represented as 8 spaces. I personally prefer and use "4-space > >>> tabs". It's a preference setting in Visual Studio that generally does > >>> not affect anyone else; except if you are trying to align comments > >>> (or multi-line) code. I attempt to avoid those situations. > >>> > >>> I use Visual Studio's AutoFormat Code feature which can be triggered > >>> by the key short-cut sequence, CTRL-K followed by CTRL-D. > >>> > >>> Note, you have to adjust some of the default Visual Studio settings > >>> available under "Options" | "Text Editor" | "C#" | "Formatting": > >>> > >>> * Under "Space" | "Set spacing for method declarations", turn on > >>> "Insert space between method name and its opening parenthesis". > >>> * Under "Space" | "Set spacing for method calls", turn on "Insert > >>> space between method name and its opening parenthesis". > >>> * Under "New Lines" | "New lies options for braces", turn off "Place > >>> open brace onnew line for control blocks" > >>> > >>> ^ If I missed one, please let me know. > >>> > >>> I prefer Visual Studio's default formatting style, but we can't have > >>> everything we want. > >>> > >>> Phil > >>> > >>> > >>> ------------------------------------------------------------------------- > >>> This SF.net email is sponsored by: Microsoft > >>> Defy all challenges. Microsoft(R) Visual Studio 2008. > >>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >>> _______________________________________________ > >>> SharpOS-Developers mailing list > >>> SharpOS-Developers@lists.sourceforge.net > >>> https://lists.sourceforge.net/lists/listinfo/sharpos-developers > >>> > >>> > >> > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > SharpOS-Developers mailing list > SharpOS-Developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sharpos-developers > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ SharpOS-Developers mailing list SharpOS-Developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sharpos-developers
