GeneratorGeneratortypeCreates a project, a component or configuration once, when you run it, rather than taking part in every build.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →

FORMfactor

A report that generates local classes with static methods from an old FORM-based ABAP program, as code to paste in by hand, without support for 740 constructs, TABLES parameters or INCLUDEs.

FORMfactor reads an old program built from FORM routines and produces local classes with static methods from it. It runs as report ZFORMFACTOR and changes nothing in the system by itself: the generated code has to be copy-pasted into the report by hand. Its own limitations list three gaps: the new 740 language constructs, TABLES parameters and INCLUDEs. Installation runs in order — abapGit, then abapOpenChecks through abapGit, then FORMfactor — and the maintainer also points to FORMfactor-Eclipse.

Facts

Last pushLicenceMIT

Where it sits

Lives in
Provides
Clean code conventionsABAPClean code conventionscapabilityThe naming, structure and language-subset conventions that make source code readable across a team — and the question of which of them a checker can enforce.
Requires
abapOpenChecksabapOpenChecksartifactFORMfactor's second installation step, after abapGit itself and before FORMfactor is installed; the README does not say what it is used for.abapGitabapGitartifactInstalls the repository into the ABAP system; the README gives abapGit as the first install step.

Who is behind it

Lars HvamLars HvamPersonMaintains this
In the atlas: maintains 13, contributes to 92, wrote 1
@larshp
maintainerDomi BiglPersonContributes to this
In the atlas: contributes to 7
@bigld
1 contributor

Before choosing this

Signals

ActivityQuietNo published releases; repository quiet for 67 months

It publishes no releases, and its repository has been quiet for at least 24 full months. This may be normal for stable software; check whether its current state still fits your use.

What it declares

Every artifact

Type
Generator
Origin
Independently maintained

As a generator

Generates
Code or test data
Run with
does not say
Distributed through
abapGit

Connections3

README

quoted from larshp/FORMfactor under MIT, read
larshp/FORMfactor/README.mdOn GitHub

FORMfactor

Helps refactoring old FORM based programs to local classes with static methods.

Also see https://github.com/larshp/FORMfactor-Eclipse

Limitations
  • Does not work with new 740 language constructs
  • TABLES parameters not implemented yet
  • INCLUDEs not supported
Installation
  1. Install abapGit
  2. Install abapOpenChecks using abapGit
  3. Install FORMfactor
  4. Run via report ZFORMFACTOR, it will not automatically change anything in the system, code has to be copy-pasted into report manually.

image

MIT, read
Clean code conventions
  1. code pal for ABAP — Cloud EditionClean ABAP check set for ABAP Cloud
  2. code pal for ABAPATC and Code Inspector checks for Clean ABAP
  3. Clean ABAPOpen, versioned style guide for ABAP

Details

Sources3
Added by handdiscovered herechecked
github.com/larshp/FORMfactortree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
discovered viaAdded by hand
first seen in the atlas
ecosystem and domainabap, learning-and-reference
abaplint
issues under its own abaplint configuration145
lines934
statements550
objects2
files2
analysed, main
abaplint version2.120.84
Contributors1

From the repository’s contributor list, .

History in the atlas1
  1. First seen.
For your agent
Ref
artifact:larshp-formfactor
JSON
/artifacts/larshp-formfactor.json
MCP
Connecting an agent