Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

DirDyVTST editor: functional redesign, and use as the basis for fragment calculations

Open
#221 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
c
Domain
desktop, tooling

Research direction

Start by reviewing the DirDyVTST editor (dirdyed) and the window screenshots in issue #210, which this issue references. The issue leaves the workflow redesign and the meaning, setup, and code coverage of fragment calculations undecided, so those requirements need to be clarified before implementation. Done means the functional redesign and fragment-calculation scope are agreed; the visual changes from #210 are already applied.

Written by the indexing model from the issue text.

Description

Summary

From the review of the #210 window screenshots (@ohlincha, 2026-10-04): the DirDyVTST editor (dirdyed, "ECCE NWChem DirDyVTST Editor") should be redesigned in terms of functionality, and should serve as the basis for fragment calculations.

To be worked out

  • What the redesign changes in the current editor's workflow.
  • What a fragment calculation means here: which fragments, set up how, and which codes it applies to.
  • What carries over from the DirDyVTST editor (its handling of several structures in one setup) and what has to be new.

The visual changes from #210 (theme colours, fonts, field widths) already apply to this window; this issue is about its function.

Dominant language
C
Stars
10
Forks
8
Avg merge
21m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from FriendsofECCE/ECCE

All issues in FriendsofECCE/ECCE

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.