I am trying to gain knowledge of CSS3 so I know user interface module, it provides a bunch of properties in that has resize property, but I dont know why it has resize property that allow user to change size of elements.In addition to that I have no idea of what is purpose of user interface module is used for.
so I hope someone can answer this to me.
very thanks.
CSS Basic User Interface Module Level 3 (CSS3 UI) by Tantek Çelik and Florian Rivoal (editors), W3C candidate recommendation of 2 March 2017, has the following to say:
The purpose of this specification is to achieve the following objectives: extend the user interface features in CSS2.1; provide additional CSS mechanisms to augment or replace other dynamic presentation related features in HTML; introduce directional navigation properties to assist in the construction of user interfaces which make use of a directional navigation model.
Please note that a styling property does not become instantly available in all browsers just because the W3C published a candidate recommendation. You should check that you can actually use the properties described in the document. Can I Use comes to mind.
As far as I can tell the specification provides some nice tools for styling interactive HTML documents, such as web-based applications. For example, it allows drawing outlines around objects, modifying the shape of the mouse cursor and other such goodies. Whether you want to use them or not, and indeed whether you can use them or not depends on your design and your target audience.
As to "why it has resize property": because it exists in some browsers. In this case the W3C just documents and standardizes an already existing technology.
Related
My AppKit app's NSSegmentedControl doesn't show any labels in the Accessibility Inspector, meaning that disabled users won't be able to use assistive devices to interact with them. Calling setAccessibilityLabel and setAccessibilitySelected on the segment controls has no effect.
Similar advice on the topic (e.g., Disable / hide accessibility element) says to use accessibilitySetOverrideValue, which does work, but it is deprecated:
accessibilitySetOverrideValue(_:forAttribute:)' was deprecated in macOS 10.10: Use the NSAccessibility protocol methods instead (see NSAccessibilityProtocols.h)
The Apple docs at https://developer.apple.com/documentation/objectivec/nsobject/1535843-accessibilitysetoverridevalue read:
This method is deprecated. Use the new method-based API instead. For more information, see Accessibility Programming Guide for OS X or NSAccessibilityProtocol.
However, there doesn't seem to be any equivalent method to override an accessibility value. How can I accomplish this without using deprecated methods?
NSSegmentedControl will pick up the accessibilityDescription of the image. So the solution I used was to ensure all my segmented controls have images, and for each one, if necessary, make a copy of the image, set the accessibilityDescription explicitly, and reset the image.
Ugly, but better than any other solution I found.
I am currently doing a research work which involves the development of a web-based simulator for Automata.
I came across Cytoscape JS as a primary component in building our proposed simulator. I would like to ask if there some way that we can customize the appearance of the nodes in Cytoscape?
In our Automata simulator that we are working on, we intend to use the standard symbols (see image) and place a string value inside the node.
Standard State Symbols in Automata
I was wondering of what would be the proper implementation of the the node and in what way can we change (customize) the appearance of the nodes?
I hope somebody knowledgeable in Cytoscape js can advise.
Use the stylesheet : http://js.cytoscape.org/#style
Use the background properties to alter the background of the node. For example, you can use a custom SVG image.
It's up to you how you do it. There are many properties you can configure, or you could go full custom and just use your own SVG images in place of the built-in shapes and styles.
CSS Cascade and Inheritance spec defines the so called 'Override origin' for style sheets that links to DocumentCSS interface (from the DOM Level 2 spec from the year 2000). This seems to be the only mention of this interface on the W3C site (except of short conversation in the www-dom mailing list from 2008). The DOM Level 2 spec has the following text about it:
The expectation is that an instance of the DocumentCSS interface can be obtained by using binding-specific casting methods on an instance of the Document interface.
Is this mechanism implemented anywhere? Is it possible to play with these 'override styles' and to see the DocumentCSS interface in action?
Sorta exists in WebKit (via KHTML) but not really, because the implementation just returns null.
And that just-return-null implementation ended up in Chrome too but was subsequently removed.
Also, as a comment above notes, a Firefox feature request has been open for it for 10+ years.
As far as Edge, there’s no indication it’s been implemented there yet either.
So it seems the answer is, it’s never actually been supported anywhere. Maybe somewhere in the CSS Houdini plans there’s something that will provide the same functionality?
The question is: Is it a good practice to use SpriteVisualElement instead of UIComponent to create custom components? The reason being I can't add Sprite or FlexSprite as direct children of View and I see that UIComponent is quite heavy then SpriteVisualComponent from code point of view.
I searched extensively to confirm if there are certain examples elsewhere which shows use of this control as the base to create custom controls but could only find this. So actually I was little less confident about weather this is Ok or not.
Below is the supplement information:
Nature of application: Educational game application for children
Target platform: Mobile device (currently only Android platform)
Application environment: Flex SDK4.6 with AIR 3.8. Blank Spark application with spark.components.ViewNavigator. PureMVC framework used. Multiple Views to contain custom components which mostly use graphics package to draw themselves and to draw child controls within them (This is where I actually extend SpriteVisualElement for custom drawing as well as containing and displaying other custom controls).
Please suggest me if what I am doing is a good practice for a mobile app or not.
Thanks in advance and regards,
Sachin.
I use it often as SpriteVisualElement is lighter. I always try to use lighter things if it's fit my needs so I think it's a good practice especially for mobile development.
I am in the process of beginning work on several ASP.NET custom controls. I was wondering if I could get some input on your guys/girls thoughts on how you apply styling to your controls.
I would rather push it so CSS, so for the few controls I have done in the past, I have simply stuck a string property which allows you so type in the string which in then slung in a "style" attribute when rendering. I know I could also use the "CSSClass" property and apply the "class" attribute.
I have not done much in the way of creating a "proper" Style property (in which you actually save the style object, and use the designer to specify its values). This to me seems like a lot of work, and TBH, I hate the Style editor UI and would much rather type in the CSS/class name to apply..
What are your thoughts on this?
Note: This is kind of subjective - so to be clear:
The accepted answer will be the one that:
Offers the pro's and con's of the various approaches.
Opinions are welcome, but a good answer should be constructive.
Backs it up with some real-world knowledge/experience.
There is nothing wrong with subjectivity. There is a problem with people being subjective and not thinking, being constructive or actually providing some insight and experience.
>>DO NOT<< tag this as "subjective" - that tag is a waste of time. "subjective" is not a technology or a category that people will look for. Fix the question rather than brush it off.
It would depend on how the custom controls are being used - A commercial, re-distributable control should be compliant with the VS IDE, and behave the way users expect it to when they implement the control.
On the other hand there is no point in wasting a lot of time to get styling to work if you or your team are the only ones to use the control, so long as it's styling works in a sane way.
Most of the custom controls I have implemented use a property to define the controls look and feel or just expose the controls' members own CSSClass properties.
The argument comes down to consistency vs. time - any element should use consistent styling mechanisms, if strapped for time, use a string method if not, implement a more complex / IDE friendly mechanism.
I think you should consider your "target market" for the custom control, e.g., the people who will use it.
If it's an internal custom control, you can pretty much mandate the use of one or the other: if it's internal to the company you will have the ability to enforce its consistency.
If it's meant for commercial consumption, however, it is required that you give an option to provide a way to use either style or class. Case in point: the ASP.NET site navigation controls, e.g., SiteMapPath, Menu, Treeview. They have a bunch of properties exposed to allow either styles, classes, or a combination of both to each aspect of the controls' appearance.