Comments (13)
Some random thoughts:
One thing I've learned from using the shared spreadsheet: The commonest 4
or 5 ingredients are worthless to log. Everywhere has them in abundance.
To me the most valuable information is details on the single rarest item
the planet yields. IE Polonium or Yttrium.
Another thing the spreadsheet has taught me: quantities are fairly
meaningless. Either a planet has a material or it doesn't. It's the metal
quality of the big rock you bust open that decides how good the drops can
be.
One other piece of data I would find useful: terrain difficulty. That is,
how flat, and what gravity? I figure the easier the terrain the more you're
going to pick up. This could be implemented as simply as a drop down box of
difficulty (easy to hard).
Btw, I've mentioned the spreadsheet quite a bit. It has been useful but I
think it's greatest failings have been in the amount of pages to fill out
and the amount of geological knowledge assumed. I don't know or care what
most of the surface types it lists are. It's assumption of one big rock
type per survey is obviously flawed. Personally I don't think it matters
where you prospect on a world at the moment, you can still get all the
known mats the world can yield.
On Jan 1, 2016 6:36 AM, "Robert Wahlström" [email protected] wrote:
Add a may to record prospecting of minerals
And a way to view known planets with minerals you wants
—
Reply to this email directly or view it on GitHub
#43.
from eddiscovery.
I think we will start with it simple.
Still debating with myself if add numbers of materials or just a check-box
to indicate that its found....
Only a check box is needed but numbers foung might be more fun.
2016-01-01 16:32 GMT+01:00 Greg Malcolm [email protected]:
Some random thoughts:
One thing I've learned from using the shared spreadsheet: The commonest 4
or 5 ingredients are worthless to log. Everywhere has them in abundance.To me the most valuable information is details on the single rarest item
the planet yields. IE Polonium or Yttrium.Another thing the spreadsheet has taught me: quantities are fairly
meaningless. Either a planet has a material or it doesn't. It's the metal
quality of the big rock you bust open that decides how good the drops can
be.One other piece of data I would find useful: terrain difficulty. That is,
how flat, and what gravity? I figure the easier the terrain the more you're
going to pick up. This could be implemented as simply as a drop down box of
difficulty (easy to hard).Btw, I've mentioned the spreadsheet quite a bit. It has been useful but I
think it's greatest failings have been in the amount of pages to fill out
and the amount of geological knowledge assumed. I don't know or care what
most of the surface types it lists are. It's assumption of one big rock
type per survey is obviously flawed. Personally I don't think it matters
where you prospect on a world at the moment, you can still get all the
known mats the world can yield.
On Jan 1, 2016 6:36 AM, "Robert Wahlström" [email protected]
wrote:Add a may to record prospecting of minerals
And a way to view known planets with minerals you wants
—
Reply to this email directly or view it on GitHub
#43.—
Reply to this email directly or view it on GitHub
#43 (comment)
.
from eddiscovery.
Already came up in conversation on Skype earlier, but to reiterate for the record, I think checkbox is the more useful option. But saving the backend data as an integer might give you more leeway to change your mind later (using 0 and 1 for checkbox values).
That probably wouldn't be hard to upgrade the database from binary to integer data, so my suggestion is perhaps breaking the YAGNI rule... :D
from eddiscovery.
Ooh, brilliant! Does EDDB store that data or will it be local data only?
Mark Jelic
iPhone: 0402 322 901
On 1 Jan 2016, at 10:36 PM, Robert Wahlström [email protected] wrote:
Add a may to record prospecting of minerals
And a way to view known planets with minerals you wants
—
Reply to this email directly or view it on GitHub.
from eddiscovery.
Certainly gravity would be good to know as that can determine the type of skip you can take fun there.
But certainly just a pop-up page of checkboxes for the materials will do. No need for quantities etc.
Mark Jelic
iPhone: 0402 322 901
On 2 Jan 2016, at 2:32 AM, Greg Malcolm [email protected] wrote:
Some random thoughts:
One thing I've learned from using the shared spreadsheet: The commonest 4
or 5 ingredients are worthless to log. Everywhere has them in abundance.To me the most valuable information is details on the single rarest item
the planet yields. IE Polonium or Yttrium.Another thing the spreadsheet has taught me: quantities are fairly
meaningless. Either a planet has a material or it doesn't. It's the metal
quality of the big rock you bust open that decides how good the drops can
be.One other piece of data I would find useful: terrain difficulty. That is,
how flat, and what gravity? I figure the easier the terrain the more you're
going to pick up. This could be implemented as simply as a drop down box of
difficulty (easy to hard).Btw, I've mentioned the spreadsheet quite a bit. It has been useful but I
think it's greatest failings have been in the amount of pages to fill out
and the amount of geological knowledge assumed. I don't know or care what
most of the surface types it lists are. It's assumption of one big rock
type per survey is obviously flawed. Personally I don't think it matters
where you prospect on a world at the moment, you can still get all the
known mats the world can yield.
On Jan 1, 2016 6:36 AM, "Robert Wahlström" [email protected] wrote:Add a may to record prospecting of minerals
And a way to view known planets with minerals you wants
—
Reply to this email directly or view it on GitHub
#43.—
Reply to this email directly or view it on GitHub.
from eddiscovery.
I vote just checkboxes.
Mark Jelic
iPhone: 0402 322 901
On 2 Jan 2016, at 3:00 AM, Robert Wahlström [email protected] wrote:
I think we will start with it simple.
Still debating with myself if add numbers of materials or just a check-box
to indicate that its found....Only a check box is needed but numbers foung might be more fun.
2016-01-01 16:32 GMT+01:00 Greg Malcolm [email protected]:
Some random thoughts:
One thing I've learned from using the shared spreadsheet: The commonest 4
or 5 ingredients are worthless to log. Everywhere has them in abundance.To me the most valuable information is details on the single rarest item
the planet yields. IE Polonium or Yttrium.Another thing the spreadsheet has taught me: quantities are fairly
meaningless. Either a planet has a material or it doesn't. It's the metal
quality of the big rock you bust open that decides how good the drops can
be.One other piece of data I would find useful: terrain difficulty. That is,
how flat, and what gravity? I figure the easier the terrain the more you're
going to pick up. This could be implemented as simply as a drop down box of
difficulty (easy to hard).Btw, I've mentioned the spreadsheet quite a bit. It has been useful but I
think it's greatest failings have been in the amount of pages to fill out
and the amount of geological knowledge assumed. I don't know or care what
most of the surface types it lists are. It's assumption of one big rock
type per survey is obviously flawed. Personally I don't think it matters
where you prospect on a world at the moment, you can still get all the
known mats the world can yield.
On Jan 1, 2016 6:36 AM, "Robert Wahlström" [email protected]
wrote:Add a may to record prospecting of minerals
And a way to view known planets with minerals you wants
—
Reply to this email directly or view it on GitHub
#43.—
Reply to this email directly or view it on GitHub
#43 (comment)
.—
Reply to this email directly or view it on GitHub.
from eddiscovery.
CREATE TABLE "Objects" ("id" INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL UNIQUE , "SystemName" TEXT NOT NULL , "ObjectName" TEXT NOT NULL , "ObjectType" INTEGER NOT NULL , "Gravity" FLOAT, "Terrain" INTEGER, "C" BOOL, "Fe" BOOL, "Ni" BOOL, "P" BOOL, "S" BOOL, "As" BOOL, "Cr" BOOL, "Ge" BOOL, "Mn" BOOL, "Se" BOOL NOT NULL , "V" BOOL, "Zn" BOOL, "Zr" BOOL, "Cd" BOOL, "Hg" BOOL, "Mo" BOOL, "Nb" BOOL, "Sn" BOOL, "W" BOOL, "Sb" BOOL, "Po" BOOL, "Ru" BOOL, "Tc" BOOL, "Te" BOOL, "Y" BOOL)
Or should we change to int for possible counting? Not that i think we will use it now
from eddiscovery.
Updated with Commander och updatetime.
CREATE TABLE "Objects" ("id" INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL UNIQUE , "SystemName" TEXT NOT NULL , "ObjectName" TEXT NOT NULL , "ObjectType" INTEGER NOT NULL , "Gravity" FLOAT, "Terrain" INTEGER, "C" BOOL, "Fe" BOOL, "Ni" BOOL, "P" BOOL, "S" BOOL, "As" BOOL, "Cr" BOOL, "Ge" BOOL, "Mn" BOOL, "Se" BOOL NOT NULL , "V" BOOL, "Zn" BOOL, "Zr" BOOL, "Cd" BOOL, "Hg" BOOL, "Mo" BOOL, "Nb" BOOL, "Sn" BOOL, "W" BOOL, "Sb" BOOL, "Po" BOOL, "Ru" BOOL, "Tc" BOOL, "Te" BOOL, "Y" BOOL, "Commander" Text, "UpdateTime" DATETIME )
from eddiscovery.
I'd like to suggest that the prospecting tool include planetary rings and asteroid belts. I've contacted gregmalcolm about adding this into EDMaterializer. I have found a number of "Material Content: High" asteroids in some planetary rings where the materials can be mined.
from eddiscovery.
Heh heh, yeah I will not roll out a v5 api interface for EDM at some point to cope with this. It means stars are now prospectable. Although probably doesn't happen much
from eddiscovery.
Is this idea dead in the water?
from eddiscovery.
prospecting part will be dead in water after 2.2 but the viewing of it will
be valid. And we will still send prospecting data from jpournal
somewhere.... Should maybe create a new issue for it
2016-07-30 10:02 GMT+02:00 robbyxp1 [email protected]:
Is this idea dead in the water?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
#43 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJRXLO9FQCI3MmVP7NqJLDWkJ15CoH8Rks5qawUhgaJpZM4G9Zik
.
from eddiscovery.
Superceeded by 2.2 ED
from eddiscovery.
Related Issues (20)
- Null ref exception when clicking "New" on toolbar HOT 1
- The app crashes when I open it HOT 2
- An unhandled fatal exception has occurred. HOT 1
- fatal exception after update to 17.0.2 HOT 4
- Enhancement: Market Data panel and Demand information. HOT 4
- Remember user data location HOT 5
- crash in search tab HOT 2
- Out of Memory Exception Adding system to Exploration HOT 7
- [Enhancement Request] Custom grouping for saved bookmarks. HOT 1
- Unexpected crash on start HOT 2
- Feature request: Make Voice Synthesis options saveable per voice and not global HOT 4
- Sync with EDSM after clearing all data HOT 2
- Strange behaviour after deleteing cmdr HOT 5
- Ramdom jumps when loading to EDSM HOT 4
- Gravity doesn't show properly on organic scans menu HOT 2
- System information not updated after FSD Jump, Scan values tab still show the previous system values HOT 12
- An unhandled fatal exception has occured HOT 2
- Documents text file spam HOT 7
- Error "loadlib failed with error 126" HOT 11
- Crash on scan grid order by class HOT 8
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from eddiscovery.