chexum_ has quit [Quit: No Ping reply in 180 seconds.]
chexum has joined #picolisp
pablo_escoberg has joined #picolisp
<pablo_escoberg>
Hey all, is there a way to predict the order of the output of `getl`? I'm using it to get a list of relations for a given entity (filtering with `type`), and I'd like that list in the order in which they were defined, but I'm getting it in a seemingly random order.
<abu[7]>
Hi pablo_escoberg, no, because the property access functions (put, get, : etc.) change the order each time
<abu[7]>
(last recently used scheme)
<pablo_escoberg>
Ah, ok. I'll find a different solution.
<abu[7]>
Why do you need this order?
<pablo_escoberg>
Trying to auto-create a form from the relations.
<pablo_escoberg>
Right now I am thinking of redef'ing `rel`, which I'm already doing.
<abu[7]>
ok
<abu[7]>
I gave up the idea of auto-creating a GUI a long time ago
<abu[7]>
It is not flexible enough
<abu[7]>
The GUI depends on other things than just the E/R
<pablo_escoberg>
I understand. The API won't. Also, everything will be override-able.
<abu[7]>
good
<abu[7]>
I would think that 'rel' should not need to be redefined. Instead, add methods to the relations (dm (form> . +String) (..) ..), (dm (form> . +Link) (..) ..) etc.
aw- has quit [Quit: Leaving.]
aw- has joined #picolisp
teddydd has quit [Ping timeout: 248 seconds]
teddydd has joined #picolisp
<abu[7]>
I did that with the new 'iter>' and 'match>' methods needed in 'search'
<abu[7]>
First definded them as (dm (iter> . ... in a separate file and tested all
<abu[7]>
Then inserted them as (dm iter> ... in @lib/db.l
msavoritias has joined #picolisp
seninha has joined #picolisp
seninha has quit [Quit: Leaving]
seninha has joined #picolisp
seninha has quit [Remote host closed the connection]
seninha has joined #picolisp
seninha has quit [Quit: Leaving]
seninha has joined #picolisp
seninha has quit [Client Quit]
seninha has joined #picolisp
<pablo_escoberg>
Well, my end goal is an almost completely declarative, minimalist syntax for the application code, so I need to squeeze as much info as I can out of those `rel` declarations. This almost works:(put *Class 'rels (list (get *Class 'rels) (cons (get *Class (car Lst)) (car Lst)))) and I'll fix it shortly.
<abu[7]>
cool
<pablo_escoberg>
I settled on this: `(put *Class 'rels (list (get *Class 'rels) (cons (get *Class (car Lst)) (car Lst))))` . Dealing with building a list of cons pairs was too hairy, plus I can just `get` the actual relation when needed.
msavoritias has quit [Remote host closed the connection]
pablo_escoberg has quit [Quit: Client closed]
seninha has quit [Quit: Leaving]
seninha has joined #picolisp
seninha has quit [Remote host closed the connection]
seninha has joined #picolisp
chexum has quit [Remote host closed the connection]