Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

May be a Terrible Idea: CSS Selector Framework #220

Closed
wants to merge 1 commit into from

Conversation

anaisbetts
Copy link
Member

Cool Ideas:

  • jQuery-type operations (XamlQuery has a good list)
  • CSS Selectors being the new WhenAny - i.e. not only will the selector return the current collection, it will update. <<-- That's Hard™
  • One-Way Binding VMs to CSS Selector results

Prior Art:

@anaisbetts anaisbetts mentioned this pull request Mar 21, 2013
8 tasks
@DamianReeves
Copy link

I love this idea. Been doing more web development lately and CSS Selectors are a killer feature XAML is missing (though I'm sure whatever solution is come up with needs to work across the presentation frameworks supported by ReactiveUI).

@bradphelan
Copy link
Contributor

Could we have a few motivating examples. In my mind a selector framework is
necessary for XAML styles.

For selection on Reactive object for WhenAny it could be complex in the
general case. For HTML selectors are simple cause it is a tree. VM can be
graphs. That might be fiddly.

In the simple case

This.WhenAny(x=>x.collection[*].field, x => x.Value)

Would be useful but it is not real c# notation. How about a linq to whenany
extension

From n in x.collection
Select n.field

@anaisbetts anaisbetts closed this Apr 19, 2013
@lock lock bot locked and limited conversation to collaborators Jun 26, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants