language-servers/slint
1
0
Fork 0
mirror of https://github.com/slint-ui/slint.git synced 2025-10-01 14:21:16 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 5
3539 commits 164 branches 55 tags 397 MiB
Commit graph

250 commits

Author SHA1 Message Date
Olivier Goffart
952ddda7c4 Force duration to have an unit 2020-07-14 16:18:12 +02:00
Simon Hausmann
39359a4e26 Add support for an offset to PathLayout 
This allows animating items on their position along the path.
 2020-07-14 15:12:03 +02:00
Simon Hausmann
a3f365417c Center items on a path layout 2020-07-14 09:43:59 +02:00
Olivier Goffart
e00491811b Get rid of the context in properties/signal 2020-07-13 18:49:06 +02:00
Simon Hausmann
992f990fa8 Allow for fitting paths into a given bounding rectangle 
... by applying a transformation. This allows designing a path in some
other path design tool and then make it fit using bindings.
 2020-07-13 15:41:11 +02:00
Simon Hausmann
79ba943882 Allow for positioning grid layouts as well 2020-07-13 14:02:53 +02:00
Simon Hausmann
f6761e2c4c Allow for the positioning of PathLayouts via x/y properties 
These are just "virtual" properties that will be transformed into
property members of the main struct through the optimized elements
sub-pass.
 2020-07-13 13:34:04 +02:00
Olivier Goffart
868468b101 Interpreter: Do not use the parent component from the context 2020-07-13 13:13:23 +02:00
Olivier Goffart
d392e00c1c Implement dynamic models in the interpreter 2020-07-13 11:50:57 +02:00
Simon Hausmann
1a70213c05 Fix path layout implementation to allow positioning 
This is not exposed in the API yet though.
 2020-07-09 15:38:26 +02:00
Simon Hausmann
4b75ec0ee8 Lay out items on a path 
This works, but it's still missing support for positioning of the layout
itself.
 2020-07-09 15:32:47 +02:00
Simon Hausmann
a83127ace8 Prepare the path element compilation for extensibility 
Avoid any element specific code in the Rust and C++ generator and
minimize the involvement in the interpreter.
 2020-07-07 14:14:17 +02:00
Olivier Goffart
d0b44a125d Support for if expression in the interpreter 
Dynamic model or expression not yet supported
 2020-07-03 17:56:48 +02:00
Simon Hausmann
5e61ed4ad2 Implement Path and LineTo in the markup 2020-07-01 15:13:23 +02:00
Olivier Goffart
8851ad0f3d Interpreter: Don't copy the property_animations from the object_tree::Component to the ComponentDescription 
They can be easily accessed from the original object_tree::Component
 2020-06-29 11:01:20 +02:00
Simon Hausmann
b8ca0fe3c9 Add support for animating color properties 2020-06-27 16:51:48 +02:00
Simon Hausmann
f7517f403c Make the color a valid property type 
This replaces Property<u32> with Property<Color>
 2020-06-26 21:46:37 +02:00
Simon Hausmann
288ad0cba8 Add support for animations of declared properties 
* Make sure to move the animation declarations when moving property
  declarations to the root
* In the interpreter, we need to do a little extra dance to get the RTTI
  right for custom properties and also apply the animations.
 2020-06-26 20:33:55 +02:00
Simon Hausmann
4f2f27cbda Simplify property and binding setting code in the interpreter 
Change the Property RTTI to take an optional animation, instead of
having to match on each call site.
 2020-06-26 20:33:55 +02:00
Simon Hausmann
45de3d832e Minor cleanup in the interpreter animation handling 
Expose the fields of the PropertyAnimation through the rtti module
instead of hard-coding them in the interpreter.
 2020-06-26 20:33:55 +02:00
Olivier Goffart
0029921f1a Pin the items in the interpreter 2020-06-26 11:55:05 +02:00
Simon Hausmann
36bd645e09 First stab at supporting animations in the interpreter. 
The sub-optimal RTTI bits are replaced with a superior solution in the
follow-up commit :-)
 2020-06-26 11:07:18 +02:00
Olivier Goffart
1b748792ad Visit the item as Pin 
A preparation to have Property::get to take Pin<Self>
 2020-06-25 18:50:20 +02:00
Simon Hausmann
c18861125d Small typo fix :-) 2020-06-25 14:22:10 +02:00
Olivier Goffart
f50a705e00 Add the #[pin] attribute to be able to project to the pinned item 2020-06-25 12:18:09 +02:00
Olivier Goffart
caca0d0ba4 Put the component in a Pin<> 
Removed the drop and create from the ComponentVTable:
since we are not using VBox<ComponentVTable>, this simplifies a bit
the code of the interpreter and everything else.

