On Tue, Feb 1, 2011 at 1:49 PM, Christian Lohmaier <[email protected]> wrote: > > Well - what you write doesn't make any sense at all. Again: > * You complain about the modal prompt > * I propse to change it > * You don't want me to change thte CMS' code
To give some context,I subscribe to the view that hacking the core CMS code means that you 'might' introduce new bugs, resulting in something that cannot be supported by the CMS community. It is an extreme example, but say someone altered the code of LibreOffice, broke it, then came complaining to us about it being broken and wanted us to fix it. Also when you start hacking the core code, then you are creating a code branch which you, or the community who comes after you will have to maintain for security and functionality, which is not always possible given the resources. This is almost a religion within the Drupal community, and hacking the core is seen as blasphemy. If you wish to add or modify functionality you write a module which does what you want via one of the many APIs, just as you would with a LibreOffice extension. IMO if you can't do something without hacking the core you don't do it. If you still need it, you have chosen the wrong system to work on. Michael Wheatland Post Script: I am not trying to have a go at Silverstripe, simply explaining the context of your statement and my total opposition to changing core code. I don't know if the Silverstripe APIs are functional enough to cope with these types of changes, maybe someone can shed some light on this? -- Unsubscribe instructions: E-mail to [email protected] List archive: http://listarchives.libreoffice.org/www/website/ *** All posts to this list are publicly archived for eternity ***
