maemo.org - Talk - View Single Post - Announce: Traveller for NIT's

	Munk	2009-05-05 , 01:14
	Posts: 229 \| Thanked: 108 times \| Joined on Oct 2007 @ Sacramento, California	#22

Originally Posted by jolouis

Code:

#!/bin/sh

if [ -r /etc/osso-af-init/af-defines.sh ]; then
  source /etc/osso-af-init/af-defines.sh
fi

if [ -x /usr/bin/dbus-send -a -x /usr/bin/gtk-update-icon-cache ]; then
  dbus-send --type=method_call --dest=org.freedesktop.Notifications /org/freedesktop/Notifications
org.freedesktop.Notifications.SystemNoteInfoprint string:"Updating icon cache" || true
fi

if [ -x /usr/bin/gtk-update-icon-cache ]; then
  gtk-update-icon-cache -f /usr/share/icons/hicolor || true
fi

Cool, thanks for that.

Originally Posted by jolouis

Maintaining cross-platform compatibility is always cool, but just remember that you're probably missing out on some of the great features of the tablets. That being said, it's entirely possible to write an app that takes advantage of things like power savings, alarmD etc AND still functions normally on other OS's, you just have to be really cautious in your coding that's all.

Agreed, but I have to admit that until recently the whole "d-bus" thing was a mystery to me. Now, I'm looking into those possibilities of adding NIT specific d-bus items.

Originally Posted by jolouis

1) Power management is IMPORTANT. Don't overlook this; don't ignore it; don't pretend that on a tablet it won't matter. Any app that has a clock and alarm functionality should either A) implement power management or B) make sure the user is aware of the possibility that the tablet will run out of juice if left on battery only over night with the app running. The first version of FC that we had drained a full battery in about 5-6 hours; the most recent version I've left running on my tablet for about 4-5 days without noticing any significant change in load between having the app on and not having anything running... this makes a big difference esp. when travelling or having alarms/etc.

Yes, while I have spent A LOT of time on reducing the CPU drain on the battery, currently Traveller will kill your battery in about six hours. Especially if you are using the "Atmosphere" portion to calm yourself for sleep. I'll look into fixing this in the future but for now, you'll want to leave the unit plugged in over night.

Originally Posted by jolouis

2) AlarmD is your friend on the tablets. You don't have to rely on it, and for cross-platform compatibility you can always just have a little option to detect if it's there and do things normally if it's missing (I've got a config setting in FC for this, but detection will be in the next version); but it does give you some pretty awesome advantages; namely helps with the power consumption thing, and lets your app auto launch at alarm times.

I agree that detection is a smart way to go. I currently detect if "battery-status" is installed and if it is, the internal temp is shown under the AM/PM indicator. I'll probably approach it the same way once I start looking at NIT specific hardware.

Originally Posted by jolouis

Anyways, seems very cool! If you need some advice/help with anything drop me a line

Thanks and thanks!

Quote & Reply |