At vero eos et accusamus et iusto odio dignissimos ducimus qui blanditiis praesentium voluptatum deleniti atque corrupti quos dolores et quas molestias excepturi sint occaecati cupiditate non provident, similique sunt in culpa qui officia deserunt mollitia animi, id est laborum et dolorum fuga. Et harum quidem rerum facilis est et expedita distinctio. Nam libero tempore, cum soluta nobis est eligendi optio cumque nihil impedit quo minus id quod maxime placeat facere possimus, omnis voluptas assumenda est, omnis dolor repellendus. Itaque earum rerum hic tenetur a sapiente delectus, ut aut reiciendis voluptatibus maiores alias consequatur aut perferendis doloribus asperiores repellat.
@saifoo.khan @Callisto @Ashleyisakitty @jamsmith @the1739man @robtobey
pls make it fast
Whats a user Interface ?
Making a user interface of the quality and complexity of facebook is not simple. What programming experience do you have?
I have a programming exp about 4 yrs
try be eclipse
There's a lot of special design work that goes into making an application like facebook. The UI is just one part. If you take out the UI and point it to another server that has the same API, it will do exactly the same. In that sense, its logic is considered separated from the server. For just the UI, usually, you expect the server to provide you with JSON objects through a REST interface. This means you need some special code for handling your requests for you (JQuery or similar is good). Beyond that, you'll probably need some type of widget package to let you create things with functionality beyond what's provided by HTML - for example a dropdown box that also searches for people. Then you need to create the logic for what people are supposed to see and when. You're dynamically showing and hiding things based on a number of criteria (what type of user it is, for example). For this UI to work, you need a server that provides you the JSON objects. That will need some security framework for authentication. Then, you've got a layer for directly handling HTTP requests (GET/POST/PUT/DELETE), where you'll check that the user is authenticated. You'll have a layer for validation and controlling any 'business logic', then you'll have a database access layer, which is where all SQL should be generated. You'll also need some way of passing objects between the layers ('model' objects). Then you'll need something to connect to your database for you. It is a lot of work getting applications of this quality up and running, if you're doing it alone with no experience in creating UIs. I described the approach that was used for the application I'm working on. Its Java using the springtools framework. If you use ASP.NET, some of those things are done for you. If you use PHP, check out the libraries that are available.