Dynamsoft Forums

I know you guys just finished V3 and are licking dealing with a bunch of 'just released' issues and people get used to the never versions but once you have some breathing room here is a suggestion to improve the key work expansion.

Assuming your automatically doing a GetLatest after a check in to get the current values;
Given the following code headers as and example;

/*
* Last edit by $Author: Thx $
* Revision $Revision: 5 $
*
*/

It would be great if the labels where collapsed when check in so it looks like this;

/*
* Last edit by $Author$
* Revision $Revision$
*
*/

that way the diff systems will not show the $Revision: ? $ line as always different.

When a GetLatest is done and the file is read only on the disk it should look like

/*
* Last edit by Thx
* Revision 5
*
*/

This not only is more present to read/print it also gives the developer a way of knowing if they are dealing with non-checked out code by doing things like.
#define SAWSRevision “$Revision: 5 $”
because when it's checked in it would be;
#define SAWSRevision “5”
sometimes a useful bit of information.

Then when the file is checked out for editing it should be

/*
* Last edit by $Author: Thx $
* Revision $Revision: 5 $
*
*/

as we started with.

This is likely why other VC systems allow you to enter $Revision$, Because it's not seen on check in and is then expanded on check out.

Also, besides the formatting improvements needed for $Log$. It also is a little special here as the text it inserts would go directly into the actual source code.

$LogStart$ and $LogStop$ would also need some special handling if you ever plan to add them to the useful key words supported.

Of course it would be nice to configure a repository as UserKeywords=Auto and then on check in have it look for something like $UseSAWSKeywords$ in the file to turn it on key word processing on a file buy file basses. But there is good and bad with that one but I'll add it here anyway.

Hi isgdre,

Your suggestion is really impressed

I've forwarded it to our team for the consideration of the coming release.

Warm Regards,

Hi All.

Is there any news on this issues. This one still drives me crazy.

Ok, truth be known I'm not going to give up on SAWS just because of this but I sure seem to be fighting it more then I care to.

Sorry, our developers are on a tight schedule now. We will consider the feature in the next release of SourceAnywhere Standalone.

I do think your suggestions make sense. What about other users? What do you think about the keyword expansion feature? I'd love to hear your comments.

Regards,

Let me guess.

The people with smaller or short term projects will not care as they don't use this feature.
People with larger groups or projects will.

Of course you could do a poll here but I'm not sure how you would get input from most of the users. Still, The keyword expansion system has issues and something like the simplification I outlined would to a long way to make it more useful and easy to use for the people that use it no matter what percentage that is.

Hi isgdre,

I've created a poll here and make it as a sticky. Let's see what other people say.

Regards,

See, 100% of the people agree with me so far.
(I found the poll)