Joss

I must get around to upgrading to ST3

The Adobe Edge Code version of brackets seems a little bit quicker, but it is still slower than Sublime. I do find myself falling back to TextPad which I have used for years.

Yes, I know what you mean, though my music site is Bootstrap 2 and it is not too obvious that it is Bootstrap. I think it really depends what you are doing. I am currently redoing my web-design site and it will use a fair bit of Adobe Edge Animate on the front page. Now, where that will take me is anyone's guess at the moment, but it may well mean that I need nothing more than a simple responsive framework because the rest has been covered.

Oh, and we are cheap too.

Jo, try Scout for Sass or Prepros which does everything.

It is probably years of working in trendy, darkened studios, but I really like light, warm rooms these days. Actually, even recording studios have gone that way now with many of the top ones having actual windows with real daylight! That has been a shock to the system for some of the old school.....

One of the nice things about using SASS with Foundation is that I can simply not include what I am not using. So my foundation.css file is half the size of normal on one site and the JS only loads specific components on the pages that are actually using them. And that is without me minimizing them yet.

oh look - another editor with dark grey surround and luminous font on a black background. Do all editor makers think we all like such unhappy work environments? I think if a few more software developers made things light and fresh with a couple of flowers and the odd puppy round the edges, computer programming would be a much brighter and breezier occupation!

Oh, sorry - you probably got the impression that the composition took a long time. I did it in 5 hours. I had to sit on it for a week so he thought it took me longer. Hence why I was so pissed off he thought I had bought the track in ....

Thanks! One of the things with writing music is that I have become hardened to people not seeing value. Mostly when a client signs off and I do the final arrangement and vocals, I get no feed back at all. They just pay the bill and use it. I have no idea whether the end client (I deal with stations or agencies) was in love with it or just thinks it is doing the job. The very rare occasion I get a client phone up and say nice things is therefore a huge bonus - though cash would also be nice! Interestingly, I did get that recently on a set of sung commercials I did that I wrote in the style of a West End musical. That one they did bother to comment on. Its at the front of my recent show reel (and a second version at the end): http://dancingbear.co.uk/site/assets/audio/showreels/DancingBear-Feb2014-recent.mp3 I did once get annoyed about it - I had written and produced this 3 minute orchestral piece with a big vocal over the top; I was very pleased with it. The client liked it but asked "where do you source your tracks to sing over?" I have no idea what he thought the £3000 he had just paid me was for!!!

And then there is the sticky issue of "what the market can stand." I absolutely know I am very underpaid for some work (both web and music composition), but if I tell the client that it will cost more than they are prepared to pay, then they go away and use someone else. I don't have the expertise to do work for larger value clients than little shops and so on, and most of those people's starting point is the ads they see on TV for business sites for £1 I know most of the devs here have work coming out of their ears, but I dont - I cant afford to not take work, sadly. That makes it very difficult to boil this down to a per hour rate. If a job pays £500 - then it should only take 10 hours at a sensible rate. But if it takes a week, then it still pays the 500. EDIT: Actually, not so much the expertise as not a good enough portfolio

I thought I was being brief! There was loads I left out, like .... Er, yeah, okay. I will go to bed now.

Hi and welcome Its easier to sort of go through this in a very boring way ProcessWire has a fairly basic construction: Fields > Templates > Pages As you would have already noticed. Firstly, it is important to realise that Templates and Template Files are not the same thing. Templates are your way of grouping fields together and template files are for markup for displaying pages. PW has no practical limits for the amount of fields, templates, template files and pages you create, so really you can do as many variations as you need - it really wont matter. The API in ProcessWire allows you to manipulate the field data associated with either the page you are currently viewing ( so $page->title, for instance) or it allows you to get or find fields from other pages or groups of pages. One of the most important areas for you to look at in the API is probably the section on selectors as this will give you a lot of details about relationships and retrieving field data. So, looking at Profiles for the moment. You might create a file in sites > templates called profile.php Then in the backend, you would create a new template - it will show that profile.php is available as a template file and you would choose that, obviously, then give your template a name - profile would be good! You now create a bunch of fields that you want to use for the profile. In some ways this is a bad example because there is already a template in the system for users, but we will pretend for the moment there isn't! However, when you create a template in the backend, after you create it you can associate other template files with it, should you wish. Add your fields to the profile template and you are half way there. From this point on, it is simply a case of using PHP and the API in profile.php to create what you need - and it is much simpler than starting from scratch. The API is very powerful and will do a lot of the work for you, while leaving you to do whatever layout you wish. That template and template file combination can now be used for creating thousands of profiles. When you link to one of those profiles, it will use the template and associated template file to render the data. The template file can be used for both displaying data and for creating input forms for editing data. (Other people can give you more of a lead about that). Now, with other pages, if you need to create completely different templates for each page because they are all completely different, then that is what you do. Not a problem. Though remember that any field can be used in any template. So, if all your templates need Title, page_meta, mani_text and so on, then you can reuse field as you wish (note, you can only have one instance of each field in a template, for obvious reasons - so if you need two textareas, you will need to create two textarea fields) The point with PW is that apart from following the relationship between fields > templates > pages, it is flexible enough for you to work however you wish, more or less and very fast once you get the hang of it.

