Hallo nore...@z505.com, Du schriebst am Mon, 12 Dec 2011 12:41:44 -0600:
> That's what I was saying, in delphi you can bypass the dumb looking event > names they give you. However for quick prototypes where I just want to > try something with a button, I use Button1OnClick because I'm just If it's _just_ a button, maybe two, and if the thing gets deleted afterwards, just having shown a concept can work, it may be o.k. If there's any chance it might survive as part of some method or component, it really should be put together more thoughtfully - one might have to work on it some more a couple years later. > throwing something together quickly. As the application progresses and is > more longer term, it makes more sense to use more meaningful names and > possibly shorter names like Btn1Save Btn1Load etc. Well, and that's a very good example of mking a bad start worse. What's the use of that "Btn1.." part, after all? Do your buttons bear captions "1", "2" and do forth? No? Then use what they say, what they _do_ as their name. Use "SaveTable" or "SaveList" or whatever they invoke, there may be several different save actions implemented - name them accordingly. > I give meaningful names for medium/long term projects. For quick throw > together prototypes I use button1 and other silly names. The idea with See above - you might have to cope with the silly names much later, if they managed to survive the integration into some more involved part of a program. > rad is rapid. For longer term projects rapid becomes less important. Still > some rapid features are used to manage long term projects. Yes, and that's just as much burden as it is relief - it relieves you from creating, positioning, sizing and so on of every component without seeing what you do (I've done a project that way), but they burden you with the responsibility to kind of document your work to reflect what every part of it does, so it remains manageable and useful. If you don't, you got to bear the burden of uncomprehensibility and unmanageability of much more than just that little misshaped component, as its _in_comprehensibility gets _inherited_. -- (Weitergabe von Adressdaten, Telefonnummern u.ä. ohne Zustimmung nicht gestattet, ebenso Zusendung von Werbung oder ähnlichem) ----------------------------------------------------------- Mit freundlichen Grüßen, S. Schicktanz ----------------------------------------------------------- ------------------------------------------------------------------------------ Systems Optimization Self Assessment Improve efficiency and utilization of IT resources. Drive out cost and improve service delivery. Take 5 minutes to use this Systems Optimization Self Assessment. http://www.accelacomm.com/jaw/sdnl/114/51450054/ _______________________________________________ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
