Page 1 of 1

[TOOL]Schematic Creator v1

PostPosted: Mon Dec 11, 2017 19:26
by LMD
Schematic Creator v1

A small, easy to execute Java application for creating schematics from blueprints.
Made by me to help you to create complex shapes.

Screenshots :

+ Screenshots


Features :

+ Features


Changelog :

+ Changelog


Instructions :

+ Instructions

License :

+ License


Download :

Schematic_Creator.zip
(22.33 KiB) Downloaded 73 times


GitHub/Source :

Application


Please contact me if you find any bug.
Ideas for other helpful applications are also welcome.
Feel free to post your .anl and .ams here.
Leave a reply if you want to be informed about updates.

Re: [TOOL]Schematic Creator v1

PostPosted: Wed Dec 13, 2017 01:23
by Wuzzy
License :

(1) You may not apply reverse engineering, if I don't give you permission to.
(2) You may not fork, modify or distribute the application without explicit permission of the copyright holder(me).
(3) You may not sell or share/release this application under your name.
(4) That means you are allowed to share it if you do not claim it as yours.
(5) In general, you may not do anything excepting for regular use of this application without my permission.


Why?

Re: [TOOL]Schematic Creator v1

PostPosted: Wed Dec 13, 2017 03:37
by GreenDimond
Wuzzy wrote:
License :

(1) You may not apply reverse engineering, if I don't give you permission to.
(2) You may not fork, modify or distribute the application without explicit permission of the copyright holder(me).
(3) You may not sell or share/release this application under your name.
(4) That means you are allowed to share it if you do not claim it as yours.
(5) In general, you may not do anything excepting for regular use of this application without my permission.


Why?

Yes, why? That is in violation of the forum TOS, right?

Re: [TOOL]Schematic Creator v1

PostPosted: Wed Dec 13, 2017 13:10
by LMD
@Wuzzy, @GreenDimond :
In general, every point says you need my permission for havin' a look at the source(Java is compiled!). But I have to admit that I may have to change some points. Make some suggestions, please ! And give reasons for them, of course !

Re: [TOOL]Schematic Creator v1

PostPosted: Wed Dec 13, 2017 13:30
by Wuzzy
That doesn't really explain why. :P

Basically, your license is draconian. For example, demanding us to not fork, ever is, well, not nice.
Asking us to not even look at the source code … hmm, I don't know if this is even legal (I am not a lawyer.).
Why do you think it is wrong to do these things you have forbidden? (This was a serious question.)

And you're posting this in a forum with a lot of free software zealots. ;-) Note that almost all software in these forums is free software. Many of use believe that sharing, forking, changing code are basic freedoms that everone should have. If everyone here would deny me or you these freedoms, it would be a much more hostile place, in which everyone basically just works for oneself. No code could be reused, everyone would be forced to do everything from scratch. Collaboration would be limited to discussion only. Frankly, I don't want this kind of “community”.

Basically I'm asking you to please show some respect to our community by choosing a free software license.
https://www.gnu.org/philosophy/free-sw.html

As practical matter, I also recommend to not write your own license (like you did), but instead choose an existing one.
https://choosealicense.com/

The reason is that existing licenses have been tried and tested for a long time and written by people who understand these things much better than we do.

Re: [TOOL]Schematic Creator v1

PostPosted: Wed Dec 13, 2017 14:02
by ExeterDad
No one in their right mind will run that code not knowing what's going on behind the scenes. Unless they like rolling dice.

Re: [TOOL]Schematic Creator v1

PostPosted: Wed Dec 13, 2017 14:30
by LMD
@ExeterDad : How many applications have you already installed ? 3 ? 10 ? 101 ? Have you taken a look at the whole source ? I am sure that there's at least one backdoor, used by a secret service, in your OS. Also, you must simply trust me that I am not uploading viruses. Consider : Why should I post it here, in a small forum ? Minecraft is way bigger ! There are so many places to release trojans, which are much more popular then this tiny forum ! Still not convinced ? If you want to, I can show you the NetBeans-Project...

Re: [TOOL]Schematic Creator v1

PostPosted: Wed Dec 13, 2017 14:33
by TumeniNodes
Someone could have simply "asked" for the permissions, as stated. It seems as though the author is open to making changes in regards to the restrictions.

I will ad, however, if this is not code one plans to market and distribute for financial gain, then why so strict on licensing and/or permissions?
Although, it could just be that the author has put some considerable time and effort into this code, and does not wish someone else to turn around, take it, and use it for financial gain themselves (which does happen IRL)

