**** BEGIN LOGGING AT Fri Feb 10 02:59:57 2012
**** BEGIN LOGGING AT Fri Feb 10 07:28:11 2012
Feb 10 09:00:42 <jhojho`> d
Feb 10 09:00:50 <jhojho> d
Feb 10 09:38:08 <cryptk> d ?
Feb 10 10:38:38 <stbuehler> :D ?
Feb 10 11:26:42 <stbuehler> ok, wtf. busyboy only support utf8 sequences with len < 3. so äöü work, but € doesn't
Feb 10 11:30:20 <stbuehler> also optware mc fails with utf8
Feb 10 11:30:34 <stbuehler> and optware vim fails with € too
Feb 10 11:30:53 <stbuehler> this is all stuff we can't fix in wterm
Feb 10 12:20:06 <stbuehler> optware bash and zsh fail even worse with utf8
Feb 10 13:18:23 <PuffTheMagic> stbuehler, that sucks
Feb 10 13:20:05 <stbuehler> the good news are: just ssh somewhere else, and it'll probably just work :)
Feb 10 13:22:04 <PuffTheMagic> we need to build new vim and bash and put them in preware
Feb 10 15:08:31 <ka6sox> PuffTheMagic, for Optware or something else : vim and bash.
Feb 10 15:10:42 <PuffTheMagic> ka6sox, if you are asking if I am going to submit something new to upstream optware the answer is probably not
Feb 10 15:11:08 <PuffTheMagic> im talking about building a working bash&vim in build.git
Feb 10 15:13:42 <PuffTheMagic> stbuehler, Brybry i pushed 0.4.0 to the feeds but it refuses to show up, idk whats wrong
Feb 10 15:13:51 <PuffTheMagic> there are no errors in the log
Feb 10 15:14:06 <Brybry> alpha or beta
Feb 10 15:15:44 <Brybry> or wait, did you increase the version number at all?
Feb 10 15:16:24 <Brybry> it should be 0.4.1 or something
Feb 10 15:16:26 <Brybry> or 4.0.1
Feb 10 15:20:19 <Brybry> hmm, actually, I guess 0.4.0 should work too
Feb 10 15:24:19 <PuffTheMagic> ya the release should be 0.4.0 is regular feed
Feb 10 15:40:00 <Brybry> does preware optware even support building from source?
Feb 10 15:40:30 <Brybry> I guess it would be better to say build.git optware
Feb 10 15:41:48 <ka6sox> no
Feb 10 15:42:01 <ka6sox> it steals from the optware builds on nslu2-linux.org
Feb 10 15:42:10 <ka6sox> I am updating those builds now to latest
Feb 10 15:42:33 <ka6sox> but first I need to get that autobuilder back online today
Feb 10 15:42:38 <Brybry> though it's really easy to build upstream optware packages (after hours of bashing my head against the wall with kismet with build.get and scratchbox I got it working in minutes)
Feb 10 15:42:57 <PuffTheMagic> autobuilder is down?
Feb 10 15:42:57 <ka6sox> you got what working? optware?
Feb 10 15:43:04 <Brybry> kismet
Feb 10 15:43:10 <ka6sox> optware one...not webos'
Feb 10 15:43:16 <ka6sox> not wosi's
Feb 10 15:43:16 <Brybry> yar
Feb 10 15:43:23 <Brybry> but wosi pulls from the same place
Feb 10 15:43:25 <Brybry> I believe
Feb 10 15:43:37 <ka6sox> yes, but I am getting that up this morning
Feb 10 15:43:57 <ka6sox> had to consolidate things...it was sprawled out over 3disks and 2TB of data
Feb 10 15:44:22 <ka6sox> its now 714GB of data
Feb 10 15:45:27 <ka6sox> this morning one of the original guys who worked on it is coming in from Guam remotely fixing it.
Feb 10 15:45:52 <ka6sox> Brybry, did you put kismet latest in optware?
Feb 10 15:45:57 <ka6sox> or with build.git?
Feb 10 15:46:19 <Brybry> I didn't put it anyway
Feb 10 15:46:21 <Brybry> anywhere*
Feb 10 15:46:31 <ka6sox> okay
Feb 10 15:46:39 <ka6sox> which method did you use to build it?
Feb 10 15:46:49 <Brybry> nslu2 optware
Feb 10 15:47:07 <Brybry> this is what I did: http://www.webos-internals.org/wiki/User_talk:Brybry
Feb 10 15:47:26 <PuffTheMagic> ka6sox, are there errors right now on build.git tha tim not seeing, i cant figure out why new wterm is not showing up
Feb 10 15:48:31 <ka6sox> PuffTheMagic, have to look at tinker...see whats happening with the builds....any buildlogs yet or nothing?
Feb 10 16:01:51 <PuffTheMagic> wterm_0.4.0-1 and wterm_0.4.0-2 show up as if they were built
Feb 10 16:02:01 <PuffTheMagic> but there is no ipk
Feb 10 16:02:05 <PuffTheMagic> and nothing in packages
Feb 10 16:02:26 <PuffTheMagic> Reading info for package ipkgs/webos-internals/armv7/us.ryanhope.wterm_0.4.0-2_arm.ipk
Feb 10 16:02:35 <PuffTheMagic> >f+++++++++ us.ryanhope.wterm_0.4.0-2_arm.ipk
Feb 10 16:10:34 <PuffTheMagic> ka6sox, did u just do something, they both show up now
Feb 10 16:11:03 <ka6sox> I guess your cache time expired :D
Feb 10 16:14:42 <PuffTheMagic> Brybry, stbuehler what do you guys think we should do about the vkb click sounds
Feb 10 16:17:20 <cryptk> PuffTheMagic, ipkg is currently pointed to my mirror
Feb 10 16:17:24 <cryptk> that mirror runs varnish
Feb 10 16:17:30 <cryptk> it has a 5 minute cache on it IIRC
Feb 10 16:18:24 <cryptk> maybe 10...
Feb 10 16:18:32 <cryptk> can't remember off the top of my head
Feb 10 16:18:32 <PuffTheMagic> cryptk, this took over an hour to show up
Feb 10 16:18:40 <cryptk> yeah, it isn't that long of a cache
Feb 10 16:18:42 <PuffTheMagic> probably close to 2
Feb 10 16:19:48 <ka6sox> caches are a PITA when doing development
Feb 10 16:19:51 <Brybry> oh yeah, PuffTheMagic
Feb 10 16:19:59 <Brybry> does the setup scene work for you on your pre3?
Feb 10 16:20:06 <Brybry> like if you try to put in a root password
Feb 10 16:20:46 <PuffTheMagic> Brybry, i did in the past when i set a root password
Feb 10 16:20:57 <Brybry> this is not something I try every day =x
Feb 10 16:21:21 <Brybry> wait, I got it
Feb 10 16:21:28 <Brybry> I just fail at tapping
Feb 10 16:22:53 <PuffTheMagic> ya enyo taps are finicky on phones
Feb 10 16:38:33 <stbuehler> PuffTheMagic: is there anything wrong with the click sound?
Feb 10 16:38:53 <PuffTheMagic> stbuehler, besides it only working on 1 card
Feb 10 16:39:02 <PuffTheMagic> s/1 card/ the first card/
Feb 10 16:39:12 <PuffTheMagic> which is usually the exhibition mode card
Feb 10 16:39:18 <stbuehler> ah right
Feb 10 16:44:26 <dtzWill> Brybry: just happened to have tried the setup on my pre3
Feb 10 16:44:30 <dtzWill> using wterm from preware
Feb 10 16:44:41 <dtzWill> set password right, can now 'su' neatly
Feb 10 16:45:13 <PuffTheMagic> dtzWill, i dont think we can do anything about the rounded cards on phones
Feb 10 16:45:17 <PuffTheMagic> unless we go fullscreen
Feb 10 16:45:25 <PuffTheMagic> which is was actually thing about adding support for
Feb 10 16:45:34 <PuffTheMagic> go fullscreen and add a thin header
Feb 10 16:45:40 <PuffTheMagic> with button for the menu
Feb 10 16:45:44 <PuffTheMagic> and with the term title in it
Feb 10 16:45:59 <dtzWill> oh cool
Feb 10 17:46:56 <cryptk> PuffTheMagic, if you add in fullscreen... have the title bar show "wTerm: Powered by caffeine"
Feb 10 17:47:29 <cryptk> or perhaps "wTerm: Standard window title as set by the application you are running"
Feb 10 18:03:17 <ka6sox> Brybry, if you have that diff we can send that in for kismet.
Feb 10 18:03:28 <ka6sox> that will get it updated
Feb 10 18:03:43 <Brybry> I'd have to clean it up first and such
Feb 10 18:03:51 <Brybry> that was mostly a proof of concept
Feb 10 18:04:09 <ka6sox> okay
Feb 10 18:04:38 <Brybry> and I'd probably want to just make a new package for the pre target as they may have reasons to be on a 4 year old build of kismet
Feb 10 18:06:11 <stbuehler> can't we get rid of the rounded corners with css?
Feb 10 18:08:42 <Brybry> I dunno that they're done at app level/I feel like they're done by luna?
Feb 10 18:08:48 * Brybry may or may not be playing with mouse stuff
Feb 10 19:15:24 <PuffTheMagic> cryptk|offline: its gonna show the title as set by the shell/app
Feb 10 19:16:29 <PuffTheMagic> stbuehler: i think its out of our hands, the rounded corners
Feb 10 19:16:42 <PuffTheMagic> stbuehler: so we could reduce the term size a little
Feb 10 19:17:19 <PuffTheMagic> and position it to avoid the corners
Feb 10 19:17:24 <PuffTheMagic> thats what we did on old terminals
Feb 10 19:53:43 <PuffTheMagic> weird
Feb 10 19:53:56 <PuffTheMagic> 2 people now have encountered this weird bug after installing 0.4.0
Feb 10 19:54:13 <PuffTheMagic> the orientation is landscape but it uses portrait keyboard
Feb 10 19:54:22 <PuffTheMagic> toggleing rotation lock has fixed it for both of them
Feb 10 20:24:09 <Brybry> what platform
Feb 10 20:24:24 <Brybry> or I guess I can hunt down the actual reports :3
Feb 10 20:31:27 <Brybry> ah, they closed it and touchpad, hmmm
Feb 10 20:32:01 <PuffTheMagic> TP
Feb 10 20:32:03 <Brybry> if it fixed when they closed it and ran it again sounds like a pref loading issue
Feb 10 20:32:22 <Brybry> though that'd be odd
Feb 10 20:41:10 <Brybry> or maybe rotationLock can be unset in the prefs database and that's somehow throwing things off, I'll purposefully feed it bad values in a bit and see what happens
Feb 10 20:48:04 * PuffTheMagic is making a character selector
Feb 10 21:32:41 <Brybry> if I put this._rotationLock = -1; at the top of rotationLockReponse() it gets stuck in portrait
Feb 10 21:35:30 <Brybry> hmm, I wonder what database rotationLock is in
Feb 10 21:41:05 <Brybry> I guess systemprefs, I'm just blind
Feb 10 21:58:24 <PuffTheMagic> so -1 might be... never ever set before?
Feb 10 22:25:33 <stbuehler> PuffTheMagic: positioning should be easy, SDLFontGL::setDimension - you can set the window in pixels
Feb 10 23:03:58 <Brybry> PuffTheMagic, that was just a test value. I didn't try actually deleting the pref from my preferences database yet
Feb 10 23:05:15 <Brybry> but, yeah, that's the idea: if the value is something we don't expect/never set before then it gets locked into portrait
Feb 10 23:05:17 <PuffTheMagic> i meant this issue is probably triggered by people who have never set rotation lock
Feb 10 23:06:00 <Brybry> I think maybe we can safely do tmpOrientation = enyo.getWindowOrientation() without the if (this._rotationLock == 0) and it'll just get overwritten if rotationlock has a valid value
Feb 11 01:02:21 <PuffTheMagic> Brybry, stbuehler just added a custom character selector
**** ENDING LOGGING AT Sat Feb 11 02:59:57 2012