You can different views for these two situations, or you can have all fields on the view and programaticaly hide the ones you don't want the user to see
On Tue, Jun 7, 2011 at 7:23 AM, gadev <[email protected]>wrote: > Apologies if I haven't explained myself properly. > > Take for instance a form of the like: > > Firstname LastName > Description > Jobtitle > > When User A is editing or viewing his profile the form will me displayed in > full, all fields and if some are empty will be displayed with default text. > However, the user may decide to leave a field or more un-edited and save the > form. > > If another User B tries to view User A's profile, I do not want to display > fields with default values. That is what I am referring to as control what > to display in the view and what not. > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-web-toolkit/-/Z3ltR3BvMVppMW9K. > > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > -- Magno Machado Paulo http://blog.magnomachado.com.br http://code.google.com/p/emballo/ -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
