[abakoboParticipant]

That’s strange!
Probably an mx2 duplicate def bug.
Or we are always supposed to use .h for definition and .cpp for implementation when using mojo/gui or use static.
With console apps I never had the problem.
Tested with static before the function in .h and works ok
Tested with def in .h and implementation in .cpp/.c and works ok

If you want to see some little example I made to learn externs: https://github.com/abakobo/learn_monkey2
It’s messy and not commented but simple. Will later use these as a base for tutos/samples

[abakoboParticipant]

Hi everybody,

you can have a look at the docs WIP at http://turdus.be/monkey2docs/docs/

added Pages:

Pointers
Conditional statements
Loops(currently empty)
Preprocessor
Index(currently half empty)
—
No modif of existing pages for now..

Please leave comments, critics,…

And please post issues at the github repo when you have difficulties understanding something via the docs or any other suggestion/request
https://github.com/mx2DocsCommunity

thx

[abakoboParticipant]

To dereference a pointer use [0]

Monkey

[crayon-5cba9fc20f2ac252415828 inline="true" ] Myptr=VarPtr i Print Myptr[0]

1 2 3 4 5

[crayon-5cba9fc20f2ac252415828 inline="true" ] Myptr=VarPtr i   Print Myptr[0]

[/crayon]

You’ll see the value of i

Monkey pointers have nothing special, they are just c++ pointers. Function pointers(function values) are a bit different but can be used just like c function pointers.

[abakoboParticipant]

I’m mainly using monkey2 for mobile targets too.
But as a cross platform productivity tool also.

[abakoboParticipant]

Gles 3 is supposed to be 100% retro-compatible with gles 2 so it’s a kind of non-issue to me..

[abakoboParticipant]

That would be great!
I planed to make some basic learning examples for chipmunk. The only thing I’ve not tested is the different joint types. Seeing how you’ve coded this adding timelineFX is quite interesting!

[abakoboParticipant]

Roseta code is very interresting!

This is worth a shot I reckon, although it might be an idea for someone else apart from me to handle docs merges as I suspect I’d be ultra-picky about it! Any volunteers (with suitable experience preferably)?

I opened an organization on github for that precise goal: merging docs by community in a way that some day it could be pulled with no conflict at all to the latest dev branch.
I already post issues about the docs on that repo, and I’m of course volunteer. But I’m not sure I’ve suitable experience. English is not my mother tongue..
https://github.com/mx2DocsCommunity

It’s mainly to stop having to search for infos I half remember that I want to do it. So I think I’ll have a try anyway.
I’m open to any other way of working as long as it helps mx2.

@MarkSibly: It’s good to have your opinion about it. Thanks.

[abakoboParticipant]

You need xcode to compile a mx2 project.
Mx2cc, the mx2 compiler, transforms you mx2 code to cpp code then it calls xcode by command line.

Edit: sorry didnt see update. Don’t what you really need exactly xcode side..

[abakoboParticipant]

Images are initialised by NewAppInstance.
See this closed issue: https://github.com/blitz-research/monkey2/issues/103

Edit: opps it’working with class so it must be something else?

[abakoboParticipant]

Yes it would be nice is thoses good old BASIC functions where included in std or any core module..

[abakoboParticipant]

added a working demo with BBquery with function Callback and UserDatas on my chipmunk_mx2 github repo. It’s not clean but readable I think. It’s a bit too big. I’ll probably start to make simpler examples because there’s to much shapes objects and that makes too much code lines. BUT it’s fully working!

https://github.com/abakobo/chipmunk_monkey2

[abakoboParticipant]

If you want some ‘rectangular array’ you can do the following:

Monkey

[crayon-5cba9fc227280067955977 inline="true" ] Local map1:= new int[10,10] Local map2:= new int[7,9]

1 2 3 4

[crayon-5cba9fc227280067955977 inline="true" ] Local map1:= new int[10,10] Local map2:= new int[7,9]

[/crayon]

or

Monkey

[crayon-5cba9fc227287537319597 inline="true" ] Local map1:int[,] Local map2:Int[,] map1= new int[10,10] map2= new int[7,9]

1 2 3 4 5 6 7

[crayon-5cba9fc227287537319597 inline="true" ] Local map1:int[,] Local map2:Int[,] map1= new int[10,10] map2= new int[7,9]

[/crayon]

If you want an array of various arrays (non-rectangular/jagged) you’ll have to loop as mark showed. h could have different values during the loop.

[abakoboParticipant]

I honestly don’t see much issue with the API docs, but you need rather more than API docs

I see some. Chipmunk is empty, other modules are empty, even in mojo there are gaps and strange doc builds.

The auto docs of the language reference could benefit of some adding too. It’s totally unsearchable. Even with “varptr site:http://monkey2.monkey-x.com/monkey2-docs/” on google you’ll have nothing. And some keywords are missing.
It would need a keyword index and a better table of contents IMHO.
For me, someone who’s used to programming and to use integrated docs should be able to understand monkey-2 with the autodocs and basic examples only (bananas).

Its more about how a module should or could be used, this kind of documentation isn’t the type that you could put in the auto doc comments.

