Jean, see my latest posting to the list. Personally, I don't relate to the idea of workflows very much. Yes, sometimes you repeatedly do sequences of steps, as in Git commits. But much of the time knowledge work requires inventing new ways of working or extending old ones, so I focus on core capabilities that people can use in creative ways as they see fit, in the same way all of Emacs' core capabilities provide this same freedom.
You used the example of handling calls. For one call, you might look up a contact, follow a URL reference, add a note with an implicit button, alter the information on your screen and send an email. Hyperbole's toolkit nature can help you in all of these respects but there is no definable workflow in such a context, you have to create it from mastering a set of primitives. Hyperbole simplifies this process by keeping the number of concepts relatively small and making the computer do the hard work. On Tue, Aug 6, 2019 at 12:20 AM Robert Weiner <[email protected]> wrote: > On Mon, Aug 5, 2019 at 8:19 PM Jean Louis <[email protected]> wrote > >> >> Hyperbole is missing more examples. >> >> One good example is MANIFEST file > > > You mean the examples provided in the DEMO and the MANIFEST file itself > are good, correct? > >> But it misses more textual examples >> with hyperlinking. >> >> I have understood the concept that I could write just any text with >> hyperlinks. Am I right? If that is so, there shall be various examples >> of such text files. If you have any text file with real world example, >> show me > > > Have you run through the DEMO file. There are extensive examples of > implicit button type usage in there. You may be more interested in > creating your own implicit button types though and for that there is only > the code right now. We have not written a Hyperbole programming manual. > But the examples provided by the code in hibtypes.el and hactypes.el are > quite good. > > In the forthcoming release, all of Org mode's link types are also > supported by the Hyperbole Action Key, so you'll be able to activate them > as well in Org major or minor modes. We could make them work in other > modes but haven't thought much about that yet. > >> .I think that Hyperbole button linking or hyperlinking could be well >> suited for workflow assignments. It could be used in training staff >> members. >> > > Yes. > >> >> For example: >> >> On Monday go over all <(people to follow up)>[1] and send them emails >> reminders. Monday evening conduct the <(database maintenance)>[2]. >> > > Explicit buttons as you have shown hide their arguments, so only the label > is visible. implicit buttons show their arguments in the buffer but > presently don't have separate labels (until the next release). Global > buttons don't show anything on screen; they are activated with a prompt > where you type in a button name. > > So you have all of those capabilities at your disposal when building > hypertexts. All of Org modes references for example can be wrapped as > implicit buttons under Hyperbole. > >> The difference between the HTML and this way of linking to actions is that >> Hyperbole is within programming environment Emacs and it would allow easy >> applications to be run. Same would be much more complex if done through >> websites >> > > Right and there is no comparison between having to write HTML or dragging > from a source to a destination to create a hyperlink. > >> and there would be data and privacy concerns. Distribution of instruction >> and >> training files together with Emacs Lisp functions would be enough for a >> remote >> person to start learning the workflows and execute assignments in ordered >> manner. >> > > Yes. > >> >> Thus I would like to see more example of how other people are doing it. >> >> > I guess we need to get more people discussing applications of Hyperbole. > > I have built indexed document repositories that can be referenced easily > within email or other text. See hib-doc-id.el. > > The git/gitlab/github references in hib-social.el greatly simplify > creating hypertexts around git artifacts. > > Since I need to test normal installations of Hyperbole before release but > also want to ensure when I follow hyperlinks in the code that I always go > to my git source directory rather than the installed version of the code, I > wrote an implicit button type that forces Hyperbole's code identifier > lookups to always go to the latest source files. > > The possibilities are pretty limitless with the strong Elisp foundation > from which to build. > > Bob > > >> Footnotes: >> [1] It would jump to the database list of people to quickly contact them >> with a >> short reminder and follow up with them. >> >> [2] It would go to different Hyperbole file where one could click links >> to >> conduct database maintenance including the personal human review of >> it. >> >> [3] It would give list of necessary information to collect, for example >> "How >> did we find about this person? " -- is something staff members often >> forget >> to tell, did person arrive by website? Or by acquaintance, or by >> flyer, >> poster, fax, friend, how? Title and position of person and similar. >> It >> would be file with instructions. >> >> [4] This could be set of multiple files that are opened for staff member. >> >> [5] This could be small application to fill the repetitive fields for >> the daily >> report. >> >> [6] This would be mostly numbers entered for personal statistics, which >> differ >> so much from one staff member to other. >> >> [7] Particular poster version. >> >> [8] This would be a patter of sales speech. >> >>
