Previous day | Jump to hour: 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 | Next day

Seconds: Show Hide | Joins: Show Hide | View raw
Font: Serif Sans-Serif Monospace | Size: Small Medium Large

Click in the nick column to highlight everything a person has said.
The icon identifies that the person is a core developer (has commit access).

#rockbox log for 2008-03-25

00:00:20 Quit BigBambi (Remote closed the connection)
00:01:06 Quit DefineByte ("Bye all")
00:02:25linuxstbpixelma: Your WPS works fine in the M3 sim, but doesn't work on the remote for the M5...
00:02:58linuxstbSo there seems to be a bug somewhere.
00:03:10*linuxstb compiles an X5 sim
00:03:41pixelmabtw. I also notice that the M3 sim seems to have problems changing the font (I used a nimbus-12 with a different WPS and now loaded cabbiev2 as theme and the font didn't change)
00:04:09pixelmaso maybe it's not font loading but theme loading
00:04:50pixelmaah yes, I can see now that it's working in the M3 sim too
00:05:36 Quit Soap_ (Connection timed out)
00:05:39 Join BigBambi [0] (n=Alex@rockbox/staff/BigBambi)
00:06:07 Quit ChAoS ("CGI:IRC")
00:06:12 Quit Jon-Kha (Remote closed the connection)
00:06:21BigBambiChAoS: The linux version works perfectly here
00:06:32 Join ChAoS [0] (n=44e4e61c@gateway/web/cgi-irc/labb.contactor.se/x-0eaa9b2c8206dd22)
00:06:38jhMikeShello...I've got two main "what ifs" I appreciate having checked out before committing this threading weirdness: iPod 5G, large sector (overall buffering speed was fixed without spinlock but glitched at first playback so that change had to wait), and a 64-bit sim (odd sensitivity to exclusion practices).
00:08:53ItalianPianistgood night guys
00:08:56 Part ItalianPianist
00:09:12linuxstbpixelma: (unsurprisingly), same problem in the X5 sim
00:09:51pixelmathat's what I would have expected too (just started to compile though myself)
00:10:44 Quit SoapH ("CGI:IRC (Ping timeout)")
00:10:58ChAoSBigBambi: Trying a reboot since my laptop was suspended from use at work and trying again... any other suggestions?
00:11:23pixelmalinuxstb: I tried commenting out the text viewport and then the status bar viewport shows, so maybe it's not general viewport handling (?)
00:11:41BigBambiNot so far as rbutil goes - I just tried the linux version and it worked perfectly. You can try the manual method
00:12:02*amiconn suspects the problem in the line array handling
00:12:03 Quit cool_walking_ (Read error: 104 (Connection reset by peer))
00:12:19jhMikeSlinuxstb: I noticed cabbiev2 just brings up the default WPS on x5 and H10 (both color @160x128) and works on my other players. Full clean, rebuild and reconfig was done.
00:12:26amiconnNow there can be several lines with the same line number (within different viewports)
00:13:01linuxstbjhMikeS: Ouch... I've just got the same thing in the X5 sim...
00:13:02ChAoSBigBambi: Only reason I am using the windows one is because the OSX one wont run on my G4.. know anything about that?
00:13:15linuxstbamiconn: Which line array are you talking about?
00:13:28BigBambiChAoS: When did you download the Mac one?
00:13:36ChAoSfew days back.
00:13:37linuxstbjhMikeS: Investigating...
00:13:40amiconnThe one that you multiplied in your first commit, and later changed back to a single one
00:13:41 Quit Soap__ (Read error: 110 (Connection timed out))
00:13:53amiconnI'm just guessing without actually looking at the code...
00:14:22BigBambiChAoS: There was a problem with the OSX one initially being compiled Intel only, but I thought that had been fixed
00:14:43linuxstbamiconn: This bug seems to just happen on remote LCDs... There is one line array per screen, so I would expect the bug to happen with the main LCD as well if there was that problem.
00:14:48ChAoShmm.. maybe I will downlaod again and try over on my mini if this doesnt work.. thanks for your suggestions!!
00:14:48BigBambiChAoS: Perhaps try the sansapatcher + unzipping the build method
00:15:19 Join ceclin [0] (n=clincher@96.240.96.79)
00:15:44BigBambiChAoS: rbutil is usually fine but it still in development so may have the odd issue, but if you still have problems, try the manual method outlined in the manual
00:16:29 Join SoapH [0] (n=621131c8@gateway/web/cgi-irc/labb.contactor.se/x-812e90254fb2e393)
00:16:45linuxstbjhMikeS: Your H10 also has a 160x128x16 LCD?
00:16:53jhMikeSyes
00:16:54linuxstbjhMikeS: Sorry, you answered that...
00:17:02ChAoSBigBambi: will do.. thanks again for the pointers.
00:17:03linuxstbI found the bug, committing now (missing |)
00:17:18BigBambiChAoS: No probs, I hope you get it working
00:17:34 Quit stripwax ("Miranda IM! Smaller, Faster, Easier. http://miranda-im.org")
00:18:31linuxstbjhMikeS: It was actually my later commit to make the %V parsing stricter that broke it - at the time I changed the WPS, the parser allowed that...
00:19:20 Join DaCapn [0] (n=dacapn@c-76-105-220-239.hsd1.or.comcast.net)
00:20:35 Join EspeonEefi [0] (i=espeonee@STRATTON-FOUR-SEVENTY-EIGHT.MIT.EDU)
00:20:54jhMikeSlinuxstb: you didn't update the 160x128, color versions?
00:21:58ChAoSAnyreason I couldnt run the rbutil 1.0.3 on osx since the 1.0.4 appears to be intel proc only?
00:22:00 Quit SoapH ("CGI:IRC (Ping timeout)")
00:22:44jhMikeSlinuxstb: just asking because the e200/gigabeat had no problem
00:22:45 Quit ender` (" The trouble with having an open mind, of course, is that people will insist on coming along and trying to put things in it.")
00:23:17linuxstbjhMikeS: Yes. The H10/X5 problem was a typo that the parser used to ignore, but I made the parser stricter.
00:23:38linuxstbs/typo/missing terminating | character/
00:25:26pixelmamaybe I should just go on committing all my greyscale cabbiev2 changes except the Iaudio remote
00:25:38 Quit fehmicans (Read error: 104 (Connection reset by peer))
00:26:15pixelmaWPS
00:27:10BigBambiChAoS: You can try. I seem to remember that Complete Install under 1.0.3 had a bug, so you will need to use the second tab to do the vootloader and build installs individually
00:27:11jhMikeSanother thing that happened but seems to have disappeared on H120 was that cabbiev2 would use the fixed font. Not sure if that was deliberately fixed or just silently showed and went away.
00:27:18BigBambis/vootload/bootloader
00:27:35 Part toffe82
00:30:25ChAoSBigBambi: Thanks
00:31:38BigBambiChAoS: You are welcome
00:31:49pixelmaI observed a strange behaviour on the Mini yesterday - going from cabbiev2 to the old text default (by loading the saved.cfg). Icons and backdrop vanished as should be but the WPS layout (tag info) was placed like in cabbie but using the reloaded font and clipped to the area the loaded WPS should have had (I think)
00:32:25linuxstbI think amiconn had the same problem - does your .cfg contain the line "wps: " (with nothing else) ?
00:32:26pixelmaa reboot "fixed" it
00:32:59pixelmaok, then he reported that already (sorry didn't read all of the logs...) :D
00:33:14pixelmait was his Mini
00:33:27linuxstbYes, I think he mentioned it was his mini...
00:33:28jhMikeSreading _all_ the logs would be way too time consuming
00:33:52linuxstbSomeone should post a daily executive summary...
00:34:02*linuxstb is not someone
00:34:05 Quit shotofadds (Read error: 104 (Connection reset by peer))
00:34:39Lloreanlinuxstb: Time for Rockbox to hire a secretary? :-P
00:35:40jhMikeSif anyone cares to do a quick check 80gig or 64-bit sim: http://jhmikes.cleansoap.org/priority-inheritance.diff (actually does a little more than the name says, ignore the crud about /uisimulator/sdl/kernel.c that may come up)
00:36:16ChAoSBigBambi: Ouch... cand find file rockbox.e200.mi4 or something then autooff.. suggestions?
00:36:26ChAoSs/cand/cant
00:36:34LloreanjhMikeS: I don't know if this is a priority issue or what. I've noticed on my Sansa that during first buffer, it's completely unresponsive to keypresses.
00:37:08ChAoSBigBambi:rockbox.mi4 and rockbox.e200 both not found.
00:42:06amiconnLlorean: That seems to depend on the theme. I observed it while testing bitmapstripped cabbiev2 on H300
00:42:07jhMikeSLlorean: yes, it is that.
00:42:20 Join SoapH [0] (n=621131c8@gateway/web/cgi-irc/labb.contactor.se/x-735aa45fb552db32)
00:42:41amiconnMy guess is that the buffering code somehow "forgets" to yield at all under certain circumstances
00:43:01*amiconn shrugs at reading the word 'preempt' in that patch
00:43:03LloreanI hadn't noticed it on my Gigabeat, but then I rarely press anything on first buffer.
00:43:44 Quit ChAoS (Nick collision from services.)
00:43:51amiconnIt never seems to happen when resuming after booting completed, but for the test I enabled resume on startup
00:43:52 Join ChAoS [0] (n=44e4e61c@gateway/web/cgi-irc/labb.contactor.se/x-451d6945727ee1b7)
00:43:57 Quit ChAoS (Nick collision from services.)
00:44:57 Quit hannesd (Read error: 113 (No route to host))
00:45:12Lloreanamiconn: My e200 had been booted for some time when I ran into it. At least long enough for me to change themes.
00:45:26amiconnah, hmm
00:45:33LloreanI'll double check
00:45:37amiconnAnyway, there seems to be a serious problem
00:45:53amiconnButtons aren't even pre-registered, at least on H300
00:46:38amiconnHmm, that'd mean interrupts are somehow disabled...
00:47:20 Quit SoapH ("CGI:IRC (Ping timeout)")
00:47:24jhMikeSthe patch has no UI stickiness on any of my players and also allows codec priority to be brought up gradually such that it's brought up smoothly
00:47:42 Join linuxstb__ [0] (n=linuxstb@i-83-67-212-170.freedom2surf.net)
00:48:27 Nick JdGordon|zzz is now known as JdGordon (n=jonno@rockbox/developer/JdGordon)
00:49:40 Quit linuxstb_ (Read error: 104 (Connection reset by peer))
00:49:48 Join linuxstb_ [0] (n=linuxstb@rockbox/developer/linuxstb)
00:50:33 Quit linuxstb (Nick collision from services.)
00:50:35 Nick linuxstb__ is now known as linuxstb (n=linuxstb@i-83-67-212-170.freedom2surf.net)
00:54:13*JdGordon loves the size of the recent wps commits :p
00:55:07linuxstb?
00:55:22 Join fasmaie [0] (n=yohann@c-98-216-170-85.hsd1.ma.comcast.net)
00:55:23jhMikeSas in file count?
00:55:26*pixelma pffs at JdGordon
00:55:54JdGordonyes, filecount
00:56:03JdGordontaking 455min to scroll down the screen
00:56:24 Join saratoga [0] (n=9803c6dd@gateway/web/cgi-irc/labb.contactor.se/x-d0f717e06b4d9a8b)
00:57:28 Join ChAoS- [0] (n=44e4e61c@gateway/web/cgi-irc/labb.contactor.se/x-c66280930c060c85)
00:58:38*jhMikeS thinks JdGordon exists in an accelerated frame of reference if it takes 455 minutes to scroll :p
00:59:10JdGordonthat was either meant to be 4, 5, 45 or 55... depends where you want the typo to be :p
00:59:24 Quit saratoga (Client Quit)
00:59:27linuxstbpixelma: I've tracked the bug down to a problem with the wps parser, but I'm not sure exactly what yet...
00:59:30 Join saratoga [0] (n=9803c6dd@gateway/web/cgi-irc/labb.contactor.se/x-3bc94cfd1a22cc3e)
00:59:53jhMikeSsqrt(1 - v^2/c^2)?
00:59:58*amiconn wants more data registers on coldfire :/
01:00
01:00:02 Join cool_walking_ [0] (n=notroot@203-59-129-195.perm.iinet.net.au)
01:00:42pixelmalinuxstb: thanks for looking into it, I'm currently preparing a commit without the Iadio remote (something more to scroll for Jd :P )
01:00:45 Quit mf0102 ("Verlassend")
01:00:58***Saving seen data "./dancer.seen"
01:01:00pixelma*Iaudio
01:04:58 Quit saratoga ("CGI:IRC (Ping timeout)")
01:05:13 Quit XavierGr (Nick collision from services.)
01:05:24 Join XavierGr [0] (n=xavier@rockbox/staff/XavierGr)
01:07:47 Join saratoga [0] (n=9803c6dd@gateway/web/cgi-irc/labb.contactor.se/x-cacbf2351a5c5280)
01:07:55 Join Xerion_ [0] (i=xerion@cp198589-d.landg1.lb.home.nl)
01:07:59saratogathe webclient has been all screwy for me lately
01:08:56 Quit Xerion (Read error: 104 (Connection reset by peer))
01:08:57 Nick Xerion_ is now known as Xerion (i=xerion@cp198589-d.landg1.lb.home.nl)
01:09:20 Join HEx [0] (n=HEx@83.231.208.215)
01:09:29ChAoS-BigBambi: Thanks!! have my first rockboxed device... starting to customize my theme already!!
01:09:39 Quit tvelocity_ (Remote closed the connection)
01:11:47 Quit loudergood (Read error: 110 (Connection timed out))
01:12:34*linuxstb slaps forehead
01:13:08 Join corevette [0] (n=corevett@adsl-75-35-113-7.dsl.pltn13.sbcglobal.net)
01:14:04 Join forehead [0] (n=54bd755c@gateway/web/cgi-irc/labb.contactor.se/x-57c0d8224f8f721a)
01:14:08 Quit DaCapn (Remote closed the connection)
01:14:21 Join DaCapn [0] (n=dacapn@c-76-105-220-239.hsd1.or.comcast.net)
01:15:36pixelmalinuxstb: does that mean I should hold back the commit and wait for the remote WPS problem being fixed or should I just go ahead and commit without it (and get my commit count up ;) )
01:16:00linuxstbI'm just compiling an ipod sim to test (no remote LCD), but yes, I think I've found the bug
01:17:05pixelmanice... but I was about pressing enter...
01:17:11 Join crzyboyster [0] (n=6210f195@gateway/web/cgi-irc/labb.contactor.se/x-fea8c330e486dcb5)
01:17:11*linuxstb prefers cabbie on the smaller LCDs - no enormous icons...
01:17:53*pixelma just went ahead
01:17:58linuxstb;)
01:18:17pixelmamaybe there is something missing anyways
01:18:27 Join toffe82 [0] (n=chatzill@adsl-75-12-168-243.dsl.frs2ca.sbcglobal.net)
01:20:35crzyboysterI'm having trouble with a wps that uses viewports and then putting in a progressbar and other icons (play, pause, etc) with not showing up. Here is my code: http://pastebin.ca/956048
01:21:01linuxstbpixelma: OK, my fix is committed.
01:21:09saratogaBagder: did you ever add my machine as a build server?
01:22:31linuxstbcrzyboyster: The icons are being displayed in the viewport you defined for the time, which is only 30x10 pixels in size.
01:22:31BHSPitMonkeylinuxstb, (little off the subject): do you happen to use facebook?
01:22:50linuxstbBHSPitMonkey: No, but I think I may have registered
01:23:06 Join RoC_MasterMind [0] (n=Free@c-71-203-172-58.hsd1.fl.comcast.net)
01:23:11BHSPitMonkeylinuxstb, ah
01:23:23BHSPitMonkeyI'll bug Bagder about it then, I know he does
01:23:41crzyboysterlinuxstb: Thanks! Let me poke around some more...
01:23:45 Quit crzyboyster ("CGI:IRC")
01:23:57*forehead is annoyed by getting slapped so often :|
01:24:02 Quit RoC_MasterMind (Client Quit)
01:24:05 Quit forehead ("CGI:IRC 0.5.9 (2006/06/06)")
01:24:21*linuxstb would have thought forehead was used to it by now
01:24:33*BHSPitMonkey is tired of the cheap /me jokes
01:24:34cool_walking_I assumed you specifically chose that name so people would slap you
01:24:57BHSPitMonkeycool_walking_, who are you talking to?
01:25:36cool_walking_hm...
01:25:42 Join ukl [0] (n=stephan@dsl78-143-208-90.in-addr.fast.co.uk)
01:26:19uklHiya. Can anybody already confirm that the bigpockets sansa c250 is _not_ v2?
01:27:00 Quit moos ("adios")
01:27:02linuxstbI doubt anyone has received one since you were last here..... I've ordered one though.
01:27:37uklI don't know when the offer began...ok, thanks for your help. I'll order tomorrow...
01:27:45uklsee you
01:27:52 Quit ukl (Client Quit)
01:28:00linuxstbOnly 288 left...
01:28:34*jhMikeS gueses by now there's no trouble with that posted patch in those two obscure corners :)
01:31:35 Quit amiconn (Nick collision from services.)
01:31:41 Join amiconn [50] (n=jens@rockbox/developer/amiconn)
01:32:23pixelmalinuxstb: build server stuck again?
01:32:56linuxstbI think it just started...
01:32:58pixelmaah no, just taking some time and complaining here helped (once more)
01:33:06 Quit Ravendug (Read error: 110 (Connection timed out))
01:33:15 Join Ravendug [0] (n=ravendug@73.100-84-212.ippool.ndo.com)
01:33:23linuxstbAlthough it combined two commits...
01:33:35amiconnThat's okay
01:34:19amiconnThe build system combines commits which are arriving within the time window, which is normally 60 seconds, but if a build is already running, the window is extended
01:34:37pixelmalinuxstb: I'll blame any red/yellow on you ;)
01:34:46 Join kushal_12_27_200 [0] (n=kushal@12.169.180.134)
01:34:50linuxstb;)
01:34:51amiconnThere's also some recovery time after one build during which it won't start a new one. I don't know why though
01:35:23 Join crzyboyster [0] (n=6210f195@gateway/web/cgi-irc/labb.contactor.se/x-c8cf35fc3b9c9ded)
01:36:28crzyboysterI have another question with my viewports wps coding. The progressbar is not being drawn with this code: http://pastebin.ca/956068
01:37:35linuxstbcrzyboyster: Again, you're drawing it outside the viewport
01:38:02linuxstbYour viewport is 14 pixels high, and you're drawing it at "toppos" 102
01:38:50crzyboysterWow. I should really analyze the viewports from an elementary level.
01:39:13crzyboysterAnd how are people making the bitmap strips. Like what program to use?
01:39:35linuxstbI use the command-line "montage" program, which is part of imagemagick
01:40:55 Join piga [0] (n=leonardo@200-161-98-23.dsl.telesp.net.br)
01:42:45 Join jas6180 [0] (n=jas6180@dialup-4.156.9.185.Dial1.Boston1.Level3.net)
01:43:35 Quit mud-rb (Read error: 104 (Connection reset by peer))
01:44:24 Quit quaal (Read error: 113 (No route to host))
01:45:02crzyboysterNow I'm truly stumped with this viewports progressbar thing. It still won't show up! Here is my code: http://pastebin.ca/956075
01:45:12 Join quaal [0] (n=rodney@pool-96-228-151-235.tampfl.fios.verizon.net)
01:45:22crzyboysterSorry about this, I'm still getting the hang of this viewports code
01:46:01Nico_Plinuxstb: I've started to look at your WPS changes a bit... I like parse_list a lot :)
01:46:03pixelmayour viewport is still only 20 pixels high, if I read correctly
01:46:22Nico_PI remember wanting to add scanf to the core for similar reasons
01:46:35linuxstbNico_P: It's not as useful as I thought it would be though... Mainly because of the optional parameters everywhere (e.g. albumart0
01:47:09linuxstbAlthough maybe it could be extended to support them...
01:48:02Nico_Pyes, it would be good. then it could also be used for the progressbar
01:48:06*amiconn wonders why the 240x320 cabbiev2 backdrop is saved as 32-bit BMP
01:48:29crzyboysterMy progressbar is only 14 pixels high, though. Updated code at http://pastebin.ca/956083
01:48:43crzyboyster(Still won't work)
01:49:07linuxstbcrzyboyster: Change 102 to 0 in your %pb line
01:49:17linuxstbThat's the y position of the bar...
01:49:31 Quit perrikwp ("http://www.mibbit.com ajax IRC Client")
01:49:41linuxstbRemember that all co-ordinates are relative to the viewport the item is displayed in.
01:49:42pixelmacrzyboyster: you only changed the y position of the viewport not the height btw.
01:50:17pixelmaor even made it less tall (only 14 pixels)
01:50:21 Quit saratoga ("CGI:IRC (EOF)")
01:50:24*jhMikeS goes to sneak one in between all the WPS activity
01:50:37crzyboysterYES! (sorry, I got a bit excited) I have a lot of wps to update to viewports so I better get the hang of this quickly.
01:51:41Nico_Plinuxstb: how maintainable does the WPS code look to you? (I think you're the first one to make sizeable changes to it since I committed the parser)
01:52:17linuxstbNico_P: It's nice, but somehow still seems very big for what it does... Although I can't think of ways to reduce it.
01:52:52linuxstbDid you see my statusbar patch I posted earlier today (in IRC)
01:52:59Nico_Pno
01:53:52linuxstbStarting here - http://www.rockbox.org/irc/log-20080324#20:26:48
01:54:27 Join kushal [0] (n=kushal@12.169.180.134)
01:54:35 Quit kushal (Remote closed the connection)
01:54:38 Join perrikwp [0] (i=4aa794a0@gateway/web/ajax/mibbit.com/x-2976ae0c57e1e5ac)
01:54:42Nico_Pthe screenshot looks nice :)
01:55:01Nico_Pwhere do you store the tokens?
01:55:39linuxstbKeep reading... It's specified as part of the main .wps file, using viewports
01:55:49Nico_Pah right
01:55:49 Join jas6180_ [0] (n=jas6180@dialup-4.156.9.206.Dial1.Boston1.Level3.net)
01:56:29linuxstbSo no more RAM usage, and very little extra code
01:56:36Nico_Pit's a nice approach indeed
01:56:52crzyboysterSo album art needs to be in a viewport, too?
01:57:18Nico_PI had started making changes to the current code so that a wps_data struct would actually have pointers to buffers instead of containing the buffers
01:57:27linuxstbcrzyboyster: It's cleaner - and prevents it being overwritten by text lines. If possible, you should design your WPS to put everything in a viewport, and for those viewports to not overlap.
01:58:00 Quit crzyboyster ("CGI:IRC (EOF)")
01:58:02 Quit kushal_12_27_200 (Connection timed out)
01:58:09kugelHey Nico_P, I wanted to ask you about the resizing stuff. You played around with integrating in the core, didn't you?
01:58:28Nico_Pkugel: I did a few weeks/months ago
01:58:36kugelyea
01:58:36linuxstbNico_P: I haven't really thought about the recording and radio screens, and how they would fit in though, if they were customisable.
01:58:51kugelAnd how's it going? Or did you give it up?
01:59:19linuxstbBut I think it might make sense for the radio and recording screens to be able to define their own status bars, which are displayed when those features are active.
01:59:23Nico_Pkugel: I haven't had much time lately. I think it's still a desired feature for the core, but I haven't been following the patch lately
01:59:57kugelThere wasn't much to follow
01:59:59Nico_Plinuxstb: my idea was to make the wps_data struct generic, and have one for each customizable screen
02:00
02:00:15Nico_Peach pointing to a different set of buffers
02:00:50linuxstbAlthough maybe it would make sense for them to share images.
02:01:19Nico_Pit probably would, yes
02:02:27linuxstbAnd I don't think 52 images is an issue now we have subimages. e.g. cabbiev2 just needs 6 of those slots
02:02:39 Join jas6180__ [0] (n=jas6180@dialup-4.156.222.238.Dial1.Boston1.Level3.net)
02:02:42Lloreanlinuxstb: I agree that they should be able to define their own. As to images, if you have a ThemeA.wps, and a ThemeA.rcwps and a ThemeA.fmwps, they should all look in the ThemeA folder, right?
02:02:52JdGordonif the image buffers are shared they should be dumped to disk in 1 file so reloading one screen isnt slwoed down too mcuh
02:03:28 Quit jas6180__ (Remote closed the connection)
02:03:36JdGordonLlorean: wps/{wps,rec,fm}/<folder name> ?
02:03:42linuxstbLlorean: Yes, although maybe it would be nice for a .wps to be able to specify its bitmap dir - e.g. the unicode and non-unicode versions of a theme
02:03:43 Quit fasmaie (Read error: 113 (No route to host))
02:04:19 Join jas6180__ [0] (n=jas6180@dialup-4.156.222.238.Dial1.Boston1.Level3.net)
02:04:34pixelmalinuxstb: ah, I can see the icons on the remote now :) going to commit... (first wps using viewports in svn)
02:04:44Lloreanlinuxstb: Some WPS meta data might be nice.
02:04:46linuxstbNo turning back now...
02:05:10JdGordontime to get the new theme site up then!
02:05:22linuxstbLlorean: What kind of metadata?
02:05:34LloreanJdGordon: Well, the idea was to share images. So /wps/blah would contain the images used the the While FM Screen, and the While Recording Screen if they all had the filename as blah
02:05:54scorcheJdGordon: hush...gotta take care of RL first =<
02:06:29Lloreanlinuxstb: Well, as you suggested the Image folder. But also perhaps the Theme Name (there might be some reason later to know if all screens were using the same overall "theme") or other such things.
02:06:31 Quit jas6180__ (Remote closed the connection)
02:06:49 Join jas6180__ [0] (n=jas6180@dialup-4.156.222.238.Dial1.Boston1.Level3.net)
02:07:03LloreanMaybe "expected font heights for used fonts" to give warning if someone changes it to a too-tall font.
02:07:36LloreanThere's surely more info that could be stored about a WPS, really, to make them more "friendly" from a user perspective when the user starts making mistakes.
02:07:53 Quit jas6180__ (Remote closed the connection)
02:08:02 Quit Mouser_X (Read error: 110 (Connection timed out))
02:08:14*amiconn thinks that a themable recording screen doesn't make sense
02:08:47Lloreanamiconn: I think it does on some targets.
02:09:04LloreanFor example, the c200 has a fairly short screen, and different people have different views on what has priority there.
02:09:05linuxstbI would just like to see the recording screen adapt more to the different screen sizes - i.e. not treat every LCD as if it's 112x64x1
02:09:08 Join jas6180__ [0] (n=jas6180@dialup-4.156.222.238.Dial1.Boston1.Level3.net)
02:09:40amiconnThat's a different thing. Of course the recording screen needs rework to no longer use the sysfont
02:10:12amiconnBut the recording screen has numerous necessary widgets, and not really optional information to choose from
02:10:41linuxstbAnd I would guess that recording types don't want eye-candy - just a clear layout of all the available info.
02:11:03Lloreanlinuxstb: Look at the various evolutions of the recording screen in the Recording Enhancement Pack.
02:11:25LloreanThey wouldn't necessarily want eye candy, but there's some disagreement as to what's necessary, and where screen space should best be used.
02:11:30amiconnFM is somewhat different, although I wonder how many pieces of optional information are on that one
02:11:57amiconn...unless a target has RDS - but we don't have one yet
02:12:07linuxstbIt's also a style thing though - making it look similar to the WPS, even if the info is the same.
02:12:15Lloreanamiconn: I think FM should be themed just for the sake of having its appearance consistent with the rest of the UI. Not really much in the way of "optional" info, but there can still be appearance preferences.
02:12:35 Quit PaulJam_ (".")
02:13:06 Quit jas6180 (Connection timed out)
02:13:33LloreanBut the recording screen has different priorities on the information based on whether you're using it in a well lit environment where you care about all the information and don't mind squinting, or whether you're stealthing and want to be able to see certain very key things at a glance (if my understanding is clear) but don't care much about other non-key things.
02:13:56amiconnStation name (from .fmr), frequency, mono/stereo, and (one some targets) signal strength
02:14:22Nico_Plinuxstb: are you still planning on allowing something like %?bl<%xdB> (with the expansion)?
02:15:02linuxstbNico_P: I'm not planning on implementing it myself...
02:15:12Nico_Phehe :)
02:15:54linuxstbBut I'm not 100% convinced it's a good idea - it may just be confusing.
02:15:56Nico_Pit'd probably need a clear syntax to allow subsets, though, don't you think?
02:16:30linuxstbI never like having multiple ways to do the same thing...
02:17:04linuxstbBut I'm not against it if others think it's useful.
02:17:08LloreanI'd rather my suggestion. ;)
02:17:24linuxstbLlorean: What was that?
02:17:24LloreanThough it wouldn't work for playback state.
02:17:56Lloreanlinuxstb: For conditionals that represent values, do like the progress bar and display a relative portion of the image. Only really useful for volume and battery though.
02:18:12LloreanBut it does mean you don't have more than one way of doing the same thing. ;)
02:18:18linuxstbNot even for volume - with the special cases
02:18:55LloreanWell, volume could have <mute, progressive image, clipping>
02:18:56*pixelma didn't want to drop the info at the top of the WPS, stupid c+p mistake...
02:19:28LloreanI just like the idea of giving WPS authors as much level of granularity as they can stomach, without needing giant images.
02:21:15LloreanSince people are already complaining about running out of space in the buffer, that is.
02:21:36*Llorean would also like it applied to skinnable peakmeters, while he's dreaming.
02:21:56*linuxstb points Llorean to the source code... ;)
02:21:58Nico_PLlorean: I'm not sure it's really useful for anything other than the progressbar
02:22:21Nico_Pthe battery, for example, usually has an outline. you couldn't do that
02:22:25 Quit jas6180_ (Connection timed out)
02:23:19LloreanNico_P: The outline can be managed either by the backdrop, or by four other images (only useful if the battery had more than five steps to begin with)
02:23:38LloreanOr, if image stacking ever works well, by one other image.
02:23:40Genesisarchos recruts some linux C coder , if some french are unployed :)
02:24:06JdGordonhehe peakmeters done the same was as the progress bar would be awesome
02:24:14jhMikeSLlorean: RB isn't about what you'd like, it's about KISS </end extreme sarcasm>
02:24:36LloreanjhMikeS: :-P
02:24:57*JdGordon grumbles off to uni :(
02:25:52Nico_PLlorean: suggest a good tag syntax and I'll implement it ;)
02:25:55*jhMikeS 's e200 just gave him an ES discharge while plugged-in for that comment :
02:26:20LloreanNico_P: For which idea? I've been spouting off too much nonsense to be sure which one you're interested in. :-P
02:26:59Nico_P"continuous" enums
02:27:22linuxstbHorizontal and/or vertical?
02:27:24Nico_PI like the themeable peakmeter even more but that one doesn't really require additional syntax :)
02:27:31jhMikeSvs. quantum enums?
02:28:05Nico_Plinuxstb: the syntax would probably need to take this into account, yes
02:28:26LloreanNico_P: For the battery one, I'd just make the the percent battery one a single-image enum.
02:28:29linuxstband direction...
02:28:59LloreanBut I thought there was a percent volume WPS tag too.
02:29:20 Join midgey [0] (n=tjross@westquad-188-46.reshall.umich.edu)
02:29:23LloreanBecause I *think* we can assume that nobody's going to use a single image to represent all charge states, normally, anyway.
02:30:06LloreanNico_P: Peakmeters, imho, need to be split into right/left individual peakmeters if they're to be made themeable.
02:30:23Nico_PI agree
02:30:29Genesisbye
02:30:36 Quit Genesis ("Quitte")
02:30:48LloreanAnd not only horizontal/vertical, but left-to-right vs right-to-left for the peakmeters at least.
02:31:01LloreanThough you could fake that with clever backdrop use, anyway
02:31:05LloreanSo it's non-essential
02:31:42*Llorean un-says the last few lines, since he realizes that would invert peaks.
02:32:03 Quit jas6180__ (Remote closed the connection)
02:32:40 Join jas6180__ [0] (n=jas6180@dialup-4.156.222.238.Dial1.Boston1.Level3.net)
02:35:03kugelHas anyone thought about costumizable list again?
02:35:18 Quit Thundercloud_ (Remote closed the connection)
02:35:38 Join jas6180 [0] (n=jas6180@dialup-4.156.9.19.Dial1.Boston1.Level3.net)
02:36:10kugelbtw, you all have great ideas for future costumizing possiblities of rockbox
02:36:11*Nico_P would love to have enough time to start making the peakmeter themeable
02:36:31kugelNico_P: If it was themable, I'd acutally use it
02:37:03LloreanIf it was themable, it'd probably hurt performance even more. ;)
02:37:25Nico_Phehe, probably :)
02:38:48Nico_Pdoes the forum have viewport-using WPS apart from arboxWidgets?
02:39:20linuxstbI've noticed a few over at anythingbutipod.com, but I'm not sure if they've been updated for SVN implementation
02:40:45kugelI have several themes that use viewports in my build. And I will update most of them to the lasted viewport implementation
02:41:57LloreanThough I do think that right now, viewports "aren't impressive enough." They still, to many people, just appear to be an implementation of what they had in unsupported builds ages ago.
02:42:18LloreanThough if linuxstb's hack becomes a reality, I think people will start wowing at the SVN rockbox, at least for a little bit.
02:42:33LloreanAt least as long as people making the unsupported builds let people know that's a feature that came from us. ;)
02:42:52kugelWell, unless other screens/contexts make use of viewports more, it's not too impressive :)
02:43:07 Part thresh
02:43:22*Llorean finds it pretty impressive, since it lets him make font size independent WPSes.
02:43:52linuxstbHow does it allow that?
02:43:57kugelBut I think it's nice that there's a little competetion between the official builds and the unsupported ones. It speeds developement a bit up ;)
02:44:07scorchethere is?
02:44:41linuxstbI'm just fed up of people coming here complaining that themes don't work...
02:44:42kugelI think so
02:44:59kugel