ericlendvai / datawharf Goto Github PK

First, I'd like to say that, even though I haven't used it, it looked really good in the demo video :) .

A few questions:

• Have you considered using an alpine-based Docker image? Alpine's big advantage is that it's designed to be small, so the resulting Docker image will be smaller.
• I notice a number of your Dockerfiles are similar. Would you like them combined into one Dockerfile that does everything when you pass parameters to it?

Thanks!

Issue with code: mxLoadStylesheets&&mxClient.link("stylesheet","mxgraph/css/common.css")
The folder name is versioned now. Not certain how to make the .link() method use a relative path instead.

Hello Thomas, could you push in the repo the new version of bstreeview you are using.
Thanks, Eric

Hi Eric!

I was using DataWharf tonight to start modelling something. One feature I noticed was missing was Field Groups.

Let me quote from https://web.archive.org/web/20121024051826/http://www.geocities.com/tablizer/top.htm

Field Groups

One of the most time-wasting process in programming table processing with many of the popular languages is having to type the names of all the fields that will show up on a screen or report. It would be much easier to specify the name of a set, and all fields belonging to that set would then be used. Although sets could be pnumonic names, we chose to use letters in our example for simplicity.

Suppose that we had to make a report that showed customer transaction detail, but which ommited customer names for reasons of confidentiality. With our setup, we could just ask for a report on all fields in set "B" (See the Groups column above). When dealing with tables with 50 plus fields, specifying a set name is much simpler than typing 50 names or building a field loop.

While I don't necessarily agree with the way Field Groups are implemented in the article linked above, I do agree with the need for them.

In the thing I'm working on, I refer to Field Groups as "Lots"; feel free to either borrow or ignore my terminology.

On an only tangentially related note, I was Googling stuff about Data Dictionaries today, and found one article that I thought was particularly good: http://www.martymodell.com/pgsa2/pgsa08.html

The thing that seemed particularly useful was the diagram of a data dictionary part way down, and then his explanation of each element in the diagram. I was impressed that it seemed both fairly generic and fairly comprehensive.

I'm assuming you already know this stuff, but wanted to link it just in case.

HTH,

It'd be nice if we could move an attribute to a different entity (ie. have a dropdown in Attribute which says which entity it belongs to). Obviously this should only happen eg. if it's not being used to link entities together.

To reproduce:

• Create a String custom data type, and connect it to a data dictionary
• Enter some data into the field in the data dictionary
• Change the type to Multi and enter some values
• See an error that says

Error Occurred
gcc release 11/11/2023 03:21:54 - Current Time: 04/23/2024
Error: Argument error
operation: STR
[ 1] = U nil
[ 2] = N 10
Called From: src/DataWharf.prg, STR, line: 0
Called From: src/WebPage_CustomFields.prg, CUSTOMFIELDSBUILDGRIDOTHER, line: 1389
Called From: src/WebPage_Modeling.prg, ATTRIBUTELISTFORMBUILD, line: 6470
Called From: src/DataWharf.prg, EXEC, line: 673
Called From: src/DataWharf.prg, MYFCGI:ONREQUEST, line: 1150
Called From: src/DataWharf.prg, MAIN, line: 50
FastCGIRunLog.pk = 2

    BuildPageModeling
    DataTypeTreeBuild
    PackageTreeBuild
    AttributeListFormBuild

Edit: Change it so that either it works, or we can't change the type on a Custom Field