Jump to content

david berneda

Members
 View Profile  See their activity

  • Content Count

    27

  • Joined

  • Last visited

  • Days Won

    4

Posts posted by david berneda

  5. Posted

    Just an alternative, TeeGrid can be used for gantt applications too. A customer from Canada recently sent us their app, the grid allows multiple top layers (columns and subcolumns, for year, month, date, etc) and rows (tasks) can contain children rows (unlimited levels, subtasks) with a "+" left column to expand / collapse.

     

    Tasks are then custom painted using the grid Canvas (Rectangle, Triangle, etc methods) using the columns coordinates.

     

    https://www.steema.com/product/gridvcl

     

    https://steema.com/wp/blog/2025/06/18/powering-precision-in-manufacturing-intelligence-dynafact-dms-with-teechart/

    Assembly-and-Order-Gantt-1536x810.jpg

  7. Posted

    Hmm, I'm not sure if the free TeeChart Lite version has this, but sure the Pro version allows "sub axes" (what you say titles of 3 layers, are the TChart.Axes.Top (first layer with dates) and two sub axes added to it, one for hours, one for seconds.

     

    Cosmetics I think allow to match the screenshot with some customization, to some extent. Navigation (scroll, clicks, drag etc) are provided.

     

    More complex is (if I see the screenshot well) the ability to expand left side texts, like a tree/explorer of levels. It can also be done but its not as easy as a property or adding "children" rows to any row.

     

     

  12. Posted

    Yes, the features that needed Python have been deprecated and are no longer needed.

    The documentation will be updated to reflect this.

    I can upload the deprecated units at a separate folder just to archive them.

    Maybe in the future if there is demand it can be restored.

     

  15. Posted

    19 hours ago, Mark Williams said:

    I've just updated my version to the latest and have found the the TRibbonApplicationModes set has been removed from UIRibbon.Pas. As far as I can see there is now no way of querying what ApplicationModes are currently deployed.

     

    Seems like an odd feature removal. I query these quite a lot. Presumably, you are now expected to keep track of the Application modes yourself. Am I missing something here?

     

    • Like 1

  17. Posted · Edited by david berneda

    We're adding a new property to axes to achieve this functionality:

     

    Chart1.Axes.Left.AutoHide := False;

     

    By default AutoHide is True, meaning the axis will be automatically made invisible when all of its associated series are also invisible.

     

    Setting it to False will always paint the axis as if all of its series were visible.

     

    If the axis min and max are set to be automatic, they will be calculated using all associated series.

     

    If you wish to beta test I'll be glad to email you the latest sources, just email me at david@steema.com

     

    This new property will also allow adding multiple custom axes anywhere, without the need of creating series, among other things.

     

    regards !

    david

     

    • Thanks 2

  20. Posted

    17 minutes ago, Fr0sT.Brutal said:

    F.ex., my colleague has project which periodically  generates charts with thousands of points and exports that to image. And the main UI has to be responsible while generating. Alas, TTeeChart is visual control so he has to use such bad practice creating it inside bg thread.

    I recently did a TeeChart fix to avoid creating its Windows Handle when just drawing it to a image without showing on screen.

     

    https://www.steema.com/bugs/show_bug.cgi?id=667

     

    We posted a beta yesterday available for download, let me know if your colleague is interested in testing I'll provide a license.

     

    regards !

    david

     

    • Like 1
    • Thanks 1

  21. Posted

    5 hours ago, David Schwartz said:

    in what respect? I mean ... what kind of use-case are you thinking of?

     

    I asked about this because I've got a bunch of JSON data (array of records) that I'm stuffing into objects added to a TList, and it seems the only way to get something I need is to use a DB-aware control to view them. So I need to get them into a dataset so they can be viewed. Then the whole thing gets thrown away.

     

    So the choice is to go from JSON --> TDataSet or TList<T> --> TDataSet, both of which are dependent on the same issues:

     

    How much time do you want to spend writing code that speeds this up by less than a second?

     

    It's a little funny to me that all of this great technology we have at our fingertips is all rooted in stuff designed back in the 90's to support Client/Server database technology while today a large amount of our work centers around data shipped between servers as JSON packets, that's either parsed and used immediately or stuffed into classes, and is mostly transient and never intended to be put into any kind of structured DB.

     

    There are even plenty of NO-SQL DBs available today to help manage this data.

     

    Yet the most useful visual components are all driven off of TDataSets that are intended to be connected to databases.

     

    DevEx grids are incredible, but last I saw, they're totally driven off of TDataSets and are useless for JSON data and lists of objects.

     

    If you need a Grid fmx/vcl to connect to TList of records etc, TeeGrid does it, without TDataset: https://github.com/Steema/TeeGrid-VCL-FMX-Samples/tree/master/demos/VirtualData/TList

     

     

  24. Posted

    Hi !

    I've just published the source code in Pascal/Delphi of "Vidi Language" v0.2-alpha:

     

    https://github.com/davidberneda/Vidi

     

    It includes a parser/compiler and a simple ide/debugger for a new programming language (Vidi).

    This is a toy-experiment project in a very early stage.

     

    Attached pdf reference, same here:

    https://github.com/davidberneda/Vidi/blob/master/documentation/Vidi_Language_Reference.md

     

    regards 

    david

     

     

    Vidi_Language_Reference.pdf

    • Like 9
×