I do think in some cases in the free/opensource software world, there are times when people need to make some exceptions when it comes to code license.
If something truly amazing were to be offered, which added some truly spectacular, or long awaited feature, yet the author wanted to protect their code from being taken by someone else, to make money with..., I am one who would be perfectly comfortable with a "No Commercial" use/gain license.

https://creativecommons.org/licenses/by-nc-sa/3.0/
I honestly feel the above license (check as there may be an updated version) should not be completely unacceptable within this community.
The reason is, as I explained. What if someone were able to give us certain features, such as the type of shaders many have voiced they would love to see, yet the author did not wish to release it without some protection?
The only downside, is code that may become deprecated and useless over time, if the author leaves the community or, fails to keep it updated with changes in development.
But, this could easily be addressed prior to release, under an agreement with developers that, if the author were to ever leave the community, etc., then code will need to be transfered to the community, but still remain under the same license, for reasons of maint.

If not, then the code might be considered already deprecated from the beginning, and therefore, useless to anyone from the start.

So LMD, please consider the above license. This way the code can be viewable, yet can also be under the protection you desire commercially. And then you may need to speak with the dev teams to look it over for release?

Re: [TOOL]Schematic Creator v1

PostPosted: Wed Dec 13, 2017 15:44
by LMD
Source published !

Re: [TOOL]Schematic Creator v1

PostPosted: Wed Dec 13, 2017 15:56
by Wuzzy
Thank you. :-)

Re: [TOOL]Schematic Creator v1

PostPosted: Mon Dec 25, 2017 11:32
by Linuxdirk
LMD wrote:application for creating schematics from blueprints.

I wish it was possible the other way round so I’d get blueprints from a schematic file :)

Re: [TOOL]Schematic Creator v1

PostPosted: Mon Dec 25, 2017 14:33
by LMD
Linuxdirk wrote:
LMD wrote:application for creating schematics from blueprints.

I wish it was possible the other way round so I’d get blueprints from a schematic file :)

That is not easily possible using mts files, and .we files are way to big, so I invented .ams, but currently, there's no Exporter excepting this application.

Re: [TOOL]Schematic Creator v1

PostPosted: Mon Dec 25, 2017 20:08
by Sokomine
LMD wrote:
Linuxdirk wrote: I wish it was possible the other way round so I’d get blueprints from a schematic file :)

That is not easily possible using mts files, and .we files are way to big, so I invented .ams, but currently, there's no Exporter excepting this application.

Both the .we and .mts file format are sufficiently documented. Reading .mts files is admittedly a bit more work. The .mts file format also supports probability, but that's more for mapgen and not for more or less static schematics and can mostly be ignored. The mapblocks stored in the database follow a very similar data structure. There are several external programs in several languages which can read at least the map file format. I'm not sure if it has already been done in Java. What advantages does your new .ams file format have?

Re: [TOOL]Schematic Creator v1

PostPosted: Tue Dec 26, 2017 11:07
by LMD
Sokomine wrote:
LMD wrote:
Linuxdirk wrote: I wish it was possible the other way round so I’d get blueprints from a schematic file :)

That is not easily possible using mts files, and .we files are way to big, so I invented .ams, but currently, there's no Exporter excepting this application.

Both the .we and .mts file format are sufficiently documented. Reading .mts files is admittedly a bit more work. The .mts file format also supports probability, but that's more for mapgen and not for more or less static schematics and can mostly be ignored. The mapblocks stored in the database follow a very similar data structure. There are several external programs in several languages which can read at least the map file format. I'm not sure if it has already been done in Java. What advantages does your new .ams file format have?


Advantages :
- human readable & writable
- smaller than .we
- can be easily edited

Re: [TOOL]Schematic Creator v1

PostPosted: Tue Dec 26, 2017 11:24
by LMD
.ams file format specifications :
Dimensions
2 2 2
Nodes
default:air, default:dirt
Schematic
1|0
0|1
0|1
1|0

Code: Select all
Dimensions
<width> <height> <length>
Nodes
default:air, default:dirt, <other used node>, <another used node>, <etc...>
Schematic
                              (Y : 0)

           (X : 0)                                    (X : 1)
(Z : 0) <n Node in enumeration>|0-> default:air                         ( -> row, x-Coordinates changing)
(Z : 1) 0-> default:air|1-> default:dirt                                             (-> columns : z-Coordinates)
-                                                                                              (Means new layer)
                              (Y : 1)

           (X : 0)                         (X : 1)
(Z : 0) 0-> default:air|1-> default:dirt
(Z : 1) 1-> default:dirt|0-> default:air

Works like a table, 'eh.