Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I have to create a user requirements specification for an application. I will need treeviews, menus, gridviews (with data). What is the quickest way to do this with little or no code and no database data. The application would need to react as almost if it was the final product. My initial thoughts is to programatically populate the treeview and gridview from xml files so i can change without any coding.
Does this make sense or what do other people do?
The application would need to react as almost if it was the final
product.
I think your first step is to set more realistic expectations and explain (possibly to the stakeholders?) the difference between a demo and a full product. If you are going to put in all the effort to make it that close to the final product, then it's probably not a demo. You might as well release it as a "beta" version.
Why not take a step back and create wireframes in a tool like Balsamiq and a simple functional spec in a Word document, Google docs or a Wiki? That can be created in a comparatively small amount of time and will give you a much better foundation to build the actual product or, at least, take a step further and create a demo with limited functionality.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I work for a small Point of Sale Company, and we are working on a in-house tool to make our lives easier when it comes to ticketing and troubleshooting. Part of my task in this tool is to write a 'softphone' in C# WPF that we can use to accept incoming and make ongoing calls with.
We currently use OnSIP as our SIP provider, and are looking to build custom software to essentially allow us to auto-generate support tickets based on the phone number of the incoming call. In addition we will need call transferring, recording, hold/wait, etc.
The question that seems to be causing me the most trouble is really where to begin on something like this. Thoughts?
I'm presuming this is a desktop application?
Lookup pjsip.org, it's a portable C library which is very well proven. It will allow you to do all that you are asking, although it'll take you some time to write the wrapper code - you can find examples on the internet, however we have written a wrapper ourselves which I'll check on as we had intended open sourcing it. This is because when we did this last year, the examples just didn't work too well :-)
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I'm starting on the second version of a large Solution/Project that I created and was wondering about the best way to go about it. I'll be changing allot of the core code, classes and projects of the solution and that makes want to make this into a separate solution and separate repository.
I've never really started on a version 2 before, so if anybody could give me advice on the best way to go about it I would truly appreciate it.
For the record I am coding in C# and using VS2012.
Thank You
Create a Branch in the repository called Version2 or something (maybe a better code name) and do all the new dev work in that. That way you still have the original Trunk if you need to go back to it. Maybe also create a Tag with the current project that will never change so you basically take a snapshot of it before making any substantial changes.
I usually keep everything in one solution and just evolve the solution. There are several benefits to this:
You refactor your tests along with the project (hope you do have some!)
Keep a tracked version of all the changes in your source control
It's easier to make sure your project is still stable after the refactoring by running test suits or running the executables in debug mode
It is safer to refactor little bits and peaces, than a global re-write, there is a risk you will go a little bit to far with refactoring
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I am about to start making a simple little video editing application, and I was trying to decide what system to create the GUI in. I know a lot about the Windows API, and actually, all of my programs thus far have been written in it. I would really like to use the new WPF framework though; however, I am a bit concerned about the fact that C# may not be ideal for a performance-oriented application. And I'm not positive, but I don't think it is possible to use SIMD instructions in C#?? Of course, my video editing program will use DirectX, and then I've read about problems of using that in C#. So then I had the idea that maybe I'd write the "core" of the program in C++ and somehow link it to its GUI through DLLs or something. Of course, that could be really messy... Any ideas? Thanks!
Why not managed C++ and either winforms or c#/WPF ui?
I wouldn't use MFC.
WPF has a future, and skills learned in it are saleable. Not so sure about MFC...
I wouldn't worry about performance of C# versus C++; there have been several benchmarks that show an approx. 10% speed increase using C++. The major issue is object creation/deletion. Reducing this is one of the main issues with C# performance.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I am starting to make my own apps and publishing them. The problem I face is that my apps are mainly for my purposes. What are some problems that you face while in windows? I need some desktop application ideas that are simple but helpful.
Rather than giving you a fish, I will humbly try and teach you how to fish:
Take a blank sheet of paper and write out as clearly as you can the problem that you want to tackle. Clarity is key because clarity of purpose gets your mind focused on what you are really trying to accomplish.
Think of at least 20 ideas and write them down on that once blank paper. Let your mind really flow and give up worrying about whether your ideas are practical or what other people will think about them.
Read over your list and determine which ones actually are good ideas. You might want to put the list away for a while and then take it out the next day to see if you still think those ideas pass whatever test you have for your ideas.
Lather, rinse, repeat.
Note that I don't necessarily know that I have a problem until you show me that I have a problem, and then show me how to fix it. Personally I think computers are still too hard to use, and I'm a programmer. Because my work life is so complex I like software and gadgets that are simple and elegant. MP3 players existed long before the iPod came out, but the iPod was able to get the mix right.
http://hubpages.com/hub/How-to-Come-Up-with-Good-Ideas
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
A couple of months ago I've coded a tiny tool that we needed at work for a specific task, and I've decided to share it on CodePlex. It's written in C# and honestly it's not big deal but since it's the first project I've ever built from scratch in that language and with the goal of opening it from the very beginning, one ends getting sort of emotionally attached to it, I mean you'd wish that the people will actually participate, be it criticism, bug reporting, or what have you.
So my question is, what can I do to actually encourage participation, stimulate curiosity or just recieve more feedback about it?
By the way this is the project I'm talking about: http://www.codeplex.com/winxmlcook/
You should:
Promote it where you think it would be relevant (forums,mailing lists etc.). Try not to spam though - it will create a backlash.
continue to provide updates as to create the appearance of an active project until more people pick it up.
Find project leaders, they are the sort of contributors that encourage others to contribute as well.
Blog about it and link to relevant blogs (creating ping-backs). Also leave comments at relevant blog posts.
Basically, your generic Internet marketing tactics ;)
You first have to acquire users by marketing the tool. Once you have users, that naturally means you'll start getting feedback.
One thing I noticed is your project description doesn't sell the project well. For example, type "winxmlcook" into Google, what gets shown is your project description but it's not likely to get someone to click on it.
I know I sound like a broken record constantly posting this book, but just about everything you could ever need to know about running an open source project is here. In particular, pay attention to these two chapters:
Getting Started
Managing Volunteers