My list:
Generally I feel Defold has already a lot to offer and would benefit from a bugfix/polish pass:
I also really like native extensions and would love to see it done for all platforms.
It may even help with opening a bit more the build process as at the moment it’s very difficult to tweak the final bundle.For instance, creating android app with a proper splashscreen (using a fake startup activity) or removing parts that are not used.
Native extensions are pretty awesome, I’m looking forward to having them for the other PC platforms, and to see Editor 2 catch up with Editor 1 some day (wouldn’t mind hearing more progress reports/“editor 2 release notes”).
+1 also for . . .
I just started using the curve editor recently. It’s pretty sweet and I don’t know why it’s not usable for anything other than particles!
Box2D was one of the reasons I decided to try Defold, so I was a bit disappointed to see how little of it is exposed. What about CCD, bodies with multiple fixtures, and joints, not to mention editor support for polygon collision shapes? I know not a lot of people want to use that stuff, but it’s already there, right?
Oh, and polygon sprites is a good feature, those can be a huge optimization.
Darn, too many features to want! Of course, focusing on bugs instead of feature creep is never a bad idea . . .
Click watch on the Defold Editor 2 Issues git to get e-mail updates https://github.com/defold/editor2-issues
Make sure you have e-mails enabled for watching too https://github.com/settings/notifications
Somehow this nice thread hasn’t been updated recently. I am improving this immediately on a generic scale. Then I’ll run around the office and inspire people share their thoughts on things that they’re working on.
So we’ve shipped FB Gameroom, Live Updates, Native Extensions, Sticky Iron and Editor 2 to beta. Yay! but what’s next for Defold?
Makes sense?
1 Need more HTML5 performance - experimental WebAssembly support?
4 Stripping physics is gooooood!
Other: improving dashboard statistic page?
AND MAIN: please make stable Steam integrations … achivments + liderboards for start
I think to early kill Editor1. Its very stable, each time when i try Editor 2 i return back to Editor1.
I extremely like this list!
Would be great if this list contain something about sound system improvements - I am sure that many users dream about it.
This list is cool!
Also I would be happy to build projects with native extensions locally without build server!
This should be a community effort. A Steam integration makes sense to do in collaboration with a team that is releasing on Steam. I’d be happy to help, but since a Steam integration is quite a bit of work I don’t want to do it unless there’s actually someone planning to use it.
Fully agreed) My puzzle appear at steam in next year so later i start to work with Steam integration and all around problems) Thx.
Another one from slack chat: make build status window more informant - for example display build stage (NE, texture packing, js compile etc), make button for instantly stop building bundle process (not easy issue? right?), etc. Also good to do local build without run (sorry i am on Editor1 maybe such option present in Editor2)
Feature request: why each new created collection has Name property set to “default”? This only disturb novice user when he working with routing … and users later rename it. Maybe better to set Name as a name collection object? Of course you need support this property when do collection “rename refactoring”. Sorry if I missed something …
Interesting choice for the physics!
Even though it makes sense to make the engine more modular or even to replace the physics system completely, I always though about its tight integration more like a plus.
There’s so much workflow gain and easy of use into having it integrated that for me it beats the benefits of having it separate (think about creating collision shapes or setting limits, etc)
Can you elaborate a bit more?
Yeah. More teasers. We had an all-team workshop today on the product development. And while there’s much more to it, and we’ll work more on it all, here’s something for the roadmap-teasers thread:
There’s probably more to tease about =]
I hope the Editor 2 text editor will get some love at some point. I’ve been using Atom instead, which is great, but the built-in editor has some things that it can’t match: hot reload, autocomplete for library modules, no need to switch applications. Unfortunately, even without any addons, Atom is waaay nicer to use, and since I spend 90% of my time editing text, the built-in editor just isn’t worth using.
You can start holding your breath soon…
here’s something from the team offsite:
I’d inspire those responsible for the given teasers come in and maybe talk a bit more here =]
The list looks really good. Regarding point 3, what I’d personally love to see is tracks support for Spine. We’ll soon be implementing a cutscene system with Spine and having tracks would be amazing. (Not to say it can’t be worked around, but it would be easier for the animator to not have to split his layers)
