Designing web-sites can be difficult for anyone .... However, inherently web based content is text oriented...
"Web design" as I see it is expressing a design in a text-based framework. Design and the serialization of it are both non-trivial efforts. Content, with the rise of podcasting and YouTube, broke out of its historical text-orientation. Which existed because text is cheaper than audio is cheaper than video--in cost, and bandwidth. But the progression was driven by the desirability of the latter across people as a whole, and the expansion of broadband.
Creation for me is a lot about seeing some result, then backtracking and editing. If I were to use iEngine, it would have to be through scripts rather than a shell, where I could try more than once to produce my desired result. It's just never going to be one-pass for me.
In reply to Re: RFC iEngine
by sapphirecat
in thread RFC iEngine
by muscipula
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |