Jump to content

falkencreative

Advanced Member
  • Posts

    4,419
  • Joined

  • Last visited

  • Days Won

    27

Posts posted by falkencreative

  1. As a screencast author for Killersites, I'll repeat:

     

    Stefan has made no requests regarding how we phrase what we call the tutorials. As a screencast author, I tend to call them "tutorials" or "videos", but not usually "movies" (perhaps I'd call a extremely long, non-stop video a movie, but in my mind, a movie is an hour+ long, so my 10 minute videos don't count). It sounds like the author of the Dreamweaver course called them "movies". How we refer to them depends on our preference.
  2. Maybe some will chime in that have experience in this area.. Everyone knows that Lynda.com in ALL their tutorials they call them MOVIES and thats what im looking to get answered. Thanks for all your input so far.. but the question is valid..

    Maybe you should ask Lynda.com support then? We have nothing to do with Lynda, so I imagine asking them directly will get you better results.

  3. Well, at least at KillerSites, we are conspiracy theory free. ;) Stefan has made no requests regarding how we phrase what we call the tutorials. As a screencast author, I tend to call them "tutorials" or "videos", but not usually "movies" (perhaps I'd call a extremely long, non-stop video a movie, but in my mind, a movie is an hour+ long, so my 10 minute videos don't count). It sounds like the author of the Photoshop course called them "movies". How we refer to them depends on our preference.

     

    Copy protection is built into anything you post online -- it doesn't matter whether one calls it a movie or tutorial or video or whatever. This has a reasonably clear explanation of online copyright: http://www.socialmediaexaminer.com/copyright-fair-use-and-how-it-works-for-online-images/

     

    Copyright attaches as soon as the original work is created, and applies to both published and unpublished works. As soon as you type words, click the shutter on your camera (or, for many of you, hit the home button on your iPhone), apply paint to canvas or paper or lay down tracks for your next hit, you’ve got a copyright (with some exceptions).
  4. Sure, "lesson" or "tutorial" would make more sense. "Movie" or "video" still gets the point across. Most lessons are recorded with a rough outline in mind, but no script, so there will be times when someone is bound to say something that isn't 100% perfect. If it doesn't change the understanding of the concept, it usually isn't worth it to potentially re-record the entire video for something very minor.

     

    I guess I don't see what the big deal is? The point is that you're learning whatever subject you are studying, not a minor word choice.

  5. Right. RGB is for web/screen work, and CMYK is for print. They have different color gamuts (meaning the range of colors they can display), and CMYK specifically has a smaller range of colors it can create from the cyan/magenta/yellow/black combination of inks. This is often why you'll see colors shift slightly when switching between the two, because the calculations used to create those colors from the combinations of inks change.

  6. Yes, if you are doing print work, you need to be working in CMYK, which is what the item will be printed in. Otherwise, yes, it will get automatically converted to CMYK, and you might get unexpected results.

  7. Hi.

    First off, great site and tutorials!

     

    Now, I have copied your tutorial and pasted in etc...

    BUT,

     

    I am now getting an error on records.php

    error is:

     

    "Warning: Cannot modify header information - headers already sent by (output started at C:\......\records.php:2) in C:\.......\records.php on line 183"

     

    I have tries reading up about it and tried different suggestions, how ever as this error then dissapears plenty others arise. Any help or suggestions would be greatly appreciated.

    A "cannot modify header information" error means that you are sending data to the browser before trying to redirect using header(). I'm not sure exactly what your code looks like, but make sure you aren't echoing anything out before calling header(), and that there aren't any stray spaces at the start of the file before the opening PHP tag.

  8. I was going to respond to your email, but doing it here makes more sense in case others run into the same thing.

     

    the get_sidebar() function loads a sidebar.php file within your theme. Get_sidebar() loads sidebar.php, get_sidebar('sidebar-2') would load sidebar-2.php, etc. So if you want to use those functions, you have to make sure that the correct files are in place. Within your sidebar.php/sidebar-2.php, you'd want to have the dynamic_sidebar() call to load the correct sidebar.

     

    It's a bit hard to tell based on your code, but I think you have a file named "sidebar2.php", when it should be named "sidebar-2.php" (note the dash).

     

    http://codex.wordpress.org/Function_Reference/get_sidebar

    http://codex.wordpress.org/Function_Reference/dynamic_sidebar

  9. Sorry, you're going to have to rephrase the question, since I'm not sure what you are asking.

     

    But my original point still stands. A CMS is a web application. A framework is a pre-built structure that you can use to build web applications quicker/easier than starting from scratch. Think of it this way: a CMS is a fully built house. A framework is the plans for the house.

    • Upvote 1
  10. They are different things.

     

    -- A CMS is a web application for content management -- usually to do with an informational website, ecommerce store or blog, allowing a user to edit the content without needing to know HTML/CSS or to code by hand.

     

    -- A PHP framework is used to build web applications, quicker and easier than by starting from scratch. You could use a PHP Framework to build a CMS, an ecommerce platform, a social networking platform, etc.

     

    Basically, a CMS is a web application, and a framework can be used to build web applications. For example, Expression Engine CMS is built on a version of the CodeIgniter framework.

    • Upvote 1
  11. What's confusing about the chart? It shows the actions handled by the controller, describing the server method used (GET, POST, DELETE), the path used, the primary action when that path is accessed, and the route name. It is there to help describe the functionality that you will be building.

     

    As for CSS, take a look at http://www.tannerhearne.com/link-to-css-file-laravel-using-html-class/. You can also hard-code the link to the CSS file, like the link to the Boostrap CSS file in http://scotch.io/tutorials/simple-laravel-crud-with-resource-controllers. CSS files should go in the "public" folder -- either directly in that folder, or within a subfolder within the "public" folder.

  12. If I can offer a suggestion to you though...

     

    -- If you are going to be reading the user manual, and assuming you have access to the internet, I'd suggest you be reading the official docs instead: http://laravel.com/docs.'>http://laravel.com/docs. What you are reading now is a version of the documentation (last updated mid last year), copied and pasted, but at least if you go to http://laravel.com/docs you know you'll be reading the most up to date information. I wouldn't suggest reading a PDF version unless you are on the go and don't have internet access.

     

    -- Secondly, I'd suggest you skip the official documentation for now, and find a relatively simple introductory tutorial to Laravel that will give you an idea of the overall structure and how things work together before reading the documentation. There's likely to be a lot of things in the documentation that you won't use very often and will just add unnecessary complexity and confusion. Perhaps start with a "getting started" type tutorial, and come back to the full documentation when you are a little more familiar with the way it works?

     

    You might consider something like this: http://scotch.io/tutorials/simple-laravel-crud-with-resource-controllers which will give you an overview of a lot of common functionality: working with routes, models, controllers, views, the database, etc.

  13. Filters allow you to run code either before or after a route (so yes, you can have both "before" and "after". Before tends to be useful if you need to do some sort of authentication checking or validation -- perhaps you want to make sure a user is logged in before they view that particular page. "After" might be used for code cleanup -- it's likely something that you won't use. In the code above, it is calling the "old" filter before the route runs.

     

    The get('age') section refers to a GET variable in the URL, so try accessing the site using something like this:

     

    yoururl.com/user/?age=50 (should redirect)

     

    or

     

    yoururl.com/user/?age=201 (shouldn't redirect)

     

    I believe that should work, since age is set.

  14. As far as I understand it, that code allows you to automatically determine where the site is running, and what environment it is running in. For example, you may be running it in several places -- perhaps locally on your computer, on a hosted development site, or live online for anyone to view -- an in each case, you're likely to have a different database setup, and perhaps certain code (logging, for example) would run only under your development environment. The environment variable allows automatic switching between environments based on the host name, and you can then use

     

    App::environment()

     

    to determine which environment you're running under and thus perform specific actions.

     

    See http://laravel.com/docs/configuration#environment-configuration for more, or do a Google search for "laravel environment".

    • Upvote 1
  15. Btw, i have red an article in http://laravel.com/docs, that after the installation, we learn about routing. So, i red this http://laravel.com/docs/routing.. It teachs about get, post, etc.. But i don't quite understand about that. Every time we want to post something, we have to go to routes.php ?

    Yes and no. If you want to create specific URLs within your application, you need to have a way of telling Laravel what action you want to happen when someone visits that URL. So yes, you need to have a route set up, to tell Laravel that when someone visits "X" URL, it needs to load "X" controller. The controller will then determine what to do and what to show the visitor. So yes, you will be likely creating a route every time you create a new page or piece of functionality... but the majority of the "work" will be done by the controller or view, not by the route file.

     

    These articles might be useful for you to get an overview of Laravel and some basics of understanding how things work together:

     

    CRUD: (using a database to create, remove, update and delete records)

    http://scotch.io/tutorials/simple-laravel-crud-with-resource-controllers

     

    Building an Instagram type application:

    part 1: http://code.tutsplus.com/tutorials/building-web-applications-from-scratch-with-laravel--net-25517

    part 2: http://code.tutsplus.com/tutorials/build-web-apps-from-scratch-with-laravel-the-eloquent-orm--net-25631

    part 3: http://code.tutsplus.com/tutorials/build-web-apps-from-scratch-with-laravel-filters-validations-and-files--net-26058

    Source code: https://github.com/nikkobautista/laravel-tutorial

  16. I think Laravel is the better long term option, especially if you ever try to get a job based on your programming skills. Overall, my impression is that while CodeIgniter is a little easier to learn, learning Laravel will help teach you modern web development practices (working from the command line, using Composer, etc.) If you have questions about getting it set up (it's a little tricky, at least for the first install), feel free to post, and I'll see if I can help.

     

    I've personally been reading through the Code Bright book that I've linked to above, and it's a good place to start if you'd prefer a book over video tutorials. I'm not all the way through it yet, but it's written in an interesting way, and seems to cover a lot of what you'll need to get started.

  17. Which book are you talking about?

     

    And no, CI_Controller can't simply be replaced. Where are you trying to use "Controller"? Have you tried using "CI_Controller", in instances where you would use "Controller" based on your book?

     

    ...one thing to note though... The future of CodeIgniter is a bit up in the air at the moment (see http://ellislab.com/blog/entry/ellislab-seeking-new-owner-for-codeigniter). Much of the community has switched over to Laravel (http://laravel.com/), so if you are considering learning a PHP framework, that's the one I'd suggest. The learning curve is a little steeper, but give you shorter, better, more manageable code. For some tutorial options (there are a lot of resources out there!), check out:

     

    -- Online documentation: http://laravel.com/docs

    -- Video tutorials (free): http://hub.tutsplus.com/search?utf8=%E2%9C%93&search%5Bkeywords%5D=laravel&button=

    -- More video tutorials (free:) http://code.tutsplus.com/tutorials/laravel-4-mastery--net-31233

    -- Video tutorials ($9/month): https://laracasts.com/

    -- Book ($29, you might be able to find places to download it online?) https://leanpub.com/codebright

    • Upvote 1
×
×
  • Create New...