Codync
무료 오픈소스 1:1 대안, Grok Bot과 Muse 대신
저장소 정보는 아직 수집하지 않았습니다.
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
메이커가 쓴 소개는 위의 한 줄이 전부입니다. 더 자세한 내용은 저장소 README에서 읽을 수 있습니다. 저장소 README ↗
README 전체를 불러오는 중입니다.
README 전문 보기 ↗Claferwiki is a wiki system integrated with Clafer compiler. Clafer is a lightweight yet powerful structural modeling language. Claferwiki allows for embedding Clafer model fragments in wiki pages and provides model authoring support including code highlighting, parse and semantic error reporting, hyperlinking from identifier use to its definition, and graphical view rendering.
Claferwiki supports informal-to-formal modeling, that is, gradually refining parts of specification in natural language into a Clafer model fragments. Claferwiki supports literate modeling - both the rich text and the model fragments can be freely mixed. Informal-to-formal modeling is important during domain modeling.
Also, Claferwiki acts as a collaborative, lightweight, web-based model publishing environment for Clafer. In addition to code highlighting, error reporting, hyperlinking, and graphical view rendering, it also provides model versioning and distributed online/offline editing capabilities as it is based on the Git distributed version control system and the Gitit wiki.
Claferwiki is also integrated with other Clafer Web Tools, allowing to open the current page in:
Try me! Also the Railway Wiki and the Traffic Lights Wiki.
If the demo is down or you encounter a bug, please email Michal Antkiewicz.
ClaferWiki is a gitit plugin: gitit loads it when it starts, compiling it with GHC, so GHC and the claferwiki package must be available where gitit runs.
cabal)plugins flag).
A dynamically linked gitit (for example, from a Linux distribution) can only load plugins with
jgm/gitit#714.All related projects are following the simultaneous release model.
The branch master contains releases, whereas the branch develop contains code under development.
When building the tools, the branches should match.
Releases from branches 'masterare guaranteed to work well together. Development versions from branchesdevelop` should work well together but this might not always be the case.
The plugin library is available on Hackage
and can be built with either stack or cabal-install:
stack build in a clone of this repository builds claferwiki and gitit;
start the wiki with stack exec gitit -- -f gitit.cnf (or ./claferwiki.sh), so that gitit finds the packages.cabal install --lib claferwiki installs the library into the default GHC package environment,
where gitit finds it; start the wiki with gitit -f gitit.cnf.The wiki needs gitit.cnf, static/ and templates/ from this repository in the directory where gitit runs.
Wiki can be configured by editing the gitit.cnf file. See Configuring and customizing gitit.
The wiki data is a git repository; see the repository-path: option in gitit.cnf.
For general usage information for the GitIt wiki see the README.
You can insert code blocks with clafer code anywhere in the page as follows:
```clafer
<here goes your model fragment>
```
The model overview, including the graph, stats, and download links, can be added as follows:
``` {.clafer .summary}
<the contents in this block are ignored>
```
To have the code blocks correctly processed, make sure to add an empty line before and after the code block, even if the code block is the last element on the page.
The blocks {.clafer .ide}, {.clafer .config}, and {.clafer .mooviz} become buttons that open the page's model in ClaferIDE, ClaferConfigurator, and ClaferMooVisualizer.
By default, the buttons link to the tools' ports 8094, 8093, and 8092 on the host that the browser used to reach the wiki.
The environment variables CLAFERIDE_URL, CLAFERCONFIGURATOR_URL, and CLAFERMOOVISUALIZER_URL give the tools' URLs instead, either full URLs or paths on the wiki's host, e.g., CLAFERIDE_URL=/claferide/.
Behind a reverse proxy, the wiki takes its own URL, which the tools load the model from, from the headers X-Forwarded-Host, X-Forwarded-Proto, and X-Forwarded-Prefix, e.g., with Apache:
ProxyPass /modelwiki/ http://127.0.0.1:8091/
<Location /modelwiki/>
RequestHeader set X-Forwarded-Proto "https"
RequestHeader set X-Forwarded-Prefix "/modelwiki"
</Location>