| Home | Forums | Register | FAQ | Search | Today's Posts | Mark Forums Read |
|
Welcome to the misticriver forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact us. |
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
I want to suggest something...
Rockbox is clearly evolved this last month a lot... and the more it evolves the more difficult it is to code it and upgrade it because of really old segments of code regarding Char-Based-LCD players... my suggestion is to disconnect those players from the rockbox project to another project which will be their's and it'll give us (the programmers) a lot of freedom of developing wide-support plugins and pathces The "Char-Based-LCD players" are a lost cause and all who have one should advance to this century... take my words seriously, think about it and say what you think here... thanks, eli_sherer. [EDIT] ofcourse future codec improvments will be implemented for both projects (Bitmaps and Char-Based)[/EDIT]
__________________
|
|
|||
|
I think that what you suggest is non-beneficial to the cause of rockbox... Rockbox was originally designed to allow people to use their DAP longer, by adding more up-to-date features and fixing problems that the original companies abandoned... Removing text-based players would defeat the purpose of Rockbox.
Do you suggest they remove Monochrome support too? Oh, wait, that would kill the H1xx series, as well as all the archos pojects it supports... What about any player with less buttons than an iRiver? That would save a lot of button code semantics changes.... oh, wait, that'll kill their IPod porting effort... Sorry - What you suggest, while practical for iRiver, would not be practical for Rockbox. We are the ones lucky enough to have our DAPs supported by their cross-platform firmware. We do not dictate how they develop their cross-platform abilities. |
|
|||
|
Also here isnt the place to be requesting such things www.rockbox.org is. To make things worse I agree with FS, what you suggest may make your life easier but in turn will make the guys at RBs lives harder, why should they make things hard for themselves when in the end it is only a few 100 people that are not happy with it. The minds of the masses here will win out. ie several thousand users happy, a few 100 programmers unhappy and several RB devs happy. It is a battle of numbers that cant be won.
A |
|
|||
|
IRC INFO(if you dont already know):
server is irc.freenode.net , chanel is #Rockbox if you have mIRC, you can type this in... /server -m irc.freenode.net and that will take you to the server connection window.... and then type in #rockbox into the newly created window, and when you connect, you will goto the rockbox chat.
__________________
|
|
|||
|
Quote:
Apart from all that, I disagree with the conclusion that the support for charcell LCD players hamper the development on and for more powerful-LCD-equipped players. I'll also second the comments about this being a totally wrong place to suggest anything to the Rockbox dev team. The rockbox development mailing list is the single best place for something like this. And you should be prepared with a busload of arguments for your cause, since I suspect this idea is gonna face some heavy resistance.
__________________
Your grumpy Rockbox hacker - http://www.rockbox.org/ |
|
|||
|
We are 39 people with CVS commit rights in the Rockbox project. Linus sure is one skilled developer, but he has no (and wouldn't want no) veto rights and neither does anyone else.
Sure we can listen to what Linus says and it is often both fun and educating, but nothing would be done on this topic until a proper suggestion with a technical motivation has been posted to the dev list and the outcome from the following discussion would say "remove". I for one would vote against it unless some pretty strong arguments are presented that so far haven't popped up.
__________________
Your grumpy Rockbox hacker - http://www.rockbox.org/ |
|
|||
|
Eli, I think that what Jens did with the volume/clipping issue worked fairly well. He discussed it at various times on the IRC list to get opinions and flesh out ideas about how things could work, and then presented a complete proposal to the developers' mailing list. Having discussion on IRC before making the proposal gave him some insight into some of the disparate views on the subject and helped him tailor his proposal to make it more acceptable to a number of people who would otherwise have disagreed. You might want to consider doing something similar.
Whatever happens with this issue, thanks for the work that you have put into the project so far. Your plug-ins have looked great, and I am looking forward to seeing what you can do with respect to the interface/WPS. |