module trimming

[AdamStrangeParticipant]

OK. Heresy alert!

Get rid of all unused modules until they are needed.

so the following can be completely archived:

chipmunk -no idea

hoedown -no idea

lite html – burn at stake

module manager -not used

mojox -not used

sqlite -???

tinyxml -never used

There is a good reason to clip all this to archive. until needed. if you don’t know what they do, then remove them. Those that know will install when needed. will make initial compile and setup much more streamlined

GET RID OF HTMLLITE – replace with something that is user friendly and allows copy of text. if no replacement can be found, then dump entirely and rethink help display!

[degacParticipant]

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

[codifiesParticipant]

I do wonder why it bothers compiling all modules, maybe it should juat gen the api docs and nothing else, then the first time a module is #imported then its compiled (but only for the build type – debug/release)

Are you sure litehtml can’t copy/paste, are you implementing it, using the apropriate methods?

Module manger, you dont use it so no one should ???

[AdamStrangeParticipant]

the module manager shouldn’t really be a module? Surely it’s an application, or extension, but not really a module?

once you’ve compiled the idea, then mojox is not needed. Majox should have been kept out of the modules entirely along with styles, and gui stuff

[coconParticipant]

My experience with Monkey is to do a weekly build from source, preferably for about 5-10 minutes, until I make coffee and have some snacks. By hitting the update script (not the rebuilt) there is a chance that it will be much faster, because it will reuse any as many existing cache objects possible.

[nerobotParticipant]

Also maybe there is a good idea to extend IDE’s “Build modules” – show checkable modules list to be able to build custom modules only.

[coconParticipant]

Good idea, I noticed this that when I tried to download a module (portmidi) there was a forceful rebuild of all the modules (I went for more snacks). Perhaps there could be a tracking of the checkbox activity in a stack, so the program knows, which module was downloaded, which was to be built.

[nerobotParticipant]

Also, I plan to add “Clean” checkbox into Build dialog. So we can get update and rebuild results (clean+makemods=rebuild).

[Author]

Posts