- developing a browser engine
- developing the GUI around a browser engine
The first is not rocket science, but lots and lots and lots of work, and will require some hacks, as there are many areas where specs aren't clear (what to do with invalid html, http headers that promise a text encoding that is not delivered, what to do when http headers say "text/html", but the url ends in ".zip", etc, etc)
The second can range from the almost trivial to whatever your imagination requires.
Unless you have lots and lots of time and/or resources and cannot use an existing engine such as Mozilla or WebKit, stay away from building your own engine.
- developing a browser engine - developing the GUI around a browser engine
The first is not rocket science, but lots and lots and lots of work, and will require some hacks, as there are many areas where specs aren't clear (what to do with invalid html, http headers that promise a text encoding that is not delivered, what to do when http headers say "text/html", but the url ends in ".zip", etc, etc)
The second can range from the almost trivial to whatever your imagination requires.
Unless you have lots and lots of time and/or resources and cannot use an existing engine such as Mozilla or WebKit, stay away from building your own engine.