Thank you for your quick reply,
I am working on my own implementation, wanted to know what is a better approach.
is it a good approach to reposition out of the grid node again. I mean, while scroll down repositions top nodes again to the bottom, will it be quick enough and smooth in functionality.
or any other approach you want to suggest?
I think reposition is the best way, but my solution is delete nodes outside and re-create it again. Since Defold is static engine this is good enough too (but much easier for use)
You can create your component in any of ways, it should be ok 
Druid 0.5.0: https://github.com/Insality/druid/releases/tag/0.5.0
Besides a lot of fixes (thanks for feedback!) two components was add: StaticGrid and DynamicGrid instead of usual Grid component (it is deprecated now).
Add component:set_input_enabled for basic component class. So you can enable/disable user input for any component.
Finally implemented on_layout_changed support. Druid components now will try keep their data between layout changing! You also can use this callback in your custom components.
Also check component.template.lua what you can use for your own custom components!
base folder to extended. In future to use them, you have to register them manually. This is done for decrease build size by excluding unused componentsreturn nil in some on_input functionsset_extra_stretch_size renamedcomponent.template.lua as template for Druid custom componentAwesome work, really impressive.
I have a question about the list/grid components.
Does it reuse the nodes (similar to a recyclerview in native Android)? I mean does it support a 100K item list or do we have to keep the number of items under the max sprites/nodes allowed?
Thanks!
Currently no, there is no druid solution for infinity scroll
Above we talked about this. In next Druid release will be added extended component to handle scroll with huge amount of data. Current release with grids is preparing for this.
Hello,
Thanks for the quick changes and dynamic grid,
it seems there is an issue with dynamic_grid added into the scroller, if the prefab_dynamic box component has some nested box component or text component, the nested component is not visible in the scroller,
I the example project, I also tried adding grid_nodes_prefab to grid_dynamic_view however its only showing the parent box of grid_nodes_prefab and not showing inner component that is grid_nodes_dot.
is anything else I need to try?
Thanks
Itâs seems not the Druid issue, but gui node management.
In Druid Example, create function just make gui.clone of the prefab node. For your case, you should do gui.clone_tree and do your stuff with gui nodes tree
Hey! Are you tired from Druid updates? (Itâs a joke)
Finally, got a time to release component to process huge amount of data. So introducing: DataList component. It can help solve your problem with GUI nodes limit reached and helps with scroll optimization. Give feedback about it!
The next important stuff is EmmyLua docs. Iâm implemented EmmyLua doc generator from LuaDoc and Protofiles, so now you can use EmmyLua annotations inside your IDE instead of website API looking or source code scanning.
Also the Druid examples is reworked, so each example will be in separate collection. Now itâs become a much easier to learn Druid via examples. A lot of stuff in progress now, but you already can see on it!
Input priority got reworked too. Now instead of two input stacks: usual and high, Druid use simple input priority value.
And I should note here are several breaking changes, take a look in changelogs.
Wanna something more? Add an issues!
Have a good day.
druid:new_data_list(scroll, grid, create_function).
fun(self, data, index, data_list)
data_list:set_data({...})add/remove functionsconst.SHIFT.RIGHT, const.SHIFT.LEFT and const.SHIFT.NO_SHIFT.
StaticGrid:remove and DynamicGrid:remove functionscomponent:increase_input_priority component function. Use component:set_input_priority function instead. The bigger priority value processed first. The value 10 is default for Druid components, the 100 value is maximum priority for acquire input in drag and input components
component.ON_INPUT_HIGH you should replace it with component.ON_INPUT and add const.PRIORITY_INPUT_HIGH as third param. For example:local Drag = component.create("drag", { component.ON_INPUT_HIGH })
local Drag = component.create("drag", { component.ON_INPUT }, const.PRIORITY_INPUT_HIGH)
helper.centate_nodes function. It can horizontal align several Box and Text nodesInput:select and Input:unselect function.Input.style.IS_UNSELECT_ON_RESELECT style param. If true, it will be unselect input on click on input box, not only on outside click.component.luaWHEEL_SCROLL_SPEED, WHEEL_SCROLL_INVERTEDScroll:set_click_zone function. This is just link to Drag:set_click_zone function inside scroll component.druid:create is deprecated. Use druid:new for creating custom componentsWhat would be the best way to hook in animations â specifically, Iâm looking to add some animation when items are added to a grid, e.g. like theyâre cards being dealt out.
If it requires modifying the druid code, thatâs fine, but Iâm not exactly sure where to look, as I wasnât able to find anything in the examples or documentation
Itâs nice example request, thanks!
Usually, for some animations like you say, I just run animations after adding elements to the grid (card appear, leaderboards, etc)
If you need animation before element deletion, I just call grid.remove in the end of this animation.
If this case is not suit for you, I need more information what you want 
so, like I said above, right now Iâm trying to basically do a card-dealing animation when the elements are added to the grid. I did eventually find the on_add_item event, which seems like exactly what I want, but only the last one is being animated. Hereâs my preliminary attempt:
self.matching_grid.on_add_item:subscribe(function(self, node, index)
local end_pos = gui.get_position(node)
print("added "..index.." @ "..end_pos.x..","..end_pos.y)
gui.set_position(node, vmath.vector3(480, -100, 0))
gui.animate(node, gui.PROP_POSITION, end_pos, gui.EASING_OUTBACK, 1.0)
end)@greay sorry for late reply!
Yea, I got the your problem. The reason is what Grid component is manage their nodes position. So after add/update/remove any element, Grid will update all their element positions. Your callback is right, but after add element all previous position is updated.
The correct way is manage position inside the root node of added elements. You can add root node (which added to Grid component) and inside root node the position_anchor node to make animations.
Iâve add the example you can check (yea, now with deep linking!)
Hi @Insality,
I use Druid library in my project and I have some issues regarding Scroll with POIs.
Both issues can be re-produced with your default example.
Perhaps I do something wrong , but I would like to use both stretching and inertion by this scroll.
Thanks for the feedback!
Iâll take a look later, itâs possible that there is some problems with POIs in the scroll. So there is a reason to look on it better
Hello! Here Iâm again with new Druid stuff for you!
The feature I want a long time to deliver for you: the different Text size adjust modes. Druid use the text node sizes to fit the text into this box.
There are new adjust modes such as Trim, Scroll, Downscale with restrictions and Downscale + Scroll. You can change default adjust mode via text style table, but by default there is no changes - itâs downscale adjust mode as before.
Iâll hope it can be useful for you for in different cases and now it will be much easy to fit all your texts for different languages!
The next features is made for add more control for availability of user input. So meet the whitelists, blacklists and custom check functions for Buttons. Now you can easily choose the more suitable way to enable/disable/restrict input for you users. Iâm sure it can be useful for you tutorials.
Another small, but cool feature on my mind is druid.stencil_check. If you did interactive elements inside the Scroll, probably you used component:set_click_zone to restrict input zone by stencil scroll view node. With this feature, Druid will do it automaticaly for you! You can enable this feature in your game.project. It will not override you existing set_click_zone calls.
Now you even able to remap default input keys! Also there are several bugfixes with Scroll, Text, Grids.
Wanna something more? Add an issues!
You can say thanks to me via stars on GitHub! 
Good luck!
Button:set_check_function(check_function, failure_callback) function to add your custom click condition to button.
Button:set_enabled has more priority than this to check button availabilitycheck_function should return true of false. If true - button can be clicked by userfailure_callback will be called if check_function will return falseset_check_function in general:buttons example collectiondruid:set_whitelist() and druid.set_blacklist() functions. Itâs affects only on input process step, you can allow/forbid interact with list of specific components
druid.stencil_check = 1 to your game.project file.
component:set_click_zone to restrict clicks outside scrolls zone for example. Now you can donât think about click zone and let Druid do it instead of you!helper.get_closest_stencil_node function to get closest parent of non inverted stencil nodecomponent.ON_LATE_INIT interest. Component with this will call component.on_late_init function once after component init on update step. This can be used to do something after all gui components are initeddruid_const.ON_MESSAGE_INPUT. The message table params:
node_id - the name of the node with component on itaction - value from druid_const.MESSAGE_INPUT. Available values:
value - optional field for several actions. For example value is text for TEXT_SETcomponent.ON_MESSAGE_INPUTcomponent:on_message_input(node_id, message)IS_DYNAMIC_NODE_POSES (default: false). Always align by content size with node anchor.
component:set_input_priority() affects on all componentâs children toodruid.set_text_function callgame.projectWHEEL_SCROLL_BY_INERTION (default - false). If true - mouse wheel will add inertion to scroll, if false - set position directly per mouse wheel event.
WHEEL_SCROLL_BY_INERTION for more controllable scroll by mouse wheel.Hi
I am having an issue testing the timer function.
I can get the timer to appear on the gui, but it remains static at the initial value - it doesnât tick down.
I have a main.collection and a main_menu.gui.
I have two scripts - main_controller.script which performs the functions of the app, and main_menu.gui.script that handles the user input. The gui script passes messages to the main_controller.script when there is user input (there are 12 gui nodes in total). Itâs a very simple project as I am pretty new to Defold.
When the app loads the timer value loads successfully in the gui node as pass as a parameter, but then it fails to change.
Is there anything I am missing?
Okay. I have managed to get the timer to run, but I cannot stop it, or reset it. Any examples of how I do this?
EDIT: I worked it out, somehow my code was creating two timers and I could only control one of them,
Hello!
In this Druid update no any huge special features. Mostly the bug fixes and reworking the componentâs interest points. If you used interests in your custom components, you should remove it from component.create and all should works as before.
Also added last row alignment in Static Grid component with âdynamic content posesâ style enabled. You can look how it is work here: https://insality.github.io/druid/druid/?example=grid_static_grid_dynamic_pos
You can say thanks to me via stars on GitHub !
Wanna something more? Add an issues!
Have a nice day!
Changelog 0.8.0
component.create function have next signature: create(component_name, input_priority)
component.create("custom", { component.ON_INPUT, component.ON_LATE_INIT }, const.PRIORITY_INPUT_HIGH) tocomponent.create("custom", const.PRIORITY_INPUT_HIGH)
... from lang_text to fixed arguments, add format function to change only string format arguments
.... Now Lang Text will support up to 7 string.format argumentsscroll:scroll_to_percent by Y positionanimate or set_to functionsset_state function
helper.centrate_nodes
Custom components update
Hello!
Here is the long awaited update! Finally I implemented some ideas how to make easier creating custom components. There is a bunch of improvements you can be interested in.
I wanna make a point that Druid is not only set of defined components to place buttons, scroll, etc. But mostly itâs a way how to handle all your GUI elements in general. Custom components is most powerful way to separate logic and make higher abstraction in your code.
Usually - custom components is set of GUI template and lua code for this template. Iâve added editor script, that can make a lua component file from your GUI scene (all boilerplate and usage code, also some component that can be defined right in GUI scene).
Auto layout from GUI script should be a powerful tool too! Also itâs brings some code structure and style across all your files. Auto layout works from node names. If its starts or equal to some string, it will add code to generated lua file. For example, if you have in your scene node with name âbutton_startâ, it will create the Druid button, stub function and annotations to this. Sounds good!
For more information see Create custom components documentations.
Also this update have some breaking changes: you should no more pass full tempalte name in inner components and the second one is renaming text:get_text_width to text:get_text_size.
The Defold 1.3.0 solves the old my issue with slider component. Now you can define input zone (not only the slider pin node) to interact with slider. Itâs because of inroduction gui.screen_to_local and gui.set_screen_position in default GUI api. If you using previuos Defold releases, this piece of logic will be ignored.
The Druid Assets repository will be closed and I move some components right in Druid repository. You can now use custom components in your game if your need. Right now itâs Rich Input (input field with cursor and placegolder) and Pin Knob (Rotating node for set value). And slowly working on adding new examples and improvements of existing ones.
You can say thanks to me via stars on GitHub !
Also you can help with testing new functions and leave feedback.
Wanna something more? Add an issues!
Take care of yourself
Changelog 0.9.0
button, text, lang_text, grid, static_grid, dynamic_grid, scroll_view, blocker, slider, progress and timer
get_node inside inner components with template/nodes
current_template .. "/" .. inner_component_template). From this update you should pass only the inner_component_template name. Itâs will auto check the parent component template name to build full template pathdruid.no_auto_template in your game.project file. By default itâs enabled nowcomponent:get_template() function to Druid Base Component
self.druid:new_button(SCHEME.BUTTON) instead of self.druid:new_button(self:get_node(SCHEME.BUTTON)) inside your custom componentsself:get_node()
static_grid:set_in_row(amount) functionslider:set_input_node(node) function. Now slider can be interacted not only with slider pin node, but with any zone you will define.gui.screen_to_local and gui.set_screen_position functions.text:get_text_width to text:get_text_size. Now it return two numbers: width and heightdruid:new functions inside gui_script.druid/custom. It will have the complex custom components. Usually you should to use default GUI template or create your own with similar GUI scheme. Currently add RichInput and PinKnob components from druid-assets repository.druid:new(Component, template_name, [nodes]). See component docs to see constructor params.IS_DYNAMIC_NODE_POSES = false style