Page 1 of 1

Re: Xstandard vs. Smarty

Posted: Thu Aug 03, 2006 2:03 pm
by cyberman
Serialthunder wrote: So know the main question: Is there still development for this module?  ???
The last version of xstandard module cames out in june 2006 - perhaps you should make a feature request  ;)?

But have you tried to "hack" the module by yourself  ;D?

Go to line 257 in modules source view and add there

Code: Select all

				<param name="Options" value="8192" /> 

Re: Xstandard vs. Smarty

Posted: Fri Aug 04, 2006 4:52 am
by cyberman
Serialthunder wrote: Why the Option does not work like I thought, I don't know. Perhaps someone has an better Idea, so please post it here!
Hmm - never used xstandard before, my favourite is TinyMCE. There's an option to create valid output. So I've read a little bit in xstandard docu. Is there an other option like CustomInlineElements (not the same) ? So you could mark CMSms module calls as valid input  ::)
Never the less it would be cool if the options could be in front-end of Xstandard-Config.
As I said - you need a feature request  :). Don't know if xstandard module devs are every time here ...

Re: Xstandard vs. Smarty

Posted: Mon Aug 07, 2006 7:40 am
by zerrvox
hi,

I have just seen your post on the Xstandard forum and your feature request.

I think that I did some testing on this subject before the last release but apperently not enough or I settled down with that it was possible if you just used the xml view but I will have a look at it again.

I have several other improvement in my mind for a new release but I have just been on vacation so I have to catch up with the workload first but development is not stopped.  :D

Hopefullly I will have a new release out within two weeks.

Re: Xstandard vs. Smarty

Posted: Mon Aug 07, 2006 11:24 pm
by zerrvox
that was actually one of the things I wanted to include into the first release but I could not come up with a smart solution so I ended up postponing it to the next version. I really hopes this makes in into the next version but I want it to require no knowledge of xml or the Xstandard api, so I will have to find a way to generate this xml file and allow the user to add and remove styles directly from the admin. If you have any ideas to how you would prefer this is implented then I would very much like to hear.  ;)

I will as a minimum add the xml file for the next release so you will be able to edit it yourself if I have not finished implenting the above solution. The next release will also have preconfigured webservices for uploading and attaching images and files to a page and spellchecking of the content all from within the editor (this will require a pro license to work).