search

YouMagine / UltiShaper

0 stars 0 forks source link

Workflow, collaboration, and app structure evolution possibilities #15

Open kaosat-dev opened 11 years ago

kaosat-dev commented 11 years ago

So as I was looking for ways to solve the modularity / git repo duplication / app structure issues I found a very interesting article and project :

http://badassjs.com/post/40691367335/voxel-js-a-minecraft-like-block-based-game-engine http://voxeljs.com/ https://gist.github.com/maxogden/5147486

The project in itself seems fun, but what caught my eye mostly was HOW they deal with modularity using Browserify : I am honestly impressed , as it seems like it would solve a lot of issues we are facing / we will be facing , and would allow people to contribute a lot more easily . What do you think ? (I will do a small proof of concept to see how well this kind of methodology works, but so far I like it a lot).

Im-Hal-9K commented 11 years ago

That looks great, I'll review some today.

On Mon, Jul 15, 2013 at 5:31 PM, Mark Moissette notifications@github.comwrote:

So as I was looking for ways to solve the modularity / git repo duplication / app structure issues I found a very interesting article and project :

http://badassjs.com/post/40691367335/voxel-js-a-minecraft-like-block-based-game-engine http://voxeljs.com/ https://gist.github.com/maxogden/5147486

The project in itself seems fun, but what caught my eye mostly was HOW they deal with modularity using Browserify : I am honestly impressed , as it seems like it would solve a lot of issues we are facing / we will be facing , and would allow people to contribute a lot more easily . What do you think ? (I will do a small proof of concept to see how well this kind of methodology works, but so far I like it a lot).

— Reply to this email directly or view it on GitHubhttps://github.com/Ultimaker/UltiShaper/issues/15 .

Thanks - Hal

ErikDeBruijn commented 11 years ago

Looks like a pretty big change, but if there's large long-term benefit to this approach, I'm all for it. Just make sure we've confirmed it with the experiment before we change all the code to the new code-reuse style.

Please excuse my brevity. I'm trying to deal with large amounts of e-mail at the moment.

-----Original Message-----

[UltiShaper] Workflow, collaboration, and app structure evolution possibilities (#15) From: Mark Moissette <notifications@github.com> To: Ultimaker/UltiShaper <UltiShaper@noreply.github.com> Cc: Tuesday, July 16, 2013 at 12:31AM

So as I was looking for ways to solve the modularity / git repo duplication / app structure issues I found a very interesting article and project : http://badassjs.com/post/40691367335/voxel-js-a-minecraft-like-block-based-game-engine http://voxeljs.com/ https://gist.github.com/maxogden/5147486 The project in itself seems fun, but what caught my eye mostly was HOW they deal with modularity using Browserify : I am honestly impressed , as it seems like it would solve a lot of issues we are facing / we will be facing , and would allow people to contribute a lot more easily . What do you think ? (I will do a small proof of concept to see how well this kind of methodology works, but so far I like it a lot). — Reply to this email directly or view it on GitHub.

 

Ultimaker - easy, open source 3D printing! http://www.ultimaker.com/ Follow us on Twitter http://twitter.com/ultimaker, Google+https://plus.google.com/u/0/b/105283675489513173942/105283675489513173942/posts , Facebook http://www.facebook.com/Ultimaker

IMAGINE IT >> MAKE IT

Im-Hal-9K commented 11 years ago

I agree it's a cool look, maybe quick POC may help ... I am just "a volunteer" so please pardon if I overstep. I think that the tool is awesome and am for anything to help making the development and user experience better.

I also that refactoring is a large pain and causes major headaches, sometimes solving less then the cause. That being said, since the boss is game what can do on this end to help with trying your idea Mark?

On Jul 19, 2013, at 3:23 AM, ErikDeBruijn notifications@github.com wrote:

Looks like a pretty big change, but if there's large long-term benefit to this approach, I'm all for it. Just make sure we've confirmed it with the experiment before we change all the code to the new code-reuse style.

Please excuse my brevity. I'm trying to deal with large amounts of e-mail at the moment.

-----Original Message-----

[UltiShaper] Workflow, collaboration, and app structure evolution possibilities (#15) From: Mark Moissette <notifications@github.com> To: Ultimaker/UltiShaper <UltiShaper@noreply.github.com> Cc: Tuesday, July 16, 2013 at 12:31AM

So as I was looking for ways to solve the modularity / git repo duplication / app structure issues I found a very interesting article and project : http://badassjs.com/post/40691367335/voxel-js-a-minecraft-like-block-based-game-engine http://voxeljs.com/ https://gist.github.com/maxogden/5147486 The project in itself seems fun, but what caught my eye mostly was HOW they deal with modularity using Browserify : I am honestly impressed , as it seems like it would solve a lot of issues we are facing / we will be facing , and would allow people to contribute a lot more easily . What do you think ? (I will do a small proof of concept to see how well this kind of methodology works, but so far I like it a lot). — Reply to this email directly or view it on GitHub.

 

Ultimaker - easy, open source 3D printing! http://www.ultimaker.com/ Follow us on Twitter http://twitter.com/ultimaker, Google+< https://plus.google.com/u/0/b/105283675489513173942/105283675489513173942/posts>

, Facebook http://www.facebook.com/Ultimaker

IMAGINE IT >> MAKE IT

— Reply to this email directly or view it on GitHubhttps://github.com/Ultimaker/UltiShaper/issues/15#issuecomment-21237465 .

kaosat-dev commented 11 years ago

Glad I am not the only one who finds this great :)

Yeah it is a rather large amount of change, so I am considering this very carefully, but it would solve a number of our issues : coffeescad/ultishaper are already modular by way of separation of the different "editors"/ stores etc, so being able to build different variations of the software in a modular fashion (seperate git repos, under an "umbrella" project, for example) would allow faster and more efficient collaborative work, solve the "merge" issues etc. Also each "building block", could be a clean, tested, easilly maintained piece of code, and that usually works best:)

I have been experimenting with different variations of such a system this week, and have found only one issue for now : handling html templates and css/styling (browserify is very code oriented). BUT even that can be worked around with ease.

As far as tooling to achieve this there is : Browserify, Component, and to an extent, Bower I am still diging to see which one fits bests (and which one has the biggest ecosystem/ longevity, and ease of use): http://www.forbeslindesay.co.uk/post/44144487088/browserify-vs-component http://procbits.com/2013/06/17/client-side-javascript-management-browserify-vs-component

(personally I prefer browserify , for its simplicity (no additional json files, simple nmp etc), its longevity etc. But not 100% sure at this point.

Hal : perhaps you could look into these as well ? Two, nay, three! minds are better than one :)

kaosat-dev commented 11 years ago

So , a bit of an update on this : you can find some of the experiments I did here https://github.com/kaosat-dev/Browserify-experiments they are all very basic, but I wanted to check out some crucial aspects before digging deeper:

and wow, I am seriously quite blown away!