The majority of the posts on this list are of two types (IMHO):
How do you do this?
Is this broke?
Thought I'd try another type. "I didn't know you can do that".
I often spend way more time than I should re-inventing something that
has already been done, probably better than my reinvention. If
someone on the list asks "How do you do this?", I can search and find
it. If nobody asks, then I''m off inventing or searching other places.
One of the problems I've had in fusebox was handing many relations in
a list of one selections with RowSets. (e.g., one PO has many line
items and I need to display some details from the many records).
Don't know why I did not realize this, but a rowset can contain
another rowset. Not sure it is the best approach in all cases, but
when I tried it last week on a new circuit, it seemed to make sense
to me. Probably would not use this approach if line items needed to
be batched.
This approach is nothing more than:
map := """
id: [foo]id;
name: [foo]name;
xxx: [foo]etc;
lineitems: `getLineItems([foo]id)`
"""
getLineItems is just a local method that creates another rowset and
returns the handle in lineitems. Probably could also do it with a
global variable and a callback. Just one of the things I didn't know
you could do.
Steve Alex
PS
Just a comment on some of the posts in "[Active4d-dev] [Off] 4D
Summit" from last week.
From the posts on the FuseBox DVD/Screencast or whatever, it looks
like quite a few people didn't try to dive into fusebox. It really is
not that hard - but it took a while to figure out that almost
everything you need is in the graphic "Fusebox flow of control".
While it was there, what I, and probably a lot of other people
forgot, is the detailed explanation - in words. Things like
"fbx_settings" are optional (except for root??), but if there, will
be executed as it passes down the hierarchy. I could try my
explanation, but there are people out there that can write better
words than I can. Probably the other thing that led to the greatest
confusion is the Demo and how it took common processes that applied
to all circuits (qry_save) and put them at the "app" level. While
that saved code, it might of been better to just do everything in one
circuit, then show how to optimize it by promoting out common parts
(might of done this, but can't remember). Again, once you figured out
how the multiple includes worked, it was not that hard.
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
