Click here to Skip to main content
15,895,709 members

Intellisense for Hirarchical Resource Library of Xaml Graphics e.g. DrawImage

Oliver Bleckmann asked:

Open original thread
hey guys,

Is there a way of using xaml graphics (from within xaml) in a hierarchical way (e.g. icons.symbols.currency.dollar.xaml) and with intellisense support!? maybe even from another assembly!? for instance, let's say a we are going to put some icons from our iconliberary into something like this:
C#
<menu><menuitem><menuitem.icon><image source=icons.symbols.currency.dollar.xaml />... 


dealing with package uris is horrible. flattening my image repository is inacceptable. and bundling a huge ressource dictionary may lead to performance issues (not quite sure about that, started using prism, hab no time to test the behaviour on sl, using dynamic, merged ressources for ui styling from another assembly), right!?

there may be some problems with this using a resourcedictionary and encapsulation items in a user control. this may cause a the whole bunch (same hierarchy) to be loaded because other, unused "images" are part of the control (hierarchy), too. i know there are ways of using a webservice and other approaches like filtering and visibility handling (inefficent), datatemplates, dependenc-properties/objects or adding requiered ressources by hand, etc.

none of them seem applicable.

by the way, the icon library is generated by t4 templates, svg-to-xaml converters, etc. maybe i can publish the results here.

thanks for help.
Tags: C#, .NET, WPF, Silverlight, UI, MVVM, PRISM

Plain Text
ASM
ASP
ASP.NET
BASIC
BAT
C#
C++
COBOL
CoffeeScript
CSS
Dart
dbase
F#
FORTRAN
HTML
Java
Javascript
Kotlin
Lua
MIDL
MSIL
ObjectiveC
Pascal
PERL
PHP
PowerShell
Python
Razor
Ruby
Scala
Shell
SLN
SQL
Swift
T4
Terminal
TypeScript
VB
VBScript
XML
YAML

Preview



When answering a question please:
  1. Read the question carefully.
  2. Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
  3. If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
  4. Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.
Let's work to help developers, not make them feel stupid.
Please note that all posts will be submitted under the http://www.codeproject.com/info/cpol10.aspx.



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900