RE: Using a source code control system

Thanks Shane and everybody for the replies.
My *.cex files have the correct "begin CLASS;" entry. Below is my fscript
file
that I'm trying with Forte 2.0.E.2 NT version:
setWorkspace ktCheckBoard
open
findproj sample1
cd c:\forte_cs\install\bin
compile sample1_sysadm.cex
importplan sample1_sysadm.cex (>>> It failed right here)
Khanh
From: Shane Howlett
To: forte-users
Subject: RE: Using a source code control system
Date: Wednesday, November 13, 1996 9:54PM
Hi Khanh,
In regards to your compile error...
We found that an interesting difference between versions 2.0.D.x and 2.0.E.x
was with the first line of an exported .CEX file.
A la ...
2.0.D line 1: begin;
2.0.E line 1: begin CLASS;
It caught me out. Just insert or remove the word CLASS using a text editor
depending on your version of Forte.
As for version control, we have been retaining workspace export files
(wascally WEX files!) as backups and plan to make greater use of Baselining
in
the repository. In terms of securing our environment, this approach
essentially meets our needs.
Shane Howlett
The Hydro.

Thanks for your help. That works.
-khanh
At 11:20 AM 11/14/96 -0800, you wrote:
>
Hi Mike,
Thanks for the reply. I think that was what I did.
Below is my fscript input file:
setWorkspace ktCheckBoard
open
findproj sample1
cd c:\forte_cs\install\bin
compile sample1_sysadm.cex
importplan sample1_sysadm.cex (It failed at this step)'importplan' is unnecessary: 'compile' has compiled the .cex file into your
project. importplan is failing beacuse it expects to see an entire plan.
Mike
Mike Schilling ([email protected])
Forte Software, Inc.

Similar Messages

RE: Using a source code control system with...

Hi Khanh,
In regards to your compile error...
We found that an interesting difference between versions 2.0.D.x and 2.0.E.x
was with the first line of an exported .CEX file.
A la ...
2.0.D line 1: begin;
2.0.E line 1: begin CLASS;
It caught me out. Just insert or remove the word CLASS using a text editor
depending on your version of Forte.
As for version control, we have been retaining workspace export files
(wascally WEX files!) as backups and plan to make greater use of Baselining in
the repository. In terms of securing our environment, this approach
essentially meets our needs.
Shane Howlett
The Hydro.

Thanks for your help. That works.
-khanh
At 11:20 AM 11/14/96 -0800, you wrote:
>
Hi Mike,
Thanks for the reply. I think that was what I did.
Below is my fscript input file:
setWorkspace ktCheckBoard
open
findproj sample1
cd c:\forte_cs\install\bin
compile sample1_sysadm.cex
importplan sample1_sysadm.cex (It failed at this step)'importplan' is unnecessary: 'compile' has compiled the .cex file into your
project. importplan is failing beacuse it expects to see an entire plan.
Mike
Mike Schilling ([email protected])
Forte Software, Inc.

Help needed to use Source code control system

Hi all
I am working on Suse 9.2 and I use JSP and Servlet in my project.I like to use Source Code Control System (SCCS) . But I have no idea about that.I need some help to initiate my project.
Thanks in advance.
-jegan

I don't know this "SCCS" but I advice you to use Subversion as it is widely used open source standard.

Having Problem in access to Source Code Control System (URGENT help needed)

I am using JDeveloper 9i first time. The repository is in Oracle 8i.
I have established a connection from JDeveloper 9i to Oracle 8i repository running on Sun Solaris.
We have created a shared area and my colleague have checked-in some files. I have all access to shared area and I can see the checked-in files, but I am not able to check-out to the local folder.
I need help to resolve this problem urgently. Please consider this as an SOS call. Thanks

Hi,
The JDeveloper help system strongly recommends that you don't use shared workareas in this way. In fact, it's not possible in the beta release of JDeveloper to work this way at all, because there is no way for you both to get the files on to your file system in a way that JDeveloper will recognize.
The JDeveloper documentation on Repository is a very good source of information on the best way to organize developer workareas (particularly the section on best usage recommendations). The Repository is a very complex product originally intended for much more than just source control and there are many ways of using it. We have necessarily had to focus on a subset of this functionality in JDeveloper, mainly to keep the UI from being excessively complex for new users.
Here's a summary of the way we recommend working:
o Create a workarea in the RON which will be used as the basis of developer workareas (developers will not actually use this workarea directly). Make this workarea shared by granting access rights to the PUBLIC role.
o Each developer uses the Workarea wizard in JDeveloper (Source Control->Configure... in the beta release) to create a developer workarea based on the shared workarea.
Thanks,
Brian
JDeveloper Team
null

Database source code control or version management

