Andrea,
On Oct 15, 10:04 am, Andrea <[EMAIL PROTECTED]> wrote:
> any extra ideas/ best practice I guess everyone has sort of
> similar issues
Your best bet is to set up a local application environment for your
designers, and have them commit changes to the repository just like
your deve
better to be project friendly and get everyone singing from the same song book
just my 2c
On 10/15/07, Andrea <[EMAIL PROTECTED]> wrote:
>
> make sense, i just thought to be designer friendly :)
>
>
>
>
> On Oct 15, 11:37 am, Andrew Scott <[EMAIL PROTECTED]> wrote:
> > I'll agree with Toby,
make sense, i just thought to be designer friendly :)
On Oct 15, 11:37 am, Andrew Scott <[EMAIL PROTECTED]> wrote:
> I'll agree with Toby, for the same reasons.
>
> The problem is a good one, and it boils down to discipline on the designers.
> You can have a share on a server for them to work
I'll agree with Toby, for the same reasons.
The problem is a good one, and it boils down to discipline on the designers.
You can have a share on a server for them to work with if you want daily
backups, but I would use it as a normal mapping for them to work with their
own work and use tortoise
Hi Charlie,
thanks for that mate.
All I had to do was ignore the fact it returned "connection failure", I have
no idea why it returns "connection failure", but I am just writing the file
to disk and it works. Cheers
PS. yes I was using getAsBinary
On 10/13/07, Charlie Arehart (lists account) <
Andrea,
I'd recommend against the shared repository - I went that way with a team a
few years ago and it was very painful. You have the difficulties of user
tracking etc, and when you start using tags and branches properly everything
goes to hell, but primarily we found using the dev server locat
Andrew...
That's exactly what I'm actually trying to achieve with solution
3... :)
I just do not want designers to have the need to install CF and apache
on their machines... designers will over-kill me ! .. that's why in
solution 3 they will work directly on the server (on a shared folder)
(comm
Maven, would be overkill.
Maven's strength is in repository and library dependence, but having said
that if anyone is using it in a CF environment it would be good to know.
As far as source control goes, a designers work should have revision as
well. How this fits into your scheme is up to you,
cool I never used maven before, I will definetely have a look at
it...
On Oct 15, 10:12 am, Haikal Saadh <[EMAIL PROTECTED]> wrote:
> IMO, the age of designers who only do photoshop or html is long gone...
> maybe they could be trained to write their presentation layer stuff as
> coldfusion pag
I'd have to agree. I've tried it a number of different ways, and the only
really feasible option is to make designers use source control. On both mac
and windows there are very easy to use ways to tie in source control through
your explorer windows or into dreamweaver etc etc but if you really wa
IMO, the age of designers who only do photoshop or html is long gone...
maybe they could be trained to write their presentation layer stuff as
coldfusion pages and/or custom tags?
That aside, if you think option 3 will break your post-commit scripts,
why not use maven instead of ant, and have
I have currently installed subversion on our server and trying to find
out the best solution for our developers and designer.
The idea is to have
- each developer working locally on a "local.xxx.dev" and committing
to the svn xxx repo. Each dev will be using coldfusion developer ed +
local apac
12 matches
Mail list logo
