First the easy part, i18n:
! hahahahaha still
a lot of work).
Basically, we can use the same technique that any other "rich client" app in
java would - properties files. We can even use eclipse to externalise all
strings (although we have to change how the generated Messages class works.
Check out the JIRA if you want to look how to help - a start would be to
make sure we can use the Messages approach in a performant way on the web,
once we have that, we can externalise ALL the strings (giving them sensible
key names), and from then on its a matter of creating the approriate
I think I get what you are saying re DSLs: There are 2 ways I think think
about now: 1. get the users to write the rules they want in they own
langauge in the description field, and then that can be used to formulate
the mappings or #2, use the alternative text based DSL editor, where they
can type it in directly as they want. Then when someone tries to build the
package, they will get errors (of course) until the DSL is create to match
what they typed.
So it is then an iterative sort of workflow.
I would like to hear any other ideas you may have for this, now you have
seen it a bit more.
On 5/26/07, Felipe Piccolini <felipe.piccolini(a)bluesoft.cl> wrote:
The BRMS looks great (very good work Michael and everyone involved in
JCR and other stuffs), but I wanna ask
if you guys have in mind a way to change the language used in the GUI and
in the Rule Editor, so the editor can be
used in a 'natural language' way from GUI.
From the same point of view, the quick-start-tutorialmovie says you can
add a DSL as an asset for the package of rules
which is great, but it doesnt help me 'much' if I'm a not technical user
who is designing rules with the rule-editor GUI
and then I wanna use DSL, because the dsl must be done a part by another
guy who doesn't know how am I writing
the rule, so there is no way he can know the code that must be write to
translate the natural-languaje-phrase of the
CE/Action I wanna use. The only way would be if he already knows the
sentences (and the associated code) before
I (business man) write the rule it self, which is not most cases (Am I
explaining well?). I mean, I like what is done, but
I would like to see a way to create from scratch a rule and associate
CE/Action sentences to new DSL sentences and
add this new DSL sentences to the DSL asset (or create a new one), see the
DSL from the rule editor and maybe edit
the DSL from the rule editor so I can update while I write the rules.
If it is possible to internationalizate the GUI I can translate to spanish
*Felipe Piccolini M.*
rules-dev mailing list