Artur wrote:All I can say now is -
(just kidding
)
I'm in 90% of the way to adapting the imagevue admin panel to my MySQL / HTML5 site.
I have few question, because I'm not sure whether should I discontinue working on my new website or not.
Some good questions coming up here, and I could probably answer an entire blog post in reply, but that would be a bit premature so let me keep it minimal.
Artur wrote:1. Will it be SQL or still XML?
Imagevue X3 will use a combination of markdown(md) files and JSON for storing- and communicating certain data. This is a non-database approach, but the combination will be much faster, flexible and readable than using XML or DB. For a long time, we considered database to be the natural evolution for Imagevue, but recently we figured it is not. Database has its place of course, but for a portfolio gallery there are no advantages: It will be more complicated, slower, less portable, less logical. Perhaps the only benefit of using a database, is to integrate possible modules like
search ... Search has never been and will never be a major feature of Imagevue, simply because this is not strong feature in a portfolio. Besides, Imagevue X3 will have additional focus on hosting images on 3rd party image-storing services (which I could write another blog post about entirely) ... These 3rd party services will support search through their API anyway. I could write much more about this, but I will wait until someone asks "wait a minute. 3rd party services?" ... What about
comments? Just like almost any modern blog or web application these days, they use stuff like
disqus for comments ... Why not? Its much more secure, less problems with spam, easier to manage, and much easier for visitor to actually make an authentic comments ... besides, its more social and "connected".
Other than that, I can tell you that Imagevue X3 will be nothing like imagevue X2 or any previous version ... The only similarity may be the structure of content (if self-hosted photos).
Artur wrote:2. Do you plan to leave doors open for ppl like me, who want to "powerify" everything around?
(by saying "open doors" I want to know whether I'll be able to fire my PHP on page, or maybe the new version will use third party minified/protected APIs or frameworks for displaying contents - kinda mobile version?).
I can't answer this specifically yet, but Imagevue X3 will be
much more flexible and modular than any previous versions. Not only will we be dealing with a single unified frontend on all devices, but since its html-based, it will be much easier to inject new modules without worrying too much about breaking any existing layout.
Also, Imagevue X3 will run from the awesome
Laravel PHP framework, which will allow an organized approach to adding new modules or bundles. Furthermore, just because the core of Imagevue will not rely on a database, does not mean that it can't easily be extended with database modules. The Laravel framework is a great fundament to work with databases, and it will be knitted in with the Imagevue gallery core system.
Imagevue X3 will basically load pages with JSON through JS, making it swift, flexible and dynamic. It will use a JS MVC framework to load and render templates on frontend, and use similar templates for the backend through laravel blade templates for compatibility in SEO purposes.
Would love to say more, but its a bit counter-productive.