Hi all.
Working on package storage in the repository, and how it relates to rules etc.
Basically, in the repo, we have packages which contain rules (rule sharing will be done by references - but forget that for now). A rule belongs to one physical package.
At the package level we have assets like we do now like funcitons, and things like imports, globals etc etc etc...
We are planning on making it so that a package configuration can be synced with an external repository - normally that means 1 rule == 1 file, 1 package == 1 directory containing many rule files (the idea being you can edit/debug in your IDE of choice).
My question is regarding DSLs: at the moment we tend to do DSLs on a per package basis: however, in the real world, I see a mix of DSL and normal rules being needed to solve problems.
a. So should we allow 1 rule in a package (which is 1 file) to use a DSL, and another one NOT use a DSL?
b. Should there be only one DSL file per package? or multiple ones?
c. If a above, should the IDE be changed to pick up the default DSL file (ie the dsl file in the directory)
d. If not a above, that means that rules need to be in different packages if they do/don't want to use a DSL - is that a problem?
e. Should DSL rules use a different file extension so the IDE can treat them differently?
Kris? opinions?
Michael.
