It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 9 years ago.
I do a lot of front end work and was thinking of picking up CSS LESS, but midway through learning it, realized it may not work the way that I thought it would work and might not be able to help me as much. So I think below is how CSS LESS works, could someone who have used it just confirm please?
CSS LESS works using the SimpLESS compiler and makes the process of
initial css coding more easy with programming elements implemented.
However, before uploading the css code, it must be converted from the
dynamic .less format to the normal .css format and once uploaded to
the server, can only act as a static .css file.
Is the above correct? I ask because I work with a lot of wordpress websites and themes that already have the majority of their stylesheet created, and if I have to compile the .less format to .css format and reupload every single time rather than being able to use it as a dynamic pre-loaded library like jQuery, then I might not be able to get as much out of CSS LESS as I previously thought it would benefit me.
Both LESS and SASS are technologies designed to aid in the development and maintenance stages of creating CSS files; they work similarly to how Coffee Script is designed to work for javascript. In the end, however, LESS and SASS end up as CSS files just as Coffee Script results in plain old js files.
In any case, there are workflows that automatically handle compilation/save/upload of CSS files to prevent that step from taking extra time and work on your part, but no - browsers do not understand them by default. You can use javascript implementations as comments have mentioned, however.
LESS/SASS have their strengths, but making minor tweaks or customizations of existing themes and styles might not necessarily be one of them. This is not to say that you might not actually get a lot out of the technologies, but that is beyond the scope of your present question and would not even be something I am presently qualified to answer.
Related
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 9 years ago.
I have to create an application for link and video sharing, similar to facebook. I tried to search any tutorial/demo/code snippet for the same. There are tons for tutorial in php to do that
Link 1
Link 2
Link 3
Link 4
Unfortunately, I didn't find any tutorial on ASP.NET. I also tried to convert the php code to asp.net but due my zero level knowledge in PHP I am not able to convert it completely. I did install PHP to ASP.NET 1.x migration but as per tutorial it is not reflecting on VS2005, VS2008 & VS2010.
Can anyone guide me how I can implement the same with asp.net? Or how I can convert the existing code from php to asp.net?
PHP is a pretty simple language to pick up and certainly isn't something that would convert to asp.net without a LOT of rework as the conceptual model is just totally different.
I'd suggest you take a look at the php.net site, specifically the language reference area. That site is the go to place for understanding php. You may also want to start with a simple example and work up from there. That way you can start reading your existing code to figure out what each function call means.
The good news is that php and c# share the same root language so things like foreach work pretty much identically between the two.
After you've gone through a bit of that, come back and post a question about a specific problem you are having or a specific area of the php code you don't understand.
Finally, if your willing to look a project that does this whose only requirement is the usage of json, then check out http://embed.ly
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 9 years ago.
When I first started learning front end development I used to see the first line comment
/* css document */
or something to that extent, I can't remember what it was...
I haven't used it recently. Is it even necessary anymore?
Was that just a dreamweaver thing?
Could having your first line of css as a comment be dangerous?
CSS doesn't need any declaration like HTML documents do need DOCTYPES (well they don't need them but it's highly recommended)
Having a comment as first line in your CSS isn't dangerous at all. (In fact WordPress themes requires this, but that's something completely else)
You never have. From what I recall, the first line css comment was a, somewhat unnecessary, feature of dreamweaver at some point. Its only purpose was to remind the user that they were writing a css file, which was only necessary because dreamweaver would automatically save the document as .css if you clicked New>CSS File.
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
I am working on a custom CSS file within a wordpress theme installation.
Within the CSS, there are times when I need to identify something like '.example', other times when it must be displayed as '#example' and other times when it is fine to keep it as 'example'.
Could someone please clarify the rules and how I can distinguish and decide for myself in the future which one to use in each instance?
This might have something to do with div ids and classes.
There is no 100% rule but generally:
An id must be unique, therefore any styles applied to an ID are only usable for the one element on the page. Therefore it usually makes more sense to style by class rather than ID because the mjority of the time you are going to want to reuse your styles. Additionally using an ID makes it harder to override the style later because id's hijack specificity.
I even take this one step further in that nothing should EVER be styled by ID but rather always styled by class. The one exception i occasionally make is for page-level scoping based on the id of the body tag. But even then a class is just as useful.
Id recommend reading up on OOCSS (note: i dont use any of the files used to illustrate the examples - im solely referencing the FAQ)
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
The question: from a programming point of view, does WordPress allow a similar kind of flexibility that I would get by writing my own Java EE system? E.g. if the site owners suddenly decided that users whose birthday was on a Wednesday had to be sent a notification email and their birthday event had to be entered into a calendar that other members of the site could then RSVP to and then give a star rating afterwards to say how much they enjoyed it... could I do that easily with WP?
Hope that's clear, really welcome any feedback.
Wordpress is a bit easier to get started out with, and you can install whatever plugins you want easily. The only problem with it, is that it is a lot like windows: it accounts for many people's use cases.
For you, with a business/corporate (you mentioned corperate applications before the edit of your question)/extensible platform in mind, I would recommend sticking with what you've got. You've written it yourself (or as a team) so you know everything about it, and what to look for when there is a bug. It's easily extended with your own code, and you don't have to sort through and learn a new language.
Wordpress is great for blogs, as that is what it is designed for. It is good for general purpose websites with dynamic layouts, but relatively static content (blog posts, write it once, edit a few times, but relatively static). Sure, you could write plugins for it, and many have been written, But it won't have nearly the capabilities you seem to require without major extensions.
Also, being written in PHP, it has to be interpreted, as opposed to java, which is a semi-compiled/optimized bytecode (a bit complex) but java runs faster than the equivalent PHP code.
So benefits of your system:
Faster
More reliable
Suited for very dynamic content
Benefits of wordpress:
Easier to extend
Suited for static content
Easier for novices to use (but your own interface may work just fine)
WordPress is incredibly flexible, and can, without a doubt, be a viable framework for your app. You should definitely check out it.
That said, if you're building something this complicated, I'd go with what you know. You're gonna make mistakes and do things in weird ways on your first few WP projects.
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
Is there any way to hide css files on WP? I need to hide style.css file and file route.
Not only style but also need to hide other css file and their routes.
The fact is, any and all Style Rules are required to be either written directly to the document itself, or referenced in the head element in the form of a link tag.
There's no big secret to styling, so I'm not entirely certain why you would want to "hide" your stylesheet from prying eyes. Even if you were to create several hundred decoy CSS files and use cleverly placed #import rules to "confuse" somebody trying to find the actual filepath, what's to stop them from using a Web Inspector and seeing the active rules and the stylesheet in which they're contained?
Sorry to say, but you're pretty much going to have to deal with the fact that Style rules can be accessed by anybody.