Revit Journal Maker
python libray for writing/reading journal files for Autodesk Revit
Writing Journals
import rjm
journal_maker = rjm.JournalMaker(permissive=True)
# creating a new model (template_name is optional)
journal_maker.new_model(template_name='My Template')
# creating a new template model (template_name is optional)
journal_maker.new_template(template_name='My Template for Templates')
# creating other types
journal_maker.new_family(base_rft_file)
journal_maker.new_conceptual_mass(base_rft_file)
journal_maker.new_titleblock(base_rft_file)
journal_maker.new_annotation(base_rft_file)
# opening workshared model
journal_maker.open_workshared_model(model_full_path,
central=False,
detached=True,
keep_worksets=True,
audit=False,
show_workset_config=1)
# opening non-workshared model
journal_maker.open_model(model_full_path)
# ignore missing links
journal_maker.ignore_missing_links()
# add custom entry to journal
journal_maker.add_custom_entry(journal_entry)
# execute an addon command
cmdata = {} # dict of data to be passed to command in journal
journal_maker.execute_command(tab_name='Add-Ins',
panel_name='Panel Name',
command_module='Addon Application Namespace',
command_class='Command Classname',
command_data=cmdata)
# execute dynamo definition
journal_maker.execute_dynamo_definition(definition_path='C:/testdef.dyn',
show_ui=True,
shutdown=True)
# load a family
journal_maker.import_family(RFA_file_path)
# ask journal to export warnings using Revit UI
journal_maker.export_warnings(export_filepath)
# ask journal to purge unused warnings using Revit UI
journal_maker.purge_unused(pass_count=3)
# sync central model
journal_maker.sync_model(comment='comment string',
compact_central=True,
release_borrowed=True,
release_workset=True,
save_local=False)
# saving non-workshared model
journal_maker.save_model()
# closing model
journal_maker.close_model()
# finally
journal_maker.write_journal(journal_filepath)
Reading Journals
Under Development
import rjm
journal_reader = rjm.JournalReader(active_journal_file)
# checking to see if the journal has crashed and stopped
journal_reader.is_stopped()
Metadata
Release files for rjm 1.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| rjm-1.4.0.tar.gz | 18.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rjm-1.4.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 28.8 kB
Release files / rjm-1.4.0.tar.gz
| Download URL | rjm-1.4.0.tar.gz |
|---|---|
| Size | 18.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0abbff2c86e188d4e1089a76de11fd808138b7754406dfc5329a75e08f938512
|
|
BLAKE2b-256 checksum How to use checksums |
9a913eab8115a5eb1a719685b41f2deb7bdda293aed4da60d1356db41a64e394
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.24.0
|
Release files / rjm-1.4.0-py2.py3-none-any.whl
| Download URL | rjm-1.4.0-py2.py3-none-any.whl |
|---|---|
| Size | 10.3 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
ba2d70293a1fd7e531ad606cecdba6e045585a9792b44709ec32a03cc3ebc6bc
|
|
BLAKE2b-256 checksum How to use checksums |
4bb1d8433975c8e24b6262fcf1fc7a9c1399a90963310b99091b71ea922c7bf6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.24.0
|
Security for rjm 1.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.