[Xerte-dev] Re: Export Code

Tom Reijnders reijnders at tor.nl
Thu May 3 11:51:03 BST 2012


It should be skipped then. I want to have a look at import as well. 
Don't know how import works at the moment.

Op 3-5-2012 12:47, Pat Lockley schreef:
> in the root folder
>
> then the issue is what happens when you import.....
>
> On Thu, May 3, 2012 at 11:41 AM, Tom Reijnders<reijnders at tor.nl>  wrote:
>> Actual question on the export code...
>>
>> If jmol and/or mastraction is used, where do they have to end up in the zip
>> file?
>>
>> Complete jmol tree and/or mapstraction in jmol cq. mapstraction folder?
>>
>> Any others? mediaViewer? Or is that only used during authoring.
>>
>> Op 2-5-2012 12:02, Ron Mitchell schreef:
>>> agreed but...
>>>
>>> Existing owners of installations will also need a way of upgrading rather
>>> than installing from scratch which previously has only required replacing
>>> files. So we'll also need a solution for this scenario too.
>>>
>>> -----Original Message-----
>>> From: xerte-dev-bounces at lists.nottingham.ac.uk
>>> [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Julian
>>> Tenney
>>> Sent: 02 May 2012 10:46
>>> To: For Xerte technical developers
>>> Subject: [Xerte-dev] Re: Export Code
>>>
>>> But if we pulled our fingers out a little, there would be no need to edit
>>> config.php - it could all be configured in /setup at installation time.
>>> That's why I don't want it to be necessary to edit config.php.
>>>
>>> I also tend to think anything that can be done through setup should be.
>>>
>>> -----Original Message-----
>>> From: xerte-dev-bounces at lists.nottingham.ac.uk
>>> [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of David
>>> Goodwin
>>> Sent: 02 May 2012 10:28
>>> To: For Xerte technical developers
>>> Subject: [Xerte-dev] Re: Export Code
>>>
>>>
>>> On 2 May 2012, at 10:09, Ron Mitchell wrote:
>>>
>>>> Could it be that inside xot config.php require_once fo the integration
>>>> config needs to be changed to require? e.g.
>>>>
>>>> if ($row['integration_config_path'] != "") {
>>>>         require_once($row['integration_config_path']);
>>>>     }
>>>>
>>>> if ($row['integration_config_path'] != "") {
>>>>         require($row['integration_config_path']);
>>>>     }
>>>>
>>>
>>> No.
>>>
>>> require_once is identical to require, it's just that it can't happen more
>>> than once within the page request/execution. this is a good thing.
>>>
>>>
>>>> If that is the case the question still arises is there any benefit in
>>>> using the database for this given that xot config.php needs editing
>>> anyway?
>>>
>>>
>>>
>>> But if we pulled our fingers out a little, there would be no need to edit
>>> config.php - it could all be configured in /setup at installation time.
>>> That's why I don't want it to be necessary to edit config.php.
>>>
>>> David.
>>>
>>>
>>> Pale Purple Ltd.  (Company No: 5580814)
>>> 'Business Web Application Development and Training in PHP'
>>>
>>> http://www.palepurple.co.uk
>>> Office: 0845 0046746     Mobile: 07792380669
>>>
>>> Follow us on Twitter: @PalePurpleLtd
>>>
>>>
>>> _______________________________________________
>>> Xerte-dev mailing list
>>> Xerte-dev at lists.nottingham.ac.uk
>>> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev
>>>
>>> _______________________________________________
>>> Xerte-dev mailing list
>>> Xerte-dev at lists.nottingham.ac.uk
>>> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev
>>>
>>> This message and any attachment are intended solely for the addressee and
>>> may contain confidential information. If you have received this message in
>>> error, please send it back to me, and immediately delete it.   Please do
>>> not
>>> use, copy or disclose the information contained in this message or in any
>>> attachment.  Any views or opinions expressed by the author of this email
>>> do
>>> not necessarily reflect the views of the University of Nottingham.
>>>
>>> This message has been checked for viruses but the contents of an
>>> attachment
>>> may still contain software viruses which could damage your computer
>>> system:
>>> you are advised to perform your own checks. Email communications with the
>>> University of Nottingham may be monitored as permitted by UK legislation.
>>>
>>>
>>>
>>> _______________________________________________
>>> Xerte-dev mailing list
>>> Xerte-dev at lists.nottingham.ac.uk
>>> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev
>>
>> --
>> --
>>
>> Tom Reijnders
>> TOR Informatica
>> Chopinlaan 27
>> 5242HM Rosmalen
>> Tel: 073 5226191
>> Fax: 073 5226196
>>
>>
>>
>> _______________________________________________
>> Xerte-dev mailing list
>> Xerte-dev at lists.nottingham.ac.uk
>> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev
> _______________________________________________
> Xerte-dev mailing list
> Xerte-dev at lists.nottingham.ac.uk
> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev
> This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.
>
> This message has been checked for viruses but the contents of an attachment
> may still contain software viruses which could damage your computer system:
> you are advised to perform your own checks. Email communications with the
> University of Nottingham may be monitored as permitted by UK legislation.
>

-- 
--

Tom Reijnders
TOR Informatica
Chopinlaan 27
5242HM Rosmalen
Tel: 073 5226191
Fax: 073 5226196





More information about the Xerte-dev mailing list