Hello -
I've extended the appointment class to add some custom fields. I followed the suggested implementation, using the WebObjectBase's GetValue and SetValue to store my new properties. Can anyone tell me the benefit of this over having my own member variables? I was hoping that this implementation would send my new properties to the UI in some way, so I can access the properties with client-side scripts.
Thanks!
-Brian
We are VERY interested in passing custom properties back and forth to a customized AddAppointmentDialog and/or our own web pages. This entails sending such properties back and forth to the client-side, obviously.
I'm trying to get an update on this issue. Does Infragistics have any plans to make this happen in the near future?
Please advise. Thanks so much.
-BillyB
Derek,
Derek Harmon"] You're right that it would be nice if these could send the custom properties to the client-side - but they do not at this time.
You're right that it would be nice if these could send the custom properties to the client-side - but they do not at this time.
I'm afraid that I might have understood what you replied to brassier. If I got it right... so even if I subclass Appointment (i did it, adding 1 extra field), customize a data provider (be it OleDB or Base), customize the forms... will I never get a custom field into my custom Appointment form or even at WebMonthView???
I'm trying to add this ONE custom field (at least, for while) for each Appointment, so I created my AppointmentSFE class. It was a pain to customize everything else, and it still didn't work, also tried to go directly to change Update, but I can never cast "context.Activity" to my class (invalid cast error). So I'm kinda stuck at it, at this time I'm just trying and trying and trying, but... if a custom Appointment form (I still didn't customize it) will never get the data (automatically through the bindings, I mean), it seems I'm just losing my time customizing something that wasn't made to be customized.
GetValue and SetValue methods are plumbing in the WebUI.Shared class library, their primary purpose is to help with viewstate handling of said property (ours, yours). In WebSchedule, Appointments are not saved in viewstate, but if you wanted to save/restore them to viewstate using these methods they would help you to bring your properties with you using the Shared class library's plumbing to do it.
Put another way, these methods have a relationship to the persistence of properties. WebSchedule (it is the only control/group of controls that does this) relies on them for its data binding (as it doesn't rely upon them for the object's viewstate management). If you subclass one of the data provider base classes, and take several steps (talked about in another thread), then property values retrieved/stored using Get/SetValue enable the data provider base classes to automatically transport it back and forth to the database.