Hi Michael, *,
On Wed, Feb 2, 2011 at 7:15 AM, Michael Wheatland
<michael@wheatland.com.au> wrote:
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.
cmsworkflow is already a module, so not "core", thus it would be OK?
[...]
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?
as the function in question uses plain javascript (the already
mentioned "prompt" command) it obviously doesn't use any silverstripe
specific api.
So it would require to rewrite it to make use of whatever higher-level
api. But I don't really think it is worth it (or better: there are
other tasks that I consider more important - like getting rid of that
pile of mail that stacked up in my inbox :-P)
ciao
Christian
--
Unsubscribe instructions: E-mail to website+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/website/
*** All posts to this list are publicly archived for eternity ***
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.