Hi Frederic,
> If i want to split them up into 2 separate repositories, what are the best
> names for 2 repositories ?
> oae-hilary-piwik-analytics
> oae-3akai-ux--piwik-analytics
Yes, that should work. Something like oae-piwik-analytics-ui and
oae-piwik-analytics-hilary would be fine as well.
> I'll create the package.json files
>
> do you have an eg ?
You can probably use this as the template for your package.json file. You’ll
still want to replace some of the values though:
```
{
"name": "3akai-ux",
"description": "Open Academic Environment (OAE) Front-end",
"version": "5.0.0",
"homepage": "http://www.oaeproject.org";,
"author": {
"name": "The Apereo Foundation",
"email": "oae-dev@collab.sakaiproject.org"
},
"repository": {
"type": "git",
"url": "git://github.com/oaeproject/3akai-ux.git"
},
"licenses": [
{
"type": "ECLv2",
"url": "http://opensource.org/licenses/ecl2.php";
}
]
}
```
Kind regards,
Nicolaas
On 25 Mar 2014, at 14:47, frederic dooremont
<frederic.doorem...@univ-littoral.fr> wrote:
> Hi Nicolaas,
>
> thanks for your help.
>
> it’s all ok ….. ;-)
>
> Indeed, I need to change my github repository.
> If i want to split them up into 2 separate repositories, what are the best
> names for 2 repositories ?
> eg :
> oae-hilary-piwik-analytics
> oae-3akai-ux--piwik-analytics
> What do you think ?
>
> I'll create the package.json files
>
> do you have an eg ?
>
> kind regards
> frederic
>
>
>
> Le 25 mars 2014 à 15:27, Nicolaas Matthijs
> <nicolaas.matth...@caret.cam.ac.uk> a écrit :
>
>> Hi Frederic,
>>
>> Your widget can’t start with an empty line. When I remove the empty line,
>> the widget seems to be loading fine. This is caused by a bug in jQuery where
>> turning an HTML string into a jQuery object doesn’t work when the string
>> starts with whitespace. We can probably make that a bit more solid on our
>> end by trimming the content of the widget. Feel free to create a 3akai-ux
>> issue for that.
>>
>> Also, you’ll need some changes to your repository set-up for it to be easy
>> to include in a Hilary and 3akai-ux deployment. The way in which contrib
>> modules are included is by adding them to the package.json file.
>>
>> e.g.
>>
>> ```
>> "dependencies": {
>> "oae-core": "",
>> "oae-piwik-analytics": "git://github.com/dooremont/oae-piwik-analytics"
>> },
>> ```
>>
>> The module is then automatically included when running `npm install -d`.
>>
>> However, because both the front-end and back-end code are in your
>> repository, that causes the back-end code to be pulled into the UI, which is
>> not desired. Therefore, you’ll want to split them up into 2 separate
>> repositories. We’ll do some thinking around how we can make that easier
>> though …
>>
>> Also, you’ll need a package.json file in the root folder of your UI/back-end
>> repositories, otherwise they can’t be defined as a dependency.
>>
>> Hope that helps,
>> Nicolaas
>>
>>
>> On 25 Mar 2014, at 13:46, frederic dooremont
>> <frederic.doorem...@univ-littoral.fr> wrote:
>>
>>> i have exactly the same error
>>> error: Syntax error, unrecognized expression: <div><!-- --></div> <!--
>>> JAVASCRIPT --> <script type="text/javascript" src="js/piwik.js"></script>
>>> throw new Error( "Syntax error, unrecognized expression: " + msg );
>>>
>>>
>>>
>>> Le 25 mars 2014 à 14:38, Nicolaas Matthijs
>>> <nicolaas.matth...@caret.cam.ac.uk> a écrit :
>>>
>>>> Can you try to add an empty div to the top of the widget and check if the
>>>> error persists?
>>>>
>>>> ```
>>>> <div><!— —></div>
>>>>
>>>> <!-- JAVASCRIPT -->
>>>> <script type="text/javascript" src="js/piwik.js"></script>
>>>> ```
>>>>
>>>> Thanks,
>>>> Nicolaas
>>>>
>>>>
>>>> On 25 Mar 2014, at 13:35, frederic dooremont
>>>> <frederic.doorem...@univ-littoral.fr> wrote:
>>>>
>>>>> Hi all,
>>>>> I have an error with my widget piwik [1] for 3akai-uk
>>>>>
>>>>> Error: Syntax error, unrecognized expression: <!-- JAVASCRIPT --> <script
>>>>> type="text/javascript" src="js/piwik.js"></script>
>>>>> throw new Error( "Syntax error, unrecognized expression: " + msg );
>>>>>
>>>>> I need your help for to understand this error
>>>>>
>>>>> thanks for your help
>>>>> frederic
>>>>>
>>>>> 1: https://github.com/dooremont/oae-piwik-analytics/tree/master/piwik
>>>>>
>>>>>
>>>>>
>>>>> Le 24 mars 2014 à 18:14, Nicolaas Matthijs
>>>>> <nicolaas.matth...@caret.cam.ac.uk> a écrit :
>>>>>
>>>>>> Hi Frederic,
>>>>>>
>>>>>> Similar to the approach outlined for the Hilary module, the recommended
>>>>>> approach would be to create a new repository for the UI widget. This
>>>>>> could be a repository for just this widget, or a repository containing a
>>>>>> number of contributed widgets. The only requirement is that the name of
>>>>>> the repository is prefixed with `oae-`.
>>>>>>
>>>>>> This can then easily be pulled into an installation by adding a
>>>>>> reference to it in the UI’s package.json file.
>>>>>>
>>>>>> In order to automatically load a widget on every page, you can add the
>>>>>> following to the widget’s manifest.json file:
>>>>>>
>>>>>> ```
>>>>>> 'trigger': {
>>>>>> 'onLoad': true
>>>>>> }
>>>>>> ```
>>>>>>
>>>>>> On each page load, this widget will then automatically be loaded and
>>>>>> initialised.
>>>>>>
>>>>>> Out of interest, is there an obvious advantage that Piwik offers over
>>>>>> the existing Google Analytics integration?
>>>>>>
>>>>>> Kind regards,
>>>>>> Nicolaas
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 24 Mar 2014, at 17:04, frederic dooremont
>>>>>> <frederic.doorem...@univ-littoral.fr> wrote:
>>>>>>
>>>>>>> Hi branden
>>>>>>>
>>>>>>> thanks for your answer
>>>>>>> In front-end oae
>>>>>>>
>>>>>>> if I create a widget. how to use automatically this widget (in the
>>>>>>> sense of to start ) ?
>>>>>>>
>>>>>>>
>>>>>>> kind regards
>>>>>>> fred
>>>>>>>
>>>>>>>
>>>>>>> Le 24 mars 2014 à 13:00, Branden Visser <mrvis...@gmail.com> a écrit :
>>>>>>>
>>>>>>>> Hi Frederic,
>>>>>>>>
>>>>>>>> I see the feature contains 2 components:
>>>>>>>>
>>>>>>>> 1. A Hilary module. To share this, the best way is to publish it the
>>>>>>>> public NPM repository [1]. OAE uses NPM to manage it's modules and
>>>>>>>> uses that to pull in external dependencies. Once published, you can
>>>>>>>> either run "npm install oae-piwik-analytics" (given that's the name of
>>>>>>>> your module) or you can customize the Hilary package.json to reference
>>>>>>>> it. Then, other people can also use "npm install" to pull it in for
>>>>>>>> their deployment.
>>>>>>>>
>>>>>>>> 2. A modification to oae.api.user.js. I'm not exactly sure what
>>>>>>>> changes were made here, but if possible it would be better to package
>>>>>>>> the work up and add it as a widget. If that's not possible and changes
>>>>>>>> need to be made to oae.api.user.js, if they are generic enough we can
>>>>>>>> consider making an update to core to accommodate different types of
>>>>>>>> analytics extensions, or at worst you could create a github clone of
>>>>>>>> the 3akai-ux repository and keep that in sync with the oaeproject
>>>>>>>> repository.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Branden
>>>>>>>>
>>>>>>>> On Sat, Mar 22, 2014 at 6:02 AM, frederic dooremont
>>>>>>>> <frederic.doorem...@univ-littoral.fr> wrote:
>>>>>>>>> this is the url github :
>>>>>>>>> https://github.com/dooremont/oae-piwik-analytics
>>>>>>>>> best
>>>>>>>>> fred
>>>>>>>>>
>>>>>>>>> Le 22 mars 2014 à 10:29, frederic dooremont
>>>>>>>>> <frederic.doorem...@univ-littoral.fr> a écrit :
>>>>>>>>>
>>>>>>>>>> Hi all,
>>>>>>>>>> I have created a widget for add Piwik Analytics tracker.
>>>>>>>>>> i have created in hilary a directory oae-piwik-analytics
>>>>>>>>>> and i have added an function in oae.api.util.js (directory 3akai-ux)
>>>>>>>>>>
>>>>>>>>>> How to share my widget with you ?
>>>>>>>>>>
>>>>>>>>>> frederic
>>>>>>>>>> _______________________________________________
>>>>>>>>>> oae-dev mailing list
>>>>>>>>>> oae-dev@collab.sakaiproject.org
>>>>>>>>>> http://collab.sakaiproject.org/mailman/listinfo/oae-dev
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> oae-dev mailing list
>>>>>>>>> oae-dev@collab.sakaiproject.org
>>>>>>>>> http://collab.sakaiproject.org/mailman/listinfo/oae-dev
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> oae-dev mailing list
>>>>>>> oae-dev@collab.sakaiproject.org
>>>>>>> http://collab.sakaiproject.org/mailman/listinfo/oae-dev
>>>>>>
>>>>>
>>>>
>>>
>>
>
_______________________________________________
oae-dev mailing list
oae-dev@collab.sakaiproject.org
http://collab.sakaiproject.org/mailman/listinfo/oae-dev