But there is still a lot of changes everywhere to support that the Component
is pinned.
This is just for the component. Which would be required if later we want
to access the properties as Pin<Property<_>>. But we have not yet ability
to do projections
 2020-06-24 14:13:27 +02:00
Olivier Goffart
fa0c393dca Interpreter: Fix property access from parent component in repeater element 2020-06-22 15:22:38 +02:00
Olivier Goffart
f8b7989c0b Access the properties in the parent component of a repeated element 
This required some refactoring of the EvaluationContext structure to include the parent context
 2020-06-22 14:38:38 +02:00
Olivier Goffart
1bb8d94ab8 Support array for model in rust and in the interpreter 2020-06-19 19:46:59 +02:00
Olivier Goffart
8f0520f2be Repeater in the viewer 2020-06-17 15:43:57 +02:00
Olivier Goffart
a4423374d8 Fix warnings 2020-06-16 13:59:10 +02:00
Olivier Goffart
6122f91fba Begin with the generation of rhe repeater (rust only for now) 2020-06-16 13:47:02 +02:00
Olivier Goffart
2fa7005c9a Interpreter: Int32 is a i32, so it can represent the negative numbers 2020-06-15 16:46:27 +02:00
Olivier Goffart
9adc55cd70 Partially revert the refactoring that changed the Element::children list 
Put the information about RepeatedElement in an Option within the normlal Element
 2020-06-15 13:42:11 +02:00
Olivier Goffart
136a90907b Refactor the element children to account for RepeatedElements 2020-06-12 22:24:50 +02:00
Olivier Goffart
30b201d946 Reduce the use of unsafe in corelib and in the rust backend 2020-06-12 19:03:15 +02:00
Olivier Goffart
e7644eba94 Fix C++ compilation with the new item visitor 2020-06-12 17:09:51 +02:00
Olivier Goffart
66dc643bf9 WIP: refactor the item visitor 
The C++ part hasn't been ported yet and some things still need polish

Introduce a visitor to not rely on the unsafe ItemTreeNode array.
 2020-06-12 13:32:40 +02:00
Olivier Goffart
e95d7da888 Parser: typed syntax node accessor 2020-06-11 17:50:28 +02:00
Olivier Goffart
8b6bb47af8 Create a type alias for Rc<RefCell<Element>> 2020-06-11 15:28:51 +02:00
Olivier Goffart
9c23326c60 Layout for the C++ as well 2020-06-10 19:41:24 +02:00
Olivier Goffart
907bea3d3b Layout for rust 2020-06-10 19:41:24 +02:00
Olivier Goffart
96a372e45d Grid layout in the interpreter 
current imploementation is just a prototype
 2020-06-10 19:40:47 +02:00
Olivier Goffart
58618c0683 Documentation for the interpreter 2020-06-10 09:26:11 +02:00
Simon Hausmann
1404cb73ae Add support for embedding resources in the rust generator 
This is relatively straight-forward via a pass in the compiler to
collect the resources to embed and then use include_bytes! (once per
resource).

What's really annoying is that the rust resource enum can't store a
&'static [u8] because cbindgen doesn't represent that, probably because
the slice representation isn't guaranteed to stay as it is. So instead
this, for now, uses raw pointers.
 2020-06-09 22:54:29 +02:00
Simon Hausmann
5bae6e01a5 Prepare for the ability to embed image data 
The Image's source property used to be a string. Now it is a Resource
enum, which can either be None or an absolute file path to the image on
disk. This also replaces the internal Image type.

The compiler internally resolves the img bang expression to a resource
reference, which shall remain just an absolute path. For now the target
generator passes that through, but in the future the target generator
may choose a target specific way of embedding the data and thus
generating a different Resource type in the final code (through
compile_expression in the cpp and rust generator).

The C++ binding is a bit messy as cbindgen doesn't really support
exporting enums that can be constructed on the C++ side. So instead we
use cbindgen to merely export the type internally and only use the tag
from it then. The public API is then a custom Resource type that is
meant to be binary compatible.
 2020-06-09 22:54:29 +02:00
Simon Hausmann
afd7319ae5 Rename corelib to sixtyfps_corelib 
This is consistent with the other packages and since corelib is now also
a cdylib, libsixtyfps_corelib.so looks much better than libcorelib.so
:-)
 2020-06-09 13:27:18 +02:00
Olivier Goffart
3651885d87 Move the compiler binary in tools/ 
And rename sixtyfps_compiler to sixtyfps_compilerlib
 2020-06-05 09:23:38 +02:00
Olivier Goffart
30d61452ba Interpreter and node API: some refactoring towards being able to set properties from JS 2020-06-03 17:33:43 +02:00
Olivier Goffart
fd829fc89f Some more refactoring of the interpreter 
Move the content of lib.rs to a module so we can have some
kind of public api in the lib.rs
 2020-06-03 17:33:26 +02:00