project structure about roboxslicerextension HOT 12 CLOSED

from roboxslicerextension.

Doing the framework for this project and planning it out well, would be fantastic. I'd suggest the package name might be RoboxSlicerExtension, but I don't know much about the normal conventions on this sort of thing. The last time I touched Java was at university, so that's... ummm... 15 years ago...

You'd be a lot better placed to make those sorts of decisions.

I think we need to decide on the scope of what we want this project to do. My $0.02 is that it should do this:

• Easily install and uninstall itself (you've already done this)
• Allow easy selection of slicer (Slic3r, Cura, Simplify3D, etc)
• Integrate as much with AutoMaker as possible. This includes grabbing the config file that AutoMaker creates, parsing it, and feeding those values to the chosen slicer. It should also respect the material choices that the user makes inside AutoMaker.
• Show a preview, if the existing slicer doesn't already have one. This might be an option for if people are happy to use the inbuilt Cura Robox slicer. (you've already done the work for this I think)
• Spit out valid GCode to the Robox Post Processor, no matter which slicer is chosen.

I can't think of anything else, if this is the list then we need to think of a good name for something that does all those things. AutoMakerHelper? RoboxSlicerExtension?

from roboxslicerextension.

👍

Project name goes without saying: 'Robox Slicer Extension' ('robox-slicer-extension' for maven artifactId, 'roboxslicerextension' for last part of the package, RoboxSlicerExtension for the class name, etc)

Group - that's where the problem is. Maven groupId, first part of the package (sometimes last part of the domain name) is where you describe 'organisation'/'group'/'group of projects', etc... The worse would be to say 'org.githib' as we have nothing to do with github except it being hosted here. Other options are 'com.roboxslicerextension', 'net.roboxslicerextension'... Any other 'virtual' company/organisation/something-else would be great! I have my own projects always done under org.ah (for short) or org.abstracthorizon as I have create web site (in days before github and such) and posted my projects there. I still do that (http://www.abstracthorizon.org and many other subdomains)

"Show a preview, if the existing slicer doesn't already have one. This might be an option for if people are happy to use the inbuilt Cura Robox slicer. (you've already done the work for this I think)"
If we set up separate executable (of some kind) where you can select which flow do go with (which slicer to have) I would use the same app to select if such preview (see here: https://github.com/natdan/gcode-preview) can be switched on or off from the 'flow'. Also, same app should be able to set up any other local scripts user wants to add (some that just modify 'raw' gcode somehow/set pause gcode at particular level, etc).

👍 for all the other bullet points you put! Plus - try to keep it as platform agnostic as possible (read: it should work on Windows, as well! :))

from roboxslicerextension.

The group could be something like org.roboxenthusiasts? org.roboxslicerextension works as well.
+1 for making it cross platform. For some reason us Mac people are in the majority for once, I don't want to treat Windows/Linux people with the same disdain that they've treated us with for years.

from roboxslicerextension.

"For some reason us Mac people are in the majority for once, I don't want to treat Windows/Linux people with the same disdain that they've treated us with for years."
LOL. I'm happy with org.roboxenthusiasts unless someone has better idea/strong(er) opinion(s)! :)

from roboxslicerextension.

Oh, oh... There's another option (but not that good): com.roboxing! It is Tom Gidden's original web site (https://github.com/tomgidden) currently hosted at my servers... So it can accommodate (if really necessary) 'web side' of the project (no matter of name of the 'group').

from roboxslicerextension.

com.roboxing is probably the best one yet. Nice catch!

from roboxslicerextension.

from roboxslicerextension.

LOL - already in the pull request! :)

from roboxslicerextension.

from roboxslicerextension.

Oh, no - don't let you stop expressing what you had in mind. Nothing is set in stone!

from roboxslicerextension.

Thanks for the discussion guys. I think we've ended up with a beauty!

from roboxslicerextension.