[gab00n]

Algorithms are fun, i'll think up one for tomorrow.

[Iron_Cross]

It's not that they're fun or not fun. It's that they don't take a team effort unless you're developing an algorithm for some super hard calculation. And you'll never know when you're done. I like writing algorithms, but that doesn't mean it's a good project for this group.

In an application you can assign different people to write different parts, you can't do that in an algorithm. That's why I say you might need to build a small application, because you can say, "Person1, you go work on the X. Person2, you go work on Y. Person3, you go work on Z." then everyone sticks their parts together and you've got a full application.

[gab00n]

Yeah i know we can just assign different modules to people and hopefully they will all work together perfectly, right guys . For the algorithm i thought we could just have a difficult problem and then everyone can give ideas until we have a nice efficient algorithm.

I recently did a reverse polish notation calculator for homework so maybe we could try make a GUI one. Just a simple + - / * ^ % RPN calculator. I don't know if you want to do it the OOP way, if everyone is familiar with that then we can. It is also more secure if we use classes.

example of postfix notation

postfix/prefix | normal infix
23 44 + 45 5 * / = (23 + 44) / (45 * 5)

[Iron_Cross]

A calculator is an application
First you need to pick a language, then you need to develop a "whitepaper" sort of thing. Then you need to assign parts to each person. Since you'll be using classes, you'd pretty much want to stick with C++ Java or one of the .NET languages. Since you're wanting it to stay simple and be pure OOP then I'd say Java or one of the .NET languages.
If you want I'll write up a little diagram of what classes we'd need and what they'd do, then y'all can take your pick from which ones you'd like to start on.

[vidyaputra]

its would be great if theres a little help(diagram of classes)^^

-vip-