Jump to content


New Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About Envrin

  • Rank
  1. Hi everyone, Been working on this for quite a while, and although still quite a ways from completion, it's done enough to begin getting initial feedback. If anyone of you have a spare few minutes, please take a look at: http://apex.envrin.com/ And quick start guide at: http://apex.envrin.com/quick_start Github: https://github.com/envrin/apex/ Would love any initial feedback. I would imagine it will get blasted as amateurish, which is fine with me, as I need it for myself anyway. Hopefully it's able to help some folks out there as well though. PS. Please ignore any design flaws. I went blind a couple years ago, but will get a designer on board shortly to fix up the design flaws. Thanks in advance!
  2. Ok, now those are some pretty damning reviews. Alrighty then. First up, on second thought, totally agree with you guys on the tutorials. Good overall concept I think, but horrible format and for now a total waste of time. I still think it's a good premise though, and will rewrite them from scratch later, but on more of a component-by-component basis instead of in a timeline format, which is obviously unhelpful. No, I'm not totally adverse to using 3rd party. For example, Bootstrap, jQuery, jQuery Validator, I have a SQL parser library in there for large SQL chunks (ie. package installation files), etc. When I integrate a WYSYWIG editor obviously I'll use ckeditor or similar, and so on. However, I am a little picky about which 3rd party components I do include, because general rule of thumb, the more you try to mix and match 3rd party components, the more clunky and restrictive the end result is. I know many with disagree, but I personally dislike PDO, as it seems too cumbersome for no reason. If I was going to go 3rd party for the DB layer it would be MeekroDB which I have used before (eg. Synala). It's excellent, clean, efficient, what takes 5 lines with PDO only takes 1 line with MeekroDB, and it's very secure. They've done extensive testing of their own, and I've had my software pen tested as well with no SQL injection found. My DB library is modelled after MeekroDB, and granted still needs some work on security, does work great. Went with my own naubky dye to logging, error handling, and debugging, but also a few other reasons. Honestly, have never used Twig, so will check it out. I'm very familiar with Smarty though, and have used it many times (eg. Synala). It's a great template engine, but couldn't use it for a variety of reasons, one main one being it doesn't really support specialized tags, especially not on a per-theme basis. For example, I need to put say "<e:tab_page title="My Tab"> ... </e:tab_page>" tags in the templates, and have them replaced correctly regardless of theme being used. Many themes format tab controls differently, and at the very least use different CSS class names. Same goes for loads of other elements on pages. I need to be able to grab a theme from ThemeForest, have it fully integrated into the framework within 30 mins, and have it perfectly integrated across the dozens or hundreds of templates, without having to go through and tweak each individual template due to a theme change. -------------------- Thanks for the nudge on the blind thing, and you're right. Will remove that, as not relevant to the content. Also thanks for the slap about PHP 7, as I somewhat missed that whole release while trying to figure out this whole blind thing. Read up on it, some cool new features that I'll will definitely take advantage of. Strict type setting I'm definitely happy about, plus the additional error / exception handling, and others. As for component vs. more standard / modern MVC format, I guess personal taste, plus other reasons. For one, I think it's more organized, as a developer can pop into a system and almost immediately get a brief overview of what's going on just by looking at the file structure without having to sift through any code. Plus I like to think it provides more standardization. With the more standard MVC model developers can sway from the path more easily, so you may end up with a dozen different development styles in the same system, which can get messy. Whereas with this, although you still have flexibility to develop anything and everything, it's more structured, again allowing other developers to easily pop in and out of projects with a reduced learning curve. . Thar, and even with multiple developers involed in one system, the end result to the client will be a coherent, streamlined system that all looks and acts the same. Maybe I'm wrong, but that's my perception at least. Definitely not for everyone, but I'm sure for some people, and definitely for me. Yep, there will of course be full unit tests available, as that's a crucial aspect. Plus extensive debugging features as well, which aren't yet developed. -------------------- Anyway, thank you guys very much for the feedback, as you helped force me take a step back adnd re-analyze everything. Development will move forward, tutorials are scrapped until development is completed, will upgrade to PHP 7 standards, will have to agree to disagree buy component design is staying, etc. Alrighty, here we go. I'll be back with a more finished version. Now just to find a volunteer to help with the jQuery / Javascript aspects. I know the code, but testing and debugging is a little tough without eyesight. Will see what I can do. Thanks again.
  3. Thanks for the feedback, and much appreciated. Let's see if I can answer everything. Yes, you're correct, too much for beginners, and advanced users aren't going to waste their time with it. I guess it's geared more towards the intermediate -- the guy who is done all the beginner stuff, and is that "ok, now what? how do I get better? what should I develop?" phase, or simply wants to hone their skills when it comes to structure, cleanliness, efficiency, security, writing a proper database schema, etc. Maybe I'm wrong, and the pool of developers is too small compared to the time investment. Regardless, this framework is getting developed, as I need it. For one, I don't really like using 3rd part frameworks, as I prefer to know how my systems work inside and out. More importantly, I went blind about 9 months ago, hence reading and sifting through third party code is quite difficult. I need all the code in my head, so when a bug fix / modification comes up, I know exactly where in the code to go. Nonetheless, once Apex is completed I'd be happy to put it up against the big boys like Laravel, Symphony, and even other non-PHP frameworks. Maybe even have a competition, one (or more) developers each use a different framework, same set of project specs, and have say 24 hours to deploy a live system. I'm sure at the very least Apex would stand up to them (once complete), if not beat them. Time will tell I guess. Regardless, I need to develop Apex for my own personal projects at the very least, so figured while doing it might as well try to help a bit by documenting the process from start to finish. Instead of just a tarball on someone and say, "ok, learn this", I thought maybe there were some developers who would benefit learning it in smaller chunks, and more of a step-by-step process. Again though, maybe I'm totally wrong and off base with that. Yep, of course will be uploaded to Github once complete. For now, the zip and tar archives are available at the top of every tutorial, which consist of the full system as is after each tutorial. Thanks, and you're totally right about styling the code blocks. My partner is out of town for the next week, but I'll take care of that when he gets back, since I'll need to borrow his eyes for it. Thanks again for the excellent feedback. Much appreciated!
  4. Hi everyone, Hope this doesn't get flagged as spam, because by no means my intention, and looking for honest feedback. I'm currently developing the third iteration of my PHP framework, which I started back in 2006, now coined Apex Framework. While doing the development, I decided to put together a series of tutorials, taking other developers through the development process step-by-step, to give them a good understanding of exactly how to develop their own high-quality PHP framework. These tutorials are quite a bit more in-depth than your typical MVC tutorials, as the framework includes things such as package management repositories, multi-language, theme library, and much more. To see what I currently have, please check out the one link at: http://envrin.com/tutorial There's 5 tutorials in the series now available now, and the onext one should be online within 24 - 48 hours. Since I'm now blind, these tutorials take quite a bit of time to write, so I'm just looking for any feedback I can get. What do you think? Are they of valuable information to you so far? Should I continue investing time in this tutorial series? Is there anything you'd like to see different? Again, I'm honestly looking for feedback here, and not plugging my site. I'm wondering if it's worth my time to put these together or not. Thanks in advance!

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.