Skip to content

08-reference-map.md

Latest commit

 

History

History
65 lines (52 loc) · 5.54 KB

08-reference-map.md

File metadata and controls

65 lines (52 loc) · 5.54 KB
Raw

Reference Map

Local References

Installed VFP 9:

Legacy local help fallback:

  • C:\vDosPlus\FPD26\FOXHELP.DBF

Mounted VFP 9 media:

  • H:\program files\microsoft visual foxpro 9

Legacy/reference code on E:\:

  • E:\xBaseEngineRFV
  • E:\VFPSource
  • E:\VFPSource\ReportBuilder
  • E:\VFPSource\DataExplorer
  • E:\VFPSource\taskpane
  • E:\VFPSource\toolbox
  • E:\VFPSource\obrowser
  • E:\VFPSource\foxref
  • E:\DotNetFromVFP
  • E:\VFP - Installers

Web References

Key Lessons Pulled From The References

  • FFC indicates the framework layer is central.
  • ReportingApps proves reporting deserves its own maintained subsystem.
  • Local ReportBuilder, DataExplorer, taskpane, toolbox, obrowser, and foxref source trees are direct clean-room guidance for Copperfin report surfaces, data explorer tooling, task panes, toolbox UX, object browsing, and code/reference search.
  • HelpFile shows documentation gaps become operational risk.
  • The official Learn language reference is now the canonical command/function inventory for Copperfin parity planning, with local VFP help, generated CHM manifests, and FOXHELP.DBF serving as fallbacks when individual pages are incomplete or inaccessible.
  • Community project indexes highlight successors for project explorer, data explorer, toolbox/task panes, code references, and automated testing, which are all directly relevant to Copperfin's missing parity surfaces.
  • The broader community ecosystem also highlights project hooks, source-control-friendly serializers, property/method tooling, automated testing, deployment helpers, and PDF/report adjuncts that Copperfin should treat as real subsystem inputs rather than optional trivia.
  • GoToDefinition and FoxcodePlus are especially relevant to the editor parity story: they validate definition navigation, richer member hints, error-list-style assistance, and deeper IntelliSense as expected IDE behavior for FoxPro developers.
  • The local foxref, DataExplorer, toolbox, tasklist, taskpane, coverage, obrowser, and builders trees are now the clearest next-wave parity references for code references, data exploration, toolbox/task panes, coverage, object browsing, and builder workflows.
  • DataExplorer points toward an explorer-first workspace with object-specific actions such as browse, query generation, definition viewing, and procedure execution instead of a flat inspector-only pane.
  • toolbox points toward a customizable operator palette with categories, favorites, saved filters, and add-in extensibility rather than a hard-coded command strip.
  • obrowser points toward progressive search and noise-control toggles so deep object inspection stays usable at scale.
  • tasklist points toward task items that stay attached to real files, classes, methods, and lines instead of becoming detached notes.
  • builders and coverage point toward context-aware builders plus explicit analysis/export modes for debugging and quality tooling.
  • Existing open xBase-family stacks show that a modern compiler, runtime, project system, and tools layer can be sustained inside the contemporary .NET and Visual Studio ecosystem, which reinforces Copperfin's hybrid native-runtime plus VS-host strategy.
  • The installed foxtools help and extension files point toward a narrow dispatch-style native extension boundary, which is more useful to Copperfin as an interop/reference clue than as a direct implementation model.
  • The wizard/template system shows productivity and scaffolding are core product value.
  • Your local xBase/FoxPro-era code provides a starting point for file engine and compatibility research.
  • A modern successor should not trap users on DBF alone; connector-based SQL support is part of the modernization value proposition.