Posted by Deevan in In the old days, the 90’s, raster technology - the employment of a single layer as a solution for all obvious publishing jobs - was king. Those days are well past and vector technology rules now. Vector solutions comprise layers of data, and this is the way all modern graphics, sea charts, printing jobs and much else is done.
Come visit us right here for more Joomla Template Info and get Three Free Joomla Template Ebooks Joomla Template Guide. http://www.joomlatemplatezone.com/
Understanding the difference between vector and raster technologies is vital for both graphics and webpage code.
you’ll need a vector graphics file, which can be scaled to any size. An example is an Abobe Illustrator .ai file, which is thus a level above Photoshop. This will conflict with the popular opinion of Photoshop being the ultimate gfx app - but sadly the truth is it’s just a basic tool now, pro work regularly demands a much better application.
the same applies to web page code, whether on hand-coded sites or on database-driven CMS websites. The old, ninety’s method was, if you like, a ‘raster’ approach : everything was on a single layer. Its use is typified by tables and cells for the layout framework.
This vectorised approach uses layers ( divs ) and CSS to build the page structure. Just as you can’t use crude raster gfx for many print roles, crude raster-based 2D pagecode is long superseded for the modern web.
Vector-based webpages have big advantages in accessibility and SEO for example. However, web writing applications such as SiteSpinner were using layer-based pages totally, years before Dreamweaver had ever heard of such a thing.
By 2004, div-and-table temporary compromises like the one Joomla uses were finished. The page code layout it uses became outdated ages back, and so changes are way overdue.
It’s true that talented developers can mitigate this to some degree, by clever template coding. However, the effect of tables in the code can never be wholly eliminated and it’s time they went. Even a remnant of this technique left in a corner somewhere wrecks the project, as progress is basically halted.
However this approach tends to end up in a very straightforward and light-weight template, as too much has to be done by the template coder.
But there is a limit - at what point do you put the cutoff point and say enough is enough? In theory, taking this to extremes, it wouldn’t matter what the core did as long as you could plug something in.
imagine what would be possible if Joomla had a core tableless code layout scheme. You’d be able to get templates that had, as well as the common features, built-in source ordering controls. Now that is what I’d call progress. You might not see that as serious but apropos SEO and accessibility ( best regarded as the same thing in any case ), that could be a massive leap forward.
It’s correct to claim that a developer can do almost anything with Joomla - but that isn’t truly the point of the project in numerous peoples’ view. If functions are available to the average website owner then the application succeeds ; if they’re not, and are only there for developers, then you have an wholly different beast. That would not be Joomla and it would not be as successful.
fortunately , Joomla is such a phenomenal multimedia publishing tool that it compares well with the best of them. However, the future looks ominous unless radical changes are made, as it’s hard to support steam age technology in the modern world.
Come visit us right here for more Joomla Template Info and get Three Free Joomla Template Ebooks Joomla Template Guide. http://www.joomlatemplatezone.com/
.
About the Author:
Come visit us right here for more Joomla Template Info and get Three Free Joomla Template Ebooks href=”http://www.joomlatemplatezone.com/”>Joomla Template Guide.
http://www.joomlatemplatezone.com/
Joomla Template Development
Article Source: ArticlesBase.com - Joomla Template Design
[affmage source="amazon" results="5"]joomla developers guide[/affmage]