standalone app without json about clics2 HOT 8 CLOSED

ah, right. ok, I'm sort of convinced. And yes, starting out with common names for locations in the file system is probably a good thing. Next would probably be common command names, and documentation a la "point your browser to file:///...".

from clics2.

in fact, this may not work, but the json is currently blown with stuff not needed which should be better put somewhere else.

from clics2.

Yes, I minimized the JSON object encoding the Graph data quite a bit for the clld app. Maybe this could be taken as starting point.

from clics2.

Yes, I think separating values in a similar fashion, maybe even using a similar way of creating json objects on the fly may be a good idea. Luckily, we don't have to do it immediately, as I think the current standalone is enough of a selling point.

What we should discuss more generally is, how we handle these cases in a way similar across applications. We have another standalone for concepticon, which makes a lot of sense for active developers but also for quick updates which are not a concrete release.

Is this something we generally want to support (I'd opt for "yes"), but if so, having similar namespaces ("app", "html") and workflows might also be useful.

from clics2.

What would be the concepticon standalone app? So far, I'd say CLICS is rather special in having a standalone HTML/JS app. So while I agree that figuring out smart ways to share code between clld app and standalone app would be good here, I don't think it is (or should be) a general feature across datasets.

from clics2.

Sorry, should've mentioned that:

• http://calc.digling.org/concepticon/

This is just an example for quick lookup in different languages. It IS useful for developers, although I hope we can also integrate it into concepticon.clld

from clics2.

and we have the CLTS lookup: http://calc.digling.org/clts/
again something we may want to integrate in some form in clts.clld, but for developers, it is again useful to have some quick access to the code via html-apps.

from clics2.

When writing up the clics draft, I'll mention the concepticon and the clics standalone. Based on what I write there, we can start discussing when everybody is reading the draft. So no need to decide immediately, but something we should have solved with concepticon-1.1 and the whole deployment of the new datasets before the SAB report, I suppose...

from clics2.