Support and General Use > Theming and Appearance Customization
Anymore themes coming for Sansa C200?
oayz:
Thanks guys (girls? :-) for replies. I'm pretty sure that from now on I'll follow new licensing rules (I own e250 now). I may even be able to dig out origins on my c240 WPS (my own comment says GFX and Nature - whatever it means :-)
Regarding backward compatability - it not a "must thing" but should not be taken lightly either. I doubt battery life is affected and code size increase is probably minor. In case BWC can not be mainted we should have automated scripts (plug-in?) to go through all WPSs and update syntax. Just render obsolete bunch of WPS used by many people is not a good practice. Using %pb is an example - instead of appending new parameters to the end the whole syntax was reshufled.
BTW, should be add some notation of WPS ID so developers can mark what version of RB WPS is designed for? This tag can later be used by automatic update scripts.
Llorean:
Are you volunteering to write a plug-in or script to update WPSes? Things happen because someone does them, not because someone says "someone ought to do this."
Battery life probably won't be affected the first time backwards compatibility is preserved, but in time things adds up. And code size/complexity means it's harder for people to work on the code, and that is a bad thing.
The %pb tag was reshuffled, I believe, because the original tag was badly designed (because things were just added on as it got more complex) and its syntax was quite different from other tags that used coordinates. Preserving compatibility is okay, but it's much easier for people to learn to use the syntax if several tags work in similar ways.
oayz:
--- Quote from: Llorean on January 10, 2009, 03:52:26 PM ---Are you volunteering to write a plug-in or script to update WPSes? Things happen because someone does them, not because someone says "someone ought to do this."
--- End quote ---
I disagree - in many cases great ideas come from people who can't code themselves and I never implied "ought to" - just "may be willing to".
Just to make things clear - I'm not professional programmer. There are people over there who write better code 10x faster. Having said that I'd like to help RB project - so
- let's start with script (well DOS based command line executable written in C). This later can be converted to plug-in
- we do need WPS version and list of incremental differencies. Where are this information will come from?
- who will be my contact in case I have questions (email or PM is preferred)
Have you worked for army? You'd be a great recruter :-)
Febs:
--- Quote from: oayz on January 11, 2009, 02:04:33 PM ---
--- Quote from: Llorean on January 10, 2009, 03:52:26 PM ---Are you volunteering to write a plug-in or script to update WPSes? Things happen because someone does them, not because someone says "someone ought to do this."
--- End quote ---
I disagree - in many cases great ideas come from people who can't code themselves and I never implied "ought to" - just "may be willing to".
--- End quote ---
What exactly are you disagreeing with? We have a feature request forum for ideas from people who can't code themselves. But that doesn't change the fact that things only happen when someone decides to code them.
--- Quote ---- who will be my contact in case I have questions (email or PM is preferred)
--- End quote ---
We have a "Getting Started and Compiling" forum that is available for coding-related questions, an IRC channel, and a developer's mailing list.
oayz:
Fine, we all understand that. I'm out - better work than talk.
Navigation
[0] Message Index
[*] Previous page
Go to full version