← all publishers

lookup-foundation

@lookup-foundation source repo

4 published skills

  1. Lookupengine Performance · lookup-foundation
    Keep the LookupEngine reflection engine and its descriptors allocation-light on the per-member hot path, and add a BenchmarkDotNet benchmark to check possible implementations. USE FOR: reducing allocations or reflection cost on the decompose path, choosing value types over heap types, pre-sizing collections, avoiding boxing and LINQ on hot paths, using spans, caching reflection metadata, disposing enumerators, reaching for unsafe accessors, and deciding when to benchmark and which candidate is the baseline. DO NOT USE FOR: writing a new abstractions or understanding the decompose pipeline structure.
    0
    installs
  2. Revitlookup UI Development · lookup-foundation
    Add a UI surface to RevitLookup as a WPF-UI page or window backed by a view-model contract both hosts implement, letting the same view run in the Revit add-in and the standalone Playground. USE FOR: defining a view-model interface, building the shared view, implementing the view model twice (the Revit-backed production version and the Playground mock), wiring navigation, and customizing per-type display with a template selector. DO NOT USE FOR: teaching the engine about a Revit type (use revitlookup-descriptor-model), or changing the shared WPF-UI control library in the LookupEngine.UI submodule.
    0
    installs
  3. Revitlookup Descriptor Model · lookup-foundation
    Teach RevitLookup to inspect a new Revit type by adding a LookupEngine descriptor and registering it in the type map, giving the object resolved members, synthetic extensions, and context-menu actions. USE FOR: creating a descriptor class, resolving members that need arguments or the active view, disabling or marking members unsupported, registering synthetic extension members, redirecting one type to another, adding context-menu commands that touch Revit through an external event, and wiring the descriptor into DescriptorsMap. DO NOT USE FOR: building a UI page or view model (use revitlookup-ui-development), or changing the LookupEngine engine itself in the submodule.
    0
    installs
  4. Revitlookup Winget Publishing · lookup-foundation
    Register a new Revit-year RevitLookup package on the WinGet community repository, the one-time manual step the release pipeline cannot do on its own. USE FOR: submitting a brand-new LookupFoundation.RevitLookup.{year} identifier to microsoft/winget-pkgs with komac, then wiring the year into the repo's WinGet DSC config and the build version list so CI updates it thereafter. DO NOT USE FOR: routine version bumps of an already-registered package (the pipeline does those automatically), or building the MSI installers and GitHub release.
    0
    installs