[Alpha release] DevTutor activity
Dear all, I am delighted to announce the alpha release of the DevTutor activity focused on understanding the Sugar API modules. Please visit - http://activities.sugarlabs.org/en-US/sugar/addon/4353 Many thanks to Kandarp Kaushik for his dedication and consistency during all the stages of the development; Ayush Goyal for designing the svg icon of the activity and Aleksey Lim for his continued guidance to the team. We look forward to hearing your feedback and experience with DevTutor activity. If you would like to put in a feature request, please do so at http://bugs.sugarlabs.org. Hope you find the activity useful. Regards, Manu ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Alpha release] DevTutor activity
We look forward to hearing your feedback and experience I'm not sure what the *purpose* of a 'tutor' should be. But - since I did not go look for additional documentation (e.g., in the wiki) - I myself was unable to figure out how to learn by using this Activity. In sugar 0.84 on XO-1, DevTutor-1 would not launch (ImportError: No module named toolbarbox). In sugar 0.90 on XO-1, the activity launched, and showed me various menus (occupying the whole DevTutor window area). Proceeding from the 'Show modules' menu entry - the only place where it showed any *detail* was as examples of some widgets - without tutoring' (i.e., without explanation). Proceeding from the 'Show activities' menu entry - I was given the choice of examining two Activities. Took me a long time to figure out that the various 'Steps' added code (unexplained) to the basic Activity structure, and that 'Show res' Mikus note: NOT a typo opened *another* session in which the output of that now-changed Activity's code was displayed. [Ergonomic note: The only way to exit from this additional session was to click on the octagonal stop sign (or on Stop in the palette of that session's icon in Frame) - that caused the 'keep' window to be shown, and subsequently an additional entry to be recorded in the Journal !!] I was never clear on whether what occupied the DevTutor window area was all that there was (or if more would have been visible if only the screen were larger). The only place where I saw scrollbars was within the another activity's session window. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] Jabber presence under NAT named under DMZ issues
On Fri, 2010-11-05 at 21:19 -0500, Anna wrote: Eventually, after many hours of troubleshooting, I put the XSXO into the DMZ in my router and the presence service quit resetting us every hour. Of course, I deleted /etc/sysconfig/network-scripts/ifcfg-eth0-local once I set XSXO in the DMZ. I edited /etc/hosts for: 67.195.160.76schoolserver.random.net random.net Don't think you want to have the router's external address in the XSXO's hosts file. I'd stick with localhost here. I put the OpenDNS IPs in named-xs.conf.in and then make -f xs-config.make named-xs.conf Think that is prior to 0.6.0 try domain_config I actually use OpenDNS DNS IPs in my router instead of my ISP's DNS IPs. Should be no problem with that. Here's /var/named-xs/school.external.zone.db @ in soa localhost. root 1 3H 15M 1W 1D ns localhost. schoolserverINA67.195.160.76 schoolINCNAMEschoolserver wwwINCNAMEschoolserver ntpINCNAME schoolserver timeINCNAMEschoolserver presenceINCNAMEschoolserver xsINCNAMEschoolserver libraryINCNAMEschoolserver conference.schoolserverINCNAMEschoolserver But then named never comes back up: Starting named: Error in named configuration: zone localdomain/IN: loaded serial 42 zone localhost/IN: loaded serial 42 zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700 zone 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: loaded serial 1997022700 zone 255.in-addr.arpa/IN: loaded serial 42 zone 0.in-addr.arpa/IN: loaded serial 42 dns_rdata_fromtext: school.internal.zone.db:1: near 'root': bad name (check-names) school.internal.zone.db:2: no TTL specified; zone rejected school.internal.zone.db:4: schoolserver...@\@basednsna...@\@: bad owner name (check-names) school.internal.zone.db:4: no TTL specified; zone rejected school.internal.zone.db:5: schoolserver...@\@basednsna...@\@: bad owner name (check-names) school.internal.zone.db:5: no TTL specified; zone rejected school.internal.zone.db:6: schoolserver...@\@basednsna...@\@: bad owner name (check-names) school.internal.zone.db:6: no TTL specified; zone rejected school.internal.zone.db:7: schoolserver...@\@basednsna...@\@: bad owner name (check-names) school.internal.zone.db:7: no TTL specified; zone rejected school.internal.zone.db:8: schoolserver...@\@basednsna...@\@: bad owner name (check-names) school.internal.zone.db:8: no TTL specified; zone rejected school.internal.zone.db:9: schoolserver...@\@basednsna...@\@: bad owner name (check-names) school.internal.zone.db:9: no TTL specified; zone rejected school.internal.zone.db:10: schoolserver...@\@basednsna...@\@: bad owner name (check-names) school.internal.zone.db:10: no TTL specified; zone rejected school.internal.zone.db:11: schoolserver...@\@basednsna...@\@: bad owner name (check-names) school.internal.zone.db:11: no TTL specified; zone rejected school.internal.zone.db:13: schoolserve...@\@basednsna...@\@: bad owner name (check-names) school.internal.zone.db:13: no TTL specified; zone rejected school.internal.zone.db:14: schoo...@\@basednsna...@\@: bad owner name (check-names) school.internal.zone.db:14: no TTL specified; zone rejected school.internal.zone.db:15: ww...@\@basednsna...@\@: bad owner name (check-names) school.internal.zone.db:15: no TTL specified; zone rejected school.internal.zone.db:16: nt...@\@basednsna...@\@: bad owner name (check-names) school.internal.zone.db:16: no TTL specified; zone rejected school.internal.zone.db:17: tim...@\@basednsna...@\@: bad owner name (check-names) school.internal.zone.db:17: no TTL specified; zone rejected school.internal.zone.db:18: presenc...@\@basednsna...@\@: bad owner name (check-names) school.internal.zone.db:18: no TTL specified; zone rejected school.internal.zone.db:19: x...@\@basednsna...@\@: bad owner name (check-names) school.internal.zone.db:19: no TTL specified; zone rejected school.internal.zone.db:20: librar...@\@basednsna...@\@: bad owner name (check-names) school.internal.zone.db:20: no TTL specified; zone rejected school.internal.zone.db:22: conference.schoolserve...@\@BASEDNSNAME\@ \@: bad owner name (check-names) school.internal.zone.db:22: no TTL specified; zone rejected school.internal.zone.db:29: no TTL specified; zone rejected school.internal.zone.db:32: no TTL specified; zone rejected zone \...@\@basednsna...@\@/IN: loading from master file school.internal.zone.db failed: bad name (check-names) localhost_resolver/@@BASEDNSNAME@@/in: bad name (check-names) dns_rdata_fromtext: school.internal.zone.db:1: near 'root': bad name (check-names) school.internal.zone.db:2: no TTL specified; zone rejected school.internal.zone.db:4: schoolserver...@\@basednsna...@\@: bad owner name (check-names) school.internal.zone.db:4: no TTL specified; zone rejected
