need help in C programming

[smiling]

hello

i have 2 projetcs to do in C language, i have one month to finish them but ididn't start yet
the seem too hard to me and i don't know how to start

here are the details:

first projetct

This project must be realized in English
Configuring a router using Internet on Mac OSX
This project is for PS1 and uses technologies of the Apple and Cisco laboratories.
If you have any question about this project, you can send an email to these laboratories.
The aim of this project is to allow a user to configure a router thanks to a graphical interface on a Mac OSX client.
The user will be able to execute a command without any knowledge of the IOS system (or of any terminal) using a program developed in C with a graphical interface.
This command will be executed from the web server and sent to the router (The router’s model must be the one present on your school’s lab) in “AppleScript” format.
It will generate a succession of IOS commands (Version 12.3 or more), and execute the desired configuration.
It will also have to retrieve the return values of the router, which will be transferred to the program.
You will have to catch the configurations/communication errors and treat it.
It will be also possible to directly generate the configuration file and to send it.
You will also have to create a Widget on Mac OSX (Using HTML, CSS, and JavaScript), giving the functionalities previously enounced.
User and technical guides must be realized in English on HTML format.



the second project

The aim of this project is to develop a cross platform mail application. Your application must be able to:
- Fetch mail from any POP3 servers.
- Send mail through any SMTP servers.
- Support of internet mail providers such as Hotmail is not required.
Your program must implement the following specifications:
-A friendly graphical user interface that matches the operating system graphical style. This interface will be composed of:
- An account list on the left.
- A menu bar on the top for default actions.
- A reading pane on the right.
- Between your reading pane and the account list, we must be able to see a message list representing mails for the selected account.
Note: You can use the look and feel of Microsoft Outlook as reference.
-A possibility of multi-accounting:
The user must be able to specify more than one mail account on your application. Account must be regrouped by server address. I.e. : if I have three accounts on my.smtp.com I must see one mail box for the server with three folder, one for each account.
-Possibilities of mail creation (new mail), forward mail and respond to the mail.
Note that you don't have to develop the associated mail server.
Project Constraints
The only programming language allowed is C.
You are free to use any graphical library you want.
The program must run on Windows and Linux, Mac Os is optional.


so, plz can anyone help me to start , or if possible be a partner in these projects' work???

i appreciate your help

My regards

[@nthony]

lol, centered, multi-colored text, asking for homework to be done with no attempted code posted and one post count... I know its only april, but I think barbeque season is upon us already...

Edit:
okay, that was more snide than it was helpful:
1) Write like a NORMAL person expecting to receive help from other normal people, not a kindergardener with his first box of Crayolas.
2) We help you help yourself, not do it for you. We need to see that you've at least attempted a solution either through code or even logical analysis before we invest time into your problem.
3) "or possible be a partner in these projects'"... wow, just wow. It's not bad enough that you can't find a partner to leech off in your class, you have to recruit online?? Did I mention this is a self-help forum, not do-it-for-you-while-you-slack-off?
4) Be specific with your problems, don't just dump an entire project specification (which contains many problems) and expect to receive solutions on each one.
5) If you neglect to follow any of the above rules, invest in a flame retardent forum-posting suit.

[KONI]

This post is 5 days too late...I'm smiling anyway

[smiling]

first sorry if the u don't like my way of asking for help, i just used colors to seperate the 2 projects
i know that i should start by helping my self first but what can i do if what we are studying in C programming have nothing to do with what they are asking us to do

in class we just make small programs like looking for palindrom, applying fibonnaci equation, conversion celcus fehrenheit.....
thee projects are way too difficult than what we study
plus this is my first year in computing science and i never touched to programing before so am so confused
and, u think i didn't tried to look for a partner in my class,!!!!! here it's just everyone for himself and god for all,so i prefered to look for support online

[itsme86]

Well, for the first project it looks like...

If you have any question about this project, you can send an email to these laboratories.

...is probably a good place to start. Are you saying you don't know how to send emails?

Instead of looking at the project as one big terrifying, nightmare...break it up into logical pieces and tackle each one separately.

[Salem]

> i have one month to finish them but ididn't start yet
So two weeks for the first one, and two weeks for the second one.

Identify 10 to 15 specific requirements in each one, and spend half a day finding out all you can about that specific point, and make some notes as to how you might implement it, or ask here a specific question about that particular topic.
Try to look at them in pairs, so if you get stuck on one (or waiting for an answer), you can be getting on with something else.
That will take you the first week for each one.

You might also write very small programs to test specific ideas, like say
"A C program to send one specific IOS command".
When you're happy you can do that bit, then forget about that program and move onto the next topic. Resist the temptation to try and expand your test program into being your entire assignment.

Then in the second week, you spend
- a day fleshing out the design - this is HOW you're going to do the WHAT you've been asked to do. In particular, how different parts of your code will communicate with each other.
- 2 to 3 days writing and module testing the code
- a day or two bringing all the modules together and testing to make sure the whole program does what you want it to.
- a day finalising whatever documentation you need to produce.

If all goes well, you'll have a day off.
If not, then you've got a small buffer to try and fix a few things up.

> thee projects are way too difficult than what we study
Perhaps its "survivor" time to see who's got what it takes and who's going to get booted off the island. They certainly are stretching tasks, but perhaps the test is as much how you tackle the problem as it is how far you get.

[@nthony]

...in class we just make small programs like looking for palindrom, applying fibonnaci equation, conversion celcus fehrenheit.....
...plus this is my first year in computing science and i never touched to programing before so am so confused

Well in that case, it doesn't take a genious to figure out what's going on here...

This post is 5 days too late...I'm smiling anyway

[smiling]

> i have one month to finish them but ididn't start yet
So two weeks for the first one, and two weeks for the second one.

Identify 10 to 15 specific requirements in each one, and spend half a day finding out all you can about that specific point, and make some notes as to how you might implement it, or ask here a specific question about that particular topic.
Try to look at them in pairs, so if you get stuck on one (or waiting for an answer), you can be getting on with something else.
That will take you the first week for each one.

You might also write very small programs to test specific ideas, like say
"A C program to send one specific IOS command".
When you're happy you can do that bit, then forget about that program and move onto the next topic. Resist the temptation to try and expand your test program into being your entire assignment.

Then in the second week, you spend
- a day fleshing out the design - this is HOW you're going to do the WHAT you've been asked to do. In particular, how different parts of your code will communicate with each other.
- 2 to 3 days writing and module testing the code
- a day or two bringing all the modules together and testing to make sure the whole program does what you want it to.
- a day finalising whatever documentation you need to produce.

If all goes well, you'll have a day off.
If not, then you've got a small buffer to try and fix a few things up.

> thee projects are way too difficult than what we study
Perhaps its "survivor" time to see who's got what it takes and who's going to get booted off the island. They certainly are stretching tasks, but perhaps the test is as much how you tackle the problem as it is how far you get.

thanks for this strategy, i'll try to make a schedule to work
your adviced seems very helpful i'll try to start with the documentation about the projects
if u got any documents or websites that may be helpful plz tell me
first i need to know the basics about the projects, for exemple the mail client, i have to know from what the program should be composed, so i can seperate the whole thing into small pieces
i am gonna start to look more, and i'll come back if i got any specific questions

[Salem]

Well POP3 and SMTP are defined by the RFCs, which are maintained at http://rfc-editor.org/
Enter the relevant acronyms into the search.