I know this has been discussed before, but I’m curious as to which calendar option most members prefer.
I’ve played around with the Google Calendar and it’s very easy to include into a FWP site using Crowbar, but it’s somewhat limiting. Plus, the calendar design leaves a lot to be desired.
The only problem with Perch, and this is probably because I’m still learning it, is there are a lot of things you have to do to get their plugins (or whatever you call them) to work. (i.e. templates, css, Crowbar code, etc.)
The Google calendar took me like 5-10 minutes to implement.
The only problem with Perch, and this is probably because I’m still learning it, is there are a lot of things you have to do to get their plugins (or whatever you call them) to work. (i.e. templates, css, Crowbar code, etc.)
The Google calendar took me like 5-10 minutes to implement.
I think one way it can be used is to create reusable code that can be dropped into other projects. I might be wrong, though. Their explanation is a bit vague. That, or maybe I’m having another of my ever-more-frequent “stupid days” where I have to read something 20 times before it sinks in.
And don’t expect Perch support to help you, ‘they don’t do css’.
A product full of potential but crippled by their attitude imho, a typically British product in many ways.
s
I’ve noticed that, but primarily with Rachel. She works better with experienced developers, IMHO. Drew is much more forgiving and has helped me personally on numerous occasions, even with stupid questions.
In fact, Drew was instrumental in helping me setup my developer server and current workflow.
I’ve noticed that, but primarily with Rachel. She works better with experienced developers, IMHO. Drew is much more forgiving and has helped me personally on numerous occasions, even with stupid questions.
Agree with you both. They’ve both been very helpful but there are times when you feel your trying their patience with not having better knowledge, certainly true in my case. Making approaching them feel like pushing your luck and wasting their time. I really don’t wish to appear ungrateful, just slightly frustrated at seeing a good product let down. Though I’m sure there’s good software out there that just plays dead with no support to speak of.
… If your going to create a nice bit of software that’s initially easy (relatively) you should be prepared to deal with all skill levels. I’ve said this before but if they spent time getting their documentation and examples up to scratch they probably could avoid a lot of numpty questions. Perhaps we’re spoilt somewhat on this excellent list.
I’ve encouraged Drew to embrace Freeway Pro users, many of whom do not have a preferred CMS, but my attempts have been fruitless. Since both are UK based companies, you would think from a logistics standpoint a Softpress/Perch relationship would work out well. Plus, since they both enhance each other’s product it would likely strengthen both companies.
I’m curious, in what way would the Perch devs embrace FW users? They make a platform-agnostic CMS, I’m not sure how or why they would want to make special allowances for a very small Mac-only web authoring tool. If anything I would think FW should more easily accommodate a wider range of CMS.
I’m curious, in what way would the Perch devs embrace FW users? They make a platform-agnostic CMS, I’m not sure how or why they would want to make special allowances for a very small Mac-only web authoring tool. If anything I would think FW should more easily accommodate a wider range of CMS.
Not really special allowances per se, just an awareness of the Perch platform and some basic help. Perhaps a printed tutorial or instructional video on how one would implement Perch into a FWP document, similar to what was done with WebYep.
Quite frankly, integrating Perch into FWP was a HUGE challenge for me and one that I would have never been able to accomplish if it weren’t for you, Nathan Garner (BigG), Walt, Dave, Thomas, and a few others.
I understand your point and it would be very useful but I think that duty rests with SP or the FW community at large, not Rachel & Drew. I just don’t see them diverting development resources to put something together for a tiny community where an even tinier percentage of FW users would even use Perch in the first place.
And even if they did put together some docs then they would they would have to start fielding FW-specific support. It’s a lose/lose for them. When you consider that the vast majority of Perch users probably use a web tool (regardless of platform) that easily allows for code-level tinkering then the Perch docs - as vague as they might be at times - actually apply to a very broad range of tools. FW is the oddball in that crowd.
Not really special allowances per se, just an awareness of the Perch platform and some basic help. Perhaps a printed tutorial or instructional video on how one would implement Perch into a FWP document, similar to what was done with WebYep.
Quite frankly, integrating Perch into FWP was a HUGE challenge for me and one that I would have never been able to accomplish if it weren’t for you, Nathan Garner (BigG), Walt, Dave, Thomas, and a few others.