A place for discussion about skinning and design. Before posting questions here you should review the documentation about creating skins.
Stupid me, I never paid attenion to the caching setting.
Thanks a lot!
Any preparations for Artisteer 3 (currently in beta)? They've added dynamic width to their templates. It would be nice to have this working in MojoPortal too.
I don't plan on working on it while it is in beta because things may change, but as soon as the final release is ready it will be a high priority.
Has anyone tryed Artisteer 3 ?
Artisteer 3 just went into public beta on December 22. Feel free to give it a whirl, but be aware that it will most definitely not work with mojoPortal "out of the box". Once the final version is out, Joe will be on it to make the necessary changes in mojoPortal to support it.
Just i want to say Thanks a lot Joe...
I just re-upped with Artisteer, and got hold of their latest (Dec 30) beta of 3.x. It's a bit of a learning curve for me; I didn't re-up last year so I'm going directly from 2.4.x to 3.x; I did get their latest version of 2.5 and their RC of 2.6, and apparently a couple of things changed (like that postheadericon thing), but the interface itself is also very different in 3.x. I'll figure it out, and then see about adapting an artisteer 3.x template to a Mojo skin. I'll post whatever I figure out, here in this forum.
I agree, it would be extremely sweet to have a direct-export to Mojo in Artisteer, and since they already do visual studio templates and DNN skins, I can't see where it would be that difficult for them to add Mojo, the page structure is really not that different from any of the major CSS-based CMS thingies -- and if I have anything to say about it (in Digg, StumbleUpon, my Facebook pages, and most of my websites), Mojo will soon overtake them all and become King of the Internet. So they oughta get with the program.
It also occurs to me to wonder if it wouldn't be a good idea to have a forum specifically for Mojo skins created with Artisteer. My recent adventures in adapting the 5-content-panes skin have reminded me that there are in fact other ways of making Mojo skins than with Artisteer, and those who create them "from scratch," as it were, or adapt CSS or other-CMS templates to Mojo might get a bit tired of all the Artisteer-yakking. Just a thought.
Aarghh. Artisteer 3.0 is a blast, it does so many new things, but I have to say, it's a real bear to convert their new styles to Mojo. I created a new design which followed the scheme of artisteer-30headermenu -- horiz menu under header, no vert menu -- but there are so many more divs involved here, I can't straighten out all the closing divs -- since I'm having to go by the new-page.html to figure out the actual structure of the page I created, and Mojo fills in a lot of the divs and /divs in its controls and panels. So I think I'm going to have to create Mojo skins using Artisteer 2.5/2.6 for a while yet.
It's also hard since 3.0 is still a beta and there are no docs for it. I know docs aren't popular these days, everyone wants a freaking VIDEO, aarghhh, but some of us do know how to read and how to learn from what we read, and videos just don't cut it -- but there isn't even a lame video for Artisteer 3.0 yet.
I sent them some feedback yesterday regarding a small problem with the arrow buttons on some of the sliders (incrementing by 10 instead of by 1), and I took the opportunity to inform them that Mojo is the best CMS that ever was or will be (since it has no unwieldy back-end!), and that they should include exporting direct to Mojo among their ASP.NET options. They're usually pretty responsive to any and all feedback (couldn't believe some clown in their forum calling them "arrogant and high-handed") so maybe they'll take the hint and include Mojo exports. Wouldn't THAT be swell?!?!
So, back to Artisteer 2.5 or 2.6 or whatever it is. For now.