<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-2" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Exactly what is the problem that this solution wants to solve? I mean that is not the teacher who selects from the lessons depending on her personal lesson plan? (Of course we could provide a default lesson plan but in the end it is up to the teacher what she wants to teach and in what order.)<br> So is it important at all to select from a predetermined date or country specific grade?<br> Can it be that I do not understand at all how those lessons would be used in the classroom? Or is this mega bundle (what bundles a lot of lessons from different subjects) solves the deployability problem and creates a selection problem?<br> <br> Christoph Derndorfer wrote: <blockquote cite="mid:bae28afe0908050024n590fb1c6j5650c600a6a32d59@mail.gmail.com" type="cite">Hi all, <div><br> </div> <div>I spent some time toying around with Chakra in the past 24 hours. As a preliminary result I have concluded that we should initially support two different "views" of the available lessons.</div> <div><br> </div> <div>(1) What I call "E-Paath" style (see the attached chakra_epaath_s.jpg) as it follows E-Paath's current flow in terms of choosing Grade - Subject - Week before being presented with an overview of the available lessons.</div> <div>(2) "List" style (see the attached chakra_list_s.jpg) which is a simple list of lessons available for that Grade and Subject (of course one could make it even simpler by listing all lessons for a given Subject, regardless of Grade)</div> <div><br> </div> <div>(Please ignore the lack of reasonable design and color choices in these screenshots;-)</div> <div><br> </div> <div>Now the question is how to generate these Chakras for a given set of lessons (which are stored in sub-folders)...</div> <div><br> </div> <div>In general the issue is that with the currently proposed Karma bundle layout (<a moz-do-not-send="true" href="http://wiki.sugarlabs.org/go/Karma/Bundle_layout">http://wiki.sugarlabs.org/go/Karma/Bundle_layout</a>) the only information we have about a lesson is it's name. This is of course too little data to create a nice Chakra with Grade and Subject choices. Subsequently I believe that we should find a way to include some additional information with lessons.</div> <div><br> </div> <div>The way that OLE Nepal currently handles it during E-Paath development is that lessons are stored in sub-folders named <Grade>_<Subject>_<Lesson Name>_<Week> (e.g. 6_English_RajuAndTheWolf_1). Based on that information a support scripts then builds the Flash menu structure.</div> <div><br> </div> <div>Now I was thinking that one approach could be to include some sort of .info file in each lesson that contains the information. While Subject probably will be fairly consistent between various countries the Grade information is highly country-specific and could be put into the respective .po files for each locale.</div> <div><br> </div> <div>What do you think, does that approach make sense? What are other possible solutions to deal with this?</div> <div><br> As always, all comments, feedback and suggestions are much appreciated.</div> <div><br> Thanks,<br> Christoph</div> <div><br> -- <br> Christoph Derndorfer<br> co-editor, olpcnews<br> url: <a moz-do-not-send="true" href="http://www.olpcnews.com">www.olpcnews.com</a><br> e-mail: <a moz-do-not-send="true" href="mailto:christoph@olpcnews.com">christoph@olpcnews.com</a><br> </div> <br> <hr size="4" width="90%"><br> <center><br> </center> <p><br> </p> <hr size="4" width="90%"><br> <center><br> </center> <pre wrap=""> <hr size="4" width="90%"> _______________________________________________ Sugar-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> <a class="moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/sugar-devel">http://lists.sugarlabs.org/listinfo/sugar-devel</a> </pre> </blockquote> <br> </body> </html>