Framework Themes, Dynamic themes and Plug-ins
1. Am I right in understanding the difference between 'standard' and 'Framework Theme' templates:
• Old (standard DWT) template: Once updated and saved, and changes ripple through pages based on that template, all changed pages need to be (re)uploaded to remote server (i.e. normal procedure).2. Am I right in understanding that 'Plug-ins' = 'includes'?
• New (WA Theme) template: Once updated, only that (WA Theme) template needs to be uploaded to remote server (along with any newly included related files)?
Right from the off, the use of the word 'plug-ins' has given me brain-haemerrhoids in my effort to comprehend any instruction on the workings of the framework. Had the word consistently been 'includes, I would (I believe) have got my noodle round the concept a lot more quickly.
I read (or at least started to read) the official guide, but ended up re-reading the same paragraphs over and over, but was constantly in the dark. Either I was too dim or the GSG bulb was broken. I am at the (st)age where no matter how much I think about and try to get to grips with new ideas, the bulk of thinking tends not to save on exit: having to translate at the same time is definitely a step too far.
3. Visual Aids
I need them. Had it not been for Russell's work on the explanatory Pdf I would be in a very large huff and feeling horribly left out of the buzz. I would love it if Russel could be part of the process on future guides, - some people (me) learn things so much more easily with visual instruction.
4. This doesn't appear to be a 'framework' or 'framework builder' as such. The framework (as I understand it) will contain other components (as advertised), e.g. a data-grid. When these arrive, will there be dot-release upgrades to existing framework builder, and will these 'slot in' to an actual framework?
5. Thanks Russell, - good job. You got WebAssist a sale (imminent).
Cheers all.