I think both have to be done. Nerobot has created a wiki and started some writing. People who want to explain how some modules work and write basic mx2 tutorials are welcome there I think.
I have learn monkey2 mechanics with some monkey-x tutorials in some ways but mainly with the mx2 language reference and module section + bananas and of course this forum/blog.

With github, people who find that an mx2 doc is unefficient, is lacking something, would need a little example, can post an issue or modify if he/she has motivation. Unlike original monkey2 github, it would have to be very issue posts oriented.
The quality of integrated docs can profit of that. There’s the problem of no copy-paste still but docs can be opened in a normal browser anyway.

[abakoboParticipant]

Working on something which might only get live doesn’t sound motivating

I understand, the idea here is to help Mark having a nice OOB doc. One that can be used with F1 and that could make mx2 a ‘solid’ set. Also a wiki is something that will only be live and importing it later to the ‘#rem monkeydocs would need a lot of work later.

How do people easily access these docs?

Ultimately by pressing F1 or in Help>Browse docs. During WIP by importing the modules from github and build docs. May be it would be better to work on a fork of the master branch instead of dev branch for it to be more easily used by people who just want to use it.
It could also be generated by a CI so it’s always visible up to date.

(How) will they be merged with new docs from Mark?

-(How) That’s what a git is for. It’s the one of the most used tools for merging that kind of things.
-Mark accepts things, he’s put Ted2Go in the distro, he’s accepted pull request but made the change by himself, he’s been putting bananas in the repo when he thinks it helps, sometimes two days after a suggestion/request it up on github dev branch and he doesn’t say anything BUT do it. If we do a good job I think he’ll probably merge, it’ll not be touching one line of code. IMHO it has to be done by big batches. He is asking for community work in some ways after all.

How about something like BlitzMax’s WikiBook?

That would be great too! It seem to be well structured and very educative. For the integrated docs I’m more thinking of something with a lot of little examples for of a lot of occurrences. But a pimp of the language reference too, witch should be educative in some sense.

your own content + export of Mark’s docs + references to original docs + links to users’ external content

Great too, but some things are missing in the original docs now.

Ideally Mark would offer more docs and there would be a strategy plus communication on how to address the situation best in the future.

It’s clear that Mark is not really into presentation/docs/communication&marketing. By trying to help, adding infos he gave us on the blog&forums but are not put in the docs, we do what he has no fun with. This can be a winwin if some of us like to do it.

[abakoboParticipant]

Monkey2 is still in WIP but is stable. You’ll have more trouble learning it because the big lack for now is the docs and other tutorials.
Also for mobile and HTML5 it works but it is more complicated than Monkey-x because you’ll have to open the projects in androidNDK/x-code. And I’m not sure you can run an IOS project in the simulator so you’ll may be need a iMobile and an Apple dev account to run IOS code (must be veryfied).
I never compiled to HTML5 thru emscriptem but I saw some people having trouble with the emsciptem configuration. With monkey-x the HTML5 target is the easiest one to get running (and is free as well as desktop targets). It has also the fastest compilation time.

So if you want direct result for mobile or html5 production Monkey-x is still better I think. If you want better performance for android, mx2 is theoretically faster as it uses the NDK and not Java.

If you want to program for fun, mx2 has more programming features but some modules are not complete. (no easy custom shaders with mx2’s mojo(planned not immediately), in monkey-x’s mojo2 they are available for example.)

The fact that mx2 is in WIP is fun in some ways but can be boring if you want to get things done fast.
Monkey-x is a mature language and works very well. There seems to be not too much people on the monkey-x forum but you’ll have answers fast I think. People who are used to it doesn’t need to ask questions anymore..
If you use Monkey-x with mojo2 and strict mode you’ll be able to switch to mx2 very easily, even port code if using functionalities available in mx2.
Monkey-x Studio is coming with ignition-x and therefore is using mojo1 so it won’t be easy to switch to mx2.
I’d rather buy the Pyro framework instead of ignitionX if you want a complete framework with examples. This way you can switch to mx2 easier because you’ll be using mojo2 and pyro2 exists for monkey2 free!
For the monkey-x IDE you have mollusk witch is osx compatible too (but not linux). Jugnle IDE seems to be a bit more advanced than mollusk but is windows only. You can use the original Ted IDE too (or use open source jentos IDE based on Ted but its a bit buggsy sometimes).
For the MX2 IDE you have Ted2,Ted2Go(fork),Ted21(fork) but non are as advanced as jungle or mollusk. Mollusk has some MX2 capabilities but I’m using ted2GO though I own mollusk (I should retry mollusk with mx2 some day)

-Monkey-x Studio(ie: monkey-Pro, Jungle IDE, Ignition-x)=99$. (but switching to mx2 not easy)
-Monkey-Pro(39$)+mollusk(10$)+Pyro(65$)=114$ (good for switcing and good to stay monkey-x1 too!)
-Monkey2+Ted2+pyro2= patreon/donate what you want!

Mx2 is a bit more strict, more strongly typed, but it’s basically the same syntax with a bit more possibilities.

[Author]

Posts