Mindomo Desktop (64-bit)

最新版本 install4j 8.0.5

install4j 8.0.5

install4j 8.0.5
Mindomo Desktop  64 位是 Windows PC 的免費思維導圖軟件,它獨特地將離線工作與在線編輯和協作相結合。一個易於使用,獨立的思維導圖軟件,具有高度多樣化的功能。如果您正在尋找完整的思維導圖體驗,Mindomo Desktop 還涵蓋了在線和移動同步。免費思維導圖軟件,可以讓您在本地創建思維導圖和概念圖,並在線上傳以便於共享:Mindomo Desktop  64 位是一款免費的思維導圖軟件。此外,您不需要網絡連接來創建思維導圖和概念圖。您只需一次點擊即可同步您的離線和在線思維導圖。這意味著您可以將您的本地思維導圖上傳到雲端,甚至可以與他人分享。 Mindomo 是一個非常易於使用的思維導圖程序,可以在所有操作系統上運行:Windows,MAC OS X 和 Linux.6235896
Mind 地圖是可以幫助您展示創意思維的畫布。使用 Mindomo 這樣的思維導圖軟件進行頭腦風暴會更有效率,因為您可以快速收集想法,專注於最重要的想法,並拖放它們以創建有意義的聯繫。創建思維導圖是從書籍和文章中保留更多的好方法。當你專注於確定主要想法和它們之間的聯繫時,你正在為你正在閱讀的內容建立一個持久的記憶。 Mindomo 思維導圖是創建項目藍圖的簡單方法。首先定義您的主要目標,然後分出任務優先級,明確指示,利益相關者的反饋和驗證要求。使用思維導圖軟件記筆記是一件容易的事情。

Mindomo 可以幫助您專注於會議的目的,並將議程中的每個項目變成主要分支。隨著會議的進行,您可以輕鬆地將關鍵點(截止日期,KPI,預算等)添加為子分支。軟件創建的思維導圖可以幫助您集思廣益,並將您的事件組織到最小的細節。能夠在一個地方看到一切,從場地選擇到約會和資源,都是無價的。另外,將您的團隊與您保持同一頁面非常容易。思維導圖可以幫助您仔細思考自己的生活,明確自己的目標和挑戰,並標出將帶領您前進的待辦事項。這是你可以用顏色和照片真實地勾畫你的人生目標的地方.

思維導圖是一種簡單的在圖表中繪製信息的技術,而不是用句子寫出來。圖表總是採用樹的基本格式,中間的一個起始點分支出來,並且一次又一次地分割。樹是由用線連接的單詞或短句組成的。連接單詞的線條是意義的一部分。使用鍵盤快捷鍵創建新的氣泡,從預定義的畫廊中選擇地圖主題和圖像,拖放重新排列所有內容,然後將地圖保存在所需的地圖中格式.

概念映射功能
構建具有靈活結構的地圖,連接線上的標籤和主題之間的多個連接.

創建外部線索
創建輪廓從頭開始或從思維導圖視圖切換到大綱視圖只需點擊一下.

任務管理與思維導圖
創建任務地圖來組織和監督你的工作:易於重組任務列表,層次概述,最後期限機制等等.

在線發布地圖
隨著“同步& 保存“功能,您可以在線上傳本地地圖,以方便共享.

完全導入導出功能.
導入導出地圖為 MindManager,Freemind,Mindmeister,XMind,Bubbl.us,PDF,Word,PowerPoint,Text,OPML,MPX,HTML,ZIP, PNG,XLS 文件.

將地圖轉換為演示文稿
使用“演示者”功能展示您的作品,並將您的地圖轉換為演示文稿.

高保真 PDF 導出
將地圖轉換為 PDF 的最高精度.

獨立許可證
一次性購買終身使用無限的地圖和主題,以及 1 年的免費更新和支持.

修改歷史 61213896“查看地圖的變化”將向您顯示思維導圖的創建過程,每一步一次.

搜索網絡圖像和視頻
搜索圖像和視頻在互聯網上,YouTube

ScreenShot

軟體資訊
檔案版本 install4j 8.0.5

檔案名稱 install4j_windows-x64_7_0_12.exe
檔案大小
系統 Windows XP 64 / Vista 64 / Windows 7 64 / Windows 8 64 / Windows 10 64
軟體類型 未分類
作者 Expert Software Applications
官網 https://www.mindomo.com/mind-mapping-software
更新日期 2020-03-16
更新日誌

What's new in this version:

New features:
- In development environments, the API runtime dependency now automatically provides the native libraries that are required by some API calls
- In development environments, the .install4j runtime directory can now be specified with the system property -Dinstall4j.runtimeDir. This allows all API calls to work, including those that require access to the config file, such as Variables.getCompilerVariable(...).
- Multiple timestamp signing services are now tried in the case of a failure. The default is now DigiCert with a fallback to GlobalSign. This can be changed on a per-project basis as explained in the documentation.

Bugs fixed:
- "Download file" action: If the digest file was created with an external tool that produces upper case letters, the check would fail
- "Execute SQL script" action: Regexp delimiters and compound delimiters with a line break like "; " did not work
- "Check for running processes" action: Prevent closing the process dialog with the window close button
- "Set the owner of files and directories" action: Leading and trailing spaces in the "owner" property were not trimmed and lead to an unhelpful error message
- The native log files of Windows installers was not deleted
- Fixed deadlock during auto-save or while saving the project when the floating license server connection was lost
- Fixed memory leak when running in-process installer applications multiple times
- When using the filter text field in the certificate selection dialogs, the wrong certificate was selected
- The check whether modules are used by launchers was not made for merged projects, so a non-modular runtime library could be generated leading to a runtime failure in a merged launcher
- Text mode overrides for bean properties did not work for elevated actions
- Installers could throw an LzmaException for large data files
- Arguments in .vmoptions files were not trimmed on macOS
- API: If a scheduled version has already been installed manually, return false for UpdateChecker.isUpdateScheduled()
- macOS: Command line executables could not use bundled JRE in macos folder archives due to notarization requirements
- macOS: The reported file sizes of notarized media files in updates.xml was wrong
- macOS: Fixed signing Java 9+ JRE bundles for macOS folder archives when the build runs on macOS or Linux
- Windows: The -manual command line option for selecting a JRE did not work as expected when the direct JRE download options was selected for the media file
- Windows: Could not use absolute locations for the Windows JRE search sequence when the build was not performed on a Windows machine
- Windows: PKCS11 code signing for multiple Windows media files could fail
- Linux: systemd service installation did not work correctly with rpm update
- Linux: Build would fail if non-ASCII characters were present in the install4j installation directory
- Linux: KillMode=process is now set in systemd files by default so additional processes started by a service will not be stopped. This is required for update downloaders that are started by a service.
- Linux: Installers running in console or unattended mode on Java 8u242+ throw an exception if no physical fonts are present on the system
- Linux: Menu entries did not work for installations with spaces in path
- Linux: File associations did not work with spaces in the installation path

install4j 8.0.5 相關參考資料