<InPhase>
Larinioides: ^ Use those if you need to give a more complete example of the problem.
To_Aru_Shiroi_Ne has quit [Ping timeout: 244 seconds]
ToAruShiroiNeko has joined #openscad
stealth_ has joined #openscad
GNUmoon has quit [Ping timeout: 264 seconds]
Guest513 is now known as buZz
mmu_man has joined #openscad
GNUmoon has joined #openscad
mmu_man has quit [Ping timeout: 244 seconds]
L29Ah has left #openscad [#openscad]
L29Ah has joined #openscad
krushia has quit [Remote host closed the connection]
krushia has joined #openscad
fling has quit [Read error: Connection reset by peer]
GNUmoon has quit [Remote host closed the connection]
fling has joined #openscad
GNUmoon has joined #openscad
snaked has quit [Quit: Leaving]
GNUmoon has quit [Ping timeout: 264 seconds]
GNUmoon has joined #openscad
mmu_man has joined #openscad
guso78k has joined #openscad
<guso78k>
kintel, I don't consider the quotes perfect either, but I need concept to mark arbritary numbers in the code, which are free from errors and are not eaten by the parser. Quotes were almost perfect for that purpose and its even possible to encode more information into it.
L29Ah has quit [Ping timeout: 260 seconds]
guest96 has joined #openscad
guest96 has quit [Client Quit]
snaked has joined #openscad
TheMaker has quit [Quit: Konversation terminated!]
Guest12 has joined #openscad
Guest12 has quit [Client Quit]
kintel has joined #openscad
<kintel>
guso78k Why not mark it using UI? right-click on a number, do some initial contextual analysis, and let users choose editing method
<kintel>
Editing methods could be a simple angle; constrained rotation, or potentially a transformation editing overlay
<kintel>
IMO, text shouldn't be "abused" for UI features
<kintel>
But the only way to figure out may be to prototype it further and play around with it (in experimental mode if needed to merge)
<kintel>
In general, I feel that our UI code is getting a bit out of hand, and at some point, we may want to clean up the internal interfaces a bit, to make it more maintainable. In particular, it's risky to change UI today as we don't have any structured (automated or manual) strategies for testing the UI
<kintel>
Just from the last year's worth of experience, it feels like feature work in the UI space tends to be pretty expensive, where I'd guess 70-80% of the time going into refactoring/cleanup
<guso78k>
kintel, this is actually an adavantage of SCAD over python: you can define the language yourself. and you could define cursor positions in the UI , which could be recognized again in the parser.y
<guso78k>
that something which is not so easy in the python parser.
<kintel>
Yeah, it's a strength, but just because it's easy doesn't mean we should do it :)
<kintel>
Consider what happens if you save the file, and now you have some hidden value somewhere messing up your design..
<guso78k>
to get this done, i have actually written a small brother of GeometryEvaluator.cc and have inversed all the transformations back to the primitives
<kintel>
Our special characters for highlighting/debugging is already questionable, IMO, but we added them and now we have to keep supporting it.
<guso78k>
actually i just found a pythonic way to do the same without misusing strings. i consider changing to the new concept
<guso78k>
you mean the 0x03 character which sits between the scad code and the -D commandline parameters ?
<kintel>
Once you pull out the literals into variables, you could annotate and do all kinds of fun stuff in python :)
<kintel>
uh, I didn't know there was such a character : /
<kintel>
I meant the #, % helpers
<guso78k>
there is such a 0x03 , just grep in openscad.cc. i have been wondering several years about the purpose, but dont dare to change it ;)
L29Ah has joined #openscad
<guso78k>
the # % helpers are an great addition and it would not be openscad without :)
<guso78k>
of course my interactive dragging is far from perfect, but without implementing trials it would be much harder to test-drive the idea and find good/bad issues about it.
<kintel>
Yeah, building a feature and controlling it behind an experimental flag can be a good way forward
<kintel>
..or even a build-time macro if it's extra experimental
TheAssassin has quit [Remote host closed the connection]
teepee has quit [Remote host closed the connection]
aiyion has quit [Remote host closed the connection]
fling has quit [Remote host closed the connection]
TheAssassin has joined #openscad
fling has joined #openscad
aiyion has joined #openscad
teepee has joined #openscad
fling has quit [Remote host closed the connection]
aiyion has quit [Remote host closed the connection]
TheAssassin has quit [Remote host closed the connection]
GNUmoon has quit [Remote host closed the connection]
teepee has quit [Remote host closed the connection]
TheAssassin has joined #openscad
aiyion has joined #openscad
fling has joined #openscad
GNUmoon has joined #openscad
teepee has joined #openscad
mmu_man has quit [Ping timeout: 248 seconds]
kintel has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
mmu_man has joined #openscad
L29Ah has left #openscad [#openscad]
snaked has quit [Quit: Leaving]
<pca006132>
kintel: btw, so openscad is not tested with the latest cmake version right?
<pca006132>
because iirc we copied the rpath thing from openscad :P
<pca006132>
and indeed it seems to be caused by cmake 4.0, I guess they changed how rpath is set
mmu_man has quit [Ping timeout: 246 seconds]
teepee has quit [Quit: bye...]
teepee has joined #openscad
linext has joined #openscad
<guso78k>
kintel, i have a hard time to understand: "Once you pull out the literals into variables, you could annotate and do all kinds of fun stuff in python", while i feel, its important to me
mmu_man has joined #openscad
L29Ah has joined #openscad
kintel has joined #openscad
<kintel>
pca006132 Yeah, all our builders are on CMake 3. I expect Homebrew on macOS to be the first one to upgrade, so I'll need to sort it out when that happens.
<kintel>
guso78k I meant "decorators" not annotations. It feels like python decorators would be an elegant way of tagging stuff for the GUI
<kintel>
( my Python skills are many years out of date :/ )
<guso78k>
kintel, i recently really learned the decorators. they are really cool stuff, but you can only apply them on functions definitions(and alter them). nothing else: not variables, not constants, not function calls
<guso78k>
and yes i could make a function like
<guso78k>
def _(number_val)
<guso78k>
which would return a custom type, with just the number inside. but it would be good enough to distignuish the number from a bare number and consider it selected
<kintel>
right, decorators are really just higher order functions; you'd need to wrap the variable somehow.
<guso78k>
BYW pythonscad also owns an decorator. it can convert the function result of a build123d object (cadquery) into openscad world
dTal is now known as robottom
robottom is now known as dTal
kintel has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
PaulWay has joined #openscad
snaked has joined #openscad
PaulWay has quit [Ping timeout: 244 seconds]
L29Ah has left #openscad [#openscad]
linext has quit [Quit: Client closed]
PaulWay has joined #openscad
stefanct has quit [Ping timeout: 268 seconds]
stefanct has joined #openscad
L29Ah has joined #openscad
aiyion has quit [Ping timeout: 264 seconds]
aiyion has joined #openscad
stealth_ has quit [Quit: Leaving]
PaulWay has quit [Remote host closed the connection]