We are using clearcase as our SCM. I have not much experience with clearcase. Now we are about to release our code to production. I want to label my code as I have done using VSS in my previous projects. But in clearcase labeling is not as easy as in VSS. clearcase is asking to create a label type before label a folder in VOB. I don't understand the concept of creating label type? Any guidance on this will be highly appreciated.
a lbtype is a template, a declaration.
a label is the instance that will be put on each versions needed to be labeled.
See mklbtype
The mklbtype command creates one or more label types with the specified names for future use within a VOB.
After creating a label type in a VOB, you can attach labels of that type to versions of that VOB's elements, using mklabel.
You also can attach a constraint on a lbtype:
By default, a new label type is constrained to use on only one version in an element's entire version tree.
This allows you to omit the branch path name portion of a version-extended path name (for example, foo.c##/JOHN_TMP)
Once you have define a lbtype, you can apply (mklabel) it to any file or group of files you want in your current view.
That means you have a view configured to select the LATEST of a branch, and at a given time, you apply this label:
cd /myView/myVob/myGroupOfFile
cleartool mklabel -nc -r MY_LABEL-1.0 .
Note: the name of the lbtype (and the labels set from this lbtype) is entirely up to you. You can set a label FOO, BAR or any other names. Conversely, you can set a label MY_LABEL-2.0, then set a label MY_LABEL-1.2 (not wise, but...).
If you want to see what exact versions are referenced by a previous existing label like MY_LABEL-1.0, you create another (dynamic) view that you set to see this label.
The following config spec ("configuration specifications", aka "selection rules" for versions) will achieve just that:
element * MY_LABEL-1.0
element * /main/LATEST
The second selection rule is called "stop rule" because it allows for all versions to "fall back" to this default rule: if no version (for a given file) is labeled MY_LABEL-1.0, then it will always stop at the "/main/LATEST" rule, to select the LATEST version of the branch main.
For those "consultation" view (i.e. "view that are only used to see versions of files"), I recommend dynamic view, for a quick access to those fixed versions.
If you now want to see the 2.0 label, simply modify the config spec of this view. Or create another view, in order to see both 1.0 (in the first view) and 2.0 (in this second new view)
Related
I resorted to using option html_sidebars template globaltoc.html to get a multi-level menu tree something as this:
1. Execution
1.1. Activities
1.1.1. Report
1.1.2. Follow up
By creating source files (.rst), I am able to build up the above scenario. On clicking the parent node Execution, the sub-nodes below all expand simultaneously. Later I added two more files, designed to be added at the end of last node. So the new menu tree looks like this:
1. Execution
1.1. Activities
1.1.1. Report
1.1.2. Follow up
1.1.3. Escalation
1.1.4. Final Submission
Now something peculiar is happening. When the top node Execution is clicked all the sub-nodes, including the newly added ones (1.1.3 and 1.1.4), expand at the same time (as I think they should be doing). However, when one of the older nodes, say, 1.1.1. Report is clicked, the new nodes 1.1.3 and 1.1.4 collapse. And to open the the new pages, I have to click on the top node 1. Execution to make the newer nodes visible again (so that these may be clicked to navigate to the doc).
I have run make clean html but situation has remained to same.
My question is: Am I correct in using globaltoc.html to build a collapsible menu tree in the sidebar. And if yes, what should be done to get the behavior (collapse/expand) right.
See the -a sphinx-build option.
If given, always write all output files. The default is to only write output files for new and changed source files. (This may not apply to all builders.)
Alternatively make clean, then make html would have the same result.
I created check box with ON and OFF option. When click on "ON" option then image show. I want to when click on "OFF" option then image remove or image filed empty
How to achieve this target in oracle forms 10g?
I don't think you can do this.
As someone suggested it, you could have thought using SET_ITEM_INSTANCE_PROPERTY (this one only applies to the current record). However, you cannot modify all the properties, only few of them : BORDER_BEVEL, INSERT_ALLOWED, NAVIGABLE, REQUIRED, UPDATE_ALLOWED and VISUAL_ATTRIBUTE.
Check the documentation of this method here (Oracle Forms v6i) : https://docs.oracle.com/cd/A97335_02/apps.102/a73074.pdf
One of the best solution you may find should be to make a custom Java Bean item which would handle this behavior. However be careful, Java Beans don't work correctly when used in a multi-records blocks. If your checkbox is used within a single-record block, it should be OK.
Here are some of my references to create your own Java Beans :
http://devtalks.blogspot.com/2008/07/creating-and-using-java-beans-in-oracle.html
http://forms.pjc.bean.over-blog.com/
https://www.baigzeeshan.com/2010/02/how-to-add-java-bean-by-writing-your.html
How can the user interface of an imperia 9 CMS be changed without
loosing the changes with the next update or hotfix?
There is a rather safe way to do it.
Say C:/imperia/dev/ is the path of your imperia development system,
then you find the imperia default views
in C:/imperia/dev/site/view/imperia. You can create your
own views in a directory next to it C:/imperia/dev/site/view/mycustomviews.
Now copy a view from the /view/imperia tree to your
/view/mycustomviews tree, keeping the structure and filename and change the content to your needs.
To let imperia know how to find your views, you have to define your your view-template directory
in the system configuration file system.conf.
"VIEW_TEMPLATE_DIRS" = "C:/imperia/dev/site/view/siau/mycustomviews"
updates
This way is rather safe, because you do not change your default. That's important. Don't touch
the files in C:/imperia/dev/site/view/imperia. You may loose your changes with
the next update.
But you should know that you may do not participate in fixes or changes concering this view. Let's think of a
optimization to the default view (may be to the behavior in a current browser). With your own view you overlay
the default and you do not get the changes in your GUI.
development
While developing your new views you should add the following lines to your system.conf:
"IMPVIEW_ERRORS" = "HTML,JS,STDERR"
"IMPVIEW_DEVTOOLS" = "1"
"IMPVIEW_CACHE_POLICY" = "timestamp"
With IMPVIEW_ERRORS you can controll where the view errors are displayed.
IMPVIEW_DEVTOOLS adds some develop methods to your views (e.g. dump).
And with IMPVIEW_CACHE_POLICY set to timestamp your views will no longer be cached. Thats great
for development, but you should remove it for productive usage. (The other two as well.)
If something went wrong and you get unecpected results comment the VIEW_TEMPLATE_DIRS line. Then you
get back the default views and you can try to reproduce the problem.
I have an application that can load in third party code. One of the capabilities that the third party code can do is add formats in which the app can export to. I am using saveDocumentTo: as means for implementing export.
I understand that I can customize the menu of available filetypes to save in via overriding writableTypesForSaveOperation: for my document, but what doesn't work is that in the save dialog an appropriate file extension isn't added to the filename when selected from the menu.
I tried overriding fileNameExtensionForType:saveOperation: but that doesn't even get called.
How can I make the Save dialog find the correct file extension (provided it isn't known at compile time)?
I've done this within a custom export accessory view for the Save Panel. The custom export accessory view just changes the NSSavePanel's allowed file types whenever the user changes the format they want to export to.
If you want to set the extension, pass an array with one element containing that extension.
The docs have some important detail for -[NSSavePanel setAllowedFileTypes:]'s behavior in this regard, for supporting more complex cases:
Discussion
A file type can be a common file extension, or a UTI. A nil value indicates that any file type can be used. The default value is nil.
If no extension is given by the user, the first item in the allowedFileTypes will be used as the extension for the save panel. If the user specifies a type not in the array, and allowsOtherFileTypes is YES, they will be presented with another dialog when prompted to save.
NSOpenPanel: In versions of Mac OS X less than v10.6, this property is ignored. For applications that link against v10.6 and higher, this property determines which files should be enabled in the open panel. Using the deprecated methods to show the open panel (the ones that take a types: parameter) will overwrite this value, and should not be used. The allowed file types can be changed while the panel is running (for example, from an accessory view). The file type can be a common file extension, or a UTI. This is also known as the “enabled file types.” A nil value indicates that all files should be enabled.
You may also see dedicated export dialogs in some cases which can reduce the complexity of this if you have several distinct formats. As before, you just update the allowed file types to support this (not necessarily dynamically in this case).
After tinkering and modifying a GUI I have been working on for some time I ended up with a group of EditControllers and Radio Buttons that I do not need any more, so I would like to get rid of them. However, if I simply delete them from the GUI edit, I get assertion errors. How am I supposed to get rid of these elements?
You need to remove all code from your program that refers to the deleted controls. For each control you want to delete, take its ID and search the source for statements that refer to it.
Start like this:
Check the ID of that given control. Copy it. Now remove the control from dialog resource.
Ensure that ID is not used by other dialogs. If not, you can use following.
Delete that ID from resource.h.
When you compile it, you'd get error (around GetDlgItem, DDX_Control etc). Remove or comment them. Remove appropriate CWnd-derived variables (like CEdit, CComboBox etc).
You are done!
If given ID is used by other dialogs (check it from Resource View's context menu Resource Symbols...), then you cannot directly remove it from resource editor. You, however, need to remove it from appropriate implementation file (of CDialog/CPropertyPage-derived class).