Anymore themes coming for Sansa C200?

[shoobey]

I have all the themes for it, there are only about 5 (one of them doesn't work, instead of a download link there is just code posted).   Just wondering if anyone thinks more themes will be uploaded eventually?  They are all really good but I constantly change the theme around so I like having a lot

[karashata]

You could always try to make your own theme, there's a guide on the Wiki here, as well as the CustomWPS page with all of the WPS tags you can use to display various information...

I'm currently working on a new theme I hope to get into SVN some day as well, you can find it here (you'll need to scroll down until you see the c200 port.)

[oayz]

Try mine - it's simple and informative. I have hard time uploading it to gallery and it probably has issues with copyright - basically cut and paste from other WPSs. This is a great oppprtunity for me to thank people who may find pices of their work here.

Link removed - BigBambi

Hope you will have no problems downloading - it's a 2 step process, look for "download" at the top of the pages.

Enjoy!

[AlexP]

If it has trouble with copyright, then please do not post it here.  If you change it so that it does not, then feel free to re-add the link.

[oayz]

Got it, thanks.  Honestly I think that tweaking WPS's should not be such big deal but if this is a rule - so be it. Hussling with copyright is way over my head.

PM always works ;-)

[Multiplex]

If it is a cut&paste from other WPSs that has permissive licences then it won't be a problem - that is presumably why everyone is trying to get the WPSs appropriately licensed.

[Chronon]

oayz: You can read the "Importance of proper theme licensing" sticky for more info.

[oayz]

Chronon: I understand and comply.

On the other hand I'm not a lawyer and have nor time neither desire to trace origins of the WPS's I've being using to compose mine. I just use it, improve it and let other people do the same with my work. If this is not acceptable I will be the only user of my work

On personal note I believe this copyright and licensing thing is too much of the deal for WPS development. That's why number of available WPS went down. Shouldn't it be more like "presumption of innocence" case where it's OK to post/modify unless complain is received? Next step - I would have to check every word of my post for plagiarism :-)

Separate comment on having WPS stop working with new releases of RB. Why there is no backward compatibility? This %pb change just cracks me - it clearly could be done backward compatible yet this change resulted in 50% WPS down. And even if feature is not supported anymore WPS parser skip it, instead it just reverts to altogether.

Anyway, sorry for this runt - it's my 2c and can be simply ignored if you think it doesn’t make sense

[Chronon]

The licensing requirements are meant to make it easier to share resources, not harder.  If all of the themes in our wiki have permissive licenses then you don't have to worry about whether or not it's possible to reuse some element from a theme you like.  This is all mentioned in the sticky.

I am not a lawyer either, but that's not how copyright works.  Unless you are granted rights specifically, then a work is copyright with all rights reserved.  By asking users to license their themes in a certain way we ensure that it's okay to share and borrow from them.  The spirit of open source is to grant rights explicitly, not to steal things under the assumption that no one will care.  These licensing guidelines appear completely consistent with the ideals of free software to me.

Another reason to prefer permissive licensing -- it ensures that anyone can post a fixed version of a theme in the event that syntax changes break themes at some point in the future.

Here is link to the currently preferred license:

[Llorean]

As to backward compatibility:

If we leave every old tag in, the parser gets more complex. It makes it harder to develop, wastes more battery and RAM, and means sometimes we need to have duplicate tags.

Simply put, it makes no sense to have backward compatibility when people can just fix their themes. It would be nice, but it's more beneficial to keep things lean.

Meanwhile ignoring tags is also a very bad idea. What's the point in displaying a half-working WPS? It's still broken. This way it's just very clearly broken so you notice immediately.

[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]

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."

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]

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."

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".

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.

-  who will be my contact in case I have questions (email or PM is preferred)

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.