tag:blogger.com,1999:blog-1944926148473713281.post8089479362468841488..comments2024-03-11T04:42:50.934-07:00Comments on News, tips, tricks and more about DevExpress Application Framework (XAF) directly from the lab: Avoiding repetitive customizations for Views of the same type or subclasses via the Model Editor - YOUR FEEDBACK IS NEEDEDDennis Garavskyhttp://www.blogger.com/profile/05439634942797151905noreply@blogger.comBlogger13125tag:blogger.com,1999:blog-1944926148473713281.post-34990304951416850202015-10-07T11:45:23.789-07:002015-10-07T11:45:23.789-07:00I prefer inheritance. Good initiative...I prefer inheritance. Good initiative...Anonymoushttps://www.blogger.com/profile/06922642938454975820noreply@blogger.comtag:blogger.com,1999:blog-1944926148473713281.post-30913010097951003892015-10-07T07:39:59.827-07:002015-10-07T07:39:59.827-07:001. Yes
2. It is important and I deal with it often...1. Yes<br />2. It is important and I deal with it often.<br />3. I think it's good but Xpand PartialViewInheritance suits my needs better.<br />4. I use Xpand PartialViewInheritance.Anonymoushttps://www.blogger.com/profile/10367341550598563333noreply@blogger.comtag:blogger.com,1999:blog-1944926148473713281.post-62927700244068338062015-10-06T00:38:22.297-07:002015-10-06T00:38:22.297-07:00Guys, I greatly appreciate your answers and additi...Guys, I greatly appreciate your answers and additional feedback on the ideal behavior.Dennis Garavskyhttps://www.blogger.com/profile/05439634942797151905noreply@blogger.comtag:blogger.com,1999:blog-1944926148473713281.post-28654890426052523692015-10-05T21:58:29.586-07:002015-10-05T21:58:29.586-07:00I can confirm here too, that's a good solution...I can confirm here too, that's a good solution to make a copy/or reference/or changeable reference of the default details view of the underlying object so that the work in object details view will not remake every time. <br />I'm very welcome your idea dennis Anonymoushttps://www.blogger.com/profile/14535376303083479221noreply@blogger.comtag:blogger.com,1999:blog-1944926148473713281.post-11395724959638786182015-10-05T21:45:39.625-07:002015-10-05T21:45:39.625-07:001. Yes.
2. Regularly.
3. Better than nothing but n...1. Yes.<br />2. Regularly.<br />3. Better than nothing but not ideal as explained.<br />4. No, <br /><br />To 3: add an Option:<br />Inherited View Changes after Class update<br />If true doit in xaf automatically , if false let the user the possibility to use the show difference solution. <br /><br />Regards Lars <br />Anonymoushttps://www.blogger.com/profile/14535376303083479221noreply@blogger.comtag:blogger.com,1999:blog-1944926148473713281.post-39907753148905410682015-10-05T07:26:24.601-07:002015-10-05T07:26:24.601-07:00In that case we will absolutely welcome any improv...In that case we will absolutely welcome any improvements in this area. I am part way developing a fairly complex XAF aplication but have not yet done much with the detail views.wadehttps://www.blogger.com/profile/04298117484273185321noreply@blogger.comtag:blogger.com,1999:blog-1944926148473713281.post-1750653071115621092015-10-05T06:20:31.948-07:002015-10-05T06:20:31.948-07:00Thanks for your comment. Yes, we are considering t...Thanks for your comment. Yes, we are considering this for DetailView as well.Dennis Garavskyhttps://www.blogger.com/profile/05439634942797151905noreply@blogger.comtag:blogger.com,1999:blog-1944926148473713281.post-4045484976831958412015-10-05T06:12:44.141-07:002015-10-05T06:12:44.141-07:00Is this also a consideration for Detail views, or ...Is this also a consideration for Detail views, or is there some way to achieve that already? <br /><br />As in your examples above but you might also have: <br /><br />class Company<br />{<br /> [Aggregated]<br /> Person Person;<br />}<br /><br />where the Person detail view within the Company detail view follows the layout of the individual Person view(or all other similar views).<br /><br />wadehttps://www.blogger.com/profile/04298117484273185321noreply@blogger.comtag:blogger.com,1999:blog-1944926148473713281.post-21463118571190412172015-10-05T01:13:36.406-07:002015-10-05T01:13:36.406-07:00Same answer as Jascha - view inheritance must be a...Same answer as Jascha - view inheritance must be applied once and auto-updated with all parent view changes.s_tristanhttps://www.blogger.com/profile/00632655152766079847noreply@blogger.comtag:blogger.com,1999:blog-1944926148473713281.post-67990886603480067122015-10-04T10:21:13.256-07:002015-10-04T10:21:13.256-07:001. Yes
2. Almost always
3. It could be helpful, if...1. Yes<br />2. Almost always<br />3. It could be helpful, if it is easy to implement then it is a win<br />4. To rethink the whole concept in connection with code annotations and optional view inheritance would be better. Anonymoushttps://www.blogger.com/profile/16882068989522826540noreply@blogger.comtag:blogger.com,1999:blog-1944926148473713281.post-22564289034605669602015-10-04T00:30:02.839-07:002015-10-04T00:30:02.839-07:001. Yes, all the time.
2. Often.
3. It's OK.
4....1. Yes, all the time.<br />2. Often.<br />3. It's OK.<br />4. Changes should be propagated automatically till freeze.Anonymoushttps://www.blogger.com/profile/02159335384249011736noreply@blogger.comtag:blogger.com,1999:blog-1944926148473713281.post-44743200550788634992015-10-03T04:01:57.987-07:002015-10-03T04:01:57.987-07:00Same point of view as Jascha : "Better than n...Same point of view as Jascha : "Better than nothing but not ideal"Anonymoushttps://www.blogger.com/profile/01472709291471195325noreply@blogger.comtag:blogger.com,1999:blog-1944926148473713281.post-67476475742993755892015-10-03T03:24:04.227-07:002015-10-03T03:24:04.227-07:00Hi Dennis,
I'm sure we asked for view inherit...Hi Dennis,<br /><br />I'm sure we asked for view inheritance a long time ago. While the above sounds like an improvement, I would favour something that would automatically update child views whenever the parent view is altered instead of having to know and manually update all descendent views if an ancestor is changed. How about a model property on a view that specifies if it should automatically inherite its layout from its parent? That could be set via a code attribute and possibly default to a model-wide setting. Answers to your poll:<br /><br />1. Yes.<br />2. Regularly.<br />3. Better than nothing but not ideal as explained.<br />4. Yes, see above.<br /><br />JaschaAnonymoushttps://www.blogger.com/profile/15681747216931024783noreply@blogger.com