This is a Messaging application for PC's running on a Network that is connected locally via Ethernet, and between multi-locations via DSL Data Network. All PC's talk to each other via the TCP/IP Protocols. Most PC's run Windows XP. A Few run Windows Server 2003, NT, and 2000.
The entire network is accessible via a Private set of IP Address - setup on the same segment; i.e. 172.20.x.y where x is the location number (currently 1 to 20)and y is the PC number (1 to 255). Just a standard TCP/IP setup. Total number of PC's maybe something around 100 to 120.
The messaging application can be developed so that messages are sent in a Peer-To-Peer fashion, or via a Server. We have no preference. We can accept both styles.
We have tried almost every application on this planet. The only one we found to satisfy our needs, did not support Arabic characters in its TEXT BOXES, and the vendor said, he has a very limited support and he cannot make any changes to the application.
We have therefore thought that we post this as a project here to have one developed and customized to us, with the following features:
1. The application will have English Interface. But it must support Arabic TEXT. Simply the text boxes that are used to input messages, or display a received message, must be setup with a font that displays arabic correctly.
2. must allow the difinition of groups and recepients.
2a. Groups will simply be Group name, Group Description.
2b. Must allow for adding recepients. recepients will be:
Recepient Name, IP Address, and Group Name.
Note: There will be a default Group called everyone. That default group cannot be deleted. Any recipient added to any group, will also automatically be added to the Everyone's Group.
Note also, When adding recepients, the Group name will be selected from a drop-down of the available groups in 2a.
The IP address is an address of another Windows PC that is PING(able) and reachable. Most probably it will be on the same segment as explained above 172.20.x.y.
3a. Send Message. The send message will ask for a recepient and a subject, along with a TEXT Box of rasonable length. Suggested length would be 4000 characters. The recepient could be a single recepient, or an entire group.
Reply is the same as SEND. The only difference is that it includes the message that is to be replied to in the message below a dashed line, and set the cursor ready for typing the reply above a dashed line. It also places RE: with the subject in the Subject field.
3c. Station ID:
This is a field that must be setup once the application is setup. It is basically a TEXT Description of the station running the Messaging Application. This will be used in the advanced eatures listed below.
4a. Application must sit in the system tray (as a service). If attempted to close, again, it silently sits in the system tray. Only when right-clicking the icon in the tray, Exit shows up to force application close.
4b. When receiving messages, it must POP UP a window. That window must be brought to TOP burning through possible MAXIMIZED windows applications currently running on the recipient machine.
4c. Auto-save messages. Application must be able to automatically save inbound and outbound messages. It must also be able to retrieve those via LOG functions to be added to application.
4d. Scan 'n' verify network. This is a fucntion that will SCAN through defined Recepients, and shows an indicator as to weather or not that ecepient is alive or not. The indicator could simply be that the Recepient's PC is PING(able) however, a better indicator would be if it can tell if the "Messaging" application on the other end is ALIVE and ready to receive messages.
4e. Save window Position and Size. This feature should allow every user resize the application's window size and position, and then click save window's position. When closing the application with X, it sits in the system tray. When a message is received. The message is POPed up and Burned through applications (Brought on TOP) to the exact position and to th same size previously saved with.
4f. Receipt Notification. When a received message POPs up. It won't be allowed to be closed or minimized unless a button "Acknowedged" is pressed. When that message is pressed, the application can then be minimized, etc. A Received "receipt" is sent to the SENDER saying: xyz received your message with the subject blah blah blah.
4g. application must be able to tell if a message is received on the other end. i.e. sending a message to a dead PC should indicate that the recepient is DEAD.
4h. Messages that cannot reach the meant recepient should be automatically re-tried and attempted every x minutes as defined in the Options of the application.
4i. All messages must be logged with Time and Date. Also, all messages must be shown when received at any station "WITH" the Time & Date it was originally sent.
5. Advanced Features:
5a. Font/Colors setup. This should allow the user configure the messaging application to display background color of received messages, font color/font name/font size of received messages according to his/her liking. Also, the same applies when authoring messages (or sending replies).
5b. Any sender who sends messages to a receipient, his Station ID, IP are automatically added to the recepient's addressbook once the POP'ed up message is acknowledged.
25 freelancer bu iş için ortalamada 1043$ teklif veriyor
We have done numerous business applications. We feel we can do a quality job delivered in the time mentioned by [url removed, login to view] are a company with numerous resources and very good manpower available. By leveraging our best we a Daha fazlası
I am interested in this project. I have 2 years of experience in .NET only so if you give me chance, I assure you full satisfaction. Want a chance only nothing else
Hi I have developed this kind of software before. I designed it as a Client-Server Chat system. Although not all the features you sited are there but I can add them to the system.