J
jon
Sat, Sep 10, 2016 3:13 PM
I just bumped into a guy who might be a prime candidate for OS, but he
needs gently curved, graceful shapes. I fear that he will wander off
quickly if I cannot show him Bezier libraries and the like. I see LOTS
of creative stuff on this forum, but often loose track of where I heard
of something.
Do we have a single repository for all things OS? The actual code need
not live there, so long as links to the actual code are present. I would
like to be able to quickly respond to his needs so that he joins us.
Jon
I just bumped into a guy who might be a prime candidate for OS, but he
needs gently curved, graceful shapes. I fear that he will wander off
quickly if I cannot show him Bezier libraries and the like. I see LOTS
of creative stuff on this forum, but often loose track of where I heard
of something.
Do we have a single repository for all things OS? The actual code need
not live there, so long as links to the actual code are present. I would
like to be able to quickly respond to his needs so that he joins us.
Jon
M
MichaelAtOz
Sat, Sep 10, 2016 11:32 PM
It's not well maintained but there is the list at the bottom of this manual
page https://en.wikibooks.org/wiki/OpenSCAD_User_Manual/Libraries .
Historically much code has been listed as Things on Thingiverse, but the
prusa dummy spit seems to have diversified that.
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!
View this message in context: http://forum.openscad.org/library-and-code-repository-tp18354p18361.html
Sent from the OpenSCAD mailing list archive at Nabble.com.
It's not well maintained but there is the list at the bottom of this manual
page <https://en.wikibooks.org/wiki/OpenSCAD_User_Manual/Libraries> .
Historically much code has been listed as Things on Thingiverse, but the
prusa dummy spit seems to have diversified that.
-----
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!
--
View this message in context: http://forum.openscad.org/library-and-code-repository-tp18354p18361.html
Sent from the OpenSCAD mailing list archive at Nabble.com.
J
jon
Sun, Sep 11, 2016 2:46 PM
Perhaps we can encourage everyone on this list to provide a copy of
their work on this list, either directly, or as links to (say)
Thingiverse items. One stop shopping. Same thing for useful code
fragments.
Jon
On 9/10/2016 7:32 PM, MichaelAtOz wrote:
Perhaps we can encourage everyone on this list to provide a copy of
their work on this list, either directly, or as links to (say)
Thingiverse items. One stop shopping. Same thing for useful code
fragments.
Jon
On 9/10/2016 7:32 PM, MichaelAtOz wrote:
> It's not well maintained but there is the list at the bottom of this manual
> page <https://en.wikibooks.org/wiki/OpenSCAD_User_Manual/Libraries> .
> Historically much code has been listed as Things on Thingiverse, but the
> prusa dummy spit seems to have diversified that.
>
>
>
> -----
> 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!
> --
> View this message in context: http://forum.openscad.org/library-and-code-repository-tp18354p18361.html
> Sent from the OpenSCAD mailing list archive at Nabble.com.
>
> _______________________________________________
> OpenSCAD mailing list
> Discuss@lists.openscad.org
> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2016.0.7752 / Virus Database: 4649/12986 - Release Date: 09/10/16
MS
Mark Schafer
Sun, Sep 11, 2016 9:11 PM
Or an 'offical' github account that could then fork (and thereby
reference) all the useful libs.
- so anyone going to that top level "openscad group" account can see all
the repositories that contain useful code
- a group of people who belong to that group determine which libs are
forked. (and thereby judge which is currently "useful" to the released
version of openSCAD.
- I woudl suggest the group did no pwork or create pull requests themselves.
Many similar examples on github currrently.
People are also discussing GitLab instead of Github but I don't have
enough info to suggest which is "better"
On 9/12/2016 2:46 AM, jon wrote:
Perhaps we can encourage everyone on this list to provide a copy of
their work on this list, either directly, or as links to (say)
Thingiverse items. One stop shopping. Same thing for useful code
fragments.
Jon
On 9/10/2016 7:32 PM, MichaelAtOz wrote:
Or an 'offical' github account that could then fork (and thereby
reference) all the useful libs.
- so anyone going to that top level "openscad group" account can see all
the repositories that contain useful code
- a group of people who belong to that group determine which libs are
forked. (and thereby judge which is currently "useful" to the released
version of openSCAD.
- I woudl suggest the group did no pwork or create pull requests themselves.
Many similar examples on github currrently.
People are also discussing GitLab instead of Github but I don't have
enough info to suggest which is "better"
On 9/12/2016 2:46 AM, jon wrote:
> Perhaps we can encourage everyone on this list to provide a copy of
> their work on this list, either directly, or as links to (say)
> Thingiverse items. One stop shopping. Same thing for useful code
> fragments.
>
> Jon
>
>
> On 9/10/2016 7:32 PM, MichaelAtOz wrote:
>> It's not well maintained but there is the list at the bottom of this
>> manual
>> page <https://en.wikibooks.org/wiki/OpenSCAD_User_Manual/Libraries> .
>> Historically much code has been listed as Things on Thingiverse, but the
>> prusa dummy spit seems to have diversified that.
>>
>>
>>
>> -----
>> 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!
>> --
>> View this message in context:
>> http://forum.openscad.org/library-and-code-repository-tp18354p18361.html
>> Sent from the OpenSCAD mailing list archive at Nabble.com.
>>
>> _______________________________________________
>> OpenSCAD mailing list
>> Discuss@lists.openscad.org
>> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
>>
>>
>> -----
>> No virus found in this message.
>> Checked by AVG - www.avg.com
>> Version: 2016.0.7752 / Virus Database: 4649/12986 - Release Date:
>> 09/10/16
>
>
> _______________________________________________
> OpenSCAD mailing list
> Discuss@lists.openscad.org
> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2016.0.7752 / Virus Database: 4649/12991 - Release Date:
> 09/11/16
TP
Torsten Paul
Sun, Sep 11, 2016 9:30 PM
I think the main thing is not the technical part, it's people
having the time and motivation to do that.
If that's there, the initial project could be just based on the
existing wiki page and then start to looking for better technical
solutions.
I still believe http://thingtracker.net/ would be a cool system
to have.
ciao,
Torsten.
I think the main thing is not the technical part, it's people
having the time and motivation to do that.
If that's there, the initial project could be just based on the
existing wiki page and then start to looking for better technical
solutions.
I still believe http://thingtracker.net/ would be a cool system
to have.
ciao,
Torsten.
JL
Jean-Paul Louis
Mon, Sep 12, 2016 1:22 AM
I agree with Torsten.
wiki pages could do the trick with a well organized FAQ with code examples.
Could be called OpenSCAD Tips and Tricks.
Jean-Paul
N1JPL
I agree with Torsten.
wiki pages could do the trick with a well organized FAQ with code examples.
Could be called OpenSCAD Tips and Tricks.
Jean-Paul
N1JPL
> On Sep 11, 2016, at 5:30 PM, Torsten Paul <Torsten.Paul@gmx.de> wrote:
>
> I think the main thing is not the technical part, it's people
> having the time and motivation to do that.
>
> If that's there, the initial project could be just based on the
> existing wiki page and then start to looking for better technical
> solutions.
>
> I still believe http://thingtracker.net/ would be a cool system
> to have.
>
> ciao,
> Torsten.
>
>
> _______________________________________________
> OpenSCAD mailing list
> Discuss@lists.openscad.org
> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
R
runsun
Tue, Sep 13, 2016 4:17 PM
Perhaps we can encourage everyone on this list to provide a copy of
their work on this list
Have been doing this with my signature.
$ Runsun Pan, PhD $ libs: doctest , faces ( git ), offline doc ( git ), runscad.py ( 2 , git ), synwrite ( 2 ); $ tips: hash ( 2 ), matrix ( 2 , 3 ), sweep ( 2 ), var ( 2 ), lerp , animation ( gif , prodVid , animlib ), precision ( 2 ), xl-control , type , rounded polygon , chfont , tailRecur ( 2, 3 ), isosphere ( 2 ), area , vol/center , RGB , CurvedImg ; $ Apps: rollApp , blockscad , openjscad , on AWS ( pdf )
View this message in context: http://forum.openscad.org/library-and-code-repository-tp18354p18386.html
Sent from the OpenSCAD mailing list archive at Nabble.com.
jon_bondy wrote
> Perhaps we can encourage everyone on this list to provide a copy of
> their work on this list
Have been doing this with my signature.
-----
$ Runsun Pan, PhD $ libs: doctest , faces ( git ), offline doc ( git ), runscad.py ( 2 , git ), synwrite ( 2 ); $ tips: hash ( 2 ), matrix ( 2 , 3 ), sweep ( 2 ), var ( 2 ), lerp , animation ( gif , prodVid , animlib ), precision ( 2 ), xl-control , type , rounded polygon , chfont , tailRecur ( 2, 3 ), isosphere ( 2 ), area , vol/center , RGB , CurvedImg ; $ Apps: rollApp , blockscad , openjscad , on AWS ( pdf )
--
View this message in context: http://forum.openscad.org/library-and-code-repository-tp18354p18386.html
Sent from the OpenSCAD mailing list archive at Nabble.com.
RU
Richard Urwin
Tue, Sep 13, 2016 11:24 PM
Perhaps we can encourage everyone on this list to provide a copy of
their work on this list
Have been doing this with my signature.
Yeah, but it doesn't give me at least (an extreme newbie) the slightest idea
what most of them do.
To my mind this sort of thing has to be wrapped in a write-up. The Design
Pattern format is a good template:
Pattern Name and Classification: A descriptive and unique name that
helps in identifying and referring to the pattern.
Intent: A description of the goal behind the pattern and the reason for
using it.
Also Known As: Other names for the pattern.
Motivation (Forces): A scenario consisting of a problem and a context in
which this pattern can be used.
Applicability: Situations in which this pattern is usable; the context
for the pattern.
Structure: A graphical representation of the pattern. Class diagrams and
Interaction diagrams may be used for this purpose.
Consequences: A description of the results, side effects, and trade offs
caused by using the pattern.
Implementation: A description of an implementation of the pattern; the
solution part of the pattern.
Sample Code: An illustration of how the pattern can be used in a
programming language.
Known Uses: Examples of real usages of the pattern.
Related Patterns: Other patterns that have some relationship with the
pattern; discussion of the differences between the pattern and similar
patterns.
For example:
https://www.gov.uk/service-manual/user-centred-design/resources/patterns/names.html
Also, if this doesn't get into the OpenSCAD Wiki, then wikidot.com would be
a good home for it. It's free to set up a new site (some subtle advertising)
and it allows powerful site design using only the wiki syntax. Also sections
of code quoted in a post have their own direct link, making downloading the
code very easy. The only thing it doesn't do as well as git is version
control.
--
View this message in context: http://forum.openscad.org/library-and-code-repository-tp18354p18387.html
Sent from the OpenSCAD mailing list archive at Nabble.com.
runsun wrote
>
> jon_bondy wrote
>> Perhaps we can encourage everyone on this list to provide a copy of
>> their work on this list
> Have been doing this with my signature.
Yeah, but it doesn't give me at least (an extreme newbie) the slightest idea
what most of them do.
To my mind this sort of thing has to be wrapped in a write-up. The Design
Pattern format is a good template:
Pattern Name and Classification: A descriptive and unique name that
helps in identifying and referring to the pattern.
Intent: A description of the goal behind the pattern and the reason for
using it.
Also Known As: Other names for the pattern.
Motivation (Forces): A scenario consisting of a problem and a context in
which this pattern can be used.
Applicability: Situations in which this pattern is usable; the context
for the pattern.
Structure: A graphical representation of the pattern. Class diagrams and
Interaction diagrams may be used for this purpose.
Consequences: A description of the results, side effects, and trade offs
caused by using the pattern.
Implementation: A description of an implementation of the pattern; the
solution part of the pattern.
Sample Code: An illustration of how the pattern can be used in a
programming language.
Known Uses: Examples of real usages of the pattern.
Related Patterns: Other patterns that have some relationship with the
pattern; discussion of the differences between the pattern and similar
patterns.
For example:
https://www.gov.uk/service-manual/user-centred-design/resources/patterns/names.html
Also, if this doesn't get into the OpenSCAD Wiki, then wikidot.com would be
a good home for it. It's free to set up a new site (some subtle advertising)
and it allows powerful site design using only the wiki syntax. Also sections
of code quoted in a post have their own direct link, making downloading the
code very easy. The only thing it doesn't do as well as git is version
control.
--
View this message in context: http://forum.openscad.org/library-and-code-repository-tp18354p18387.html
Sent from the OpenSCAD mailing list archive at Nabble.com.
R
Ronaldo
Thu, Sep 15, 2016 7:32 PM
I also agree with Torsten about a code repository. We would need a voluntary
to do or, at least, start the hard job.
However, I think that a chapter in the OpenSCAD Manual could comply with the
demand for Tips and Tricks without much effort. It could have a basic,
medium and advanced sections. The basic section should be recommended for
all beginners in other parts of the Manual. I would contribute on that if
such chapter is created and I believe many of the advanced users would do
the same.
--
View this message in context: http://forum.openscad.org/library-and-code-repository-tp18354p18390.html
Sent from the OpenSCAD mailing list archive at Nabble.com.
I also agree with Torsten about a code repository. We would need a voluntary
to do or, at least, start the hard job.
However, I think that a chapter in the OpenSCAD Manual could comply with the
demand for Tips and Tricks without much effort. It could have a basic,
medium and advanced sections. The basic section should be recommended for
all beginners in other parts of the Manual. I would contribute on that if
such chapter is created and I believe many of the advanced users would do
the same.
--
View this message in context: http://forum.openscad.org/library-and-code-repository-tp18354p18390.html
Sent from the OpenSCAD mailing list archive at Nabble.com.
R
runsun
Fri, Sep 16, 2016 9:38 PM
Yeah, but it doesn't give me at least (an extreme newbie) the slightest
idea what most of them do.
To my mind this sort of thing has to be wrapped in a write-up.
Well, life is not perfect :( At least, I've started it long time ago.
$ Runsun Pan, PhD $ libs: doctest , faces ( git ), offline doc ( git ), runscad.py ( 2 , git ), synwrite ( 2 ); $ tips: hash ( 2 ), matrix ( 2 , 3 ), sweep ( 2 , 3 ), var ( 2 ), lerp , animation ( gif , prodVid , animlib ), precision ( 2 ), xl-control , type , rounded polygon , chfont , tailRecur ( 2, 3 ), isosphere ( 2 ), area , vol/center , RGB , CurvedImg ; $ Apps: rollApp , blockscad , openjscad , on AWS ( pdf )
View this message in context: http://forum.openscad.org/library-and-code-repository-tp18354p18395.html
Sent from the OpenSCAD mailing list archive at Nabble.com.
Richard Urwin wrote
> Yeah, but it doesn't give me at least (an extreme newbie) the slightest
> idea what most of them do.
>
> To my mind this sort of thing has to be wrapped in a write-up.
Well, life is not perfect :( At least, I've started it long time ago.
-----
$ Runsun Pan, PhD $ libs: doctest , faces ( git ), offline doc ( git ), runscad.py ( 2 , git ), synwrite ( 2 ); $ tips: hash ( 2 ), matrix ( 2 , 3 ), sweep ( 2 , 3 ), var ( 2 ), lerp , animation ( gif , prodVid , animlib ), precision ( 2 ), xl-control , type , rounded polygon , chfont , tailRecur ( 2, 3 ), isosphere ( 2 ), area , vol/center , RGB , CurvedImg ; $ Apps: rollApp , blockscad , openjscad , on AWS ( pdf )
--
View this message in context: http://forum.openscad.org/library-and-code-repository-tp18354p18395.html
Sent from the OpenSCAD mailing list archive at Nabble.com.