Windows Conformity

[slim]

Hi,

Does anyone now anywhere can I get information on windows conformity in relation to programming.

Thanks

Slim

[Paul Komski]

No-one's replied and I would do my best but not just sure what you mean. Maybe obvious to others but maybe you could elaborate on just what you want to conform to what.

[slim]

Hi,

Should have made myself a bit clearer, I'll try to explain better.

Basically, the company I work for is having some software developed by a programming house for processing mail ordering. The programming house are coding the application in visual basic and at this time we are starting to test a beta version of the software. What we would like to know is there any information avaliable regarding visual basic programming standards and conformity.

For example:

In the beta version of the software the drop down boxes in the application are a fixed size and do not adjust to the content size or add scroll bars if the content is greater or smaller than the size of the drop down box.

Another annoying thing, is that the developers have fixed the window size of the application to 800 x 600 (due to technical reasons they say) but we know for a fact if they were to use a simple windows api function, the window size could be adjustable, after not everyone has the same size screen.

So if anyone knows of anywhere we could get information on visual basic programming standards and in particular its relation to windows, it would be greatly appreciated.

Slim

[Paul Komski]

Apart from books and newsgroups one of the most comprehensive sources for programming with microsoft products is the MSDN library. It can be long-winded searching MSDN on the web (though it should of course be up-to-date) but if you can get your hands on a recent (recent enough to match the version of VB being used) CD of the MSDN library it can speed-up searching for any relevant information. A copy of the CD usually ships with any purchase of a Visual Studio product.

It is easier to create a program with a "fixed-size" GUI and "fixed-size" elements or controls than one which is more "plastic" to the different users' pc settings - so it sounds like the "technical reasons" could be more of a convenience or a way of getting the application running more quickly or even at a lower cost of development. Perhaps the program only runs in full-screen mode.

I have never created a drop-down (or combo) box that didn't have scroll bars enabled when needed, so that sounds like it only needs a little tweak.

Hope that is of a little help. "Conformity" is a difficult word in this context since there are so many ways of skinning cats and a wide range of third-party com and activeX controls can be included in what was pure microsoft at the start. The programming language has to conform (at least syntactically) but that language can control many diverse elements.

[HeadachesAbound]

As Paul said, "Conformity" is a difficult word.

It sounds like they are doing what most VB Developers, including myself, would do. Design for the most likely possibility (screen res) and go with it. Making the drop downs expand shouldn't be an issue though.

It is very possible that the "technical reasons" are entirely justified dependent on the interface that is being designed. It is also probable that having to allow for a more flexible range of resolutions would cause difficulties in the programming aspects and possible increase development time and cost.

A good place to look for some of those tips / tricks / tweaks for VB is http://www.mvps.org/vbnet/.

If you are truly in doubt, you might consider having another outside source look at the software specs and see what they suggest. It may be a viable alternative to go with someone else if they are unwilling / uncapable of providing you with what you have requested. After all, why pay for something that doesn't meet your needs.

[deddard]

You can try the following microsoft sites:
compabitility (http://www.microsoft.com/windows/catalog/default.aspx?subid=21&xslt=about&pgn=moreinfo)

or
windows catalogue (http://www.microsoft.com/windowsxp/partners/catalogoverview.asp)

These should give you a few pointers