but we should easily allow for the use of one not to mention that we are pushing for this in 3.2. Also as I have stated its an element and by that definition it gets its own selector simply adding icon-user to the a makes it a modifier which is invalid.
also as for the : all browsers still allow and accept this and you will be hard pressed to see anyone adapt to one extra character for no real gain. Its in in valid spec in my eyes also CSS is completely different than html
css spec is almost never adhered to as its always behind where html is not.
[Define New Theme] 12. In-Depth Design study on each block of content semantics + modularity
Forum rules
Please do not post support questions regarding installing, updating, or upgrading phpBB 3.3.x. If you need support for phpBB 3.3.x please visit the 3.3.x Support Forum on phpbb.com.
If you have questions regarding writing extensions please post in Extension Writers Discussion to receive proper guidance from our staff and community.
Please do not post support questions regarding installing, updating, or upgrading phpBB 3.3.x. If you need support for phpBB 3.3.x please visit the 3.3.x Support Forum on phpbb.com.
If you have questions regarding writing extensions please post in Extension Writers Discussion to receive proper guidance from our staff and community.
Re: [Define New Theme] 12. In-Depth Design study on each block of content based on semantics
No problem. See the button "New Topic" with class .btn-new.hanakin wrote:Try and recreate the current New Topic buttons of prosilver using font-awsome icons then hide the text below 480px. omit the gradients and shadows just focus on colors and size.
Instead of specifying the font size in pixels, you can use rem units, but, unfortunately, does not support IE8 and some other browsers.
Sorry for my English.
Re: [Define New Theme] 12. In-Depth Design study on each block of content based on semantics
3.2, here we comecallumacrae wrote:phpBB doesn't use an icon font library.
Re: [Define New Theme] 12. In-Depth Design study on each block of content based on semantics
hmm, not sure thats going to flySumanai wrote:No problem. See the button "New Topic" with class .btn-new.hanakin wrote:Try and recreate the current New Topic buttons of prosilver using font-awsome icons then hide the text below 480px. omit the gradients and shadows just focus on colors and size.
Instead of specifying the font size in pixels, you can use rem units, but, unfortunately, does not support IE8 and some other browsers.
it still breaks modularity as I have stated the icon is an element level model and thus requires its own selector by proper design. Its not a modifier which is how you are using it.
Re: [Define New Theme] 12. In-Depth Design study on each block of content based on semantics
Do not see the point of blockage markup. Icon is a design, and it should not be present in the markup. In addition any conceivable icons in any manner there is no problem, as I have shown in the example.
Sorry for my English.
Re: [Define New Theme] 12. In-Depth Design study on each block of content based on semantics
its less extensible and less controllable. lets say we decide not to use a font on a project but instead a sprite with my approach you can define exact dimensions to the icon whereas with yours it requires large files as you have to account for the size of the container. also how do you go about stacking icons in your approach http://fortawesome.github.io/Font-Awesome/examples/ ?
by working with pre-defined re-useable blocks of code in this manner we simplify the browser space as well as increase modularity in that its fully and truly an object based approach.
by working with pre-defined re-useable blocks of code in this manner we simplify the browser space as well as increase modularity in that its fully and truly an object based approach.
Re: [Define New Theme] 12. In-Depth Design study on each block of content based on semantics
Sorry, but I do not see nothing "expandable" and "uncontrollable".hanakin wrote:its less extensible and less controllable.
I changed the example, increasing the size of icons on screens up to 480.hanakin wrote:but instead a sprite with my approach you can define exact dimensions to the icon whereas with yours it requires large files as you have to account for the size of the container.
Make as much as I do, and compare spent bytes.
I honestly do not care what they show in some examples the use of some font.hanakin wrote:also how do you go about stacking icons in your approach http://fortawesome.github.io/Font-Awesome/examples/ ?
If there is a tag used <marquee>, you will promote it?
My version of more pre-defined and re-useable. To create a button with gradient and border in style forum just add one class in one tag. At your version to copy the entire structure of the markup.hanakin wrote:by working with pre-defined re-useable blocks of code in this manner we simplify the browser space as well as increase modularity in that its fully and truly an object based approach.
Sorry for my English.
Re: [Define New Theme] 12. In-Depth Design study on each block of content based on semantics
with your way you a specifying how the icon is used. with mine I can place the icon anywhere I want and the same css works you want it before the text in the button place it there in the html no css needs changed. <-- more controllableSumanai wrote:Sorry, but I do not see nothing "expandable" and "uncontrollable".hanakin wrote:its less extensible and less controllable.
all icons should be in one sprite. so count the number of icons and the fact that they are different sizes and used in different ways in prosilver. you will end up with a very complicated extremely large file full of a lot of white space. With mine all the icons fit on a single row with no spacing in between.Sumanai wrote:I changed the example, increasing the size of icons on screens up to 480.hanakin wrote:but instead a sprite with my approach you can define exact dimensions to the icon whereas with yours it requires large files as you have to account for the size of the container.
Make as much as I do, and compare spent bytes.
It shows usage an modularity the ability to stack icons, spin them with modifiers applied to the element. <-- stack two icons with your method?Sumanai wrote:I honestly do not care what they show in some examples the use of some font.hanakin wrote:also how do you go about stacking icons in your approach http://fortawesome.github.io/Font-Awesome/examples/ ?
If there is a tag used <marquee>, you will promote it?
its not because you have to create a new style based on positon of icon based on the size of the container and the content with in <-- add your class to the search to add the icon what happens you have to make a new class. <-- less modular HTML & CSSSumanai wrote:My version of more pre-defined and re-useable. To create a button with gradient and border in style forum just add one class in one tag. At your version to copy the entire structure of the markup.hanakin wrote:by working with pre-defined re-useable blocks of code in this manner we simplify the browser space as well as increase modularity in that its fully and truly an object based approach.
Re: [Define New Theme] 12. In-Depth Design study on each block of content based on semantics
You change the markup, I styles. Just different approaches. Only your approach requires additional markup, and my no.hanakin wrote:with your way you a specifying how the icon is used. with mine I can place the icon anywhere I want and the same css works you want it before the text in the button place it there in the html no css needs changed. <-- more controllable
And if you want to put all the icons before the text, you have to change the position of elements in many places.
Sprite? You have the same font icons. What do you mean?hanakin wrote:all icons should be in one sprite.
For what? Fictional situation.hanakin wrote:It shows usage an modularity the ability to stack icons, spin them with modifiers applied to the element. <-- stack two icons with your method?
However, I still have a pseudo element :after.
In my case, one class describes the button with gradient and border, the second adds an individual icon. Everything else is solved styles and media requests. What separate class?hanakin wrote:its not because you have to create a new style based on positon of icon based on the size of the container and the content with in <-- add your class to the search to add the icon what happens you have to make a new class. <-- less modular HTML & CSS
Sorry for my English.
Re: [Define New Theme] 12. In-Depth Design study on each block of content based on semantics
exactly the concept of this entire post the html should be the first piece created using the block/component/element method based on the content. An icon is a piece of content that can be used in several ways and place throughout the html. Also by your method you are not building an object in css as you have to reinvent the wheel with each use case.Sumanai wrote: You change the markup, I styles. Just different approaches. Only your approach requires additional markup, and my no.
And if you want to put all the icons before the text, you have to change the position of elements in many places.
you missed the point by declaring an icon element you are not restricting your self to an icon font having to be one way and a sprite based concept another. They both can utilize the same object.Sumanai wrote: Sprite? You have the same font icons. What do you mean?
their is no such thing as a fictional situation when it comes to OOD its meant to be self contained and infinitely configurable. This actually comes in handy when working with complex icon concept like that of the forum imagesetsSumanai wrote: For what? Fictional situation.
However, I still have a pseudo element :after.