Lucian,<br><br>thanks a lot for raising that issue, it's certainly an aspect we hadn't considered!<br><br>Cheers,<br>Christoph<br><br><div class="gmail_quote">2009/7/22 Bryan Berry <span dir="ltr"><<a href="mailto:bryan@olenepal.org">bryan@olenepal.org</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">that's a good point, we may end up just naming it index.html but<br>
referring to the starting page as "the Chakra"<br>
<div><div></div><div class="h5">On Wed, 2009-07-22 at 12:59 +0100, Lucian Branescu wrote:<br>
> Now that I'm actually looking at the layout, I realise that you MUST<br>
> rename chakra.html/karmaplatz.html to index.html.<br>
><br>
> If you host the karma bundle somewhere on a web server, when you go to<br>
> the bundle ROOT path the server will try to serve index.html, because<br>
> that's the default. Since it's not there, it will 403.<br>
><br>
> Furthermore, if a random web developer with no knowledge of karma<br>
> looks inside the karma bundle, they will instinctively look for<br>
> index.html. Web devs also expect english, so chakra or karmaplatz will<br>
> not tell them anything.<br>
><br>
> ]karmaindex.html might be alright for devs, but it still confuses web<br>
> servers and there's no reason to deviate from the de-facto standard of<br>
> index.html.<br>
><br>
> Sorry for the rant, but I really believe you're making a mistake by<br>
> not naming the file index.html. You may call the interface element<br>
> 'karma index' if you like, because that's what it is.<br>
><br>
> 2009/7/22 Bryan Berry <<a href="mailto:bryan@olenepal.org">bryan@olenepal.org</a>>:<br>
> > On Tue, 2009-07-21 at 17:49 -0500, Felipe López Toledo wrote:<br>
> >> Hi Bryan.<br>
> >><br>
> >> I have one question about<br>
> >> <a href="http://wiki.sugarlabs.org/go/Karma/Bundle_layout" target="_blank">http://wiki.sugarlabs.org/go/Karma/Bundle_layout</a><br>
> >> I'm working with our new layout ;)<br>
> >><br>
> >> until yesterday, each lesson could work independently. each lesson had<br>
> >> their own js files.<br>
> >> The beauty of that way, was that you could take a specific lesson<br>
> >> folder and put it everywhere and it would work.<br>
> >><br>
> >> if we want to do that with the new arrangement, it would be necessary<br>
> >> to carry:<br>
> >> The specific Lesson folder + Karma lesson bundle folder<br>
> ><br>
> > Exactly. the stuff common to all the lessons, like karma.css, jquery.js,<br>
> > goes in the top-level directory<br>
> ><br>
> > so ROOT > js/ , css/ , karmaplatz.html, lessons/<br>
> > lessons > js/, css/<br>
> ><br>
> > Does it seems like too much overhead to carry around the karmaplatz? I<br>
> > figure that most of the time devs will want the karmaplatz to accompany<br>
> > their lessons.<br>
> ><br>
> >> I would suggest to merge Karma lesson bundle / js with Lesson / js.<br>
> >> The problem is that we will have repeated files.<br>
> ><br>
> > Yeah. my best solution is just to separate them as specified before<br>
> ><br>
> >> also, the Main Karma Package has its own js folder ("..contain the<br>
> >> code common to all examples.."), I suppose it is not necessary since<br>
> >> we have the examples folder that will be (I suppose) a Karma Lesson<br>
> >> bundle folder.<br>
> >> or maybe I'm misunderstanding things.<br>
> ><br>
> > I want the examples to use the same common js/ and css/ folders as<br>
> > lessons/ . By default, the links to the examples will appear in<br>
> > karmaplatz.html . I want the paths used in the examples to be the same<br>
> > ones that can be used by the new user-created lessons in lessons/ .<br>
> > Using the same file directory layout makes this easier.<br>
> ><br>
> > So, I want the examples to look at root > css/, js/ for their common<br>
> > files just as the new "lessons" in lessons/ will<br>
> ><br>
> >><br>
> >> felipe<br>
> >><br>
> > --<br>
> > Bryan W. Berry<br>
> > Technology Director<br>
> > OLE Nepal, <a href="http://www.olenepal.org" target="_blank">http://www.olenepal.org</a><br>
> ><br>
> > _______________________________________________<br>
> > Sugar-devel mailing list<br>
> > <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a><br>
> > <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
> ><br>
</div></div>--<br>
<div><div></div><div class="h5">Bryan W. Berry<br>
Technology Director<br>
OLE Nepal, <a href="http://www.olenepal.org" target="_blank">http://www.olenepal.org</a><br>
<br>
_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Christoph Derndorfer<br>co-editor, olpcnews<br>url: <a href="http://www.olpcnews.com">www.olpcnews.com</a><br>e-mail: <a href="mailto:christoph@olpcnews.com">christoph@olpcnews.com</a><br>