JohnnySheffield's Forum Posts

  • Hey man, i understand your worries.

    I'll release it with MIT license as soon as somebody offers to maintain it. Are you interested?

  • DatapawWolf

    Here you go, i've made the repo public, anybody is allowed to download and play with this plugin;

    http://git.machina.hr/c2-socketio/socket-io

    Few things to keep in mind:

    • Needs a custom version of a socket.io client library (one-liner change).
    • MIT license.
    • Want to contribute? Email me and i'll open up an account.

    edit: i've just saw this thread. Some good stuff is mentioned here!

  • Nope, no response for now, which is kinda sad. It would be great to know what are plans for this bug, will it fall in the "wont fix" or "on todo list" category.

  • I'm using git for dev with c2, and it's been an bumpy experience.

    Biggest problem is here as a bug report, and is main cause for never-ending conflicts:

    project-file-contains-ui-state_t105824

    I don't mind so much the conflicts, but it's rather difficult to resolve them beacuse a single change in editor can change the projcet code on multiple places. Proper diff tool designed for c2 would be of great help, i'm currently using kdiff3 and it's not intended to use with C2-like projects and sometimes it's rather difficult to solve conflicts.

    Except team communication who's doing what, and separating all logic on multiple event sheets (and including them as necessary) so devs don't step on each others toes i have not found a good solution, but it's manageable (sort of). I tend to create the whole project structure with all of the event sheets created but empty, and hope for the best.

    There's also a tutorial from ashley on working with svn and is a good source of info, but does not touch the conflict problem. https://www.scirra.com/tutorials/537/ho ... svn/page-1

    Unfortunately, this is my main problem with c2, makes working in teams rather difficult, and i do believe it will be hard ( if not impossible ) to fix. Fix would probably need to change the .xml files structure (and subsequently change some code in the editor, and ashley already stated it's hard to change editor code). It makes me kinda sad.

  • Ashley

    You obviously did not look very carefully, thehen created a great plugin for flurry a while ago:

    Great plugin, would like to see it gets an official support.

  • There is also problem with mysterious 

    sid="8119851569918457"[/code:3i3a7des] fields which can cause conflicts when merging two branches.

  • Here's my quick stab at it, as i could take advantage on a better random expression.

    The repository is located here: http://git.machina.hr/c2plugins/Crypto-API

    Documentation is located on wiki pages: http://git.machina.hr/c2plugins/Crypto-API/wikis/home

    If you're not into git and contributing to this simple and immature plugin, just download whole repository as a zip (button located on right side). A simple test and a .c2addon file included in the repo.

    Released under MIT license.

  • +1

    I've already asked Ashley is this something for a bug report, got no response. It should be addressed as it really complicates work with any VCS.

    Or even less if you pay income taxes to your state/country.

    I'm good with any set of rules, they only change dev's strategy on how to compete on the market and answer to a simple question "is this market worth competing on?"

    No matter how good your product is, you'll only get that many visitors/potential customers as they come to the store. If the price is capped to 5$, only thing that can make this market viable is the amount of people they will attract to the store. Let's say you're selling the ultimate plugin that is unbelievable for that price, and your product page is visited by 100 users per month. There's no way for you to make more than 100 sales, and you'll probably sell to a small percentage, let's approximate 1% or 1 sell a month. If there are 10000 unique (with a big percentage of new users) visitors per month, then 5$ is acceptable, as you'll earn around 300-350$ per plugin.

    With 5-6 good plugins and low maintenance costs, you'll start to see some significant earnings. It seems like a good strategy, it'll force devs to create smaller, more defined plugins, with a focused and specific need, which are easier/cheaper to maintain. It'll also force devs to expand, offer documentation for the plugins as separate eBooks, or sell advanced examples that come bundled with the plugin for the price of one. And the most importantly, it will give easier/cheaper access to the addons for the users of C2.

    I'm more ready to spend 5$ on any plugin than 29.99. With 5$ i'll buy it if it's interesting enough, store it to aside and use it when the time comes (just like steam games, probably never ). If it doesn't work as i expected, i won't be so angry. It just 5$ after all. But if it's 29.99$ i'll be careful with my purchase, and be more ready to request charge-backs if it's not what i expected.

    In the end, the only thing that matters are the rules, and how clear they are. After the market is open, pretty soon we'll know all the info we need and either Scirra will adapt, and/or sellers will adapt to the new information.

    Tom

    After some analysis and a nice cold beer, i've changed my mind regarding pricing of the addons.

    5$ is actually acceptable, if the volume is big enough and similar rules are applied to the whole store. As i don't have any info on the volume, i'll give Scirra benefit of doubt and hope they'll do their best to gather customers.

    If we're going cheap, it will only work if the whole store is cheap.

    Also, i'm not fond of the "per developer" license if the price is maxed at 5$. As a trade-off i can propose "5$ per year per developer" as it will motivate dev's to maintain their plugins, and 0,42 cents per month is laughable for a piece of code that enables you to create better games.

    I've changed the price on the store for my plugin. It's up to you to work out the licensing.

    Tl;dr: I'll live with 5$ per pop. It's your store, please decide what you want to do and stick with it, the developers will adapt.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • 8 Bit Destiny — Now for sale in the Scirra Store!

    https://www.scirra.com/store/royalty-free-music/8-bit-destiny-41

    <p>Created with love, this two beautiful themes will suite your game like it's meant to be.</p><p>You will receive two high quality wav's that will make your game stand out!</p>

    Use this topic to leave comments, ask questions and talk about 8 Bit Destiny

  • Jumpin' Pig Guido — Now for sale in the Scirra Store!

    https://www.scirra.com/store/royalty-free-music/jumpin-pig-guido-153

    <p>Jumpy, Cheerful, a little bit of DnB! Listen to the preview, you'll wanna fly!</p><p>Created with love, this two beautiful themes will suite your game like it's meant to be.</p><p>You will receive two high quality wav's that will make your game stand out!</p>

    Use this topic to leave comments, ask questions and talk about Jumpin' Pig Guido

    I agree with Fimbul in every point.

    My stance is that majority of work regarding selling plugins is not development itself, but rather customer support.

    Sellers ability to respond to and manage user requests, questions and requirements is what will separate plugins that will succeed in sales, and those that will decline after first few sales. And customer support is not cheap, requires a lot of time, and a platform more advanced than forums and a few faq's.

    I my preparations for store launch most of my time was spent into maintaining and deploying a software that will allow customers to get the support they deserve for the price, with every aspect that involves (an online platform with integrated issue reporting, possibility to communicate with other users of the plugin, even access to the git repo of the plugins, tests to run with servers deployed around the world, extensive documentation) without creating noise that scirra forum offers.

    My service was not just the plugin and the code, it involved a lot more. With servers deployed in three locations around the globe, i have monthly fees that can hardly be covered with price set to 5$. I'll shut down the whole network until more information is available from Scirra.

    Tom, those are massively discouraging words.

  • This is not a bug, it behaves as expected.

    The for loop is executed in one tick, so it moves "instantaneously". Also, expressions are executed from top to down, so your wait action actually has no effect!

    You could try with this to get the behavior you expect:

    for "i" from 1 to 9 -> wait loopindex seconds

    Set Y to ...

    I've attached a simple capx to demonstrate when the for loop is executed. Please check the browser console (ctrl+shift+j) to see in which tick is the action called!

  • There are multiple ways you can create a window in node-webkit, because of security concerns (enabling newly open window access to require enables them access to multiple dangerous settings.) You are probably using the window.open from browser object?

    Probably the newly open window has the 'node-enabled' set to false, to disable access to the node (more accurate, none of the parameters passed, so probably node is disabled by default, thus required not defined).

    You can pass all of the parameters of the manifest format to the new windows:

    var win = gui.Window.open('https://github.com', {
  position: 'center',
  width: 901,
  height: 127
});[/code:31thx1i5]

but mind that we're not doing the window.open, but rather gui.window.open.

I have managed to get multiple c2 projects together in a nw app, but i packed it manually, had custom manifest file, used custom plugin for opening new windows, and it was long time ago. 

I would recommend to dive in [url=https://github.com/rogerwang/node-webkit/wiki/Window]window[/url] and [url=https://github.com/rogerwang/node-webkit/wiki/Security]security[/url] and [url=https://github.com/rogerwang/node-webkit/wiki/Manifest-format]manifest[/url] parts of the wiki for starters.

edit: sorry, i've written first, then opened your capx second -> i do not get any errors!