I would like to know if it is possible (and if so how) to add buttons to the SAS Application Toolbar via SAS script.
For instance, I have a button which submits "signoff" via the command line, and would like to distribute this to the rest of the team via our shared autoexec.
Save the catalog that contains your new toolbar items somewhere everyone can get to. In your autoexec create a libname to the folder that contains the saved catalog. Then use this command in the autoexec file (replacing the libname and toolbar name with your specific details):
dm "toolload bar <libname>.profile.<name_of_toolbar>";
Related
Complete newbie here. Built a new site and a new app. Installed the new app. Want to add a custom script, but can't find the ".py" files for the doctypes I created.
The "Custom?" checkbox is left checked and greyed out.
I am logged in as an administrator and I set the site developer_mode config to 1.
(I know I can add custom scripts from the gui, but still, it's sometimes more convenient to work on my own IDE).
Basicaly I want to create a table as a child ("Reciepe") of a doctype ("Dishes"). The table should have a data field (quantity) and a select field (raw_material). I want to populate the raw_material with var_name field from another doctype ("Raw Materials", which also has their prices, thus allowing me to calculate the cost of each dish).
Inside the sites directory, there will be site_config.json file. Ensure developer_mode is present in that file.
$ cat sites/dev.localhost/site_config.json
Clear the cache b running
$ bench clear-cache
After that, go to Browser console and verify developer_mode, user.
If these 2 values are shown correctly in browser console, then Custom? will be unchecked and .py files will be generated.
I followed the tutorial and created the app "library_management". The py-files were created here:
/home/myuser/frappe-bench/apps/library_management/library_management/library_management/doctype
I am trying to make a browse / export button in Access 2003. What I need is a command button that will allow me to browse for any file located on the computer using the standard file open dialog. Once the file has been located, I need a button to export that file to a specific location on a drive (S:\eDNA\admin\eDNA\Engine Data).
What you really want to do is copy a file from your local drive to a network drive, not export it. In order to do that, add this to your code:
Dim fso As Object
Set fso = VBA.CreateObject("Scripting.FileSystemObject")
Then you could use
fso.CopyFile(source, destination[, overwrite] )
You should be able to capture both the source and the destination from the Standard Dialogue forms.
I want to send files to my application without using openfiledialog....lost??
OK.
You select a file in my documents, in the SendTo menu, I want my application to be an option,
when you select my application, the file that was selected should be add to the list box in my application, the same way it would do if I was using openfiledialog. But I want my application to run in the background, which means I don't want to use openfiledialog.
Please help??
Using .NET 3.5
I believe this is what you are looking for. You do not need to write any code to get your app in the 'sendTo' menu. Just following the instructions here:
HowToGeek - Customize 'Send To' menu
once the files / references are being passed to your app, you will have to write code to handle those command line args
I am to create a new design (CSS & HTML) for a web site which is created using Interwoven ContentCenter Professional.
Now, I can see the existing files in CMS (Interwoven) but, I can't make changes. My changes are displayed only when I'm in edit mode. Nothing in the live page. I tried to submit, create editions of files but still no good.
How should I create or edit pages in Interwoven CMS?
Thanks.
If you're talking about generic pages, then once you are finished you have to click on the Generate option, then choose a directory and click Finish. Last thing you should do is to choose yeswhen it asks you to Re-generate the page.
What you are trying to do is just creating a new file, not generating a file from TeamSite's Formpublisher. It is just like if you are in Windows Explorer and creating a new file. In order to generate a file from a form entry, you need to be in the templatedata directory, ex: /default/main/branch1/WORKAREA/wa1/templatedata/category/type(on unix) or Y:/default/main/branch1/WORKAREA/wa1/templatedata/category/type (on Windows). There should be a file call datacapture.cfg there. There is another directory called data under the above path which stores your data content record (dcr) that are created from the form. This is the file that you can use to generate which will use the (tpl) file under the presentation directory.
I need to just translate form error messages in my application.
The application is not multilingual, it is al in Slovak (so I already write labels and stuff in Slovak language), just need to translate error messages.
I have made this method in my bootstrap file:
protected function _initTranslate()
{
$this->translate = new Zend_Translate('gettext',
'/path/to/translation/source-sk.mo',
'sk');
Zend_Form::setDefaultTranslator($this->translate);
}
But how to create the source-sk.mo file? Do I need to download it somewhere from the Web?
First you will need to download the PoEdit software and then you will need to configure it according to this post.
Once you have completed those steps, you will need to create a new catalog file from within PoEdit. In the creation dialog, click on the keywords tab, and then add function names that you wish to scan for in your code. With Zend Framework, this is typically just translate since you are probably using the translate() view helper. However you will want to also include setLabel so that it pulls your Zend_Form labels as well.
After you have created your catalog, you will need to scan your source code for translations. You do this by clicking Update from Sources under the Catalog menu. Once it has completed scanning your source code, it will display a list of all strings that need to be translated. You then go down the list and enter in the translation for each string. Now save the catalog to somewhere within your ZF application, preferably /languages, point your Zend_Translate declaration to this location and you are good to go.
If you adjust any labels or strings later on, you can always reopen the catalog with PoEdit, run Update from Sources again and it will pull all of the new changes for you to translate.