I find that Fusedocs are great when working with html designers - we had a whole heap of really long, complicated forms for a project. I wrote the Fusedocs and gave them to the html guy. He could see straight away what the form fields were, what to call them, how big to make them, what they were for etc etc. What would have been a nightmare to organise, create and test became quite simple.
K. > -----Original Message----- > From: Gallant, Ron [mailto:[EMAIL PROTECTED]] > Sent: Saturday, 13 April 2002 3:18 AM > To: '[EMAIL PROTECTED]' > Subject: RE: tips on working with non-fusebox designer/html guy?? > > > I do like Patrick's reverse psychology. I am a > designer/FBer, and have been on both sides. People just don't > like being told NO or CAN'T. And usually if your saying > that, it's because you never tried to compromise. Make each > other happy and in the end it will make the client happy. > And that's what is important here, right? > > -----Original Message----- > From: Jim Robson [mailto:[EMAIL PROTECTED]] > Sent: Friday, April 12, 2002 2:02 PM > To: [EMAIL PROTECTED] > Subject: Re: tips on working with non-fusebox designer/html guy?? > > > Jeff, > > I am coming from the other direction, so maybe I have a > different perspective. On my last project, I was the graphic > designer / static HTML guy, with no knowledge of ColdFusion > or Fusebox. On my current project, I am the ColdFusion / > Fusebox guy porting a Fusebox app to an existing static site. > > On both projects, I collaborate with people over 1500 miles away. > > First: if you don't already have one, set up a development > site that is accessible via the Internet. This way both you > and the graphic designer will be able to see the project as > it progresses. > > Another suggestion - and this is just a suggestion, without > knowing the particulars of the site you're building - is to > be open to the possibility of using some static HTML pages on > the site. We did this on the last project, and it worked out > great. The main page of the site is mainly HTML, with just a > little ColdFusion logic to switch Generator templates > depending on whether the user is logged in. The actual login > form is in the Generator template itself. The login function, > of course, is controlled in the Fusebox. This allowed me > maximum control over the look and layout of the main page, > while still tying it in to the Fusebox "heart" of the site. > Unfortunately, the site is on a corporate intranet, so I > can't show you how it came out. But the client was happy > enough that my current project is with another business > segment in the same corporation :-) > > We had the best of both worlds: the functionality, > efficiency, and portability of a CF/Fusebox app, with the > design freedom of static HTML and Flash. > > Most important - and this probably goes without saying, but > I'm going to say it anyway - is to maintain a professional > attitude. Respect each other's ability, be ready to learn and > ready to teach, and communicate everything. Communicate all > the time - ask questions, make suggestions, let the other guy > know what you're up to and why. That's how I went from > knowing nothing about CF / Fusebox to building my own apps to > porting apps to other people's sites - all in less than 6 > months. I'm no FB Guru, but I learned a lot. Meanwhile, the > developer learned some things about graphic design, DHTML, > and Flash. It was great. > > I wish you the best on your project, however you decide to go > about it. > > Jim Robson > Master CIW Designer > http://RobsonDesign.com > > > ----- Original Message ----- > From: Jeff Fongemie <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, April 12, 2002 10:37 AM > Subject: tips on working with non-fusebox designer/html guy?? > > > > Hello fusebox, > > > > I've been asked to collaborate on a site project with another > > guy who has great graphic arts background and knows a bit of html. > > > > His responsibilities will be the visual layout, design and content > > to some degree. > > > > I'm in charge of structuring the site, (fb) and making it > all work. > > > > This guy knows nothing of FB, and has only worked with > static html. > > > > I've got to be able to let him freely do his thing, and > come up with > > what he wants, but I'm thinking I should give him some constraints > > in his design (this guy loves frames). I can't teach him FB > > methodology, > but he will need to > > understand some of it I suppose. > > > > I may start by having him come up with one static html page, > > complete with all graphics, and then I'll break that up into a > > layout file, show him what will be called in the switch file and > > what is static on the layout file. > > > > Any tips for getting a non FB person up to speed on a project? We > > are also 2000 miles apart, so all interaction is by telephone and > > email. > > > > -- > > Best regards, > > Jeff Fongemie mailto:[EMAIL PROTECTED] > > > > > > > > > > > > Blue Cross Blue Shield of Florida, Inc., and its subsidiary and > affiliate companies are not responsible for errors or > omissions in this e-mail message. Any personal comments made > in this e-mail do not reflect the views of Blue Cross Blue > Shield of Florida, Inc. > > > ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