Hi all,
I work in a data warehouse development project, where database schema changes form majority of development work. As a development DBA I look after ensuring that all the database schema changes are version controlled properly.
We currently use CVS as a source code control system. We can use CVS well enough where stored procedures, functions and packages are involved. But when it comes to table definitions, we are finding use of CVS bothersome.
Hence I would like to know, which tool are you using for version control of schema changes. Any links to best practices on DB version control would be much appreciated.

I think Oracle have introduced something in 11g for version control. Also you can use third party Software like ERWIN. You can also explore Oracle Data Modelling software which is Beta currently.
Regards

How to use Source Code Control for Large Application?

Hi, All!
I would like to collect knowledge about "best practice" examples for using Source Code Control and project organization for relative large application (let's say approx 1000 SubVIs).
Tools used:
LabVIEW 8.0
CVS Server
PushOK CVS Proxy Client
WinCVS
With LabVIEW 8 we can organize large project pretty well. This described in article Managing Large Applications with the LabVIEW Project.
I have read this article too: Using Source Control Software with LabVIEW In this Article Source Safe used, but with PushOK all looks nearby the same and works (some tricks for compare function are required).
Example. Two developers working together on same project. Internally project is modular, so one developer will work with module "Analysis", and another one with "Configuration" without interferences. These modules placed into Subfolders as shown in example above.
Scenario 1:
Developer A started with modification of module "Analysis". Some files checked out. He would like to add some SubVIs here. So, he must also perform check out for the project file (*.lvproj), otherwise he cannot add anything into project structure.
Developer B at the same time would like to add some new functions into module "Configuration". He also needed to check out project file, but this file already checked out by Developer A (and locked). So, he must wait until lvproj file will be checked in. Another way is mark *.lvproj files as text files in PushOK, but then one of developers will get conflict message by checking in and then merging will be necessary. This situation will coming very often, because in most cases *.lvproj file will be checked out all the time.
Question: Which practice is better for such situation? Is Libraries better than folder for large project?
Scenario 2:
Developer C joined to the team. First, he must get complete project code for starting (or may be at least code of one Library, which assigned to him).
Question: How it can be done within LabVIEW IDE? Or WinCVS (or other SCC UI) should be used for initial checkout?
Scenario 3:
Developer D is responcible for Build. Developers A,B,C have added lot of files into modules "Analysis", Configuration" and "FileIO". For building he need to get complete code. If our project splitted into folders, he should get latest *.lvproj first, then newly added SubVIs will appear in Project Explorer, then he should expand tree, select all SubVIs and get latest versions for all. If Project organized in Libraries, he must do the same for each library, isn't?.
Question: Is this "normal way", or WinCVS should be used for this way? In WinCVS its possible with two mouseclicks, but I prefer to get all code from CVS within LabVIEW IDE recursively...
That was a long post... So, if you already working with LabVIEW 8 with SCC used for large project, please post your knowledge here about project structure (Folders or Libraries) and best practices, its may be helpful and useful for all of us. Any examples/use cases/links etc are appreciated.
Thank you,
Andrey

Regarding your scenarios:
1. Using your example, let's say both developers checked out version 3
of the project file. Assuming that there are only files under the
directories in the example project, when Developer A checks in his
version of the project, there will be new files in one section of the
project separate from where Developer B is working. Developer B,
notices that there is now a version 4 of the project. He needs to
resolve the changes so will need to merge his changes to the latest
version of project file. Since the project file is a text file, that is
easy to do. Where an issue arrises is that after Developer B checks in
his merged changes, there is a revision 5. When Developer A and B go to
make another change, they get the latest version which will have the
merged changes to the project file but not the referenced files from
both Developer A and B. So when A opens version 5, he sees that he is
missing the files that B checked in and visa versa. Here is where the
developers will needs to manually use the source control client and,
external to LabVIEW, get those new files.
Where libraries help with the above scenario is that the library is a
separate file from the project so changes made to it outside of the
project do not require the project to be modified. So this time, the
developers are using a single project again which time time references
two libraries. The developers check out the libraries, make changes to
the libraries, and then check those changes in. So when each developer
opens the project file, since it references the project file, the
changes to the library will be reflected. There is still the issue of
the new files not automatically coming down when the latest version of
the library is obtained. Again, the developers will needs to manually
use the source control client and, external to LabVIEW, get those new
files. In general, you should take advantage of the the modularity that
libraries provide.
2. As noted in the above scenario, there is no intrinsic mechanism to
get all files referenced by a LabVIEW project. Files that are missing
will be noted. The developer will then have to use the source control
provider's IDE to get the initial contents of the project (or library).
3. See above scenarios.
George M
National Instruments

Source Code Control - Check in problems

Some of my vi's have been marked as "Server copy has changed" and some have even been marked with "both local and server copies have changed". When this is the case I cannot find any way to check in my VI without getting an error. Looking for a work around - help.

kh,
Which version of LabVIEW are you using? Built-in SCC have been rewritten from 6.0 to 6.1 and there are different issues related to each version.
With 6.0 I have encoutered a bug that wrongly checked most of my VIs as "local copy has changed" as soon as they are in memory with panel closed. I worked with NI Support and we found no workaround. Unfortunately, this behavior stayed even when the VIs were upgraded in 6.1 so that my problem was a dead end. I switched with great success to CVS, another source code control software.
I do not use 6.1 but if you do, make a search on NI's site and you'll find hits that address a SCC bug. If I remember correctly, checking out a VI, making a small change and checking it in again often solved the problem.
G
ood luck.
LabVIEW, C'est LabVIEW

How to setup source code control with StarTeam

Hi,
Could anyone please tell me what should I do to set up the source code control?
My company use StarTeam Borland as a source code control tool. I try to set this as a Source Control for Labview by go to SourceControl category ins the Options setup, but I cannot select anything form the list of provider name. Do I have to do any extra step to make it right?
Best regards,
Thang Nguyen
Message Edited by THANG NGUYEN on 08-12-2009 05:23 PM
Attachments:
SourceCodeControl.JPG ‏64 KB

Read this: Source Code Control Provider Does Not Appear In LabVIEW Options. (A simple search would have yielded this.)

Using JMF source codes to build applets........

hi anybody tried to use the source codes to build an applet
that installs/creates JMF registry or its fuctionality on client side make JMF use with no need to install on client side.
if anybody have any idea's abt this please help me...
or please give any references about the same..
thanks

This was announced in November.
Unfortunately after May 1, you’ll need to have a full DPS license or know someone that has one, in order to create or update Single Edition apps.
There are several threads on this topic already. Here's one: The end of DPS Single Edition

Source Code Control for Java development in 6.20

I am new to Java development. How do you control source code (versioning/transport) for Java development with the base R/3 is 6.20. I believe Java Development Infrastructure (JDI) is only available in 6.40. Is this the correct statement? Anyone that has work on 6.40 with Java can explain?
Let say we have this setup:
Applications are in 6.20
Portal will be EP 6.0
Do we need Web AS 6.40 to develop Java for Portal with base R/3 of 6.20. Or we can use Developer Studio to create Java accessing R/3 6.20 and display in Portal 6.0. If this is the case, how do you manage transport is you are not using JDI in 6.40.

Hi Nablan,
I believe you are development J2EE applications. JDI only runs with WebAS 6.40 which supports J2EE spec. 1.3. The developed J2EE archive will not be able to deploy to WebAS 6.20 which only supports J2EE 1.2 spec. So if you want to deploy the created software build from JDI and deploy it to WebAS 6.20, then the answer is unfortunately no.
But, if you just want the Portal be able to display your application in an iView inside, then maybe you can just develop and deploy your application to the WebAS 6.40 system. Then create an iView in your EP to point to the app in the 6.40 system. That way your app will not need to deploy to WebAS 6.20.
Regards,
Marc

Is source version control inluded already?

I've read posts where some guys announced including source version control into SQL Developer. Is it done already?
TIA,
kazelot

We have not yet included this in SQL Developer, but our intention is to do this in our next major release. While we do not yet have a detailed Statement of Direction available, there is a document you can review on OTN.
<p>SQL Developer does offer the ability to add external programs and some users are using this to connect to their source code control systems.
<p>Sue

Dis-advantages of not using Teststand source control feature.

I'm in the process of creating a Workspace file for our project, primarily because we want to use the Teststand Deployment Utility.
Included in this process is the choice to use Teststand's source control features.
So far we have been using Microsoft's Source Safe application directly to provide source control with no problems.
But now, having tried to incorporate Teststand's source control feature, which utilises Source Safe, I find myself getting bogged down in a tedious and time consuming process which I feel will eventually cause more confusion and errors than it prevents.
If we choose not to put the files in Source Control when the Workspace file is created, do we run the risk of problems at a later stage ?
Thanks.

Hi Gary,
there's no "risk" as such, however by not useing some sort of source code control or configuration management, you are making a definite commitment that you will not roll back to a previous version, and you'll be doing your own backups, and making sure that if several people require access to a particular file at the same time, that only one person is going to be allowed (by agreeing to it) to modify the file.
There's nothing that says you have to go through the TestStand sequence editor and the other workspace and projects to do the source code control.
If you prefer, then use Visual Source Safe as a stand alone interface, and check out the files by hand to your local drive, and then work on them, and then check them back in once you're finished.
Of course, you have to make sure that your relative and absolute paths are correct when you do check out the files.
By going through the TestStand sequence editor to check in and check out files, it's more convenient for most people, since they don't have to dive around two environments (TestStand and VSS) to get to the point of being able to modify a file, or even find out if someone else is modifying it.
Hope that helps.
Thanks
Sacha Emery
National Instruments (UK)
// it takes almost no time to rate an answer

Using source code?

Sorry for noob questions, but I'm confused on how to use source code on Flex.
Say I download saqoosha's desktop fireworks -
http://saqoosha.net//?s=fireworks
I ussually just extract the folder into my workspace, go to flex, create a new actionscript project and name it the name of the folder in my workspace. Most of the time this doesnt work, as I dont know how which actionscript file launches the app. Does anyone have an tips for me? And if possible could somone explain how I can use saqooshas source code and launch it through flex.
Thank you so much,
Michael

Try unzipping the folder somewhere else, and using File->Import->Flex Project to bring the project into your workspace, rather than copying directly. Then Flex will figure out what file to run etc for you. I pulled down the fireworks project you mentioned and ran it without issue.

Is there an jdev ARCS (appl. revision control system) extension available ?

Is there an ARCS ( application revision control system ) extension available for Jdeveloper ?
Googling took me to OAF developer guide which said -
"With the ARCS (Applications Revision Control System) Extension for JDeveloper, you can perform most
source control tasks without leaving JDeveloper. For additional information about enabling and using this tool,
see the E-Business Suite Application Development Services ARCS Extension for JDeveloper web page."
Can someone point me where to look for this page ? ( I am in Oracle Intranet, so it is accessible for me even if it is an internal page )
Thanks

Hi,
source code control is through Subversion (recommended). For more read up about Team Productivity Center - http://www.oracle.com/technetwork/developer-tools/tpc/overview/index.html
Frank
Edited by: Frank Nimphius on Aug 18, 2011 11:23 AM

LabView Control System Engineer Job Opening - Seattle

LabView Control System Engineer Job Opening - Seattle
Seattle Safety is looking for a qualified individual to fill an
opening for Software Controls Engineer. Seattle Safety designs,
manufactures, and installs advanced crash test sled systems that are
used in automotive and aeronautical industries. The duties of the
Controls Engineer include:
Maintain existing control software code base, written in LabVIEW (including the Real-Time Module).
Improve existing software based on requirements and requests from customers and colleagues.
Troubleshoot and repair any functional software bugs that may arise.
Continuously investigate opportunities for system improvement through new or alternative hardware or software approaches.
Support installations of crash test equipment at on-site locations worldwide.
Provide technical support for team members locally and abroad
in subject matters concerning performance, installation, and
maintenance of software and data acquisition hardware.
Maintain professional relationships with suppliers and vendors in order to keep up with industry developments.
Furthermore, the ideal candidate would possess the following skills:
Beginner-to-intermediate knowledge of LabVIEW.
Passing understanding of binary logic.
Familiarity with at least one low-level programming language (Assembly, C, COBOL, etc)
Ability to analyze empirical data against theoretical predictions to enhance and improve mathematical model of system.
Familiarity with data acquisition concepts and hardware.
Ability to troubleshoot electrical and electronic systems at the module and equipment level.
Discipline and organization with respect to software
maintenance and version management. Experience with source
configuration management tools a plus (CVS, ClearCase, Perforce, etc.)
Experience with sophisticated high-speed feedback control systems
General skills in areas such as frequency domain analysis,
systems analysis, digital filtering, and both linear and non-linear
signal processing.
BSCS, BSEE, or BSCmpE are preferred but not required depending on experience.
Ability to work both alone and with colleagues to solve problems and to weigh the merits of differing approaches.
Pay is commensurate with skills and qualifications of the applicant.
Contact:
Seattle Safety
John Covey
(253)395-4321
822 3rd Ave S
Kent, WA 98032
[email protected]

Dear Sir / Madam,
I am an experienced engineering professional skilled in Post Silicon Validation by Automating using LabVIEW, Power Measurements, Jitter Measurement & Analysis, Audio Characterizations, Silicon Validation Test Cases, Multi-Channel Data acquisition and Triggering using NI DAQ Cards, Control Systems, Serial Communications using VISA and Serial I/O Interface, Code Native Interfaces, Call Library functions to interface with third party and custom dlls, ATMEL and PIC Micro Controller programming, Temperature Controllers like Honeywell, ESPEC-641, TestEquity 115, Hand held terminal programming to drive servo motors, C/C++/VB Programming for developing embedded applications.
Good experience on Windows API, protocol implementations, ARM11 & ARM7TDMI on-chip programming using Register Map and Pinout Specs using C/C++ Metrowerks Code Warrior and MULTI-ICE for ARM Debugger.
Looking for L1/H1 Job
Thank you for your time and consideration.
Please find an attachment of my resume in MS-Word format.
Sincerely yours,
K.Sowjanya. B.Tech
Message Edited by Support on 04-04-2008 08:39 AM

RE: Using a source code control system

Similar Messages

Maybe you are looking for