On 17/09/2007, Jonathan Mitchem <[EMAIL PROTECTED]> wrote: > Alchemi.Windows.Forms == good
Could you expand on exactly how that would be done? That's a notion my crud-coding hasn't yet come across... > > I know it sounds overbearing, but I think the Alchemi code could benefit > from a "coding standard". I've already been going through the code and, > while not changing the end result of how things work, have been trying to > use some "best practices" to get things into shape. My main reference has > been the appendix of Juval Lowy's book "Programming .NET Components" -- an > excellent read for anyone interested. One of his guidelines is "Never use > Hungarian Notation except for UI elements.". He has a lot of good tidbits > there -- I'll try to type them up if I get a chance and put them in the > Developer's Handbook for future reference. Things like never using public > fields (use properties), never use public events (use event accessors), make > all On<eventname> functions virtual, etc etc. I *completely* agree with this. I have the MS framework recommendations book and will have a look through. We are not too bad apart from public fields which not only is very ugly, but actually was the cause of a bug! The MS UI people seem to just assume you will not use them so completely that things sometimes don't even work if you do! > > So, just so we have a list: > > > > txtTextBoxName > > btnButtonName > > cmbComboBoxName > > grpGroupBoxName > > lblLabelName > > mnuMenuItemName > > lvListViewName > > > > I can't think of the others -- chime in if you remember. I would go with tb for textbox and cbo for combo, but that is completely arbitrary :-). I remember seeing a "Microsoft sanctioned" list somewhere a few years ago (apparently the Office people still use it everywhere!), but it must be pretty old now. In any case, I will have a look for a reasonably "official" looking list (whatever that means!) and post it for inclusion. > > While I'm thinking about it -- what does everything think about factoring > out an Alchemi.Windows.Forms project to keep all of the UI forms and > controls in? There are some projects that use "links" from within visual > studio to reference forms from other projects, and I think that's a poor way > to do code resuse. Thoughts for/against? > See above. Cheers Anton -- echo '16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlbxq' | dc This will help you for 99.9% of your problems ... ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Alchemi-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/alchemi-developers
