This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 12818 - Teach "Open" action in "Revision Explorer" to be cleverer, please.
Summary: Teach "Open" action in "Revision Explorer" to be cleverer, please.
Status: CLOSED WONTFIX
Alias: None
Product: obsolete
Classification: Unclassified
Component: vcscore (show other bugs)
Version: 3.x
Hardware: All All
: P4 blocker (vote)
Assignee: issues@obsolete
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-06-13 16:16 UTC by Jiri Kovalsky
Modified: 2003-07-01 12:57 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Kovalsky 2001-06-13 16:16:54 UTC
Development build of NetBeans #209 on Windows 2000 with JDK 1.3.1.

Description:
============
Binary files added into repository such as pictures can't be investigated throu-
gh famous "Revision Explorer" because if you use "Open" action on particular re-
vision it is checked out but opened as text file. It would be nice if for exam-
ple for picture it would determine proper dataobject and open it in its native 
editor.

Steps to reproduce:
===================
1. Mount CVS filesystem and place there arbitrary picture.
2. "Add" and "Commit" it into repository so that it becomes [Up-to-date].
3. Invoke its "Revision Explorer" and try to do "Open" action on its 1.1 revisi-
   on but you will see that it will be opened into standard editor :-(
Comment 1 Milos Kleint 2001-07-30 09:15:33 UTC
this might be a problem. This can be hardly done for binary files
only. You'll have to perform the dataObject search on all
fileobjects.. (I'm not aware how to decide which objects should be
involved and which not.)

However then we'll run into problems with multidataobjects. eg. forms.
A form dtat object consists of 2 fileobjects.. and we will retrieve
the older revision only of the first one.. There's no easy way how to
learn the right revision of the remaining fileobjects.. thus we could
end up with having one older file together with the newer file.. which
can/will collapse and give bad results..

There is a slight change of finding the right revision for the other
file atha works for cs, however not sure if it works for other version
control systems..
do log for the initial file, find out the date at which the wanted
revision was commited, find all files with the same and and different
extensions and try to get the revision at that time. 

However will would need to put the files on the path for dataloaders
for recognition (not sure how to do that without overwriting the
current files.. maybe to a temp dir on the default filesystem?)

Martin, feel free to reopen the bug if you feel there's solution..
Comment 2 Jiri Kovalsky 2001-09-03 15:05:15 UTC
Okay, it seems I am the only one missing this feature. I am verifying 
it if it is so hard to implement. I thought only some easy going bina-
ry files could be affected but never mind.
Comment 3 Quality Engineering 2003-07-01 12:57:28 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.