Home I am PR Another Hubra slant

Another Hubra slant

by admin

Why not? Because all the other neklons are also neklons. Even livestreet is now a neklon in its latest version. And why my engine is worse? Well, of course it has a lot in common with hubr, but it has its own. Although, since there is a system of extensions, all of his allocated to separate extensions, but never mind. I’d like to introduce my blog-like social networking engine (c) Envos.Blogs
But unlike other non-clones, I didn’t intend to do something similar to hubr, and it wasn’t hubr that inspired me. I was inspired by a friend of mine, over a bottle of beer after soccer practice. He suggested that I write a website for our soccer team so that people could come in and read announcements about new games and practices and sign up. I wrote, but nothing came of that idea. People didn’t want to click the "come" button. Then I wrote a photo gallery to post pictures from training sessions. Then I wrote blogs that would be able to post reports. I added a guestbook for communication. And I was so carried away by it, that I did not notice how the engine ala hubr turned out.
So it’s fair, I didn’t copy hubr, I just wrote, and it turned out this. By the way this explains why there is no, for example, statistics, why the system of ratings is weak, why the user profile is so ugly. Copying would have been a hubr, everything would be. But I do not need it all for my tasks. So later I’ll make and karma and voting, and even ratings for comments.
A little later, of course, thoughts about how I could make some money. Well, damn, I have done a lot of work, a lot of code was written, the product has turned out, as it were. So, tried to do a couple of projects on the engine, but apparently SEO from me no SEO, I have not achieved a special attendance, and since I have little free time, I still work, and that is spent on his wife and the development engine, from the idea of something to promote I decided to give up. Remained on the engine a couple of or three projects, but they are for the soul, I’m not going to make money on them.
So, the engine is based on Framevork’s own MVC called Envos. I’ve been writing it for 5 years now, with big and small breaks. Don’t blame me for reinventing the wheel. When I started there were no other good products, and even now the only one which deserves attention is Yii. But it just recently appeared (nevertheless I managed to take some ideas from it already). So, the engine is fully MVC, it even has ActiveRecord, validation, caching and other stuff. There is scaffolding, and some tests based on SimpleTest. As always there is no documentation. I told you, I don’t have much time.
In general, the engine has been developing very rapidly lately. Recently a system of extensions has been developed, and it seems to me that it is quite convenient and simple. There are even dependencies, this is when one extension uses the capabilities of another, and this other is not, or it is the wrong version, or just turned off, all will work correctly (or rather correctly will not work). Or here is the design theme system, with inheritance. You can create a new design, with lots of templates, and lots of extension themes, with a minimum of wrappers and css, where only some templates will be overloaded, and the rest will be taken from the parent.
There is also an installer, which allows you to put the engine, even a complete lamer. There is a login by OpenID, there is a photo gallery, guest book. And there is something that no one else has! This is a module of soccer forecasts! That is, it is a module that allows you to conduct competitions for prognosticators, such as games of the Championship of Russia on soccer. You start tours, add matches to them, and users are trying to guess with what score the match will end.
There is also a module called "Discussions". The idea is that you can create a topic that you want to discuss, and invite people there. The topic can be open, closed, and readonly. Accordingly, in the first case everyone can read and write, in the second case only invited people can read and write, and in the third case everyone can read and only invited people can write. But you can ask for an invitation, from the author of the discussion, using a special button.
There is also CNC in the engine, which is implemented as in ZendFramework. To tell the truth, I don’t know why, but there is less code. Although it works fine.
The engine knows how to check for a new version, and update itself (this is not by itself, you have to press a button). In general, update system is tricky. She has a dual purpose. Well, the first is to check for new versions and directly to update. But that is not all. This same script is necessary for me to keep statistics of installations of the engine. At the same time I pick up RSS feed once a day. Just in case, in case you have something interesting to write there 😉 But do not worry, you can disable the check and then no data about you will not be transmitted anywhere.
And one more tasty thing. The engine can be installed once in one directory, and then direct different domains to it. And for different domains will be its own site, with its own settings, and even the design theme. Only users will be common. Often in hosting is a limit on the number of sites. You can not have more domains directed to different directories than is allowed. With Envos.Blogs the problem is easily solved.
What’s missing? There’s a lot that’s not there. Something just isn’t needed, something is in a workable form, but not in the way it was originally intended. For example, "Discussions" is not tree-like. Just do not have the ability to separate branches into separate discussions (there is no branch), or to arrange a vote on the admission of new members, or expel guests. And all this was conceived originally, rather than inspired by Google Wave, as you might think. But on the other hand, a lot of room for creativity of those who suddenly decide to help me, because almost every module can be improved. And without even looking at the hubr. Envos.Blogs is a ne’er-do-well. Isn’t it? 🙂
Now for the plans. Well the immediate plans can be seen Google.Code project. How quickly these plans will come to fruition, I can not say, but, as I said, the project is alive, has been alive for a year and a half, and the enthusiasm is still there. And if my project will be warmly received on hubra, it will only add incentive. This is a kind of hint 😉
And hopefully this won’t be my last post about Envos.Blogs. In the near future I will tell you the best way to install the engine, how to update it, and how to write modules for it. Even if you don’t need Envos.Blogs, you’ll probably be interested in how it’s made, maybe something useful for you, and probably something for me.
And Happy New Year to you!
P. S. One more thing. The engine should work on Windows, but I’m not responsible for full functionality. For example, for sure will not work installer, and engine update. For the photo gallery you will need ImageMagik. Envos has an OS abstraction mechanism, but it’s not used everywhere. Over time, the platform-dependent stuff will be rewritten, but anyway, I am not responsible for Windows, I have no time to test on it yet. And what for, just to give me an opportunity to play with the engine locally? Use Linux in general 🙂

You may also like