[news.eclipse.technology.epf] Re: Guidance Attachment

["Peter Haumer" <phaumer@xxxxxxx>]

I fully agree and that's why you can embed attachments in every rich text 
field in the tool.  The separate attachment fields were intended to remind 
people not to forget attachments.  We are currently updating the forms for 
example, reusable asset, report and whitepaper to have such a field as well.

-- 


Thanks and best regards,
Peter Haumer.

______________________________________________________________

PETER HAUMER
IBM | Eclipse Process Framework Committer
______________________________________________________________
"Jan Masaryk" <jan.masaryk@xxxxxxxxx> wrote in message 
news:op.tmcg80g8clxtfu@xxxxxxxxxxxxxxxxxxxxxxxxxx
> Hi Peter,
>
> I definitelly agree with you that we should be very carefull in using 
> attachments in model
> but during using EPFC I recognized that it can be very helpful has
> option to attach file to Example.
>
> Just let's imagine that we have Template 'project plan' in MS Project plan 
> format.
> We find usefull attach some examples how this template can be use ... and 
> that's again MS Project file. :-)
>
> all the best,
> jan
>
>
> Hello.
> (1) As I mentioned in the email list, you can attach and provide URLs in 
> the
> rich text fields using the Add Link button.  The reason why there is not
> separate field is that attachments for these types are not the normal 
> case,
> but rather the exception until you migrated your content in the EPF 
> format.
> For templates an attachment is required as you need to provide the
> attachment for that third party tool the template describes.  That's why
> there is a separate field, to remind people.
>
> (2) We could provide another field for templates that manage URLs, but in
> most cases you want to document your URLs, i.e. explain what they point 
> to,
> don't you? So the rich text fields seem to be the best place to put these.
>
> On Fri, 03 Nov 2006 19:32:28 +0100, Peter Haumer <phaumer@xxxxxxxxxx> 
> wrote:
>
>> Hello.
>> (1) As I mentioned in the email list, you can attach and provide URLs in 
>> the
>> rich text fields using the Add Link button.  The reason why there is not
>> separate field is that attachments for these types are not the normal 
>> case,
>> but rather the exception until you migrated your content in the EPF 
>> format.
>> For templates an attachment is required as you need to provide the
>> attachment for that third party tool the template describes.  That's why
>> there is a separate field, to remind people.
>>
>> (2) We could provide another field for templates that manage URLs, but in
>> most cases you want to document your URLs, i.e. explain what they point 
>> to,
>> don't you? So the rich text fields seem to be the best place to put 
>> these.
>>
>
>
>
> -- 
> Using Opera's revolutionary e-mail client: http://www.opera.com/mail/