Thanks for the heads up about all the yummy goodness of 1.7. Drooling has commenced.

One small question though...
Will 1.7 allow the Smarty {include} to be used in templates, to include template bits like 'headers' and 'footers', for leaner templates with less repetition?

Simon66

_________________
A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools.

This must be Thursday. I never could get the hang of Thursdays.

Douglas Adams - The only sane person in the asylum.

Why use {include} when there is {global_content}?

_________________
Ara Garabedian
Multimedia Designer / Developer
http://ara.ifky.com.au

If I allow my client access to Global Content Blocks I don't want them to have access to bits of the template.
I would prefer all unchangable template elements to be kept in 'templates' which only designers and developers have permissions to access.

I do use a GCB as the footer on all of my sites, but if I try to export from the Theme Manager it leaves out the GCB, which is another reason not to use GCBs more often in templates.

GCBs are brilliant for content, but I like to keep content and templates separate.

Just My 2cents.

Simon66

[EDIT] I also use them for editable content in templates, just not for template elements.

_________________
A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools.

This must be Thursday. I never could get the hang of Thursdays.

Douglas Adams - The only sane person in the asylum.

++ ... a clean separation  is IMO very important. 

Cheers,
Alex

Hi,

First of all, thanks for all this excellent job!
I have a question, will CMS MS be compatible also with PHP 5.0.0 and more ?
I have some website with some older version of PHP 5

Thank you for the answer!

@Solutic
CMS 1.7 will support php 5.2+

@others
The style dropdown was voted out of microtiny intentionally.  it won't be in.

_________________
Follow me on twitter
--
if you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
----------------
Don't make me angry..... you won't like me when I'm angry....

What possible reason would there be NOT to include the style dropdown? I think a better explanation than 'it got less votes than something else' is warranted.

Inline styles are fundamentally wrong and against best practices. It is imperative that there is a clear separation between the sematic and the aesthetic.

I really hate having to use TinyMCE in the first place, but now we're on the verge of having something clean and simple available with the advent of microtiny and its already being stuffed up!

_________________
Ara Garabedian
Multimedia Designer / Developer
http://ara.ifky.com.au

I have to agree - the styles dropdown and the SelfLink button are the standout features of TinyMCE. They really make things easy for my clients and staff.

Will begging, pleading and fawning make any difference?

Simon66

[I do understand that I'll be able to use the full editor as a separatre module, but the microtiny is such a good idea, that with styles it would be everything any of my clients would ever need.]

_________________
A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools.

This must be Thursday. I never could get the hang of Thursdays.

Douglas Adams - The only sane person in the asylum.

My guess - there are more developers in the dev team and few designers. Developers are not interested in designer stuff but programming functions. Therefore designers cannot push something by simple voting and are always overruled

_________________
CMS Made Simple 1.6: Beginner's Guide
Overview of modules, themes, tutorials and websites made with CMS Made Simple
Webseiten mit CMS erstellen

No, it's about focus on our core intentions:
a) separating content from design as much as possible
b) creating a tool where customers (the average receptionist, or spouse) can easily update content without messing up the look and feel of the site.    Edit:  and without having to memorize a bunch of 'rules'
c) creating a small easy to use, lightweight editor.   We wanted to get rid of a wysiwyg all together, and just go with a basic html or bbcode editor.  (something like the default html editor in wordpress) but we compromised.

A small editor with just a few limited options (bold/italics/underline, h1 thru h5, code and blockquote), and a properly configured stylesheet and template will allow the average end user to do 95% of what they need to do.

Designers should know HTML, and CSS, and know about the concept of separating design from content.  If they need a wysiwyg with 30 block styles in the list so that they can layout a page properly, they need to go back to school IMHO (I've edited a few sites built by other people where this was the case, the designer didn't have a real clue about what he was doing).   Otherwise, they can install and configure the full tinymce and muck along like they always did.

_________________
Follow me on twitter
--
if you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
----------------
Don't make me angry..... you won't like me when I'm angry....

Hello all,

thanks for the news about 1.7dev.