Hi allwhat is to be kept in mind while developing web application? any special things other than Notes Client?
Secondly while deploying application to web what is the process that converts designing in notes to web.Is it admin procedure or it can be done by developer?
anyone having any idea pls explain me.
thanks
Subject: web development
Mary,
If your server is running http then you can open the db with a browser already! So you can see that it’s probably 80% functional but very ugly.
For the web, you typically have to do a lot more work to make it pretty, compared to the work to do this for Notes Clients. You also typically have to do a bit of juggliing for field computations of hide/whens or buttons that do lookups or popups. Backend script works just fine, but you trigger it differently.
It’s a bit of a different ballgame for these things, but there are some books out there and it’s all good fun.
good luck,
raphael
Subject: web development
The HTTP task takes care of the conversion of forms etc as it sends /recieves the HTTP transaction. This said I prefer to keep the Notes and Web forms separate. It does mean some double design but IMHO it does make the whole process somewhat simpler. I also use subforms to include common element that don’t need special Web or Notes consideration. As for the forms I create two forms with the same alias one visible to the Notes Client and the other visible to the web client. Now each client loads the document with the correct form and it is rendered either by the Notes or the Web client as the case maybe.For simple applications that can be view well in either client then I design a single form, but remember that there are Notes UI issues that do not represent well on the web. For a simple example Tables when you get fancy with merging cells and borders in Notes it ain’t necessarily the same on the web.
The beuty of Domino is of course you can create and view the results in either the notes client or the web client even on a stand alone machine or lap-top.