亲爱的MS VS 2005开发者 [英] Dear MS VS 2005 developers

查看:49
本文介绍了亲爱的MS VS 2005开发者的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

有没有人知道我可以将这封信发送给谁,以便它在回到家之前

Visual Studio 2005投入生产?


亲爱的Microsoft Visual Studio 2005开发人员,


这是要求您将四个最基本的控件改为

改进它们并使它们之间更加一致。


我说的是输入文本的四个控件:


a。文本框


b。蒙面编辑


c。组合盒


d。日期时间选择器


e。复选框(好吧,所以它真的是五个控件)


让我们从一些我称之为改进的东西开始:让我们停止浪费4
$在上面列出的每个控件上,b $ b像素的有价值形式的房地产。

这是浪费:在每个

周围画一个3D边框需要3个像素这些控件(我想那就是3D中的3来自哪里,嗯?)。但是严重的是,如果将边框绘制为单个像素,那么只需要2个像素的空间来绘制每个控件,而不是6个像素。现在,

当你将表格上的控件数乘以4个浪费的像素时,

等于每个表单上浪费的大量房地产。


3D控制边框什么都不买。此外,以上五个控件的'3D

外观与tabpages,菜单项,listviews,

工具栏等等不一致。我认为这是'时间我们都放弃了古老的3D外观

并成为平地的好公民。一个例外是按顺序:允许

flat和3D按钮。因为现实世界中按钮的模拟真的是真的

3D,所以它应该看起来需要被推动。


现在我们知道如何回收每个控制四个像素,让我们不要停止

那里。为什么文本框的高度必须为20像素?在边框和文本本身之间必须有至少3到4个像素的空白区域。

让我们标准化所有的18像素高度四个文本控件。

在那里,我们为每个表单上的每一个

控件保存了另外2个像素的空间。这样就留下了16x16下拉箭头图标,没有需要更改



现在让我们继续讨论一致性问题。这五个(四个)文本控件的

属性不一致在Visual

Studio中确实存在问题。每个控件都应具有以下属性:


a。 FlatStyle(不适用于DatePicker)


b。 BorderStyle = FixedSingle(不适用于DatePicker)


c。 MaximumSize(在ComboBox中重写)


d。 TextAlign(如标签)文本位于DatePicker底部,位于18

像素高度。


因为所有这些文本控件都可以并且经常一起出现在

单一形式,所有这些都应该是高度可对齐的并且可以文本对齐

做出最好的演示。为了与组合框的高度相匹配,必须让它们全部高度为21 b / b
这是荒谬的。


最后,如果你想看看如何全部在进行任何控制重新设计或编码之前,这些控件应该看起来像是b $ b,我可以将你推荐给这个网站: http://www.lumisoft.ee/lsWWW/ENG/ind...?type=产品


如上所述,您会在其中找到文本框,日期选择器,组合框,屏蔽编辑框和

复选框。并且,请,请查看每个控件中内置的

..FlashControl属性。它使你的

ErrorProvider控件不必要且可能过时了。 (这也浪费了

更多来自房地产)。


为什么我告诉你这一切?是的,我正在使用这些控件,而不是你的b
。问题是,它们不具备足够的工业强度,足以用于企业应用程序。如果你只能重新设计你的控件以便它们看起来像这些控件,并用你的

工业强度属性和方法来支持它们,应用程序设计的世界

将是一个更好看,更具房地产效率,以及更多

一致的开发地点。


我我现在要离开我的肥皂盒等待你的回复。


感谢您的倾听。


Dean Slindee

Does anybody know to whom I can send this letter so that it hits home before
Visual Studio 2005 goes production?

Dear Microsoft Visual Studio 2005 developers,

This is a request for you to change four of the most basic controls to
improve them and make them more consistent amongst themselves.

I am speaking of the four controls into which text is entered:

a. Textbox

b. Masked Edit

c. Combo Box

d. Date Time Picker

e. Check boxes (ok, so it''s really five controls)

Let''s start with something I call an improvement: Let''s stop wasting 4
pixels of valuable form real estate on each and every control listed above.
Here is the waste: it takes 3 pixels to draw a 3D border around each of
these controls (I guess that''s where the "3" in 3D came from, huh?). But
seriously, if the border were drawn as a single pixel then it would take
only 2 pixels of form real estate to draw each control, not 6 pixels. Now,
when you multiply the number of controls on a form times 4 wasted pixels,
that equals a lot of wasted real estate on every form.

