It's long been on my list of todos to remove all the styles from within the classes and just include external css files for people to include and alter as they like....
<sigh> so many projects, too little time. On Mon, Aug 15, 2011 at 7:25 PM, Philip Thompson <[email protected]>wrote: > Well, I figured that I could put the options with StickyWin.Modal, but when > I moved the options to the StickyWin.ui 3rd parameter I got more expected > results... > > Btw, the reason I'm overriding the default functionality is so that the > window it creates is not image-based and uses CSS(3) features to create the > window. IE's not my target audience, so I'm not restricted by the same lack > of features... > > Thanks, > ~Philip > > > On Mon, Aug 15, 2011 at 9:03 PM, Aaron Newton <[email protected]> wrote: > >> I don't know which options you're expecting. The shortcut method (* >> StickyWin.ui()*) instantiates an instance of StickyWin.UI: >> >> StickyWin.ui = function(caption, body, options){ >> return document.id(new StickyWin.UI(caption, body, options)); >> }; >> >> >> Your example invokes this shortcut but passes no options: >> >> new StickyWin.Modal({ >> content: StickyWin.ui('this is the caption', 'this is the body.'), << >> NO OPTIONS HERE >> destroyOnClose: true, >> width: 800, >> ... >> >> What options where you expecting? >> >> On Mon, Aug 15, 2011 at 6:42 PM, Philip Thompson >> <[email protected]>wrote: >> >>> I'm sorry if this is more Clientcide-directed and not so much Mootools. >>> Check out this fiddle. http://jsfiddle.net/philthathril/pnWnR/ It >>> appears as though the options are not getting propagated when implementing >>> the StickyWin.UI.build method. View the console and view the options object >>> (and ignore the error afterwards). Is this a bug that the options don't >>> appear to get passed? >>> >>> Thanks, >>> ~Philip >>> >>> -- >>> http://lonestarlightandsound.com/ >>> >> >> > > > -- > http://lonestarlightandsound.com/ >
