Lots of members have been asking what the difference between FullXMLwebsiteV2 and V3 is.
First of all we might have made the mistake of calling it V3 because it looks like an update of V2 which actually it isn’t and of course uses the same design and menu. There are big differences.
When we fist created V2 we thought buyers were interested in a full dynamic website. A website where the menu would be adapted to a preset content like a image gallery, content pages, video players and contact form. No matter the number of contents, the user would be only managing XML files and V2 would deal with the right swf file to open it. When programming this gives us the information of the type of content a user is going to have on each section and the website deals with the menu structure, meaning that if you add a new gallery the website will group all galleries in the same sub-menu, same for videos. The philosophy when creating V2 was to give a easy way to manage a website without too much knowledge.
In V3 is a total different story. A few days after releasing V2 we realized users where more technical and wanted to mess with everything on the template. Decide the menu structure; add any swf file opening from the menu, and so on. To give this liberty we had to think in two directions. On V3 we will be upgrading the file to make it as flexible as possible so that is easy to integrate whatever you want with it, we are changing code to dynamic parameters and make it better structured to include the modules. All modules are now also being upgraded to more dynamic files and better integration within V3. For example, V3 already as a full screen button and some of the modules too, so we made the full screen button a parameter on all modules and created a config file to manage this options so that you can use a module integrated or alone and add the options you want. Another example is the sound console. Sound console on V3 runs within the template, on the next V3 upload this will also be a parameter in a configuration file, because if you want to call a new dynamic mp3 player on the stage you would get two sounds playing at the same time. Ok these are just some of the features of V3, but because of its flexibility we will not create a V4, instead we will keep tuning V3. In the next generation template we are thinking in using the modules as well, in the same way we use it on V3 and this is because if you already bought modules for V3 you can use it on any other future template of ours. Isn’t this awesome? Now about V2, you can look at it as a hard top car. You can’t convert it into what you want. It is what it is. A set of modules already installed and flexibility is not a plus. But you don’t have to worry with messing up with swf files; confusing for most users that don’t understand that a swf can call another, and they don’t really care. Modules and other things on V2 are already and automatically installed and managed by the navigation menu. V2 puts flexibility on our side. A good example and already thought for V2 is the inclusion on icons on the menu. Since we know what is going to be opened we can just use an icon for a video or image gallery, same for contents and contact form. So this means that V2 is better for us to explore, but it’s done our way; buyers will have somehow to know AS2 or stick with it as it is.
To finish we will keep upgrading V2 and V3 (Same files), each one following its own philosophy and we do understand that users might not see the difference in a first approach, but there is nothing we can do about it besides explaining the differences, which unfortunately will only become more visible over time.
Triworks.net team
Posted 3 months ago
and you’ll get an e-mail soon. (We´re thinking)
