Have you checked out our CMS templates ? Try our Universal template (last one), check out the admin demo and if you want you can send us some feedback on improving the CMS for ease of use for you or other clients you know. We plan on constantly improving it and adding features so any feedback helps.
I think you misunderstood what I said, there are powerful flash templates with CMSs, just not inside Flash. We might (at one point or another) create a full flash cms, but we’re still wondering if it’s worth it, there’s a lot of work involved to do it properly and keep it very flexible and there are also some other issues, namely the fact that a stand-alone cms would make certain actions much easier than an overlay one.
I always use the latest technologies. Now I’m using Flash CS4 and for some people I export them in CS3 . I already installed CS5 on my laptop and I’m ready to switch and never use CS3 . I stopped using CS3 when I found out that in CS4 you can embed a font from an external file(using the [Embed] tag) that let’s you have any language in your textfields. That was the biggest problem with the CS3 font renderer: I could not have different languages for different people in other countries.
The embed directive is for flex projects, where you don’t use a .fla. Instead of the flash Library you can link to external assets on your hard drive, but after compilation they are added (embedded) in the swf. In conclusion you are not using an external font, you only tell the compiler what to embed. It is the same thing as adding (embedding) a new font inside the Library of a .fla. I think you were referring to loading a A.swf that has a font embedded, into a B.swf, and using the registerFont method to make that font available for the B.swf, which you can do very well with CS3
Hey. Thanks for the feedback!
With regards to the music player that stays the same when changing to a new HTML page, this can only be accomplished using frames.
Quite interesting, funny enough we do have a project concept along these lines, although quite more clever and flexible. Unfortunately we’re not sure if it would be a good idea after all since you’d need to specifically program the flash template to seamlessly work with the cms, it’s not necessarily complicated in theory, however in practice it can be a bit of a pain for people not familiar with it that want to change features unsupported by the CMS (flash customization). I think for stock flash files it’s best to keep the CMS separate from the Flash files at this point like we do with our php cms that will be improved steadily over time.
Also take into account that their templates are very poorly designed, look&feel ourdated by todays standards and you’re paying for the priviledge of using them each month (same price you’d pay to OWN a template here). Not that much of a good deal. Also we should understand that while the system is quite clever as far as data management goes, it lacks tons of useful features and most importantly it limits the possibilities for the front end enormously (while external cms that generate the xml files don’t in any way since they are not dependent on the actual Flash template in any way).
Looks interesting at first but when you analyze it in more detail it’s just another limited site builder with no advanced features whatsoever. Probably enough for beginners but I doubt it would satisfy more demanding users.
Good news, for sure.
Just voted, there are a couple of really nice entries
By the way, the _blank for the links is not working properly in the html formatted descriptions. We’re not on the new system and have put _blank everywhere, just hoping it will be fixed
Since we didn’t know if it’d be fixed or not, we made a php parser so we’re currently changing all our descriptions to html formatting instead of textile. Will textile still be used or will html be the recommended formatting from now on ?
Sorry, I’m confused. What’s wrong? The links DS posted seem to work just fine for me. So do all the links on your profile, Oxylus. Am I missing something?
Hello Lance, that is because we fixed and rewrote everything with html tags instead of the textile plugin code that has been used on AD for so long. We are going to have to do the same for all our products since if we try to edit anything that was in the older format, it gets screwed up.
The old systems is no longer bloody working and if you edit an item and make any changes it will get all screwed up. Now we have to edit ALL our items using the html code formatting. Would’ve been nice if both of the systems could work in parallel … Oh well, you gota do what you gota do.