PowerVCS Forum
April 28, 2024, 05:02:07 PM *
Welcome, Guest. Please login or register.

Login with username, password and session length
 
  Home Help Search Login Register  
  Show Posts
Pages: 1 [2] 3 4
16  PowerVCS - Development / Change Log / Report to show changes in a date range on: May 03, 2013, 07:57:07 AM
Browser - 1.2.5.0 A new report, Report->All Changes in Date Range, will show changes, additions and deletions for a project within a specified date range.
17  PowerVCS - Development / Change Log / Option to show dates in local time zones on: May 03, 2013, 07:53:54 AM
Browser - 1.2.5.0 Select "Display times in local time zone" in Edit->Preferences.  Times for all repository items will be shown in the local time zone.  The local time zone is determined by querying the browser and is automatic.  When this option is not set the times are shown in the time zone of the repository server.
18  PowerVCS - Development / Change Log / XML Error in Version Pane on: September 04, 2012, 02:27:21 PM
Browser - V1.2.3.1 If version descriptions had special xml characters, version list would not display and an XML error was displayed.
19  PowerVCS - Development / Change Log / V 1.1.15.0 - SCC_API. Support for XML Spy on: December 27, 2011, 02:27:30 PM
Interface tested with Altova's XMLSpy.  Minor revision to SCC-API to support XMLSpy displaying icons with correct source control status.
20  PowerVCS - Development / Change Log / Find in Files in Root Project Directory on: November 22, 2011, 09:59:50 AM
Browser - V1.2.3.0 Find in Files was searching all projects at the root directory, rather than just the active one.
21  PowerVCS - Development / Change Log / Find in Files in FireFox on: November 22, 2011, 09:58:51 AM
Browser - V1.2.3.0 Find in Files not functioning properly in FireFox
22  PowerVCS - Development / Change Log / Report All Checked Out Files on: November 21, 2011, 02:13:14 PM
Browser V1.2.2.0 - Was not functioning IE8/9.
23  PowerVCS - Development / Change Log / 'Response contains no XML' in FireFox on: November 18, 2011, 09:09:22 AM
V1.2.1.0 - Browser interface. The incorrect 'Response contains no XML' error appearing in FireFox has been removed.
24  PowerVCS - Development / Change Log / Getting Labeled Files on: October 10, 2011, 10:07:37 AM
V1.1.6.0- Command line interface.  Recursively getting files based on label was stopping when encountering a folder with no matching files.
25  PowerVCS - Development / Change Log / Removing and Restoring Folders on: May 13, 2010, 08:52:31 AM
V1.2.0.0 - Browser interface.  Functions to Remove and Restore Repository folders has been added to the web interface.  These functions are available in the Project menu.

As with files, when a folder is removed it is just tagged as removed; it is not deleted from the Repository.  You can restore the folder at any time.  In the restore function when you browse the Project folders, you are shown which folders are the in the removed state (normally these folders are not shown).  You can select a removed folder and then choose to restore it.
26  PowerVCS - PowerBuilder Integration / General Discussion / Shared PBLs on: May 07, 2010, 01:27:46 PM
Files in different Projects will be saved as separate entities in the Repository even if they were initially added from the same PBL.   The result is that you have two different Repository entities updating the same PBL, which is not good. 

What this means is that any shared files (PBLs) should be part of the same Project.

Second the directory structure in the Repository is going to reflect the directory structure of the Workspace/Targets relative to the “Local Root Directory” of the PowerBuilder Workspace.  For example if the Root Directory is C:/source1 and a PBL is in that directory it’s objects will appear at the root of the Repository for that Project.  If the PBL were in C:\source1\base, than the objects for that PBL would be in the ‘base’ subdirectory from the root of the Repository in the Project.  I believe this is what is happening in your case 2.  Although this imposes a restriction in how shared PBLs are structured, I believe this design is the only way to handle the objects with duplicate names.

So if you wish to share objects (PBLs) between Targets, then the rule is:

  1. The Targets must be part of the same Workspace (PowerVCS Project).
  2. The relative paths to the shared objects must be the same in each Target.

Phil
 
27  PowerVCS - Development / Change Log / Refreshing Edit User Window on: May 07, 2010, 01:20:31 PM
V1.1.1.9 - Browser interface.  After a change to a user, the Edit User window had to be manually refreshed to show the change.  This has been changed to happen automatically.

Phil
28  PowerVCS - Development / Change Log / Activating Removed Users on: May 07, 2010, 01:19:12 PM
V1.1.1.9 - Browser interface.  If you have removed a user, the user is not deleted from the Repository but marked as removed.  Now you can reactivate a removed user through the Edit User interface.  A new checkbox indicates the active status of the user.  You may toggle the checkbox to change the status.

Regards,

Phil
29  PowerVCS - PowerBuilder Integration / General Discussion / List of Checked Out Objects on: March 15, 2010, 12:04:46 PM
In PowerBuilder when you choose to Check In objects for a Target or Workspace you are presented with a list of all objects that are checked out, NOT those just checked out to you.

I believe this is a "behavior" of PowerBuilder.  But if users have seen a different implementation or, if not, a workaround, let us know.

You can view a report in the Browser interface of the objects checked out to you.

Regards,

Phil
30  PowerVCS - Development / Change Log / Project Label Applied to Removed Objects on: March 15, 2010, 12:01:23 PM
V1.1.1.8 - Browser interface.  If you choose to create a label for a Project that has had objects removed, the label was being applied to the removed objects.  Then the Get (by label) function was retrieving the removed objects.

Pages: 1 [2] 3 4
Powered by MySQL Powered by PHP Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!