Thanks!
Hugh, I fixed the missing dependencies and committed a configuration file
that I had forgotten that fixes the error you found. Doing so made me
realize that there is no way at the moment to develop on windows machines.
This can and should be fixed, eventually.
Syd, as you figured out, you only need nodejs and npm if you want to
develop. The end result is a static site (HTML, CSS, JS) that can be
dropped anywhere. If you want to obtain that output to use it offline, you
will find it at the gh-pages branch
https://github.com/raffazizzi/romajs/tree/gh-pages (I'll updated it every
time I report back to council). Also beware that some design assets may be
remote for now, so I can't guarantee full off-line use.
Other responses in-line below:
On Thu, Apr 27, 2017 at 8:56 AM, Syd Bauman
I don't know how to add comments to or edit a GitHub wiki. (Not much of a wiki if others can't edit it, is it? But it's probably just me. I so rarely use the GitHub interface.)
Any GitHub user should be able to edit, so make sure you're logged in. The edit button is on the same line as the wiki page title, far to the right.
|> can't fix: it would require traversing the ODD again and I'd rather |> keep the redundancy in the ODD (moduleRef/@exclude AND |> elementSpec[@mode='delete']as it doesn't change the ODD at |> compilation.
I'm really suspicious of this. While I get that it's a lot of work, it does not seem to me like a minor thing to send an ODD back to the user that has both an <elementSpec mode=delete> and a
for the same element. We are going to get *lots* of complaints of the sort "I have an ODD that deletes X; I want X back, so I removed the <elementSpec ident=X mode=delete>, but X is still missing from my schema!".
That's a very good point. Will look into this again.
Besides, aren't you going to come across other things that will require traversing the ODD again? (Whatever that means :-)
Thoughts on the UI:
- at some point, perhaps future version: when a particular list is "active" (i.e., when it is the one that gets scrolled), give the user completion -- allow me to type the first few letters of an element to scroll to it, and to select/deselect it by pressing SPACE or RET or some such.
Good idea. I'm keen on making it as accessible as possible. In addition, I
It means having the program visit all of the tree nodes again. You're right that there may be a handful of cases where this is inescapable, but it slows things down, which is not great when you want a responsive UI. plan on creating a search box at the top that would allow the user to filter the module and elements. So typing "pers" would considerably reduce the lists to only show those modules containing elements whose tag name start with "pers".
*- **Break it*:
Worked for me on 1 simple test. But what, pray tell, is a canonicalized ODD?
Not sure whether that's accurate terminology, but it's what Oxygen calls resolving external dependencies (usually --exclusively?-- via XInclude). You find it under "Tools" > "Canonicalize..." I was just discussing this with James: a JavaScript web application will have trouble obtaining external dependencies, even if they're on the web. We may need to rely either on the user to canonicalize their ODD, or on a server-side component (hopefully oxgarage?), though that will still not fix all issues. Basically working with Roma JS will be like sending your ODD to a friend. If you don't make sure all parts are included, your friend won't be able to fix that troublesome schematron and generate a new schema for you.
- start bugging people directly for help
I was thinking of reaching out to you and Lou for looking over the wiki page with the tests and you have. Thanks! Can you think of other ways of including, adding, excluding, removing, etc modules and elements that are not in that list? Raff