pimhwang/ILSpy - ILSpy - git.quantfans.net

Author	SHA1	Message	Date
Christoph Wille	002748d5d0	Give dark-theme syntax colors a perceptual contrast floor The dark palette is hand-authored for C# only; every other highlighting definition -- XML, IL, Asm, and all AvaloniaEdit built-ins -- is derived by inverting HSL lightness. HSL lightness is not perceptual luminance, so the result depended entirely on hue: blue carries a 0.0722 luminance weight, so plain Blue landed at 4.08:1 against the editor canvas, and an already-light source such as Asm's #8080FF inverted downwards to 1.29:1 -- invisible. Reported against XML resources in #3986. Enforcing a 5.5:1 WCAG floor on the converted foreground fixes every affected definition in the one place they all route through, which a per-language palette would not: the AvaloniaEdit built-ins (JSON, Markdown, JS, HTML, CSS, Python) have no palette to author. 5.5 is where the existing CSharpDark values already sit; the 4.5 AA threshold was measured and only moves the reported blue to 4.51. The floor is deliberately foreground-only -- forcing a span background to contrast with the canvas would repaint Asm's #EEEEEE Registers background as a bright block and bury the text on top of it -- and it is measured against the surface the foreground lands on, which is that span background when the colour declares one, so a light-on-dark span cannot be pulled apart into two colours that no longer contrast with each other. The same function's desaturation guard only fired when the inverted lightness stayed below 0.75, so a dark fully saturated source (DarkMagenta) came back light and still fully saturated -- exactly the neon the softening exists to prevent. Only the softening becomes unconditional; the lightness lift paired with it stays scoped to over-saturated colours, because it is not monotone across its own 0.75 boundary and would reorder neighbouring greys. Hyperlinks were a second, unrelated path: nothing ever set TextView.LinkTextForegroundBrush, so the About page and every decompiler-view link used AvaloniaEdit's registered default of pure blue, 1.94:1 on dark. They now share a themed ILSpy.LinkForeground with the metadata table's token cells, which take it from a style rather than a local Foreground so the selected row's white override still wins over the accent fill. Assisted-by: Claude:claude-opus-5[1m]:Claude Code	1 month ago
Siegfried Pammer	51aafa0fd9	Move ILSpy UI code back to the ICSharpCode.ILSpy root namespace The Avalonia port had placed the UI app in an ILSpy.* namespace tree, while the csproj RootNamespace and every prior release (through 10.1) use ICSharpCode.ILSpy.*. Restoring the historical namespace reduces the public API diff against release/10.1 for plugin authors and removes the shadowing that forced global:: qualifiers in the test project. The Images class and AccessOverlayIcon enum move back into the root namespace (as in 10.1), since an ICSharpCode.ILSpy.Images namespace would shadow the Images class for all code inside ICSharpCode.ILSpy. Assisted-by: Claude:claude-fable-5:Claude Code	3 months ago
Siegfried Pammer	28c345ca0f	Keep metadata {Column}Tooltip props out of the grid columns The reflection-driven column builder turned every public property into a column, so each {Column}Tooltip companion (NameTooltip, FlagsTooltip, ...) rendered as its own raw column next to the column it describes. That text is already surfaced as the sibling cell's hover tooltip by MetadataCellTooltip, which reflects the property off the row directly, so dropping these properties from the column set leaves the tooltips intact and removes the duplicate columns. Assisted-by: Claude:claude-opus-4-8:Claude Code	3 months ago
Siegfried Pammer	102bf2cc5b	Per-column filter inputs in metadata grid headers Replace the single text-bar above the grid with one filter input per column, baked into each DataGridColumn's header. The page model carries a ColumnFilters collection alongside Columns; the filter predicate ANDs every non-empty column's case-insensitive substring match. Column instances are built fresh per page so sibling tabs don't share filter state, and the column name moves to Tag for cell-level lookups now that Header is a Panel. Assisted-by: Claude:claude-opus-4-7:Claude Code	3 months ago
Siegfried Pammer	3ae24fc12a	Render token cells as hyperlink-styled buttons [ColumnInfo(Kind=Token)] properties now produce a DataGridTemplateColumn whose cell is a transparent-background, blue-foreground Button — the hyperlink affordance the user clicks to jump to the target table row. Click raises NavigateToCellRequested(Row, ColumnName) on the owning MetadataTablePageModel; Phase 3c subscribes from the dock workspace, resolves the token to its target table tree node, and scrolls into view. Assisted-by: Claude:claude-opus-4-7:Claude Code	3 months ago
Siegfried Pammer	508331c5cb	Datagrid tab infrastructure for metadata tables Lays the rails for Phase 2 without flipping any existing nodes onto the new path: MetadataTablePageModel + MetadataTablePage view + MetadataColumnBuilder (cached per row type), an ILSpyTreeNode.CreateTab() hook the docking host now consults before falling through to the decompiler tab, and an App.axaml DataTemplate routing the model to the view. PE-header / heap / table nodes still decompile as text — they get flipped to CreateTab() one batch at a time in subsequent commits. Assisted-by: Claude:claude-opus-4-7:Claude Code	3 months ago