M
MichaelAtOz
Wed, Nov 29, 2017 9:10 PM
then put all json files in a json subdirectory.
Perhaps a Customiser (debate English/Yank spelling) would be a better
directory name.
And/or configurable like the library paths.
And/or in the same directory (prob better a sub-dir) where the backups go.
??
Admin - PM me if you need anything, or if I've done something stupid...
Unless specifically shown otherwise above, my contribution is in the Public Domain; to the extent possible under law, I have waived all copyright and related or neighbouring rights to this work. Obviously inclusion of works of previous authors is not included in the above.
The TPP is no simple “trade agreement.” Fight it! http://www.ourfairdeal.org/ time is running out!
Sent from: http://forum.openscad.org/
jdawgaz wrote
> then put all json files in a json subdirectory.
Perhaps a Customiser (debate English/Yank spelling) would be a better
directory name.
And/or configurable like the library paths.
And/or in the same directory (prob better a sub-dir) where the backups go.
??
-----
Admin - PM me if you need anything, or if I've done something stupid...
Unless specifically shown otherwise above, my contribution is in the Public Domain; to the extent possible under law, I have waived all copyright and related or neighbouring rights to this work. Obviously inclusion of works of previous authors is not included in the above.
The TPP is no simple “trade agreement.” Fight it! http://www.ourfairdeal.org/ time is running out!
--
Sent from: http://forum.openscad.org/
MS
Mark Schafer
Wed, Nov 29, 2017 9:23 PM
inkscape does this but keeps all the UI json in a single file config.xml
IIRC
But then its extension UI seldom changes
Personally - if the customizer is on - then save the json file - if its
values differ from the original
Then:
- if you don't use the customiser(switched off) - no extra json file
- if you use it occasionally but reset params before final save - no
extra json file
- if you use it - you get scad and matching json file
win/win
On 11/30/2017 10:10 AM, MichaelAtOz wrote:
then put all json files in a json subdirectory.
Perhaps a Customiser (debate English/Yank spelling) would be a better
directory name.
And/or configurable like the library paths.
And/or in the same directory (prob better a sub-dir) where the backups go.
??
Admin - PM me if you need anything, or if I've done something stupid...
Unless specifically shown otherwise above, my contribution is in the Public Domain; to the extent possible under law, I have waived all copyright and related or neighbouring rights to this work. Obviously inclusion of works of previous authors is not included in the above.
The TPP is no simple “trade agreement.” Fight it! http://www.ourfairdeal.org/ time is running out!
Sent from: http://forum.openscad.org/
OpenSCAD mailing list
Discuss@lists.openscad.org
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
This email has been checked for viruses by AVG.
http://www.avg.com
inkscape does this but keeps all the UI json in a single file config.xml
IIRC
But then its extension UI seldom changes
Personally - if the customizer is on - then save the json file - if its
values differ from the original
Then:
- if you don't use the customiser(switched off) - no extra json file
- if you use it occasionally but reset params before final save - no
extra json file
- if you use it - you get scad and matching json file
win/win
On 11/30/2017 10:10 AM, MichaelAtOz wrote:
> jdawgaz wrote
>> then put all json files in a json subdirectory.
> Perhaps a Customiser (debate English/Yank spelling) would be a better
> directory name.
> And/or configurable like the library paths.
> And/or in the same directory (prob better a sub-dir) where the backups go.
> ??
>
>
>
> -----
> Admin - PM me if you need anything, or if I've done something stupid...
>
> Unless specifically shown otherwise above, my contribution is in the Public Domain; to the extent possible under law, I have waived all copyright and related or neighbouring rights to this work. Obviously inclusion of works of previous authors is not included in the above.
>
> The TPP is no simple “trade agreement.” Fight it! http://www.ourfairdeal.org/ time is running out!
> --
> Sent from: http://forum.openscad.org/
>
> _______________________________________________
> OpenSCAD mailing list
> Discuss@lists.openscad.org
> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
>
>
> ---
> This email has been checked for viruses by AVG.
> http://www.avg.com
JD
Jerry Davis
Wed, Nov 29, 2017 9:38 PM
I have hundreds of .scad files scattered around (not only the main openscad
directory), but in many subdirectories as well.
If I would like to keep customizer on, but not have my directory and
subdirectories cluttered with .json files, what then. Not a win-win IMHO.
If .json file really need to exist, what would be the options to NOT
clutter the directories with it? But still provide the functionality needed?
--
Extra Ham Operator: K7AZJ
Registered Linux User: 275424
Raspberry Pi and Openscad developer
The most exciting phrase to hear in science - the one that heralds new
discoveries - is not "Eureka!" but "That's funny...".- Isaac. Asimov
On Wed, Nov 29, 2017 at 2:23 PM, Mark Schafer mschafer@wireframe.biz
wrote:
inkscape does this but keeps all the UI json in a single file config.xml
IIRC
But then its extension UI seldom changes
Personally - if the customizer is on - then save the json file - if its
values differ from the original
Then:
- if you don't use the customiser(switched off) - no extra json file
- if you use it occasionally but reset params before final save - no extra
json file
- if you use it - you get scad and matching json file
win/win
On 11/30/2017 10:10 AM, MichaelAtOz wrote:
then put all json files in a json subdirectory.
Perhaps a Customiser (debate English/Yank spelling) would be a better
directory name.
And/or configurable like the library paths.
And/or in the same directory (prob better a sub-dir) where the backups go.
??
Admin - PM me if you need anything, or if I've done something stupid...
Unless specifically shown otherwise above, my contribution is in the
Public Domain; to the extent possible under law, I have waived all
copyright and related or neighbouring rights to this work. Obviously
inclusion of works of previous authors is not included in the above.
The TPP is no simple “trade agreement.” Fight it!
http://www.ourfairdeal.org/ time is running out!
Sent from: http://forum.openscad.org/
OpenSCAD mailing list
Discuss@lists.openscad.org
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
This email has been checked for viruses by AVG.
http://www.avg.com
I have hundreds of .scad files scattered around (not only the main openscad
directory), but in many subdirectories as well.
If I would like to keep customizer on, but not have my directory and
subdirectories cluttered with .json files, what then. Not a win-win IMHO.
If .json file really need to exist, what would be the options to NOT
clutter the directories with it? But still provide the functionality needed?
--
Extra Ham Operator: K7AZJ
Registered Linux User: 275424
Raspberry Pi and Openscad developer
*The most exciting phrase to hear in science - the one that heralds new
discoveries - is not "Eureka!" but "That's funny...".*- Isaac. Asimov
On Wed, Nov 29, 2017 at 2:23 PM, Mark Schafer <mschafer@wireframe.biz>
wrote:
> inkscape does this but keeps all the UI json in a single file config.xml
> IIRC
> But then its extension UI seldom changes
>
> Personally - if the customizer is on - then save the json file - if its
> values differ from the original
> Then:
> - if you don't use the customiser(switched off) - no extra json file
> - if you use it occasionally but reset params before final save - no extra
> json file
> - if you use it - you get scad and matching json file
>
> win/win
>
>
>
> On 11/30/2017 10:10 AM, MichaelAtOz wrote:
>
>> jdawgaz wrote
>>
>>> then put all json files in a json subdirectory.
>>>
>> Perhaps a Customiser (debate English/Yank spelling) would be a better
>> directory name.
>> And/or configurable like the library paths.
>> And/or in the same directory (prob better a sub-dir) where the backups go.
>> ??
>>
>>
>>
>> -----
>> Admin - PM me if you need anything, or if I've done something stupid...
>>
>> Unless specifically shown otherwise above, my contribution is in the
>> Public Domain; to the extent possible under law, I have waived all
>> copyright and related or neighbouring rights to this work. Obviously
>> inclusion of works of previous authors is not included in the above.
>>
>> The TPP is no simple “trade agreement.” Fight it!
>> http://www.ourfairdeal.org/ time is running out!
>> --
>> Sent from: http://forum.openscad.org/
>>
>> _______________________________________________
>> OpenSCAD mailing list
>> Discuss@lists.openscad.org
>> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
>>
>>
>> ---
>> This email has been checked for viruses by AVG.
>> http://www.avg.com
>>
>
>
> _______________________________________________
> OpenSCAD mailing list
> Discuss@lists.openscad.org
> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
>
TP
Torsten Paul
Wed, Nov 29, 2017 10:13 PM
On 29.11.2017 22:38, Jerry Davis wrote:
If .json file really need to exist, what would be the
options to NOT clutter the directories with it? But
still provide the functionality needed?
It is not supposed to exist in the empty form as shown in the initial post.
ciao,
Torsten.
On 29.11.2017 22:38, Jerry Davis wrote:
> If .json file really need to exist, what would be the
> options to NOT clutter the directories with it? But
> still provide the functionality needed?
>
It is not supposed to exist in the empty form as shown in the initial post.
ciao,
Torsten.
MF
Michael Frey
Thu, Nov 30, 2017 2:07 AM
then put all json files in a json subdirectory.
Perhaps a Customiser (debate English/Yank spelling) would be a better
directory name.
And/or configurable like the library paths.
configurable sounds good, until you start sharing designs reallying on
presets.
One example would be the literal examples that come with openscad.
A compromise would be, that openscad is always looking for the json file
in the same path as the scad file.
If it exists, use that. If not, look in the user configurable path. If
not, create the json file in the user configurable path.
(a "load/select preset" button opening a file dialog to select a json
file would resolve issues when users us a different configurable path,
but share designs)
And/or in the same directory (prob better a sub-dir) where the backups go.
??
How would you plan on handling presets for scad files with the same file
name in different folders?
(off course, if it is just stored there as a back up, it would not matter)
with kind regards,
Michael Frey
MichaelAtOz wrote
> jdawgaz wrote
>> then put all json files in a json subdirectory.
> Perhaps a Customiser (debate English/Yank spelling) would be a better
> directory name.
> And/or configurable like the library paths.
configurable sounds good, until you start sharing designs reallying on
presets.
One example would be the literal examples that come with openscad.
A compromise would be, that openscad is always looking for the json file
in the same path as the scad file.
If it exists, use that. If not, look in the user configurable path. If
not, create the json file in the user configurable path.
(a "load/select preset" button opening a file dialog to select a json
file would resolve issues when users us a different configurable path,
but share designs)
> And/or in the same directory (prob better a sub-dir) where the backups go.
> ??
How would you plan on handling presets for scad files with the same file
name in different folders?
(off course, if it is just stored there as a back up, it would not matter)
with kind regards,
Michael Frey
TP
Torsten Paul
Thu, Nov 30, 2017 9:55 AM
On 30.11.2017 03:07, Michael Frey wrote:
A compromise would be, that openscad is always looking for
the json file in the same path as the scad file.
If it exists, use that. If not, look in the user configurable
path. If not, create the json file in the user configurable path.
(a "load/select preset" button opening a file dialog to select
a json file would resolve issues when users us a different
configurable path, but share designs)
It's additional data that belongs to the model file itself.
I think putting that in random other locations is not a good
idea. Right now, there is no cross platform support for
storing additional meta data related to a file.
Currently the file is generated always if the Customizer
is enabled. That's a bug and will be fixed eventually (once
someone finds the time to work on that... it's still an
experimental feature.).
We may not need to create a huge complicated logic including
extra UI and configuration just to hide a file which is
mostly not there in the first place once the bug is fixed.
Basically what Mark said earlier.
ciao,
Torsten.
On 30.11.2017 03:07, Michael Frey wrote:
> A compromise would be, that openscad is always looking for
> the json file in the same path as the scad file.
> If it exists, use that. If not, look in the user configurable
> path. If not, create the json file in the user configurable path.
> (a "load/select preset" button opening a file dialog to select
> a json file would resolve issues when users us a different
> configurable path, but share designs)
>
It's additional data that belongs to the model file itself.
I think putting that in random other locations is not a good
idea. Right now, there is no *cross platform* support for
storing additional meta data related to a file.
Currently the file is generated always if the Customizer
is enabled. That's a bug and will be fixed eventually (once
someone finds the time to work on that... it's still an
experimental feature.).
We may not need to create a huge complicated logic including
extra UI and configuration just to hide a file which is
mostly not there in the first place once the bug is fixed.
Basically what Mark said earlier.
ciao,
Torsten.
MF
Michael Frey
Thu, Nov 30, 2017 6:04 PM
Currently the file is generated always if the Customizer
is enabled. That's a bug and will be fixed eventually (once
someone finds the time to work on that... it's still an
experimental feature.).
Torsten Paul wrote:
> Currently the file is generated always if the Customizer
> is enabled. That's a bug and will be fixed eventually (once
> someone finds the time to work on that... it's still an
> experimental feature.).
Well, let us see if that fixes the discussion:
https://github.com/openscad/openscad/pull/2207
With kind regards,
Michael Frey
M
macdarren
Thu, Nov 30, 2017 6:45 PM
I'd like to suggest that we do not have a separate json file at all unless
there is some project mechanism for keeping it together with the .scad file
and the .stl and any other files needed or generated.
Since I think that would overly complicate things and building a full IDE is
probably not the plan,
how about just add customizer information to the foot of the scad
file...either a single line identifier like
used for comments or maybe a separate section with a header and footer
identifier to specify this info is for customizer and should generally not
be changed by the programmer directly.
In general like to use a customizer for some of my designs, especially those
I share. I would hate to loose or have end users loose custom
configurations they spend time setting up because some file was separated or
worse invisible and separated. Having deal with two 'source' files is a
problem for many novice users...many don't keep the output files (if then
are able to regenerate them quickly) so having them separated is not as big
an issue....
--
Sent from: http://forum.openscad.org/
I'd like to suggest that we do not have a separate json file at all unless
there is some project mechanism for keeping it together with the .scad file
and the .stl and any other files needed or generated.
Since I think that would overly complicate things and building a full IDE is
probably not the plan,
how about just add customizer information to the foot of the scad
file...either a single line identifier like
used for comments or maybe a separate section with a header and footer
identifier to specify this info is for customizer and should generally not
be changed by the programmer directly.
In general like to use a customizer for some of my designs, especially those
I share. I would hate to loose or have end users loose custom
configurations they spend time setting up because some file was separated or
worse invisible and separated. Having deal with two 'source' files is a
problem for many novice users...many don't keep the output files (if then
are able to regenerate them quickly) so having them separated is not as big
an issue....
--
Sent from: http://forum.openscad.org/
T
TLC123
Fri, Dec 1, 2017 5:52 AM
I concur.
--
Sent from: http://forum.openscad.org/
CC
Chris Camacho
Fri, Dec 1, 2017 10:13 AM
I've been thinking about this since the thread started and while I'm no
over bothered myself about an extra file being "untidy" I can see them
getting separated - especially by a less technical user (isn't this for
the customiser for the less technical)
Someone mentioned about putting the info in comments, I can see some
people baulking at this but its not as bad as it sounds, and you could
go further and directly embed it into the command set
either way, splitting one thing (and it is really) into two files,
really isn't going to benefit the code blind, and is going to irritate
the OCD, have you seen the crap that some games do to MY home directory!
I've been thinking about this since the thread started and while I'm no
over bothered myself about an extra file being "untidy" I can see them
getting separated - especially by a less technical user (isn't this for
the customiser for the less technical)
Someone mentioned about putting the info in comments, I can see some
people baulking at this but its not as bad as it sounds, and you could
go further and directly embed it into the command set
either way, splitting one thing (and it is really) into two files,
really isn't going to benefit the code blind, and is going to irritate
the OCD, have you seen the crap that some games do to MY home directory!
