All excellent questions! I want to know too... ! David?
Not sure if this should go in here or the Skins forum, but since I'm not actually making a CF skin, I figure here is best.
Put simply, What is FluxMedia's stance on people copying CFs Onyn WS look and feel for their own (skinnable) applications and plugins (possibly to the extent of extracting the PNGs and changing the text on them etc.)
I ask because presumably if someone is developing a CF plugin then providing it with an Onyx WS skin is the obvious thing to do so that it looks like part of CF. I'm sure David wouldn't have a problem with people doing this.
but what if I make an app that's designed to just be embedded into any front end. Somthing that I plan to do because I can't get my head around .net and the CF SDK and also because my apps will likely be for relatively obscure purposes that only certain people will want, and I don't want to tie them into a specific front end or operating system.
I use CF and I'll be wanting an Onys WS skin for my app. I really can't be bothered to make an alternative skin, so if someone chooses to use my app with Mobile Impact then they can make there own MI-like skin.
But the fact remains that I'll have ripped off David's copyrighted work and distributed it with my own software that may not end up being used with CF.
... can I distribute my app with an Onyx WS skin
... can I make an Onyx WS skin for it and post it separately, perhaps only in the Skins subforum
... can I make an Onyx WS skin, but have it use some PNG files directly from the Centrafuse folder rather than bundling them with the app
... or can I not make an Onyx WS skin at all?
There is no problem using the look and feel of the current Centrafuse skin for CF plugins being written. A PSD with sample backgrounds, headers, and buttons is most likely going to be added to the SDK download to make it easier...
This is so Centrafuse plugins can fully integrate seemlessly into the current version.
They should not be used for stand alone applications.
Too bad. This is going to have the following effect:Originally Posted by veetid
People developing general purpose apps for carputer frontends will not create a skin to match CF. They are not allowed. So they will effectively considfer CF out of the scope of their frontend testing. hence, it might not even work correctly in CF (not to mention will look awful if no CF skin is provided).
I for one love the idea of having CF plugins, and prefer them over generic apps, but I fully understand and support this community's developers position, when they decide that they will put time and effort against a piece of software that everyone can enjoy, and create a frontend-agnostic application.
Lastly, I don't really understand what FluxMedia fears about an app distributed with a CF-like skin. Its not like someone will use RR and integrate a CF skin within their app. That would make no sense, and here again would look awful.
This can only benefit the CF community.
Why not? The RR community is already "borrowing" graphics from CF skins..Originally Posted by justintime
Exactly and without permission... If things like this would not have happened and people would have asked permission, then our stance might be different...Originally Posted by tj!2k4
All the graphics are trademarked and some even registered trademarks, not to mention multiple copyrights with some features patent pending...
Most plugins up to this point, Mappoint, Calc, and others, asked permission before using our graphics, but again we don't really have a problem when it is a CF plugin...
We look at external applications as temporary unproffesional solution that is in place simply since their is not currently a plugin for everything yet...
And THAT is something that needs to be addressed. Using a CF skin for another frontend's main layout is a no no, but that is different....Originally Posted by tj!2k4
I'm not saying it will never be allowed, but permission must be asked, case by case... As for writing a CFPlugin you will simply just be able too...Originally Posted by justintime
Wow... you see that as unprofessional? I hope you're kidding David! It might not be the 'best way' to integrate an app, but to consider it an unprofessional approach?Originally Posted by veetid
With this stance, I can see a new breed of CF-haters starting to rise. I'm not amongst them of course. I do hate to think that by adopting CF as my frontend, I will feel isolated from all the other goodies out there.
I was an avid Apple user for almost 20 years, and this exact attitude was what drew me away from that platform a few years ago... I was in fact an active MacOS Classic / Macos X developer back then, but I had enough of it!
People can do it all day long, end users working with the Retail version... I'm just saying from a distributor standpoint it is, very much so, considered unprofessional... Any distributor needing custom functionality will have a CF plugin designed and built for them before they pre-install and integrate on hardware they sell...Originally Posted by justintime
Now some external applications that are designed to look like Centrafuse and our touch-screen friendly, those are not that bad... I am mainly speaking of embedding external windows applications that require mice and keyboards...