Splash screen for Personal JUCE 5 license?


#23

Okay, fine :slight_smile:


#25

lol relying on user morality, eh? good luck with that :stuck_out_tongue:


#26

Surely users can remove the splash screen without violating the terms of the GPL (next question: is JUCE still going to offered free under the GNU public license).

I’m all for crediting JUCE in my software, and I do every chance I get. If some of our applications already feature a splash screen, is it be Ok for us to simply modify it so that it states quite clearly, ‘made with JUCE’ or whatever text is required? As big or small as you like, along with your logo. Or must we now show 2 splash screens if we wish to show our own?


#27

I’ll trade having to open source my code for a splash screen! :stuck_out_tongue:

But in all seriousness, will there be any new functionality in the ProJucer? I know some components aren’t fully supported in the ProJucer and some componets can’t be implemented through it, has anything in this field been added?


#28

WTF WTF WTF ???

Is this Unity or something like it???

OMG OMG OMG

mandatory splash screen?

  • We will keep paying, this is not about the money, we will continue paying the PRO license
  • Who think this was a good idea?
  • Cause this is the stupidest idea ever

Im sorry but im super pissed about this,

How about the DSP module? (Vaporware)
How about the RTAS?
How about the Android Video and Native Views component?

  • And you implement a mandatory splash screen?
    This will hurt performance im sure

Do you have a phone where we can talk about this?

CAn we just buy JUCE from ROLI and make it once RAWMATERIALSOFTWARE <-ill put some 250k on this easily right now

This just sucks


#29

In case I wasn’t clear, I’m Ok with the splash screen. But I would rather plug JUCE on my own splash screen according to their requirements than have to show two splash screens crediting those who contributed to the development of my applications.


#30

OMG OMG OMG, what a lot of crazy over-reaction and panic!

Please ignore the FUD that the post title suggests - the splash screen is NOT “mandatory”!

It’s a new, additional option that some users may want to choose.

Up until now, if you didn’t want to use the GPL and you didn’t want to pay the license fee, then you simply couldn’t release a closed-source product with JUCE.

This just provides a new option that lets people do that. It does not replace or affect the GPL in any way. A GPL app does not need a splash screen, and it’s easy to disable it. And anyone who’s already a paying licensee won’t be affected by this at all.

But we get many emails from people who want to launch a closed-source product but have no budget, and this is a way for them to do that.

The rest of you, calm down and carry on!


JUCE 5 Licensing - What We Know [Community Edition]
#31

So, users of the free model can release apps that are closed source, as long as they display the splash screen?


#32

Perhaps a better planning of the newsletter and the overall communication will avoid this mess in the future.

A nice pinned post with all the details you want to disclose about the new version would have helped.


#33

There seems to be conflicting information, regarding AAX, between the newsletter and the website version (Apologies for the volume setting splash):


#34

Fair enough, now that it’s clearer I’ve removed the word from the title.

The possibility of releasing closed source products even for developers with no budget is certainly welcome.

As mentioned by @Rory above, would you also consider slightly different means for showing the “Made with JUCE” claim? The observations and questions he made seem pretty reasonable to me.

I’ll add to that that, for someone not willing to display it in form of a splash screen, permanently adding a “badge” of specified minimum size to the GUI of the applicaton may be a more attractive alternative, possibly even more effective if said badge is a clickable “link” that launches the browser to “www.juce.com


#35

The correct information is the one in the second table, with 4 columns, so AAX is included.

See: AAX support will be included in Indie for JUCE 5


#36

I think the splash screen is better than a badge as it might encourage more users to buy an indie license to help contribute and fund further development… i think the ability to release products without releasing your source is a great way to encourage people to develop without any up front costs but they have to buy a license to stop annoying people once they’ve made a bit of cash…

just my thoughts


#37

Wow, so developers can release closed source apps just by displaying a splash screen? That’s quite generous. All the same, I’m more than happy to plug JUCE in my splash screens :wink:


#38

Ah, fair enough. I think your point is correct and that a little bit of annoyance is needed to promote the upgrade to one of the paid licenses.

Still, it would be nice if ROLI could accept the merge of the information in their splash screen within another splash screen if the app already needs one, as @Rory proposed.


#39

That seems to be it, but only for developers or companies which make less than $50k per year.


#40

How is this splash screen supposed to work? Each time the plugin gui is displayed or once per daw session / only first time the gui is openend?


#41

So far, this sounds great:

  1. free live engine for all
  2. free closed source projects (with splash screen and under 50k)

Could we get some info on the “user interfaces” and maybe any improvements with components in the ProJucer?


#42

i love you jules, sorry about that, btw i need your address want to send you a present


#43

That addresses my last concern. I’ve considered it thoroughly and IMO these are fantastic licensing changes (after the AAX inclusion) that are really fair for all brackets of developers. I am more pumped than ever for the future of JUCE!

Though, I say that from the POV of a student who uses JUCE extensively for open source projects and shoves it on his co-workers, I haven’t shipped anything commercially…