1. Is there any way or tools to perform a Code Coverage testing for Pocket PC 2003 application developed using .NET CF 2.0?
2. Is there any Profiling tools available for obtaining memory usage statistics for for Pocket PC 2003 application developed using .NET CF 2.0?
I have created a website geared towards scientists and engineers to exchange code. Please visit and provide input, any codes you want to share, or request help with your code!
Any feedback mucho appreciated.
Having visited your web site, I have a number of suggestions
1. Try to change the width of your pages (1024). It is rather annoying that a simple web page has to grow horizontal scroll bars half as much as my browser window. My browser window is set to 800x600. I suggest that setting 800 wide is the norm to use.
2. Your bulletin board states only "C" code accepted. Yes that language is no doubt important but it is not the only language that engineers/scientists/others employ. Why restrict potential thus enabling a reduced interest in your web site offerings. And it is rather rude to suggest that people convert their hard-worked code just to satisfy you.
Thank you for your feedback Richard!
You bring in two very valid issues. I chose the 1024 width as a compromise...I know some people have their display resolution set to 1280, some 800, but seems to me nowadays the first one is most common. 1024 fits on 1280. Of course, some people browse from a window which can vary in size...it's hard to acommodate everyone
Let me stress out that if someone has a complete code, in any language, they are more than welcome to submit it to the site.
However, for the collaborative process, only one language can be used and C is the most common overall. Granted, scientists and engineers use Matlab a lot, as it is rather tailored for their environment, but I assumed not everyone has or is willing to purchase the Matlab package.
Visual basic is a valid alternative, and easier to use than C, but it exists, at elast to my knowledge, only in the Windows environment, and a lot of scientific programming is still done on Unix computers.
Since this issue has been brought up before, I plan to allow people to request help with codes written in Visual Basic as well.
Now that Code Project has altered its web site, not just in its colours but in the width of the browser window, apparently 800 wide window is no longer "the norm". Look at the comments and critisisms that Code Project got this past few days after altering their web site.
As an idea for your web site, those people/organisations who submit code to you, are these people going to be able to put together a suitable tutorial, not just to explain the code, but also explain the reason for the existence of the code - namely to solve (or attempt to solve) a problem, and how this problem manifests itself. This tutorial used use drawings (such as UML/SSADM/???) and the english-like psuedo-code to help explain "where from (starting point), where to (the target), and how to get there". Perhaps including powerpoint presentations as a means to get greater understanding of issues presented.
I have covered that in the submission guidelines. To keep things simple, I upload each program as a text file. I'd like the purpose of the code well stated in the beginning, input and output format well documented, and the code nicely commented. If the theory behind the program is well established, the submitter need only provide a reference such as textbook or publicly available paper.
Also, without meaning to offend, I think your site could do with some serious UI overhaul.
May I suggest:
• Don't use grid layout/absolute positioning. If you change to flow layout you won't have to worry about screen resolution as much.
• Your main navigation bar across the top of the screen could be downsized a bit. You could use a vertical navigation bar (like an inverted "L"?) or turn your solvengineer graphic into a link to the homepage so as to do away with the "main page" link.
• Put the search box below the main graphic & make it (the search utility) smaller.
• Remove or resize the "Welcome to Solvengineer.com" in pink. It serves little purpose. Besides, without trying to sound chauvinist, I don't think many engineers have pink as one of there favourite colours.
• Take the rss feeds & code search out of scrolling forms & give them their own separate space, even if it means another page. Make the latest news the main focus of the homepage.
• Get rid of the links below the embedded code search from Google - they're redundant and confusing.
• Make the point of the site more concise (i.e. to the point) & make the main feature of your home page the latest news. If need be, you could add another page with a more in-depth explanation of what the aims of the site are.
• Move the advertising to the bottom of the page - keeping it near the top gives the impression of a "cheap" site. Try to make the ads less "google like" (if possible, I've never worked with advertising through Google).
Once again, this is not intended to offend but to encourage. I didn't want to criticize your site without giving you some useful tips for you to consider. I like the concept of your site & I think with a good UI & some smart management you could turn it into a useful resource.
I've written an article on low-level keyboard hooks in C# based on an application to prevent babies and other animals from causing too much damage when they hammer the keyboard. The article is quite in-depth and I'd like someone to have a look at it to check that it all makes sense! Any volunteers?
If you are using PC-Lint 7.50 or 8.00 with Visual Studio 6.0 under Windows 2000 or later and are in the position to help us to verify the performance of Visual Lint on that platform, we'd like to hear from you.
Anyone who participates will have access to this version of the product well before it becomes available on the open market, and will also of course have the opportunity to suggest changes and enhancements as the product develops. There is no-cost or sales committment required; all we ask is that a non-disclosure agreement be signed between the tester and ourselves since our testers have access to internal product information.