USB certainly springs to mind (mainly because I'm currently looking into that) :)
PDF rendering, printers support ?
Going a little crazy here, but: Support for 3D Kits, like the Oculus Rift?
Was rather hoping that 10 people would all pop up and request the same thing, but thanks for your requests!
Hmmm.. maybe you could make a poll? Where we can choose from a few selected options?
It's all stuff that we have in our backlog already - maybe when we've got the summit finished and are planning the priorities for next year, we'll poll you guys to help decide!
Some of these may be out of ignorance i.e. things I have struggled with rather than something lacking in JUCE but if so then more documentation to cover them instead:
- The Projucer will help with tweaking the UI but more comprehensive layout classes to start off in the right way.
- Improved support for Active X controls - I couldn't get MFC Active X controls with graphics to work properly in JUCE.
- Adding support for standard C++ libraries like VTK/ITK, OpenCV directly from the Projucer rather than having to mess with CMake.
- Make application commands easier to understand and use.
- Make localisation easier.
- I love ValueTrees but they could be made easier to use in a more object based fashion.
- Any enhancements to help make plotters, graphs to display data.
- Application properties are great for simple things but if you want to allow the user to edit them and choose say one out of three options it is not easy. Also you lose the type so automated editing forms are hard to build.
+1, especially to printer support!
the 2nd time a licensing thread gets turned into something else... Jules, we can see what you're up to! ;)
Wasn't deliberate, but will note down that trick for future reference..!
1 Like
This. Currently waiting to hear whether there will be any additional licensing options before considering other libraries, not feature requests. :p
Our intention was to keep it cheap for the one-person indie outfits, and offer more expensive support packages that will suit bigger companies with bigger budgets.
I think that a revenue-based licensing model fits better with this goal. For example, Unity 3D Personal is free for everyone as long as their yearly revenue is less than US$100,000. Looks like this may be a good reference for differentiating indie developers from bigger companies.
This is the actual excerpt from the Unity Personal (free) license:
----
Except for a thirty (30) day trial period, Unity Personal (including the iOS and Android platform deployment options) may not be used by:
- a Commercial Entity that has either: (a) reached annual gross revenues in excess of US$100,000, or (b) raised funds (including but not limited to crowdfunding) in excess of US$100,000, in each case during the most recently completed fiscal year;
- a Non-Commercial Entity with a total annual budget in excess of US$100,000 (for the entire Non-Commercial Entity (not just a department)) for the most recently completed fiscal year; or
- an individual (not acting on behalf of a Legal Entity) or a Sole Proprietor that has reached annual gross revenues in excess of US$100,000 from its use of the Unity Software during the most recently completed fiscal year, which does not include any income earned by that individual which is unrelated to its use of the Unity Software.
----
You may consider offering an Indie license much in the style of the pre-V4 model, but applying the above restrictions.
I personally have no problem with the desktop licenses. Its the mobile licenses that went from... oh... sure, i'll license them in case I need them, to... nope... i'll figure something else out if it comes up. I was at the Roli checkout on day one ready to support without question but when it all added up, it made me dig up my license agreement and because 4 was included, i'll take a wait and see. Unfortunate, i've never been cynical about JUCE, but something has changed.
Considering there isn't(as yet[and I haven't looked in a while]) any gesture swiping for table views for scrolling, or a mouth dropping implementation that goes..yes... this is almost as good as native controls. Its hard to justify spending the additional licenses. Maybe its just early days, and after a while the additional license costs will be justified, but to me, its still too soon. When I compare how a test app feels on Android/iOS using Juce or Native(even something like Appcellerator), its not really a contest(at the moment)
As for requests...I would like to see a 3d (4x4) Matrix and associated AffineTransform. That'd be pretty easy, and would allow some neat transition effects. (iOS multitasking window where they are slightly rotated away).
Hey hey, just chiming in as a freelance Juce dev. Wow, the new mobile license prices have sky-rocketed. I've been in talks with a new startup (Kickstarter funded, limited cash) that are making a new instrument and want a cross-platform companion app. After the recent price-hike they are much less interested in using Juce, thus much less interested in hiring me. Which sucks.
999 for the desktop licence is a good price considering the features. But 2 grand for Android and iOS support is actually outrageous, when the current feature set is so limited. Just compare the feature set of mobile Juce to other cross-platform frameworks at similar pricing. Juce has no support for in-app purchases, camera access, bluetooth, gestures, native UI, easy responsive layout stuff, services/toasts/view-switching/you-name-it. At the moment, mobile Juce is mostly just desktop Juce squeezed into phone, so it seems unfair to charge so much. Especially to charge separately for iOS and Android when most mobile devs would have to buy both to get the advertised cross-platformness.
I appeciate the work you guys have put into Juce, including mobile support. But the simple fact is that $2000 is way too expensive when developers still have to implement a lot of core features themselves.
Rob
I completely agree.
+1
Ever heard of the expression "boiling the frog" ?
Could you please give us the upgrade prices to the Professional license?
- for someone that has a v3 ?
- for someone that has a v3 that is including v4.x?
- from an indie license to a professional one?
This is exactly what I've been waiting for to start using JUCE.
The previous per product licensing was a killer, and having the option to pay monthly helpd out.
The licensing page is a bit misleading in not mentioning that there are separate (and equally expensive) licenses for iOS and for Android.
That's the exact position I'm in. The price for the desktop version makes it an easy decision, but I can't justify spending an additional 200% just to create a simple tie-in mobile app.