As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I am just beginning my career as a web developer. I have noticed alot of writings about iframes, and they seem pretty neat (pardon the venacular). However...
My instructors always frown on the use of frames. Is there a difference between frames/frameset and iframes? Should they be so negative in their views? Should I ignore iframes (as they suggest) and start learning ajax?
I am concerened about best practices moving forward.
Framesets are totally different than iFrames. Framesets break up a 'page' with a collection of items that contain content completely separate from one another. This destroys the ability to really bookmark anything other than the frameset itself unless you 'view frame content'. (These, quite frankly, are still around for purposes of historic preservation)
IFrames are simply a supported wrapper that lives within any html page that contains information from another page...whether it be a local or absolute reference. So, if you wanted to put the front page of 'http://theonion.com' inside of a div wrapper on some random page...you could...
As far as best practices go, I really can't imagine much reason to use either. If you really want to show content from elsewhere these days, you can get it in many different ways.
In terms of iframes & ajax...well...as you move forward in your career...try not to refer to them in the same sentence as having anything to do with one another.
=2 cents...
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I have always heard that it is better to avoid using <table> in HTML.
However, I encountered a situation in which a table would make my life easier when building a page that shows multiple products and their characteristics.
Should I try to hack it so that I do not need a table, or should I just go with a table?
No, you should not avoid the TABLE concept. Learn/Use it to display tabular data, not web layouts.
Learn about those elements from the W3C.
Tables
Div
Span
I use tables constantly in web apps - they provide a perfectly good and predictable way to display results in any browser.
Tables are for tabular data (like an excel sheet, etc)
Use CSS for times when the data is not tabular.
Tables are not dead, you just need to use them right :-)
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
Which is a better interface for designing an ASP.net application: drag and drop or manual positioning?
That defines on how you define "better".
"Better" in the sense that even an unskilled developer can get a webform up and running in no time: Use drag and drop.
"Better" in the sense that it gives a skilled developer more control over the generated HTML and CSS, potentially leading to
more robust layouting, compatible with a wide range of browsers, and
easier maintainance, due to a lack of unnecessary tags and attributes:
Use manual positioning and a lot of knowledge about HTML and CSS.
You use them all - anything to make the design you look for.
Drag Drop, Manual position, tweak changes, css write/change/delete/re-write, copy/paste, open close ten programs, search on google for other css, anything to make what you have on paper - and then is not good and you start over. Anything you can have you use it.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
We're bringing in outside content to our existing site along with its associated external CSS stylesheet and need to identify the CSS selectors that share the same name across the two files. Once identified, we plan on manually modifying each duplicate in the newly imported file, then changing the HTML accordingly.
Does anyone know of a tool that will do this? One painful way I thought about was to combine all the CSS into one Word Document and going down the page doing manual Finds? That would be nice to avoid though.
There is a firefox plugin called Dust me selectores which is designed to find unused CSS code. It may be what you're looking for.
You could merge the files into one, use a tool like CodeBeautifier with sort selectors enabled. A word of caution though: sorting selectors may change how they are applied to the final document.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I've been using Paint.NET to create mockups for my web application. They're pretty, and it's not hard to save the constituent graphical elements. However, the process of getting my layout into CSS is completely manual and time-consuming.
I'm aware there are better tools out there for this. Should I be looking at DreamWeaver? I'm not looking for any auto-generated web or data access functionality, and I'm happy to code all the behavior myself. I'm mostly looking for a great-looking layout editor that understands both layered imaging and CSS. (Preferably, one that can map a layered image to HTML and generate initial CSS with the right styling.)
Thanks in advance for any and all insight!
Jeff
A text editor, really.
It's time consuming, yes, but so is doing anything right. I have yet to use any program that builds the design of a website with a level of markup quality that I find even remotely acceptable. Where you may give a div a class of userInfo, most layout programs might give that div a class of style12 or something equally unhelpful. This results in unmaintainable markup, which is especially hard to build into a web application.
So learn how to do it by hand, and then do it by hand.
Axuer can be used to take mockups/prototypes and export as HTML/CSS: http://www.axure.com/
I only ever used it for prototyping.
There are no apps that will make it a css3, they apps that exist will give you a lot of image sprites and css2 and a lot of bugs you have to fix manually :/
So suggest coding it manually or hiring someone who does it(Kinda cheap these days even I would do it if I get paid well enough)
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
Why Views are not used in widely in Drupal?
The question is so vague.
Disadvantage of using Views module? One of the disadvantages I can think of is its difficulty to configure it properly. Too many configurations needed to make things work.
p.s. this should move to Drupal Answers.
Your question should really be "why do some programmers discourage the use of Views in Drupal?"
And the answer would be because of the massive amount of extra page overhead and extraneous markup that's generated by the module. Those of us who care about DOM complexity and semantic markup wouldn't touch Views with a 10 foot pole on a normal day, preferring to write quick custom modules to output code that we have full control over (and I mean full control without having to override countless template files for specific Views/display modes).
Don't get me wrong, Views is excellent for what it is and a newcomer to programming in Drupal would likely find it very useful. Also there are many, many contributed modules that extend Views and many that expose their data in a fashion accessible to Views so you can build some complex, well related queries if you know what you're doing.
I would also echo what Shivan Raptor has said in that the UI for Views is an unwieldy behemoth at the best of times; I'm sure to those who wrote it it's as easy as pie to use but I have been frustrated so many times trying to find how to make the simplest change to a View that I gave up using them altogether (except for Views provided by other modules that are already complete!)
So to summarise, your question's premise is indeed false, but if you wanted to know some of the reasons Views isn't more widely used then you do now :-)