Here are my answers to your questions.

> Great. It's not clear from the presentation if you pushed sakai data
> to XWiki or if you overriden the auth, groups and rights services ?
Data is pushed from sakai to XWiki. The authentication, groups and rights 
is controlled by the tool and pushed to XWiki. So permissions set in Sakai 
are pushed to XWiki.

> Is the iframe velocity script changes available somewhere ?
> Integration like that comes up from time to time and we don't have a
> clean "skin less" skin.
We are in the process of committing the code to the Sakai repository and 
will include the velocity scripts as well.

> You mention FCKEditor vs XWiki Editor ? What make you choose not to
> use the XWiki Editor ?
> Are you storing content as HTML/XHTML or are you talking to the XWiki
> conversion backend ?
We chose the FCKEditor since this is the editor used in all Sakai tools. 
We did not want to introduce a different editor for the wiki.  The output 
of the editor is in HTML/XHTML.


> It would be great to list the REST issues that you had and also any
> missing REST services that there might be.
> We should make sure our API is complete for people to work with.
Will do so in a separate email.

Hope I was able to answer your questions satisfactorily.  Let me know if 
something is still unclear.

- Adam


Adam Hocek
Information Technology
Marist College
tel: 845-575-3948



From:   Ludovic Dubost <[email protected]>
To:     XWiki Developers <[email protected]>
Date:   07/04/2011 05:20 AM
Subject:        Re: [xwiki-devs] a successful integration of XWiki with 
Sakai
Sent by:        [email protected]



Thanks for the feedback. Some more questions below.

2011/7/1 Adam Hocek <[email protected]>:
> Hi Ludovic,
>
> Thanks for your reply back.
> Sorry for not getting back sooner.  I do have a link to the presentation
> at http://www.slideshare.net/ahocek/xwiki-sakai-integration .
>
> I would be happy to give you more details on the integration and options
> we looked at.
>
> In short we implemented a Sakai tool that used Sakai's user, group, 
roles
> management tools to map to XWiki groups and permissions.  We have hooks
> into when a Sakai course site and roster are updated so to synchronize
> with XWiki users and groups.

Great. It's not clear from the presentation if you pushed sakai data
to XWiki or if you overriden the auth, groups and rights services ?

  We looked at two UI options, exposing XWiki
> through an iframe or writing Sakai-side UI components to interface
> directly with XWiki.   We opted for a mixed implementation with most of
> XWiki being exposed through an iframe using XWiki css and velocity 
scripts
> to customize.

Is the iframe velocity script changes available somewhere ?
Integration like that comes up from time to time and we don't have a
clean "skin less" skin.
It could be nice to share it.

> For editing we use Sakai's standardized editor, FCKEditor (later will 
move
> to CKEditor).  We added widgets to the editor to allow XWiki pages to

You mention FCKEditor vs XWiki Editor ? What make you choose not to
use the XWiki Editor ?
Are you storing content as HTML/XHTML or are you talking to the XWiki
conversion backend ?

> reference Sakai resources. There could of course be other widgets that
> could added into the editor and integrate with specific Sakai  tools. 
 The
> rest of implementation exposes XWiki in an iframe for views, 
annotations,
> comments, history, etc..
>
> Last comment on the implementation, we looked at both XWiki'a REST and 
RPC
> implementations.  We first implemented using the REST API and found that
> response was a little slow for certain accumulative queries and
> iterations.  The RPC implementation was more responsive, but in the end 
it
> sounds like the XWiki community is more interested in supporting the 
REST
> API so we would go with a REST implementation too.

It would be great to list the REST issues that you had and also any
missing REST services that there might be.
We should make sure our API is complete for people to work with.

>
> Thank you for the mention of curriki.org.  Many Sakai deployments are in
> colleges and universities, but there is a growing number of K-12 grade
> schools using Sakai, in which case the curriki integration would be a 
good
> match.

Note that Curriki is available as separate software, so it's not
necessarly about the K-12 content of Curriki.org.
Curriki could be used as the software as a content repository.

Ludovic

>
> - Adam
>
> Adam Hocek
> Information Technology
> Marist College
> tel: 845-575-3948
>
>
>
> From:   Ludovic Dubost <[email protected]>
> To:     XWiki Developers <[email protected]>
> Date:   06/29/2011 04:29 PM
> Subject:        Re: [xwiki-devs] a successful integration of XWiki with
> Sakai
> Sent by:        [email protected]
>
>
>
> Hi Adam,
>
> This is great ! I've seen some tweets during the conference that 
announced
> the session.
> I heard a lot about Sakai and it's great that there is now an 
integration.
>
> We'd love to know the type of integration you did. Is it authentication,
> UI
> level integration, content integration.
> If you have a pointer to your slides of the presentation that would be
> great.
>
> You might also know the Curriki (http://www.curriki.org) is build on top
> of
> the XWiki Software, which is an education oriented software which is 
also
> released under the LGPL licence.
>
> It could be possible to piggyback on your integration to integrate 
Curriki
> with Sakai.
>
> Ludovic
>
>
> 2011/6/29 Adam Hocek <[email protected]>
>
>> Hello XWiki Developers,
>>
>> I wanted to let you know that we completed our first release of
>> integration of XWiki with Sakai (sakaiproject.org).  Sakai is an open
>> source collaborative teaching and learning application used by many
>> educational institutes worldwide.  The integration replaces an older
> less
>> supported wiki tool in Sakai.  We presented the new tool at the recent
>> Sakai 2011 conference in Los Angeles, CA, and are anticipating several
>> schools to begin using the tool.  I think this will be bring about
> greater
>> exposure and have a positive impact for the respective open source
>> communities.
>>
>> If anyone has any questions I'd be happy to try and answer them.  We
> will
>> probably be emailing to this list sometime soon with some specific
>> questions and requests.
>>
>> Cheers,
>> - Adam
>>
>> Adam Hocek
>> Information Technology
>> Marist College
>> tel: 845-575-3948
>> _______________________________________________
>> devs mailing list
>> [email protected]
>> http://lists.xwiki.org/mailman/listinfo/devs
>>
>
>
>
> --
> Ludovic Dubost
> Founder and CEO
> Blog: http://blog.ludovic.org/
> XWiki: http://www.xwiki.com
> Skype: ldubost GTalk: ldubost
> _______________________________________________
> devs mailing list
> [email protected]
> http://lists.xwiki.org/mailman/listinfo/devs
>
> _______________________________________________
> devs mailing list
> [email protected]
> http://lists.xwiki.org/mailman/listinfo/devs
>



-- 
Ludovic Dubost
Founder and CEO
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
_______________________________________________
devs mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/devs

_______________________________________________
devs mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/devs

Reply via email to