I can think of plenty of music videos over the years that "felt" 24 hours long. I think I probably did sound on a couple of them, which is worrying.

Very nice design, especially for a classical composer.

Never heard of them, but a google search does seem to bring up quite a few moans: http://www.webhostingreviews.com/000webhost-reviews.htm

Yep! Admin, just like everything else, is a page. So, if you click on Admin on the pages list, edit and then go to settings, you will see you can change the name (and therefore the path) just like any other page. You will need to log back in after, and don't forget what you changed it to!

Inspired by that, I should have added: Windmills of the mind Here I go again And this that I did for a commercial: http://dancingbear.co.uk/site/assets/audio/single-jingles/liecestershire-parknride-full.mp3

Yeah, always likes that! I remember the original by Trent Reznor

Good grief - I got something right! You might also find this useful: http://processwire.com/talk/topic/4991-sub-arrays-dates-times-and-pure-hell/#entry48484 This was about taking the date, splitting it into years (looping it), splitting it into months, then days .... The result can be seen here: http://harlestonanglingclub.co.uk/fixture-list/

Okay, this is not an area that I am great at.... but assuming your date field is called "date" I would think you need to do something like: $todaysdate = time() $posts = wire("pages")->find( blah blah .... date>$todaysdate .... ):

hmmm - like this. Could neaten up some of my image fields....

Not sure about "favourite" programming music, but I did think of a few that are possibly appropriate; Tears of a Clown Puppet on a string (think about it...) All the burning bridges still I held my head up high Suicide is Painless Brand New Toy (Tom Paxton) After Midnight (The late great JJ Cale) All by Myself I cant get no (Satisfaction) Wont be fooled again Pigs on the Wing Is there anybody in there? The entire "Tommy" album And just about anything by Leonard Cohen

Okay, first of all, I have not done that with websites - well, I did many, many years ago with a large community site, but that was chaos! However, I have managed huge event productions and video productions where you have a lot of different talent supplying different technical skills with a lot of overlaps. I also have a nephew who is a lead developer on several very large games. The trick I have found is to try and reduce overlaps and to make sure the main development parameters are set in stone BEFORE anyone starts coding, drawing or anything else. So, everyone should know what it is meant to look like, understand every aspect of the brief (not the client brief, but the one you write as project manager) and know exactly what their responsibilities are right down to what scripts or functions they should be writing. AS part of that process it is worth having a short lived debate on style and structure, then put that in the brief too. Then, when someone goes sick or drops out, their work can be understood. That project brief document is important and is often neglected. The last time I did one was for a community zone for an online game where the community applications would need to talk in detail with the game application. Horrendously complicated! The final project bible for that was 40,000 words long - but nothing was missed out and in the writing of it, we solved huge amounts of tech problems and knew what it would look like, how it would feel and had even tested out how it would work with players and what they thought. It just needed to be manufactured - and it would have been if the people behind it had actually coughed some money up! I am often amazed how many large projects are created on the hoof - but then, going by how many IT projects end up as camels (a horse designed by committee) , it is probably no surprise at all. Imagine Ford walking onto his first production line and saying, "Okay, guys, we are going to make the first mass-produced private vehicle. No, sorry, I have no idea what it is going to look like or how it will be put together, but I am pretty sure it will be called the Model ... er ... something. Right, turn the production line on!"

I know this may sound very obvious, but with field, templates, template files and so on I try and use nice, easy to understand names, remembering that sometimes you may want to sort alphabetically Since from the website point of view, it only ever sees page names, I can call the rest what I like - so I might as well chose things I have a fighting chance to remember! When it comes to actually coding, I don't have any fixed way of laying things out, but I try and remain consistent throughout a project - so I will comment in the same style, or tab in the same way and so forth. This makes debugging much easier. I also sometimes break things down a bit. If I have a lot of functions being kept in an include file, I might break those up into multiple files just while I am working, then stick them back together for production. Again, it is really just helping me find my own way about. Not that anything I do really gets very complicated! I am a bit influenced by a PERL magician who helped me put together a very early web 2.0 style community site in the 90s. Almost the entire site was in a single file called index. It was scary to work through, but very efficient!