[Xerte-dev] Re: [Xerte] Re: plain text connector page problem in XOT

Pat Lockley patrick.lockley at googlemail.com
Mon Oct 29 22:05:04 GMT 2012


Shall we just make a google doc (roadmap and api as separate ones), I
am itchy fingering

On Mon, Oct 29, 2012 at 9:59 PM, Julian Tenney
<Julian.Tenney at nottingham.ac.uk> wrote:
> Indeed. That was always the dream. We need to get that roadmap / current piees of work page going somewhere, community site again I guess. I need to get to grips with how you've done that modularity stuff and make sure that works really nicely too.
> ________________________________________
> From: xerte-dev-bounces at lists.nottingham.ac.uk [xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Pat Lockley [patrick.lockley at googlemail.com]
> Sent: 29 October 2012 21:46
> To: For Xerte technical developers
> Subject: [Xerte-dev] Re: [Xerte] Re: plain text connector page problem in XOT
>
> Do we have time (in a Nottingham sense) to structure around this?
> Because I think XOT 2 could have a shedload of features - not just the
> HTML5
>
> I don't want to see possessive - I really did plan to do a little less
> round here at some point, but the idea of making a learning object CMS
> seems kinda tempting.
>
> On Mon, Oct 29, 2012 at 9:41 PM, Dave Burnett <d_b_burnett at hotmail.com> wrote:
>>>I don't think anyone debates that we will need to do this at some point
>>
>> I do.
>> I refuse to allow it.
>>
>>> From: Julian.Tenney at nottingham.ac.uk
>>> To: xerte-dev at lists.nottingham.ac.uk
>>> Date: Mon, 29 Oct 2012 21:40:15 +0000
>>
>>> Subject: [Xerte-dev] Re: [Xerte] Re: plain text connector page problem in
>>> XOT
>>>
>>> No, we're not trying to take them away, the question was more about how we
>>> continue backward compatibility with standalone xerte, and that's going to
>>> be a bit tricky, because a some point we will need to say 'snip'.I don't
>>> think anyone debates that we will need to do this at some point, my own view
>>> is the roadmap expressed before:
>>>
>>> - parity in xenith with the current suite of templates which Nottingham is
>>> undertaking
>>> - except for connectors, which aare off our radar for the current list,
>>> but which we want to include by Easter maybe?
>>> - Then we release version 2. I cannot tell you hw many emails I've had
>>> personally about release dates.
>>> - GIve it a while to see what happens, helping people through the install,
>>> and finding anf fixing the gribbles.
>>> - Have another AGM in October to capture where we are then
>>>
>>> where does 'snip' go in the list? FOr me I think it's after the v2
>>> release, and we then release any dependencies between the two svns, so they
>>> can bth go in their own directions.
>>> ________________________________________
>>> From: xerte-dev-bounces at lists.nottingham.ac.uk
>>> [xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Dave Burnett
>>> [d_b_burnett at hotmail.com]
>>> Sent: 29 October 2012 20:35
>>> To: xerte-dev at lists.nottingham.ac.uk
>>> Subject: [Xerte-dev] Re: [Xerte] Re: plain text connector page problem in
>>> XOT
>>>
>>> >Page connectors could be the same - just support the addition of them,
>>> > and let them work in their own way
>>>
>>> Which is what I was getting at it the "app store" bespoke version.
>>> I'm sort of confused as to why some here are so adamant about including
>>> page connectors with a base install.
>>> We're not trying to take them away.
>>>
>>> ________________________________
>>> From: patrick.lockley at googlemail.com
>>> Date: Mon, 29 Oct 2012 20:20:12 +0000
>>> To: xerte-dev at lists.nottingham.ac.uk
>>> Subject: [Xerte-dev] Re: [Xerte] Re: plain text connector page problem in
>>> XOT
>>>
>>>
>>>
>>> What we must avoid is a situation where people try and build content and
>>> then give up because it just doesn't work quite right, and have then
>>> essentially wasted their time. This is an important principle for toolkits.
>>>
>>> This....
>>>
>>> Then maybe the connector pages should be withdrawn from the XOT release
>>> until we have a common approach to the pages and resolved the navigation
>>> options.
>>>
>>> And this are two sides of the same coin
>>>
>>> People need to be able to know their contributions are worthwhile else
>>> they won't contribute. Part of 1.9 is making it more modular, but also 1.9
>>> is all me so far and for all I know it'll get thrown away.
>>>
>>> But we fix this with a road map and modularisation. You want to mess the
>>> site up, go ahead. But out of the box is this.
>>>
>>> As a side point, the XOT Wordpress plugin gets about 100 downloads a month
>>> and I support that all by myself.
>>>
>>> I.e with modularisation we can decentralise code and the project. Every
>>> Drupal install uses views but it is optional. Page connectors could be the
>>> same - just support the addition of them, and let them work in their own way
>>>
>>> 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 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
>>
>> _______________________________________________
>> 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
>
> _______________________________________________
> Xerte-dev mailing list
> Xerte-dev at lists.nottingham.ac.uk
> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev



More information about the Xerte-dev mailing list