A 3D control border buys you nothing. Besides, the above five controls'' 3D
appearance is inconsistent with that of tabpages, menu items, listviews,
toolbars, etc, etc. I think it''s time we all abandon the archaic 3D look
and become good citizens of flatland. One exception is in order: allow both
flat and 3D buttons. Since a button''s analogue in the real world is truly
3D, therefore, it should look like it needs to be pushed.

Now that we know how to reclaim four pixels per control, let''s not stop
there. Why do text boxes have to be 20 pixels in height? There must be at
least 3 to 4 pixels of white space between the border and the text itself.
Let''s standardize on an 18 pixel height for all of the four text controls.
There, we''ve saved another 2 pixels of real estate for every one of those
controls on every form. That leaves the 16x16 dropdown arrow icon as is, no
changes needed.

Now lets move on to the problem of consistency. Inconsistency in the
properties for these five (four) text controls is really a problem in Visual
Studio. Each of these controls should have the following properties:

a. FlatStyle (not for DatePicker)

b. BorderStyle = FixedSingle (not for DatePicker)

c. MaximumSize (overridden in ComboBox)

d. TextAlign (like label) text rides at bottom in DatePicker at 18
pixels height.

Since all of these text controls can and often do appear together on a
single form, all of them should be height-alignable and text-alignable to
make the best presentation. It is ridiculous to have to make them all 21
pixels in height just to match the combobox height.

Finally, if you would like to see how all of these controls should look
right now, before doing any control redesign or coding, may I refer you to
this web site: http://www.lumisoft.ee/lsWWW/ENG/ind...?type=products

There you will find a textbox, datepicker, combobox, masked edit box, and a
check box as described above. And, please, please, please check out the
..FlashControl property built into each of these controls. It makes your
ErrorProvider control unnecessary and possibley obsolete. (It also wastes
more form real estate).

So why I am telling you all this? Yes, I am using these controls, not
yours. Problem is, they are not quite industrial-strength enough to use in
enterprise applications. If you could only redesign your controls so that
they could look like these controls, and back them up with your
industrial-strength properties and methods, the world of application design
would be a much better looking, more real estate efficient, and a more
consistent place to develop in.

I will get off my soapbox now and await your reply.

Thank you for listening.

Dean Slindee

推荐答案



" Dean Slindee" < SL ***** @ charter.net>在消息中写道

新闻:VB ****************** @ fe02.lga ...

"Dean Slindee" <sl*****@charter.net> wrote in message
news:VB******************@fe02.lga...
有谁知道在Visual Studio 2005投入生产之前,我可以将这封信送到家里
吗?
Does anybody know to whom I can send this letter so that it hits home
before
Visual Studio 2005 goes production?



< snip>

这是'的地方。

http://lab.msdn.microsoft.com/vs2005/default.aspx


请注意产品反馈中心标题下的链接。题为:


提出建议或报告错误

-

Peter [MVP Visual Developer]

所有行业的杰克,无人掌握。


<snip>

Here''s the place.

http://lab.msdn.microsoft.com/vs2005/default.aspx

Note the link under the heading "Product Feedback Center" entitled:

"Make a Suggestion or Report a Bug"
--
Peter [MVP Visual Developer]
Jack of all trades, master of none.


院长,


除了彼得,也许以及更适合您要求的地方

http://forums.microsoft.com/msdn/Sho...spx?ForumID=32

然而你让我很好奇为什么不是日期时间选择器,我所看到的
这些新闻组中的
是组合/列表框旁边需要的控件

最受关注。


Cor
Dean,

In addition to Peter, maybe as well a better place for your request

http://forums.microsoft.com/msdn/Sho...spx?ForumID=32

However you make me curious why "not the datetime picker", what I have seen
in these newsgroups is that the control that needs beside the combo/listbox
the most attention.

Cor


" Dean Slindee" < SL ***** @ charter.net> schrieb:
"Dean Slindee" <sl*****@charter.net> schrieb:
在Visual Studio 2005投入生产之前,是否有人知道我可以将这封信发送给谁以便它回家
Does anybody know to whom I can send this letter so that it hits home
before
Visual Studio 2005 goes production?




我怀疑在Whidbey

版本中有很高的机会得到修复,但是,你可以在MSDN产品中报告建议和错误

反馈中心:


< URL:http://lab.msdn.microsoft.com/productfeedback/>


- < br $>
MS Herfried K. Wagner

MVP< URL:http://dotnet.mvps.org/>

VB< URL: http://classicvb.org/petition/>



I doubt that there are high chances to get that fixed in the Whidbey
version, however, you can report suggestions and bugs in the MSDN Product
Feedback Center:

<URL:http://lab.msdn.microsoft.com/productfeedback/>

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>


这篇关于亲爱的MS VS 2005开发者的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