Features Requests and Ideas
From LintouchWiki
This page serve the purpose of brainstorming new ideas for the future versions of Lintouch.
Contents |
[edit] Advanced scripting in the server
HynekPetrak 09:02, 26 April 2006 (CEST)
[edit] Description
As of current version (1.10) the lintouch, plugins can't access variables of each other. It is not possible, for example, from Lua plugin read the variables received over a Modbus/TCP connection. If we add a possibility of a read-only access for real-values and eventualy a read-write access to requested values of other plugins, it opens a wide range of new possibilities like:
- extract bits/bytes from bigger variables
- calculations on variables
- unit conversions
- variable monitoring with
- etc.
[edit] An Example
Modbus plugin has a variable "HEIGHT_FT" which is a height of something in feets. The height in feet is fetched over Modbus/TCP form some device. The Lua plugin has a variable "HEIGHT_M" which represents the same height of something but in meters. The Lua plugin with following code makes the magic:
while should_run() do
height_in_feet = global_variables.modbus.HEIGHT_FT
height_in_m = height_in_feet * 0.33
-- send to lintouch the new time
set_real_value( variables.HEIGHT_M, height_in_m )
-- sync results back to lintouch
sync_real_values()
sleep( 0.01 * 1000 * 1000 )
end
[edit] Comments
Any word on this feature request. I would also find this very helpful.
[edit] Password protection for project files
Nelson Mambre 26 April 2006
[edit] Description
Lintouch could offer the possibility to protect a project file, with different protection levels. This way we can control the way the end user (the client) can access the project content.
[edit] Justification
- To prevent the end-user to modify the project, sometimes too much power for an inexperienced user is dangerous.
- Maybe you have a Lua script with some control logic that you don't want everybody to see.
- ...
[edit] Desired Features
- Possibility to lock whole project or parts of it
- Protection of scripts, conections, variables, layout separately/independently
- Password for editing and for running the project.
- Possibility to lock some scripts, leaving others open for the user to modify.
- ...
[edit] Implementation Considerations
- A project file is basically a zip file, so it could be possible to use the same mechanism to password protect (parts of) the file.
- Most probably a first implementation could be just locking the whole project. (Seems to be easier)
- Check if it is possible to assign different passwords for normal zip files, and also if possible to protect part of the content in the zip file.
- If not possible to create different passwords for a single zip file, maybe a workaround could be a password for the whole file, and a second (protected) zip file in the project containing lists of other passwords
- ...
[edit] Comments
(Please add your comments here, or if you can place it in the above sections, you can add your name to it)
[edit] Miscelaneous user interface modifications and features requests
Felipe Ledesma 27 April 2006
[edit] Description
It would be nice to have:
- Locking objects
- Pop-up panels
- Link to panels for the button widgets
- Mouse over behaviours
- Active/Inactive for SVG images
Other issues not related to UI:
- When you load an app that has a plugin that isn't installed you get kicked out, and get a segmentation fault.
[edit] Justification
- To have a more flexible user interface.
- It is easier and faster to develop the panels.
