dotSoftwaredotDevelopmentdotCustomersdotAbout us
PushOk logoblank
bullet Home
bullet My software
bullet Support
bullet My payments
bullet My info
bullet Subscriptions
bullet Voting
bullet Contact us
fast linksFast Links
news&eventsnews and events

2012-12-21 
Major update of SVN SCC plug-in - versions 1.7.2 are finaly released

2012-12-21 
Major update of SVNCOM version 1.7.2 are finaly released

Lightweight embedded Node.js database with MongoDB API.

Ticket

Search go
PushOk Logo blank
leftTicketright

PB9 - some actions slow

( CVSSCC )
Type: Public Status:Closed Created: 04 May 04 05:00 Updated: 19 May 04 05:00
--> Igor Pushkov (admin)  at 19 May 04 05:00 writes

Yes we fetch status for entire folder. This is some optimization
technique. Since usually IDE ask status for all (or many) source files
at one time. And this technique can reduce time.
Right now, with new function, you can try to switch on option "Delete
power builder generated files" in PB option, and press button "Preset
for PB" in plug-in configuration window. This way status retrieving
should work faster. Since now only version of files will be compared,
not the content.
Also better to switch off option "Perform diff" on status update. It
is not needed.
--> Dan Cooperstock (user)  at 18 May 04 05:00 writes

I'm trying the new version now. (Figured out that the dates on the download
page must just be wrong.)

One thing I notice is that when I do a Get Latest Version on an object, in
your popup window, first I see "Updating [object name]", then I see
"Fetching status info for folder [directory name]". That 2nd step often
takes quite a while (say, 30 seconds) on a largish PBL. (This was the same
on the previous version too.)

Why would it be fetching status for the whole directory, or am I
misinterpreting this message?
--> Dan Cooperstock (user)  at 04 May 04 05:00 writes

Some actions with PowerBuilder 9 seem to be quite fast with PushOK and CVS,
such as opening a PBL (which includes getting status on the objects in it).
However, some seem unreasonable slow. For instance, if I right click on one
object and do a Refresh Status, that can take up to 30 seconds. That
doesn't make much sense to me.

One other thing related to refreshing status. When I first open a PBL and
it takes a while talking with CVS getting the statuses of every object,
often what happens is that most objects in the PBL come up with the correct
status, but a few show a question mark. I have seen this behaviour with
Borland StarTeam too, so it's certainly possible that it's a PB bug. On the
other hand, it never happens with Merant Version Manager.

In terms of settings, I have everything turned on to make it get good
statuses. In PB, I have "Perform diff on status updated" checked, and in
the PushOK CVS options, I have all of the following checked: Check server
for file status, Determine "need update or out of sync" status, and
Determine "checkout by someone else" status. My experience so far is that
all of these need to be turned on to make sure we get correct statuses.

Any ideas on this problem with the occasional question marks? If I do a
"Refresh Status" on them they get fixed, but the next time that PBL is
opened, usually the same objects come back with a question mark again.
Rate this ticket:
Not useful at all
Partially useful
Useful
Very useful



You are 9751807 visitor since 20 Jan 2003.
2761 visitors today and 16 online right now.
blank left to top right blank

© Copyright by PushOk Software, 2003-2024, webmaster@pushok.com