krballard94

I'd recommend using something like: Atom (Free) PHP Storm (Paid) Sublime Text 3 (Paid - Free Unlimited Trial)

My advice, don't even bother with MC Codes, it's a terrible way of coding.. Just try and make some one page scripts and get functionality out of that. Start to include other files after and build up that way. Always use up-to-date technologies like PDO, classes, interfaces and traits as well.

[MENTION=68406]-BRAIDZ-[/MENTION] Next time, dissect a few mod and try and help yourself first, that's how I learnt.

No worries! I find it useful when increasing the width so I can recognise where my templates will change from rendering on a phone to table to a desktop! Best thing about it, it's unobtrusive but it's there for when you need it.

I find it very useful, especially to get a basic responsive design for the engine I'm creating!

[MENTION=65371]sniko[/MENTION] - Both ways are good, but I personally would go for the code approach.. MySQL triggers, are good but for this example I wouldn't use it. I would rather explicitly show it in my code as this can make editing it a lot easier as well and you might not even remember the trigger being called a month down the line. Not to mention that if you made an error in your trigger, you'd have to drop it to re-create it. Just my opinion though.

Sometimes while working with Bootstrap, I like to see what my current viewport size is. This helps me edit my site for that specific size and make sure it renders how I expect it to. So I thought I'll share it. (Just remember to remove it before the site goes live!) http://pastebin.com/fnP5y7zZ

What I mean, I'm still going to go with the original folder stucture. modules/ AuthorOne/ ModOne/ ModTwo/ AuthorTwo/ ModOne/ AuthorThree/ ModOne/   And use the namespace Modules/AuthorOne/ModTwo

I rather your second option what you said, creating a new namespace.

Surely that would end up in the vendors directory?

It's changed, a lot!

I got a little bored and I wanted to have a break from my various other projects. I had a very old Gravatar class I made a long time ago, so I started to look at it and make some changes... I ended up scrapping it and starting fresh! Anyway, after a little while of coding and a lot more putting a set of docs together. I give you the new and improved class. https://github.com/krballard/gravatar I would appreciate feedback - constructive criticism welcome!

Just say there is a conflict, although I had to create a whole new validation method for what I needed! (Laravel's unique is database only, where I needed it to check an array!) Now time to try and sort out to install modules.

Exactly, and I'm trying to make it create the modification structure via a form while validating the mod name hasn't been used already within the app.

I see. At the moment I'm currently implement a more modular structure to the engine. All the core files will end up in the app folder, where as new modifications will end up being in the modules/ModificationName folder

I'm not entirely sure, so I'll take a look into CodeIgniter's hooks tomorrow..

Just a quick update, I have a fully functional permission based access layer with roles included with an admin side. This is including adding new permissions, roles and users while being able to attach and detach permissions to roles and giving a user a role. I'm just wondering now what people would like a core features? Remembering it's only an engine and not a game.

I've updated your code as I wanted to do something different for a little bit. There was quite a bit of unnecessary mark up but good effort! I've added the CDN references and a few little bits to make it look better on a mobile display as well. HTML - http://pastebin.com/n7uBb0Dn CSS - http://pastebin.com/Q0Vfscjz   Edit: I didn't even realise that this was from last year...

I personally didn't find the need for it. I'm quite happen doing my local development on XAMPP.

My only guess would be trying to install Homestead on Windows... I'm not using Homestead personally, it seems to much effort to install it.

Yes, but very bad example Read this tutorial and it'll give you a better understanding despite being a little outdated.

Laravel is quite like this, but uses relies on namespaces (which is a good thing in my opinion). Obviously there are difference among the frameworks, I know this as I used to mess around with CodeIgniter! Here's a controller which I'm currently working on at the moment.   <?php namespace App\Http\Controllers\Admin; use App\Http\Controllers\Controller; use App\Permission; use Notification; use Request; use Validator; class PermissionsController extends Controller { /** * Display a listing of the resource. * * @return Response */ public function index() { $permissions = Permission::paginate(10); return view('admin.permissions.index', compact('permissions')); } /** * Show the form for creating a new resource. * * @return Response */ public function create() { return view('admin.permissions.create'); } /** * Store a newly created resource in storage. * * @return Response */ public function store() { $input = Request::all(); $v = Validator::make($input, [ 'display_name' => 'required|unique:permissions|max:255', 'description' => 'sometimes|required|max:255', 'slug' => 'required|unique:permissions|min:10|max:255', ]); if ($v->fails()) { return redirect()->back()->withErrors($v->errors())->withInput(); } Permission::create($input); Notification::success('You successfully created the ' . $input['display_name'] . ' permission.') ->glyphicon('ok-sign'); return redirect('admin/permissions/create'); } }

I'd recommend to pull these packages into your projects for development: barryvdh/laravel-debugbar and laracasts/generators Myself personally I find them both very useful.

Laravel is a good framework and one I personally favour. I've recently started to create a basic OS engine with it as well!

I really do like Laravel, alot! Composer makes the installation really easy, even to bring outside packages.