c-smile

18 ms·

181.
by c-smile 4y ago
That reminds me again that flexbox is so needlessly complex that you need quite non-trivial guides each time you use it. It could be significantly simpler and, well, flexible: https://terrainformatica.com/2018/12/1
182.
by c-smile 4y ago
"obj is replaced by a different instance" Could you provide real life scenario when you will need that? I mean to change all references to the object in the heap at runtime ...
183.
by c-smile 4y ago
In fact in most cases dynamic subclassing is enough for such things. In JavaScript that's achieved by changing __proto__ reference on an object. So "obj instanceof A" becomes "obj instanceof B". As of persistence ca
184.
by c-smile 4y ago
CSS was designed for running on different UAs and there is special mechanism built in it. If you take a look into source of that demo page, you will see: /* browser */ @supports (display:flex) { section { display
185.
by c-smile 4y ago
Sciter works on Windows, MacOS, Linux, Android and is packaged in two forms: windowed and windowless engines (a.k.a. headless). It supports rendering trough Direct2D/DirectX, GDI+, CoreGraphics, Cairo and (through Skia) DX12, Vulkan, M
186.
by c-smile 4y ago
Sciter supports flex units but not flexbox. Flex units (and grid layouts) are in Sciter since 2007, ~10 years before browsers got them. Flexibility is the must for desktop UIs so it was in the engine from the very beginning. Sciter's
187.
by c-smile 4y ago
It is not about binary size per se, but of features/binary ratio. Can Cobalt run, say, ChartJS as it is ( https://sciter.com/chartjs-in-sciter/ )? Seems like not as I do not see <canvas> in the list of its sup
188.
by c-smile 4y ago
> But binary has ~45mb ... Even this is too much I think. Sciter is 7 Mb on Windows and 11 Mb on RaspberryPi. Extra 3 Mb is Skia for rendering on Vulkan and/or OpenGL. And it supports full set of HTML5 elements. JavaScript is at ful
189.
by c-smile 4y ago
For what it's worth... In Sciter you can simply define tree view as <select type="tree">: <select type="tree" treelines> <option> <caption>Giant planets</caption
190.
by c-smile 4y ago
It could be interpreted that way too. But usually managers interpret it this way: let's mold it now from that pile of shit and firewood and think about concrete foundation later. VC driven development they say. It makes sense in some c
191.
by c-smile 4y ago
Except of few ideological mistakes, I would say, quite a lot of time was wasted on doubtful technical decisions ... One year was wasted on trying to make it as WPF application, .NET all that ... 5, if not more, years were wasted on making i
192.
by c-smile 4y ago
Yeah. > And enterprises of great pith and moment, > With this regard, their currents turn awry, > And lose the name of action. Hamlet, William Shakespeare I was employee #3 at original Evernote, when we were just implementing that
193.
by c-smile 4y ago
In some cases it produces recursive definitions, for example: Q: Big Bang Big Bang is the popular name for the theory of cosmic inflation, a cosmological model that describes the first few instants of the Big Bang .
194.
by c-smile 4y ago
Yes, that's close. Only one thing: that static styles construct shall eventually go into a separate <style> DOM element inside shadow root. Probably not a big deal if there are not that many such components.
195.
by c-smile 4y ago
FYI, component styles in Sciter can be placed directly in JS module using `CSS.set` string literal (gets compiled at runtime to special style set object). The style set is a collection of styles rules local (rooted at) to the component. :r
196.
by c-smile 4y ago
For some reasons, I've found that good, old, Verdana (as used on this very HN) is the most editor/writer friendly. IMHO of course.
197.
by c-smile 4y ago
My Sciter [ https://sciter.com ] uses that since 2012 : https://terrainformatica.com/2012/11/04/caret-positions-in-h... The feature there is named "directional caret"...
198.
by c-smile 4y ago
Why do we need to defend a hammer against a sickle? Each tool has its own value it was designed for ... Try to imagine LISP without lists ...
199.
by c-smile 4y ago
Memory could be an issue as I have 8 Gb on that machine. 95% of code is the same on all platforms.
200.
by c-smile 4y ago
I've got one already. Here are real-life / practical numbers so you will know what to expect. Compiling Sciter ( https://sciter.com ) full rebuild (C++): i7/32GB - just 64 seconds. That ARM (WDK)/32GB machine -
201.
by c-smile 4y ago
That's what I did in Sciter: 1. Added element.$("selector") and element.$$("selector") functions. Later one allows to work with JQ sets: for(let el of parent.$$(".child")) ... 2. Added el
202.
by c-smile 4y ago
My uncle (elder brother of my dad) died on Oder River offence. Two weeks before end of the war. 20 years old guy, sigh. And I also lost all my grandfathers there. Memories in our family are quite fresh.
203.
by c-smile 4y ago
What was wrong with CTRL? What for is that frustration of us who work on different platforms?
204.
by c-smile 4y ago
Yes, CSS is not a strict "language" unfortunately. prop: a b c / d e f; can be treated in some properties as list: prop: a b (c / d) e f; and some others as prop: (a b c) / (d e f); Same t
205.
by c-smile 4y ago
And what is wrong with it? and ~ combinator and :nth-child(n) selector for that matter too.
206.
by c-smile 4y ago
You can store index of the node in parent m_children collection. Iteration on array is faster (cache locality) than DL list traversal. And there are issues when you traverse tree while changing it. In any case I've found that storing c
207.
by c-smile 4y ago
> You don’t need parent You do need parent, check this: https://developer.mozilla.org/en-US/docs/Web/API/Node/parent... > You want sibling nodes otherwise you will have to traverse back to the
208.
by c-smile 4y ago
No, you didn't get it. You may have children accounted as DL list and so each Node should have m_next / m_previous node references. + Parent node to have m_first_child reference (if list is circular). + m_parent (Node ) reference
209.
by c-smile 4y ago
Interesting, from libHTML: class Node { Vector<Node*> m_children; Node* m_next_sibling { nullptr }; Node* m_previous_sibling { nullptr }; } Either m_children or m_next_sibling/m_previous_sibling are
210.
by c-smile 4y ago
> I'm not sure if this article is a joke Of course not. There is even a book about it: https://sciter.com/wp-content/uploads/2022/08/master-finnish...

More ›