Hi all, Hacking the thread to add some comments about our experience in C1 about anonymous access:
Initially, any user could access courses of "public" visibility, simply by entering the course (permissions flags would be "lifted" by the fact the course was public). This, however, generated users frustration, mostly because they wanted to enter a learning path or an exercise and... be able to see their own tracking! (yeah, users are strange) So we implemented a complete user "role", with one user by default being granted this role upon installation of the platform. This single user would then be used by anonymous people and generate user tracking in the database, which ultimately allowed users to "see their own tracking". The only problem is that multiple simultaneous anonymous users can connect to the same exercice or learning path at the same time, thus registering two different attempts, thus confusing the users a little bit (mostly when multiple attempts were disabled). I think that, by designing a "pool" of users with the "anonymous" role, one could easily get a very logical behaviour, even on a site with many simultaneous visitors. I'm not sure what you have in mind, but I wanted to bring that experience on the table. For packaging of applications, I hope the people looking at it are also looking around at stuff like the Features module in Drupal and the packaging models from great Linux distributions. I'm sure this could avoid loosing a lot of time. Yannick E l lun, 21-02-2011 a las 12:04 +0100, Hans De Bisschop escribió: > Hi all, > > Considering one should forge the iron while it's hot, there's no > better time to plan the next Chamilo 2 code sprint then right before > the one coming up tomorrow and the day after tomorrow. > > First and foremost I've set up a Doodle, so you can enter your > preferences date-wise. All options are located in the week of March > 21, 2011. Please do keep in mind that Chamilo 2 code sprints typically > last 2 days (more if so requested), but do feel free to check all > dates at which you consider yourself available for this event. It's > always better to have you there one day then none at all. > > The Doodle is located at: > http://www.doodle.com/hi2gqiwwk5mvgeea?newDesign=true > > Also considering that the people at Hogeschool Gent were as kind as to > host the upcoming code sprint, this time Erasmus University College > Brussels will be your host once more. > > Tentative planning / agenda: > * Unification of platform-wide AJAX calls > A basic manager is available to do AJAX calls in a uniform > (OO) way. This has been implemented in a few places, but far > from everywhere. > * Distributed architecture / configuration for our integrated > HTML editor > Different packages and contexts can have different > requirements as far as the available options in the HTML > Editor are concerned. Following our own architecture, the > configuration of said editor should be customizable per > package as well. > * Static page content > One of the things keeping us from actually using Chamilo 2 for > regular websites is the lack of some kind of "static" page > application, based on objects but which is, for the end user, > not seen as an application. It should fully integrate into the > platform menu-structure. More details and discussion on the > code sprint. > * Metadata / context linker integration into the core > The people at VUB did a terrific job implementing a metadata / > context linking application for Chamilo 2. This opens up a > world of possibilities for content, users and groups. As a > final push forward this would have to be integrated into the > core. While not that hard in theory, doing it together during > a code sprint (perhaps combined with a little "education" on > the concept of the application and metadata itsel) would be > benificial to all. > * Handbook integration > Pretty much the same as the previous topic, but for the > handbook application developed by the VUB-team ... > * Package Manager > A package manager is being developed to easily distribute new > versions of packages. Progress report and brainstorm / > discussion on how far we want to or should go with this. > * Anonymous access to Chamilo 2 > At this moment a user still HAS to be logged on to be able to > do anything. Different approaches exist to allow people access > in an anonymous way. We should try to figure out which > approach we want and how we can implement it as easily as > possible. > * WebLCMS > Some structural issues remain, management of courses and the > courses themselves is somewhat intermixed and then there's > also the matter of the course types. We should discuss how we > can fix these issues once and for all and keep the WebLCMS > from becoming the ugly duckling of our family. > It goes without saying that any additional topics are always welcome. > If you have a project you want to present (to developers), this could > be the moment to do it. If you need technical feedback for a project > or just want to brainstorm about it ... you're always welcome. It goes > without saying there's also and always time to discuss recent > developments as well as new developments. > > Depending on the outcome of the aforementioned Doodle, more details > will follow (as well as a more concrete planning and/or agenda) > > Best regards and hope to see you then, > > Hans De Bisschop > Hoofddeskundige ICTO | Lead Developer Chamilo 2.0 > Software Coordinator Chamilo Association > Erasmushogeschool Brussel > Nijverheidskaai 170 | B-1070 Brussel > T 02 559 02 54 | i 254 > hans.de.bissc...@ehb.be | www.erasmushogeschool.be > > Kom eens langs: www.erasmushogeschool.be/infodagen > of lees onze elektronische nieuwsbrief: ehbrief.ehb.be > P Before printing, think about the environment > _______________________________________________ > Dev mailing list > Dev@lists.chamilo.org > http://lists.chamilo.org/listinfo/dev _______________________________________________ Dev mailing list Dev@lists.chamilo.org http://lists.chamilo.org/listinfo/dev
