Wiccle Web Builder is closer than the closest, coming soon from the closet!

Here's a preview of the new Wiccle Pro skin straight off the drawing board (almost complete), coming out in several color variants. Every rounded box type has flexible width/height, can be interchanged, and are easy to customize.

And can of course be dragged around in any and all configurations! The templating improvements now make it extremely easy to fill your pages with all varieties and looks of custom content, aside the dynamic content provided by Wiccle Modules, and frame both into any flavors of boxes or no-boxes you wish.

Looking forward to it

The last week has been spent (again) with pre-release client websites, which will be showcased soon enough. We're getting a good deal of new funky AJAX stuff, add-on photo slideshows, SEO-friendly inline content windows, and more, all integrated into the Builder. Tomorrow I'm doing a full-day review of Wiccle, have a chat with Keith, and on Monday, keep your eyes open at Fusion!

Figured you guys must of been neck deep in something... looking forward to the release of Wiccle

That's pretty much the status quo. Right now I'm in the middle of setting up a dynamic, incremental, multi-level cache system, that together with the class dependency optimizations will bring down the memory and CPU imprint of both Wiccle and iWiccle 1.20 a great deal.

um... this is what I understand from your post... lol

"That's pretty much the status quo. Right now I'm in the middle of setting up a (*&%#(*@*&^DOHWBOB O*&YWX&BO&*#COYGOYXBO that together with (*&^#IJBCO*&YWDH will bring down the memory and CPU imprint of both Wiccle and iWiccle a great deal."

- I'm happy you guys are busy, that means progress, although it does get lonely in here sometimes

- I like the sound of a "greener" script very much.

December is when our global marketing will get into full motion. We now have a new sales assistant onboard who'll be charting the cyberworld and contributing to more overall action happening on the global fronteer — up to the end of November, our marketing focus is with local business — turning Galway into a Wiccle City.

In December, I will also have less deadline-code on my desk, and more time to focus on building up our community, resources, and everything else that we have in plans for the growing iWiccle/Wiccle userbase. December will not be boring — 100% guaranteed! (And please check your mail & tickets! Sorry for the delay.)

"Dynamic, incremental, multi-level cache system"

This means for example that:

• The cache is built on-demand, or at the first request of any given element, meaning you won't have redundant cache content to take space in your file system. This also contributes towards server load balancing.
• There is a central cache database registry, where cached items are tagged as in or out of synch with the actual data, and regenerated accordingly when needed.
• Cache-elements for the different post etc. formats are automatically built to reflect the way your site layouts are configured in the Builder.
• There is also a pre-cache-parsing combining templates with language packs, that further cuts down the memory and CPU imprint for creating cached elements when they are requested.
• Currently the cache will be stored on the file system. A MySQL-based cache version will become available as an option for those with more database storage space.

More information to come on all this as we near the release.

Class dependency optimizations

This means that:

• The amount of code that's loaded into the memory is minimized through careful isolation of different areas of the code (generally structured into classes), as every bit of code from our framework is loaded only once, and only when required, and is buffered into memory in the event of a similar need further on as the page units ("boxes") are created.
• A similar isolation and optimization of templates and languages has already been done. (Typically applications like this have a good deal of code overhead that makes them bloated, hogging huge amounts of memory.)
• This approach also makes modifications of all varieties much easier, because everything you may need to change is found exactly where it's meant to be, and there are no stray bits of language, templates, or code, that you would also need to change to get your customizations done.

If the above may come across as a tad bit cryptic. the bottom line is that Wiccle rocks when it comes to performance and ease of customization.

Bottom line, Wiccle kicks ass when it comes to performance and ease of customization.

Now this part I understood! lol