Forum Replies Created
-
Posts
-
Many thanks!
(so obviuous now! :P)Hi
to place source code use the button ‘crayon’ in the text-box, it will open a proper ‘code editor’ where you can paste the source.
About list and ‘compare’ method follow this example
http://monkey2.monkey-x.com/forums/topic/a-clever-way-to-filter-lists/
I don’t know if this is a sign of ‘lack of communicating’ or not.
Surely he seems to be deeply coding the 3d module… so maybe he changed the (his) priority (at the moment).mx23d phsyics @60fps video test:https://t.co/M9NtUpW755
— Mark Sibly (@blitzmunter) March 9, 2017
I don’t want to write an heresy, but IIRC Monkey1 has already something (MonkeyStore or similar). So ‘translating/adapting’ it should be not so *much* work (of course I’m a completely noob in this!)
Thanks very much!
One question: is it programmed for a specific MX2 version?
I tried to compile the source code with MX2 1.0.5 and I got errors
[/crayon]12345[crayon-5cba9a512d0a5503316213 inline="true" ]mx2cc version 1.0.5***** Building app 'E:/PromptInvasion-master/PromptInvasion.monkey2' *****Parsing...E:/PromptInvasion-master/PromptInvasion.monkey2 [1734] : Error : Expecting expression but encountered ']'there are some errors in the ‘assets’
background.png (missed data/)
hit.mpr
hita.mprshould be hit.ogg, hita.ogg
Wow!
Incredible work.
It’s quite fast in downloading/rendering the ‘map’.ps: many thanks for the source code!
Well, many other products (similar) are selling ‘support-fee’ (ie: 49,99 per year) + the cost of the original licence (in this case isn’t an OPEN software of course).
Support fee could be always considered (=it does mean that the buyer has some sort of warranty on the stability/functionality of the software he/she bought – like in case of a new OS system)
And about my idea of ‘paid-docs’…
* basic docs (the one that should explain the language itself, and the ‘core’ modules – call it LEVEL 0) should be free and always available.
* other docs (like sqlite in my previous post) could be paid (call it LEVEL 1)
* price of these docs could be very low (ie: 5 USD/year for the sqlite, 7 USD/year for sqlite+another_one etc..) – the logic is copying the ‘google effect’: single low cost but for higher number is still an interesting amount! I suppose none will critic the fact that for (for example) 25 USD I have access to docs and examples about 5 different modules (sqlite, http-curl, IAB etc) – they ‘buy and own’ something – and honestly the logic of ‘donation’ could be not efficient!
* in any case – after some time – docs at LEVEL 1 could be passed to LEVEL 0 (=free for everyone) and BRL/Mark could add ‘another LEVEL 2’ of documentation (ie: video-tutorial, preset of themes, shaders etc – just ideas!)Or you could tell me how much you will pay a ‘paper manual’ (like the Blitz3d) – with all the limits of being of paper.
The idea (of course not perfect!) is to have some sort of regular money flux… donations don’t grant this.
BTW, my are only suggestions, I know Mark’s low (my website(s), my rules!)!
Well, the paid module is the right way. And Itch.io seems to have high potential.
I don’t know how ‘well’ (or not) in terms of money is offering a pre-built binary, for a ‘open’ language.
Unless there’s some automatism that creates – periodically – a working binary to download and install it, so I would quite happy to pay for having something ‘ready’ and gain time to download/setup/compile etc…ps: [stinker mode on!] … (I’m ready to be insulted of course!! :D) – how much I should pay to have documentation ?
Mark could prepare some ‘packets’ to sell (ie: documentation for modules completed with examples etc) – maybe extern to the in-source code… only the ‘core-basic’ language documentation should be free and available for everyone.
Everything ‘more’ (like sqlite for example) could/should be sold separately.
Of course the ‘packets’ could be an userid+password to access to a locked wiki, so only authorized (=paid) users could access.
Or it could be something to install locally on the user computer or both the solutions.
In many ‘free’ projects support is something paid… so it will be no so much ‘strange’ selling ‘manuals’Just an idea to have money for Mark, a motivation for him to give docs, and docs for the final users.
[/stinker mode off]I’m happy (of course) for Mark for the ‘granted’ income and for the enthusiasm.
But I prefer Mark will focus on Monkey2 demos/games (just read his own post on the web) etc than to start a long (very long!) journey in the creation of a 3d module…
New users could help deciding better what technology use (gles2.0 or gles3.0), what platforms are prior etc.
Waiting so much time (no doubt on the skills in 3d engine programming of course!) could be potentially a problem for everyone, new and old users.I agree.
TO put immediately on wiki/documentation.Thanks a lot!
What I really would like to see is MORE examples: from the ‘basic’ one, to the complex one. Reading it, changing it is a good way to understand what commands/functions are for.
Technically at least 3 examples for arguments are needed – the basic one as simple introduction, the other to cover more features/special cases.
A wall of text – in some cases – is not-needed AND can be (via wikibook or other solutions) provided in future.From the point of view of a ‘BlitzMax’ user, when MonkeyX1 was launched with an independent website I was thinking “wow, BRL this time has big ideas and MX1 seems very promising”.
Eveyone known that BlitzMax was OK, it was ‘mature’, it was (is) working without (too much) problems on 3 different platforms and – only in rare case – a ‘support’ from BRL was/is necessary/needed to continue to use it.
And this is the situation.
Splitting the community – at the time – was a consequence of the different nature of the language… many users (myself included, I’m using BlitzMax for desktop applications) look at Monkey1 like a ‘toy maker’ (just the HTML5 target has some potential for ‘working’ application in my view).Then Mark decided to suspend Monkey1 (it’s mature, it’s too complicated to evolve, it will be just maintained). AND Mark moved to Monkey2 openining a new website for it.
Again faraway from Blitz-thingy…From my perspective this seems to indicate that ‘Blitz-userbase’ is just a brake, a weight to development… I see ‘this’ forum a sort of home for an ‘elite’… people (very) talented but ‘superior’ to the ‘simply’ Blitz-people.
I know I’m not a pro-programmer, I know my limits, but splitting & separating the user base was not a big move (in terms of market) and in terms of support I believe.
Even in BlitzMax forum there are (were) people very talended in other advanced languages… I would prefer that Monkey2 had ‘home’ in its roots (BlitzMax): even Mark wrote that Monkey2 takes something from BlitzMax (modules logic etc).I just want to say that is most probable that a BlitzMax user looks at Monkey2 (comparing syntax & features) in the same forum than jumping here… with a decades of ‘code-base’ I would prefer to find the ‘blitzmax’ version and the ‘mx2’ version (like the B3D or BlitzBasic version actually).
End of rants
I hope Mark will follow up what he wrote in the blog at the start of the year – at last the one I consider important
Write/sell a simple game in mx2 both to raise funds AND to have a decent ‘this was written in mx2’ demo.
Everything then will be a simple consequence of this (demo, marketing, publicize MX2 and ‘monetization’ of modules).
More users probably more supporters.
One (or more) games means (maybe) money AND (if they are developers or interested in) new user ‘beyond the blitz’3d module – in my vision – should be one of the ‘monetizable’ thing for MX2 – and I think Mark could/should make a proper section of the ‘WIP’ (maybe with screenshot, video, piece of code etc) of those modules: it helps to publicize them.
Well… I suppose if we sum the Patreon+PayPal donate that amount was already reached.
In any case, good for Mark, and I hope it will be a ‘constant’ not just a ‘spike’…Well, it’s not an ‘heretic’ suggestion after all.
The ‘right’ solution is having 2 different setups:
1. a ‘full’ of everything (even not needed) (with an alert/message… ‘could take a bit longer to compile everyhing’)
2. a ‘basic’ one (of course where dependencies modules are not needed)
2.1 with the internal ‘module manager’ it’s quite easy to download/install/compile everything else.ps: mojox not used??? Without it you can’t build the IDE
The major lack of the current documentation in Monkey2 is the ‘module’ section (mainly the ‘extern’ ones): take a look at litehtml and see. You can find only a generic
More information about litehtml can be found at http://www.litehtml.com/
Not a description, not a tutorial, not a clear way to use it.
And following the link I get lost… I still haven’t found a proper documentation! Worst & worst!Core-language features are in-source coded, so in time they could be better (and there’s something – very basic – at the moment): I don’t think this is a problem.