Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Sep 16 2018 06:53
    underscorediscovery closed #69
  • Sep 15 2018 18:02
    darmie opened #69
  • Aug 22 2018 13:00
    darmie opened #68
  • Jul 10 2018 15:44
    darmie opened #67
  • Jul 07 2018 17:44
    darmie closed #103
  • Jul 07 2018 06:23
    darmie opened #103
  • Mar 27 2018 18:22

    underscorediscovery on master

    Removed some trailing whitespac… Made the cpp char* to ::String … Merge pull request #102 from 96… (compare)

  • Mar 27 2018 18:22
    underscorediscovery closed #102
  • Mar 27 2018 18:22
    underscorediscovery edited #102
  • Mar 27 2018 16:32
    96AA48 opened #102
  • Feb 09 2018 19:25

    underscorediscovery on android-open-url

    JNI; fix inline statics (compare)

  • Feb 09 2018 15:06

    underscorediscovery on android-open-url

    android; block in url_open help… (compare)

  • Feb 09 2018 14:53

    underscorediscovery on master

    android; JNI; import wip JNI api (compare)

  • Sep 29 2017 20:51

    underscorediscovery on master

    Audio; fix leak; detach audio b… AudioSource; add unique id, ens… (compare)

  • Sep 29 2017 18:44

    underscorediscovery on master

    Audio; move logging back to deb… (compare)

  • Sep 29 2017 18:38

    underscorediscovery on master

    audio; more destroy cleanup fix… (compare)

  • Sep 29 2017 05:43

    underscorediscovery on master

    audio; minor fixes and safe gua… (compare)

  • Sep 08 2017 13:55

    underscorediscovery on master

    audio; suspend on system wide f… (compare)

  • Aug 08 2017 02:29
    darmie closed #96
  • Aug 01 2017 15:16
    jeremyfa opened #101
Sven Bergström
@underscorediscovery
I like yaml but I like json style more
as with any choice any where, there's always a million options :) the one I chose is the one I wanted to use
the new version has more deviation to make the conditionals a lot cleaner
Anton
@outkine
that totally makes sense - the reason I was curious is because I didn't know if you implemented your own parser too and if so why all the work
Sven Bergström
@underscorediscovery
ah, right, well writing a parser isn't actually a lot of work typically, esp not for simple stuff like json
(well, that is, not strict json RFC, cos that's wild)
Anton
@outkine
even with all the optimization?
Sven Bergström
@underscorediscovery
in the current I had used node.js, and therefore just used an "unstrict json" parser
Anton
@outkine
oh ok that makes it easy then
almost cheating :)
Sven Bergström
@underscorediscovery
yea, pretty much, it's not great cos it opens up non-ideal syntax
(like I didn't document those because they lead to bad things)
like strings don't need to be quoted and other Silly Ideas™
Anton
@outkine
no trailing commas
Sven Bergström
@underscorediscovery
but it worked enough and then later I added comments
Anton
@outkine
why
that's my biggest gripe
Sven Bergström
@underscorediscovery
then in the new version I wrote one from scratch in haxe
Anton
@outkine
I feel like if you're serious about this then you should go ahead and also make a separate website/style guide/extensions for all the massive editors
but that's a lot of work
Sven Bergström
@underscorediscovery
serious about? remember flow is alpha still, I've been busy on my main project but slowly working toward a new alpha that has a much better workflow in general and further drives the project
Anton
@outkine
I'm really fascinated by how you're pretty much building a whole ecosystem from scratch
Sven Bergström
@underscorediscovery
(just had a look - the new haxe parser is only 247 lines for example, and is rigid and well defined in terms of rules)
well I was building things I needed to achieve my goals, and the parts of that that are useful as a general thing fall out of it.
like I needed flow because hxml or whatever existed at the time (over 2 years ago now) just didn't do anything I needed
like copying files, templating things, etc. there was no ecosystem for that
Anton
@outkine
which is also pretty exciting because it means that you have a chance to legitimately influence the Haxe landscape
compared to really established communities like node
Sven Bergström
@underscorediscovery
I personally think I have in many ways already, which was part of my goals, but whether the "haxe landscape" finds use for it isn't on me
in practice I'm just pragmatic, I needed something so I made it, but I've been around the block so I try to make it in a way that benefits others
Anton
@outkine
beauty of open source
you're using luxe for your own games, right?
Sven Bergström
@underscorediscovery
yea. (I hope you read the dev logs, as luxe no longer uses haxe directly)
Anton
@outkine
I've read some
which one specifically?
Sven Bergström
@underscorediscovery
the snowkit stuff going forward is more about completing the vision for the projects, like the all the linc libraries, the new version of flow, and seeing snow hit beta etc
4 and 5 speak about the language needs of luxe
I really like the new version of flow, I was wrapping it up recently, it's all in haxe now and uses cppia (and maybe soon HL) for scripting commands
Anton
@outkine
give me a couple of minutes to read the 5th dev log
Anton
@outkine
that's neat - I don't think I've ever seen a 'language-independent' framework
does that mean that luxe will also be written in C?
Sven Bergström
@underscorediscovery
3 or 4 mentions that the core is c++ yea
Anton
@outkine
just got to that part
my bad
Sven Bergström
@underscorediscovery
no worries
the snowkit stuff like flow etc is distinct btw, if you're interested in discussing luxe stuff it's at https://gitter.im/luxeengine/support now
here we go, finally found the gist I was looking for
this shows how different the new flow is from json in the way conditionals work, making it much much nicer to use for define based filtering
and the bonus is the output of the parser unit tests
Matt Johnson
@mattj1
Is there any way to get proper debugging working with an IDE for flow projects?