~walter/sugar-old/walters-clone

	Commit message (Collapse)	Author	Age	Files	Lines
*	restore sugar-launch by bundle id substring, fixes #897 sucrose-0.84	James Cameron	2010-10-12	1	-3/+13
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	sugar-launch uses GetBundlePath which calls bundleregistry.get_bundle(). In this patch, the get_bundle() method is changed to retain as much of the original API as possible, yet in the situation where it might return None it will now return a bundle if there is only one bundle that matches the search string. http://bugs.sugarlabs.org/ticket/897 http://dev.laptop.org/ticket/9189 Patch tested on Sugar 0.84.16 on OLPC XO-1.5 build os206. Test case: import jarabe.model.bundleregistry registry = jarabe.model.bundleregistry.BundleRegistry() tests = ['org.laptop.Terminal', 'Terminal', 'terminal', 'e', 'asdqweas'] for x in tests: y = registry.get_bundle(x) if y is None: z = 'None' else: z = y.get_bundle_id() print x, z Output before patch: org.laptop.Terminal org.laptop.Terminal Terminal None terminal None e None asdqweas None Output after patch: org.laptop.Terminal org.laptop.Terminal Terminal org.laptop.Terminal terminal org.laptop.Terminal e None asdqweas None
*	Release 0.84.23 v0.84.23	Simon Schampijer	2010-10-06	1	-1/+1
\|
*	Journal: Show alert when error occurs while writing to external devices #10312	Simon Schampijer	2010-10-06	3	-5/+71
\|
*	Missing file for Sugar Ad-hoc networks	Simon Schampijer	2010-09-30	1	-0/+280
\|
*	AP: separate signal strength from status #10347	Simon Schampijer	2010-09-22	1	-21/+20
\|
*	Add default Ad-hoc networks #9845	Simon Schampijer	2010-09-22	5	-132/+339
\| \| \| \| \| \| \| \|	This patch adds three default Ad-hoc networks, for channel 1, 6 and 11. They are represented with designated icons in the neighborhood view. This will mimic the mesh behavior on devices where mesh hardware is not available and make the "under a tree"-scenario possible in those cases. If Sugar sees no "known" network when it starts, it does autoconnect to an Ad-hoc network.
*	Connect to gabble immediatly when possible #10350	Simon Schampijer	2010-09-22	2	-1/+20
\| \| \| \| \|	We make sure this happens after registration and when setting a new jabber server.
*