Re: Release schedule proposal
On Sun, Nov 9, 2008 at 11:56 AM, Frank Gevaerts [EMAIL PROTECTED] wrote: I think there's a reasonable chance that attempted 3-month cycles will turn out to take 4 months anyway (and 4-month atempts would take 5 months), so I think staying with 3 months is a good idea Plus, if we find that three months is too short a timeframe, we can always extend the release period to four months, or however long we need. Will.
Re: Release schedule proposal
On Wed, Nov 5, 2008 at 1:59 AM, Dave Chapman [EMAIL PROTECTED] wrote: * Releases happen every 3 months, with the date of 3.0 (23rd September) being the reference point, so releases would be: I quite like this idea. With Rockbox it is quite difficult to quantize what makes a release, so time based releases provide a manageable system to work by. WINE also uses this approach and it seems to work pretty well for them. For major releases (ie. 3.0, 4.0, etc) we could have more specific requirements, for example a UI rework or some other quite visible change. Just my quick 2c... Cheers, Will.
Re: New port, question about hidden partitions
The *INF.PVR files describe the *DAT.PVR files from what I can see. I've just given them a quick look over - and all I've gleaned so far is that the the second dword in the file is the size of the DAT file in bytes. Additionally the 63rd dword is either equal to the 2nd (the file size) or the 4th, but I'm not sure what this means. I'd say that the firmware resides on the flash - 16mb is more than enough. Cheers, Will.
Re: New port, question about hidden partitions
On 8/3/07, Jacob Rau [EMAIL PROTECTED] wrote: I cannot see any place online where firmware files are available--this might mean bad news for me. I suppose there is probably a way to re-write the chip, even if it isn't inside the player. As far as I could see, there aren't any firmware updates for it online. Is there any method of upgrading the firmware mentioned in the manual (or in the firmware itself)? Without a way to upload your code, a rockbox port becomes much more difficult - you'd have to start searching for buffer overflows and the like. Where is a good source for datasheets? Should I be trying the manufacturer first? I've just been Googling like mad. If the manufacturer's website doesn't have the datasheet, you can occaisionally find them on sites dedicated to hosting datasheets. But yes, googling like mad helps. :)
Re: editing english.lang
Hi Daniel. Unfortunately making rockbox speak that particular piece of information is not possible simply by editing english.lang. However, if you tell me what type of MP3 player you are using, I could possibly make a customized build of Rockbox that would read out the time remaining. Will. On 3/13/07, daniel dalton [EMAIL PROTECTED] wrote: Hi I want to make a few more things speak in my rockbox daily build. I want the time remaining of the battery to speak which is in the rockboxinfo screen and the size of the disk which is also in the rockbox info screen to speak. Does anyone know how I would go about doing this. Would I need to edit english.lang or something like that. Any help is greatly appreciated. Cheers Daniel Email [EMAIL PROTECTED] msn [EMAIL PROTECTED] skype daniel_3680 If you add me to skype or msn please send me an email telling me who you are.
Re: how to become developer
Hey there Alex, glad to hear you're interested. A good place to start would be to grab a copy of the rockbox CVS source and modify it to add the functions you like. Once you've done that you could make a patch and submit it to the rockbox patch tracker (http://www.rockbox.org/tracker/index.php?type=4) and hopefully somebody with CVS commit access will take a look at it and commit it. Cheers, Will. On 1/5/07, Alex Gerchanovsky [EMAIL PROTECTED] wrote: Hello! I have Toshiba Gigabeat F20 player and want to become Rockbox developer. So, I can add some features and make them available to all users. My main interest here is: - get Album art from id3 tags - add Alpine M-Bus CD changer interface (port Alpine CD Changer Emulator plugin to Gigabeat) - WPS - Some interface improvements --Alex
Re: Reviewers and committer for talkative RB
I've been advocating these patches on IRC, but I haven't actually gotten around to looking at them myself.I've made a point to actually compile a build with the splash screen enhancements, and I'll post back my thoughts once I've done this. Keep up the great work :)On 11/1/06, Paul Louden [EMAIL PROTECTED] wrote: Often what happens is that the developers who are capable of committing patches are just very busy people. They see a patch of interest, think I'll look through that later, when I have time and then proceed not to really have time for several days, by which time it has become lost in a pile of plenty of things to look at. One of the most helpful things you can do is to try to visit the IRC channel, and ask about specific patches and whether any of the developers can offer feedback as to whether anything is preventing your patch from inclusion. On 11/1/06, Stéphane Doyon [EMAIL PROTECTED] wrote: On Thu, 12 Oct 2006, Linus Nielsen Feltzing wrote:Anyway I'd like to work on some of that, in what little spare time I have:-). I just wanted to make sure there's no actual opposition to this sort of stuff. Absolutely not! We are delighted to have a coder that gives these things some attention.Thanks for all the responses I got on this thread. However, when I asked whether there was any interest for improved voice feedback, I should have asked whether there was any such interest AMONG DEVELOPERS :-). I havereceived almost no feedback to any of my patches. Is there anything I cando to change that?It would be motivating to get some of this stuff committed. P#6159 Add voice to roughly 100 splashe screens and yesno menusI'm pretty much satisfied with that one. It's nice to be told things likeDirectory buffer full, Really delete, Erase dynamic playlist?, etc...P#6171 Talking quick screenSeems to work fine.P#6138 Be more talkative in info menuPretty trivial stuff...P#6236 talk mp3 clip fallbackThis one did receive comments. I have rearranged the existing settings as suggested. Works for me.P#6237 Shorter hover delay for talk mp3 clipsFeedback and testing would be nice.P#6239 Lack of protection against reuse of p_thumbnail: tentative fixWorks for me. P#6240 Improved voice feedback in bookmark selectionWorks for me. Seems to me the most recent bookmarks list is pretty muchuseless for blind users without this.P#6271 Say something when entering an empty directory Just posted that one, seems to work.P#6188 Tracklock: audio book mode, avoid unintentional track skipsThat's the one preventing inadvertent track skips, such as for audiobooks. I'm never losing my place anymore. I would like to know what others think about the way it's done though. Also it's incomplete: missing keymappings and visual feedback.I also have this one that's not voice / accessibility related:P#6238 A few more intuitive key mappings for X5 Do these make sense?Thanks--Stéphane Doyon[EMAIL PROTECTED] http://pages.infinit.net/sdoyon/
Re: Reviewers and committer for talkative RB
I'm indifferent about the info screen talkativeness, but I really like the splash screen work, and a talking quick screen would be excellent.I really hope someone can find the time to look at these patches and commit them, I believe they would enhance the voice experience a significant amount. WillOn 10/12/06, Steve Moskovchenko [EMAIL PROTECTED] wrote: I remember some people talking about how they use RB becasue it isaccessiblein this way. So it would seem your efforts would beappreciated.On Wed, 2006-10-11 at 22:47 -0400, Stéphane Doyon wrote: If I may ask (candidly): how much interest is there for what I'm trying to do, which is to improve speech support and accessibility?
Re: how should the settings screen work?
I also vote #4On 9/26/06, Bluechip [EMAIL PROTECTED] wrote: First off, I would vote for the little-tick option-setHowever I would propose option 5RIGHT = move tick; ON = move+exit; LEFT = exit; OFF = cancel+exitbut unless people think ^that^ idea is kewl, I suppose it's a vote for user-configurable keys :(BCAt 11:10 26/09/2006, you wrote:ok, time to solve this once and for all...we have 3 (possibly 4) options on what each key should do in thesetings screen, and I would really like to get a final answer on how it should work.1) like it was before actions. left and right both accept the settingand exit, off cancels and on accepts2) like it is now, off and left both cancel and exit, right and on accept and exitthe next 2 options require lowlights patch which adds a little tickicon next to the currently selected option, but i cant find the linkand i dont tihnk its on FS :( (you can see a screenshot of what it looks like @ http://users.monash.edu.au/~jdgor1/screeny.bmp )3) on - move the tick (i.e change the selection) and say in thescreen, left/off exit the screen using whatever is the ticked option for the setting.4) LEFT cancels, RIGHT applies and backs out, SELECT applies and staysin the menu without any splashes at all?So, which option do we go for?OR, do we add an option to allow all 4 (or 3 or 2) of them and just argue about which shuold be default?
Re: Tetrox renamed to Rockblox, for trademark reasons
Oh well, I preferred the name Rockblox anyway :)It is a worry though, these increasing claims - how long will it be before one of the many users of the word Rockbox (or similar) come after us - or do we have some kind of immunity on that one?
Re: my next crazy idea... rework the menu system
On 8/23/06, Jonas H [EMAIL PROTECTED] wrote: Of course, in that case, people will be unable to change certain optionswithout having to use a computer. Maybe some sort of .cfg-file editorplugin could be created, which would then expose all available options (or maybe just the hidden ones).What, like the text editor plugin? BTW - I think the idea of shipping some options off to .cfg files is a fine idea.(again, sorry for continuing discussion of the tangent, but as Jonas said I don't have any basis forming an opinion)
Re: test
Test recieved.On 8/8/06, mat holton [EMAIL PROTECTED] wrote: test
Re: Feature freeze is lifted
I'm in full support of this decision. When feature freeze wasn't in effect there were a lot of really interesting and cool new things being added, and honestly, the most interesting thing that's happened in the CVS logs in the past week has been some kind of solitaire bugfix (I play solitaire a LOT). I hope the featurefreeze lifting doesn't cause too much trouble in the way of the 3.0 release, I'm looking forward to it, even if it is only the speech parts of the OS that are being fixed - a feature that I personally rarely use - having 3.0 I'm sure will give me a nice fuzzy feeling.Viva la rockbox! On 7/18/06, Björn Stenberg [EMAIL PROTECTED] wrote:Hi all.It is with mixed emotions I hereby announce that the feature freeze for 3.0 is now lifted -- without 3.0 having been released.We have been in freeze for over three months now. And we have indeed fixed many bugs, but we still have critical problems that prevent a 3.0 release. With summer in full swing and many core developers away on well-deserved holidays, it is impropable that these problems will be fixed before august, which would mean four months of freeze. A third of a year. That's not fun.I, Linus and Daniel discussed the freeze over lunch today and decided that in this difficult situation, we need to focus on the core values: Rockbox is about having fun. Being in freeze with no clear end in sight is a drain on morale and enthusiasm, which is not how we want Rockbox to feel. So we decided to end the freeze now and unlock the doors to creativity and programming joy. At best, we'll get lots of new improvements and exciting features without much negative impact. At worst, the changes will destabilize the code base severely and push the prospect of a 3.0 release even further into the future than today. In order to hedge our bets, we have set a tag in CVS which we can return to and branch from if we later fix the critical bugs and would like to release Rockbox in today's state. We still think the freeze was the right decision. We just weren't able to reach the state we wanted to, in the time we wanted to. And rather than stubbornly repeating we freeze until release, we adapt to the current reality and unfreeze. Gentlemen, start your compilers.--Björn
Re: New Forum Proposal
Hi Paul.I think the forums probably could do with a clean up, and most of the stuff you have suggested rings true, but I think the fact that you've designated sections to bug reporting and feature requests are not needed. I feel that it makes the bugs/feature requests far harder to track, as you'd have two places to keep track of everything - I'd bet that people would either put the bug only in Flyspray or only in the forums, rarely both. Perhaps if we kept the categories for bugs and feature requests, but only have a locked thread linking users to Flyspray should be created to help point users wishing to report a bug in the right direction.Just my thoughts, feel free to reject them as harshly as you please :) Will.
Re: New Forum Proposal
Hrm, you make many valid points Paul, especially on the fact that Flyspray doesn't really attract the same level of input as the forum does. I guess as long as the issues that are reported on the forums were transferred to flyspray once they were confirmed and discussed, it would keep everything in one place. This would really help developers, they'd be able to just look at flyspray, rather than wade through the forums to find bugs that need fixing, and it might also cut a lot of the crap that's on flyspray at the moment, depending on how it's implemented. Thanks for the work Paul.
Re: Ladies and gentlemen, we have SOUND!
I think we can say that you hold the current record for fastest rockboxing at the moment.Now, who wants to break it!And congratulations!Will.On 3/31/06, Manuel Dejonghe [EMAIL PROTECTED] wrote: On 3/30/06, Jens Arnold [EMAIL PROTECTED] wrote: Today I finally received my newest rockboxable device - an iPod mini, 2nd generation. And thanks to many parts already being prepared in rockbox and the sources of the friendly ipodlinux project, I am glad to announce that less than 12 hours later it already plays music :-)gosh, congratulations.time flies when you're having fun, isn't it ? Drink one on that, will you ?~lImbus
Re: Signing off.
Bluechip, as far as I see, you're wasting your time here.You clearly stand nothing to gain, as you have made it completely clear that you aren't going to reveal your real name, and the rockbox team have made it just as clear that this is a requirement for the acceptance of your code. The only reason there has been such a big debate about this is because you have obviously been spending all your time somehow trying to bring the rockbox three (as you put it) down, with these constant and completely ineffective replies. It's proving pointless and it makes you look silly. Use your time more effectively and take some advice from the people that have already contributed - take your code to an offshoot project and enjoy yourself.Will.On 3/16/06, Bluechip [EMAIL PROTECTED] wrote: How exactly is it unlicenced?http://www.mp3licensing.com/royalty/Björn pointed this out. You refused to respond (to that too). Well, first off, I have already apologised fornot reading the full thread-to-date before I replied.The above was in reply to a post made BEFORE Bjorn's post.Secondly, I did not see any questions in Bjorns post or any points which appeared to require a rebuttal.He knows it is thorny and repulsive, andbecause of his take on European SoftwarePatents he believes we are in the clear If there is anything specific you want my inputon, please pose it to me in the form of a question.If not, then as far as I see it, Rockbox's hasopined formally with 'we don't think we'rebreaching Thompson/Fraunhofer's license' ...and at that point, you need someone with far morelegal experience than I have to help you out.they haven't sued anyone yetThen The Rockbox-Three are probably safe then :) Why would anyone sue one of us even if this was true?I remember saying that when I was told that mypen-name could cause legal trouble for you [collective].So I say, whatever your [collective] reasons were then, will probably guide you to the answer this time.Rockbox is not a formal organization of any kindand I don't see how one of us is personallyresponsible for Rockbox as a whole. Possibly we could be blamed for distributing it, yes, butthen I'd guess they'd sue the admins or the owner of the server(s).Is that why Linus' name has been removed from internic's database?The Rockbox-Three were VERY clear about their stance on Trademark infringement when theyinsisted on changing the name of the Tetrisplugin. I use this example merely to highlightthe duality within the Rockbox 'code of conduct' We are clear and that has not changed. Wehaven't been made aware of any trademarkinfringements to my knowledge. Now when you'vebrought it up and I checked around I can only_assume_ that you are talking about our use of the name 'Bejeweled'. Is that so, or can youplease clarify? You speak in vague terms.Indeed, Bejeweled was the one that leapt out atme.But as you also have focussed on this, Iguess I have been misinformed (by a Nokia games coder at Vodafone) that Popcap own the trademark on the name. As I said before, The big-3 (ala Rockbox.org) have claimed that their rockbox.org is a domain and there are lots ofmore people than three that support and producewhat we do in the Rockbox project and thatresult is hosted on the servers using that domain name. In context of the post to which I was replying,you had been collectively referred to asrockbox.org, hence my placing it inparenthesis, so the chap to whom I was replying understood my reference. Feel free to read up on the subject if you wishto understand fully, most correspondence is publicly available :)...Again, aimed at the guy to whom I was replying,who seemed to be lacking a large chunk of info. I have no interest in provinganything.Merely highlighting parts of realitywhich have been carefully shaded by The Rockbox-Three.The info is publicly available and yet carefully shaded? (Not that I even understand what infoyou're talking about in either of these cases.)Well, in the first case, it was in reply to theoriginal post which you have snipped.In the second case, the incongruitites created by The Rockbox-Three are generally eschewed, not inwhat HAS been said, but more in what has NOT been said.It's just another requirement, along the linesof 'rockbox is written in C and assembly' and 'comments start with /* not //'. The world is full of requirements.Yes, that's another fine example of arequirement which is only relevant when TheRockbox-Three say it is relevant.Well spotted!Did you pick the same example as me?Do you actually think that only we three do allCVS commits, code reviews and enforce the source code rules?No, but then you are being deliberately silly No, Jens seems to do most of the work thereNo, but you should enforce ALL your rules with equal vigourAre you aware of what amounts of code we have?YesAre you aware of the amounts of contributions and submissions from people we get?YesDo you understand how much time we already spend on this?Yes.In fact I honestly wonder how you guys earnmoney.My best
