This classified ad has expiredClick here to view current advertisements similar to this one.
In the old days, the ninety's, raster technology - the utilization of a single layer as a solution for all visible publishing tasks - was king. Those days are well past and vector technology rules now. Vector solutions comprise layers of information, 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. [please contact me for website address] Understanding the difference between vector and raster technologies is vital for both graphics and net page code. you will need a vector graphics file, which can be scaled to any size. This may conflict with the popular opinion of Photoshop being the ultimate gfx app - but sadly the truth is it's merely a basic tool now, pro work often demands a far better application. the same is applicable to net page code, whether on hand-coded sites or on database-driven CMS internet sites. The old, ninety's technique 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. Around 2002 this strategy became outdated and layer-based page code took over. This vectorised approach uses layers ( divs ) and CSS to build the page structure. Having a 3rd axis means that the page code is an order of magnitude better, and there are great advantages. 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 net pages have big advantages in accessibility and SEO as an 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 such as the one Joomla uses were finished. This is the most imperative change that should be made to Joomla, and beside this all other requirements seem far less applicable. Even a remnant of this strategy left in a corner somewhere wrecks the project, as progress is fundamentally halted. Joomla 1.5 has total overrides available to template coders. However this approach tends to end up in a particularly straightforward and lightweight template, as too much is having to be done by the template coder. It is not a bad thing for SEO, of course, if a template is lightweight - but what if you need a full-feature one with 30 collapsible module positions and 10 inbuilt color variations? just about anything can be plugged in or overridden in Joomla. This is a component of the tradition, and one of many reasons it is such a robust machine. But there is a limit - at what point do you put the cutoff point and say enough is enough? In principle, taking this to extremes, it would not matter what the core did so long as you might 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. It's correct to say that a developer can do almost anything with Joomla - but that isn't really the point of the project in many peoples' view. 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 tough 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. [please contact me for website address] |
