Thread Rating:
  • 2 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[Feature] Portable Atmospheric Depot
#7
(07-31-2018, 01:47 PM)kyle2143 Wrote: I disagree, I think the relative paths make it look cleaner. Though I suppose I see your point considering you can declare new procs for datums anywhere in the codebase outside dm which can make it tough to figure out where everything is. But, if you ask me, THAT is what should be guarded against in a style guide since it's terrible.

I think relative paths make it look awful, but the asthetics of relative versus non-relative paths are up to the person. However, you get a tangible benefit from using non-relative paths in that you can search the codebase more easily.

As to code placement, being able to group related components next to each other even if they're not related in the object tree is actually one of the very *very* few things that DM does well. Enforcing rigid object tree placement would completely invalidate stuff like TG's module system (not that it's on g16, but whatever) or having all the chemistry tools grouped together.
Reply


Messages In This Thread
[Feature] Portable Atmospheric Depot - by Kubius - 05-21-2018, 05:22 PM
RE: [Feature] Portable Atmospheric Depot - by elan_oots - 07-31-2018, 04:40 PM

Forum Jump:


Users browsing this thread: 1 Guest(s)