Forum Replies Created
- 
		AuthorPosts
 - 
		
			
				
Hey Wiebow, will your sublime text language highlighter be available as a package at any point?
Hi Mark, this is what caused the Duplicate identifiers, simple test module:
Module name “test” with files:
test.monkey2:
[/crayon]Monkey123456789[crayon-5cb9cfaaaf01b699289039 inline="true" ]Namespace test.collision#Import "something"'Types of collisionConst tlBOX_COLLISION:Int = 0Const tlCIRCLE_COLLISION:Int = 1Const tlPOLY_COLLISION:Int = 2Const tlLINE_COLLISION:Int = 3something.monkey2:
[/crayon]Monkey123[crayon-5cb9cfaaaf023511935647 inline="true" ]Namespace test.collision#Import "test"I guess it mattered more in monkey where you could import only part of a module if you needed too so those individual imports needed to be there in each file as dependencies, but now that the whole module is imported you can organise it differently which I quite like, feels less messy.
I see, I was confusing myself where I’m just converting monkey 1 code and running each file individually to catch errors and seeing duplicate identifiers. Now I’ve moved all my imports into the main module file and everything makes sense again, I can just run the main file now and it reports errors on all the imported files (or just makemods to do the same). Thanks!
Regarding the “Modules must not have cyclic dependancies.”, in monkey I had collision.monkey, and quadtree.monkey, they both imported each other which won’t work now. So should I basically have them both in one file or is there a different way of going about it?
Ahh ok, that makes sense, thanks
February 4, 2016 at 11:49 pm in reply to: Welcome to the monkey 2 development discussion forum! #267Looks good to me. If you use chrome you can open the developer tools (ctrl+shift+i) then in the top left of the console there’s a little mobile icon you can click on to emulate a site in different devices if you need to test anything.
A quick fix for the mobile issue with code boxes:
[/crayon]Monkey123456[crayon-5cb9cfaabd466400046172 inline="true" ]@media only screen and (max-width: 768px) {.media-left, .media-right, .media-body {display: block;}.bbp-reply-author {overflow:auto;margin-bottom:15px;}.bbp-reply-author .clearfix {display:none;}.media-body {width:auto;}}Plonk it where ever the theme allows for custom css or just stick it at the end of your style.css.
Yeah themes can be a bit hit and miss sometimes. A good resource I like use is the envato market place, specifically themeforest.net. Although the WordPress themes there are not free, the standard is usually high, (not always! But you can check the user comments and ratings for any gotchas). Some of the themes specify bbpress compatibility but it’s always worth checking with the author. I should think the majority will work fine and perhaps just need some css tweaks at the most. I got my theme for rigsoft from themeforest and I don’t think it specified bbpress but it it worked fine.
You could stick with this theme for now as it seems to serve the purpose well enough, and then when monkey2 is closer to a full release and you’re a bit more comfy with WordPress you can think about sprucing it up a bit
It’s worth noting also that it’s good practice to create a child theme of whichever theme you’re using (if you’re not already) so that you can make changes to the theme without overwriting the original. That way if there’s an update to the theme you won’t lose your changes. More on that here.
All the best with the monkey 2 development, looking forward to working with it
I work in WordPress all the time so if you need any pointers on anything give me a shout!
A couple of plugins I can recommend for starters: Wordfence which is a security plugin which has various features for scanning for malware, blocking IPs etc., and also Anti Spam by CleanTalk does a great job at stopping spambots for only about $7 a year which you’re bound to have issues with at some point, I use it on my site and it stops loads all the time, was a real pain without it, stats here: https://cleantalk.org/my/stat?aaid=62ef759c
Wordpress is also php 7 compatible already too which is 2 or 3 times faster than 5.x, might want to check your plugins are compatible too though before upgrading.
 - 
		AuthorPosts