cliu/ci-server-engineer
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
No description
102 commits 2 branches 1 tag 3.5 MiB
Find a file
cliu a298fdebc1 Layouts: every Layouts.xml parameter tested on desktop and web (#23) 
## Summary
- `graphics/tasks/layouts.md` §6: tested reference of every `Layouts.xml` parameter for the Operator Interface (desktop) and the HTML display (web) — frames, window options, menu/toolbars/status line, all commands, popups/modal/maximumOpen, translations, debug key, tabs.
- New rules: web-compatible frame shape (one `n*` per frame set, nested frame set only in that slot), `type="check"` required for `toolbar`/`statusline`/`playback record` (else the desktop client does not start), profile initial display replaces `initialDisplay` of frame `default`, always set `title`.
- Issues ISS-062..067 (readme differences and web limits), progress row, skill index.

## Test plan
- [x] 5 rounds of test layouts (`LT_*`) in a marked block of `Layouts.xml`; desktop via `jwuipoi -layout <name>` with window captures/recorder, web via `?d=…&l=…` in the browser and the web client code (CI Server R1.03.00).
- [x] Launcher display `LT_Launcher` for layouts opened from a display.
- [x] Clean-up: test system restored to its pre-test state; `LT_Launcher` removed.
- [ ] Not tested: print orientation/margins, playback, second-screen positions, `maximumTabs` limit for new tabs.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Reviewed-on: cliu/ci-server-config#23
Co-authored-by: cliu <cliu@noreply.git.yokogawa.tech>
Co-committed-by: cliu <cliu@noreply.git.yokogawa.tech>
2026-10-02 22:26:29 +10:00
.claude/skills Layouts: every Layouts.xml parameter tested on desktop and web (#23) 2026-10-02 22:26:29 +10:00
examples Micro Trend: connect item names (ISS-055 cause 1), document the remaining history-fill problem 2026-10-02 14:25:32 +10:00
knowledge Layouts: every Layouts.xml parameter tested on desktop and web (#23) 2026-10-02 22:26:29 +10:00
tools Add phase 2 setup and security summaries, setup check script 2026-09-30 14:09:30 +10:00
CLAUDE.md Complete phase 1 and build the CI-Eng-Sample project 2026-09-30 14:01:33 +10:00
README.md README: manuals are only needed to extend the repo, not to use it 2026-10-02 14:52:53 +10:00

README.md

ci-server-config

A knowledge base that lets Claude Code work as a Yokogawa CI Server (R1.03) engineer. Open this repo in Claude Code and describe what you want to do in CI Server.

Layout

Path Contents
CLAUDE.md Always-loaded instructions: role, version, where to look
.claude/skills/ How to do things. One skill per CI Server area; each task is its own file
knowledge/ Shared reference. Document map, glossary, known issues, cross-area concepts
examples/ Verified, working artifacts (class descriptions, reports, scripts)
tools/ Helper scripts Claude can run (e.g. the setup check)

Prerequisites

Using the repo needs no manuals: the knowledge is in knowledge/ and .claude/skills/. Only to extend the repo (summarize a manual, check a citation) you need the CI Server EN manuals locally. They are not stored in this repo. The default location is C:\Users\Public\Yokogawa\tls\doc\EN\; see knowledge/document-map.md if yours is different.

Contributing

  • Add task knowledge under the matching skill: .claude/skills/<area>/tasks/<task>.md, and add a row to that skill's SKILL.md index.
  • Write in your own words, cite the manual (IM number + section) and the version, and mark the content as verified or from docs.