Forum Replies Created
-
Posts
-
123Local MyArray:Int[] = New Int[](1, 2, 3)' I think. xD
Well BuddyPress Docs is a WordPress plugin that seems to be exactly what we need for community editing. It handles User Invites and Authoring of Pages. So Mark would have to install that on this site, and give a few of us permission to edit various sections(Permission being handled by the plugin). Also has feed back capabilities.
I think Fibers are an alternative way of looking at Threads in abstraction, but ultimately I think they have the same inner workings for asynchronous programming…
Sorry for the late reply @xaron.
As Mark said you can only use Client/Server functionality using Mojo/MojoX. However, he might try and implement it down the road. For now, I would just emulate a Terminal using Mojo or MojoX… There is a “Console” View for Mojo X that is used in Ted2/Go that does almost the same thing as an output terminal; though I’m sure with some tweaking you could get a nicely polished command line with Monkey2 features and support.Yes, that would be amazing.
+1I should’ve noted that this requires you to make a new module for each std-*.monkey2. while containing the source for each. My bad. Just make a new folders in the module directory containing the std-*monkey files along with a filledout module.json file and it should work when you import it on it’s own after a rebuild. Sorry for the missing info. xD
Eample:
modules/
– std-colections/
– – collections/
– – std-collections.monkey2
– – module.json
– std-graphics/
– – graphics/
– – std-grahics.monkey2
– – module.json
– std-filesystem/
– – filesystem/
– – std-filesystem.monkey2
– – module.jsonAs far as the Standard Module goes for Monkey it’s nicely structured for aggregation in terms of the directory structure… So in other words you could create a std-collections.monkey2 document in the “monkey2/modules/std/” directory and have it contain only the import directives to all files in “std/collections/”
std-collections.monkey2
12345#Import "collections/container"#Import "collections/stack"#Import "collections/list"#Import "collections/map"#Import "collections/deque"You can do this with almost any module, to ultimately reduce the final compile size. Just rebuild the modules after your edits and then make a test to see if it works then act accordingly. This is what I’m doing right now and I’m getting nearly half the compile sizes compared to the default implementation of std and other modules. Hopefully this will become the norm. I hope this helped out.
Yes, @codifies –
Moving the monkey2 directory to a space absent path does the trick without the need for admin privileges. Thanks lots guys.
Solved! Just run as Admin apparently… Weird… Not sure why.
There aren’t any “proper” instructions that I know of at the moment.
I just used the ol’fashioned process of trial and error, and google. xD
All I know is that a fresh install of the Raspbian/Pixel OS is missing a lot of packages for building Monkey Apps.
base-devel
libsdl-dev
libudev (I think)I don’t remember exactly what I did. xDxDxD
I’ll see if I can do it again and make “proper” instructions after the new year.Wow, this goes deep into the 1 and 0’s.
I guess since it’s even working in the first place is a huge step forward. I’m sure we’ll get there.I’ll just add Window Controls on the top of the Ted2 GUI specifically for the raspbian build and see how far I can get with it. xD Thanks for the reply!
I’ve opted to go with that solution for now. Hopefully this won’t be too hard to fix. xD
Edit: Oh I see. xD Yeah I’ve noticed building apps takes forever
As for any workarounds. I found THIS and it appears that.
“After talking to developers in the SDL FreeNode IRC channel, it would seem that SDL 2.0.3 has removed all windowed mode support for Raspbian. So the answer is: It’s currently not possible to have windowed SDL2 programs on Raspbian.”
So I guess the only way would be too downgrade the libsdl-dev to a version lower than 2.0.3… But this is where my knowledge stops. Heh…
To start, we should Document the Standard Library since it’s the simplest, and then move on to Mojo, then Mojo X. As such we can focus on the other modules that exist by default at the moment.
And as for the Downloadable Modules, I guess we’ll have to just add Documentation for those unless the developers of said Modules have their own Documentation ready. I’ve noticed Pyro by Playniax has a great start on Docs already so we can leave that one out for now. (Unless Playniax Might want us to help too. xD)
So should we make a Git repo for this? Or just a website where you make an account, request to help write/update Documentation as needed. This should be requested from Ted2 using ‘litehtml’ like the normal.
So far the only reusable stuff I’m seeing in the current docs source directory are just CSS files and a JS Tree. That literally seems to be most of this website’s code just duplicated for ease.
I’m pretty good with HTML and CSS and some PHP. But I’d rather use Git or WordPress.It’s never too late. xD
I’d imagine that we could implement this quickly by pretty much copying the current Docs available and just updating the HTML/JS, however this would be very difficult beings how the Docs are generated by mx2cc. I’ll take a look and see if there’s anything reusable for this as a starter template. Word later…
I think maybe Mark has his hands full with the project itself. Another approach would be to create a Community Documentation Project. I propose that we maybe set up a Wikipedia-like site where trusted users can commit changes to any particular documented code or, add new pages based on Marks commits on Git and the Articles on his Blog. So far we can take most of what we have from this website for Monkey 2 and maybe a little info from the Monkey 1 the Docs since they’re kinda identical syntactically.
That way Mark can focus almost exclusively on Monkey where as we can keep the docs as descriptive and informative as we can, thus allowing newer users to get started quickly.
Who’s up for this? I am.
