name mode size
.Installers 040000
0000-Config 040000
Choose Which App Handles VUE Web Urls 040000
Console Commands 040000
Etc 040000
Libraries 040000
Make Folder of Symlinks to Vuemaps 040000
Mapmakers 040000
Named Thumbnail Maker 040000
Recover from Keyboard-Disabling Glitches 040000
Resize Images 040000
Resize and Rotate Images 040000
Test Maps 040000
VUE Launchers 040000
test runners 040000
tests 040000
.gitignore 100644 177B
Beam Test Maps to apmaps 100644 335B
Detailed diffize Test Maps 100644 334B
Diffize Test Maps 100644 325B
Go to Test Maps 100755 49B
Go to apbin copy 100755 79B
Go to private mapmakers 100755 124B
Go to vuerbs vuemaps 100755 89B
Go to workspace copy 100755 84B
LICENSE-AGPL 3 100644 34.52kB 100644 7.64kB
Update apbin copy 100644 278B
# VUE-Related Bash Scripts by Apollia - []( These work in Lighthouse 64 Puppy Linux 6.02 Beta 2. []( Might have to be modified to work properly in other [GNU/Linuxes]( ---- [VUE: Visual Understanding Environment]( is a wonderful [concept mapping]( program which I use very frequently for most of my notes. <br> I made these VUE-Related Bash Scripts to easily: <br>* Create new concept map files using whatever templates I want. And usually I like to create sets of maps, so most every map I create has its own associated scraps maps where I can paste anything from my main map that I want to put aside without deleting entirely. <br>* Create specialized sets of maps all at once, such as my Crystal/Log/Moss/Timeline sets, and [Logical Thinking Process]( logic tree maps. (However, so far, I didn't make any fancy special templates for these map types.) * A **Log** map is where I put whatever thoughts, observations, URLs, pasted text, etc. I want on the map's topic or task in chronological order of when I thought of or found them, without trying to organize them. * A **Crystal** map is where I try to [crystallize]( (or [distill]( all the best info and present it in a more organized, clear, less chaotic and less repetitious way than the log map. That's more work than my log and moss maps where my standards are far more relaxed, so I mostly have been adding to my log and moss maps, especially when dealing with topics or tasks where I'm not at all certain or clear on the answers yet. * A **Moss** map is a more wild, freely-growing map which doesn't have to be in any particular order. A good place to work on drafty new stuff which isn't polished or definitive enough to go in a Crystal map (yet). I finally realized I needed Moss maps when I kept putting somewhat incomplete stuff in Crystal maps, for lack of anywhere more appropriate to put it. Why the name "Moss"? Because it matches the theme of the name "Log" - both logs and moss can easily be found in forests. And crystals somewhat fit into the forest theme too, even though they'd generally be a much rarer thing to find there. And I love moss's beautiful green color. []( And the word "Moss" is short and doesn't take up much space in my VUE tabs. * A **Timeline** map is like a combination of a Log and a Crystal - all the best info presented in chronological order alongside a long line, with dates on one side, and things associated with those dates on the other side. <br>* Archive ("pastize") old map files, and replace ("freshize") them with a fresh, new, mostly empty template. <br>* Convert images of any size to a standard small size, suitable for my maps. The image scripts require ImageMagick: []( <br>* Create symlinks or hard links to all of the maps I have in my maps folder. Then, I can easily drag and drop all those links into a VUE map, and open any of my VUE maps easily. **WARNING**: Currently (April 21, 2019), VUE gets confused by both hardlinks and symlinks, so when you save your map, VUE will overwrite the link, instead of saving to the map's real location. <br>* **New as of April 21, 2019!:** Run [Salty XML Transformer]( on new maps to transform them, possibly quite drastically, with [XSLT]( 1.0, 2.0, or 3.0. Requires [Saxon/C](, [PHP](, and [Salty XML Transformer]( The way I install those (among many other programs) is by installing APSK GLMP-GTK, which currently isn't available to download, but my notes on how I built APSK GLMP-GTK are in this repo: []( <br>That repo also contains my temporary, "macgyvery" installer scripts which I've been using to set up APSK (Apollia's Puppy Linux Setup Kit) - including APSK GLMP-GTK - since I haven't yet finished renovating APSK. I call them my "macgyvery" installers because they were hastily improvised rather than slowly and ponderously designed, yet they still get their jobs done quickly and effectively. Sort of reminiscent of the TV character MacGyver, a show I don't think I ever watched an entire episode of. But I did see the MacGyver parody movie MacGruber. :-) My vuemap "Misc/APSK Journal.vue" contains many buttons which make it easy to run all my macgyvery installers - however, they definitely won't all work, unless you have all the files I have at the filepaths they're expected to be at. And because my macgyvery scripts were only meant as a temporary solution to my problem of APSK not being fully renovated yet - I haven't yet made all of the required files available to download, nor devised adequate partially automated ways for people to download the required files and compile various binary programs themselves on their own systems. <br>But hopefully, the fact that I can now relatively easily use XSLT to transform my vuemaps will somehow result in things that will make it much easier to complete the renovation of [APSK (Apollia's Puppy Linux Setup Kit)](, among many other projects. Perhaps now I can finally build some simple [visual programming systems]( using VUE and XSLT, as I've been daydreaming about for years now. []( Maybe some of my experiments will even qualify as forms of [literate programming]( <br>------------------------------------------------------------------------------ Under the GNU Affero General Public License v3.0. Copyright (C) 2017-2019 Apollia This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more details. You should have received a copy of the GNU Affero General Public License along with this program. If not, see <[](>. Contact info: [](