Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.forth > #3578

Re: colorForth markup tags

Show all headers | View raw

On 2011-06-25 20:45:38 +0100, John Passaniti said:

> On Jun 25, 4:35 am, Mark Wills <markrobertwi...@yahoo.co.uk> wrote:
>> I thought colorforth already had an html export function?
> 
> I don't believe so.  I know there is (or at least was) some cumbersome
> process of converting a screen to a PNG image.  Something like insert
> a freshly-formatted DOS floppy, execute some code that put an image on
> the floppy (by writing a hard-coded directory block with fixed
> filename and image file at known, contiguous sectors), remove the
> floppy, load on another machine (real or virtual), copy to a new file,
> and then use it.  See how ColorForth reduces complexity?  By making
> the process of getting code out of that closed system so annoying that
> you never want to leave.
> 
> If there is a way to export ColorForth code as HTML, it likely takes a
> similar process.  And, it is probably unidirectional.
> 
> Quite some time ago, back when ColorForth was first discussed, there
> were two base ideas that were expressed that I thought were crucial to
> understanding it.  They were that color was an obvious but largely
> arbitrary choice to attribute words with.  The second was that
> ColorForth wasn't intended to be a single thing, but a larger message
> (and approach) of empowering programmers to build their own tools from
> the ground up that precisely matched their needs.  So one could
> reasonably expect to see the color in ColorForth replaced with font
> changes or with prefix characters or some other notation.  And that we
> wouldn't all be talking about Charles Moore's ColorForth, but our own
> variations on that theme, each potentially wildly incompatible with
> each other, but each matching our needs and aesthetics.  I think
> ColorForth was and still is a great idea and Charles Moore's model for
> it serves as a valuable reference as a starting point.

Haveing it represented as different fonts in a standard editor would 
IMHO be far easier. But why do that when you can throw away all your 
existing editors, and their macros, and design a custom keyboard that 
dosn't actually map onto the same chars of a standard keyboard and 
needs the chops of an idiot savant to learn it... ;)

Chris

Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

colorForth markup tags Brad <hwfwguy@gmail.com> - 2011-06-23 10:12 -0700
  Re: colorForth markup tags Mux <spam_catcher123@hotmail.com> - 2011-06-23 14:15 -0700
    Re: colorForth markup tags John Passaniti <john.passaniti@gmail.com> - 2011-06-24 16:17 -0700
      Re: colorForth markup tags Brad <hwfwguy@gmail.com> - 2011-06-27 09:53 -0700
  Re: colorForth markup tags Jean-François Michaud <cometaj@comcast.net> - 2011-06-23 15:01 -0700
  Re: colorForth markup tags Albert van der Horst <albert@spenarnc.xs4all.nl> - 2011-06-24 10:23 +0000
  Re: colorForth markup tags Mark Wills <markrobertwills@yahoo.co.uk> - 2011-06-25 01:35 -0700
    Re: colorForth markup tags John Passaniti <john.passaniti@gmail.com> - 2011-06-25 12:45 -0700
      Re: colorForth markup tags Paul Rubin <no.email@nospam.invalid> - 2011-06-25 13:26 -0700
        Re: colorForth markup tags John Passaniti <john.passaniti@gmail.com> - 2011-06-27 07:39 -0700
      Re: colorForth markup tags Chris Hinsley <chris.hinsley@gmail.com> - 2011-06-27 16:24 +0100
  Re: colorForth markup tags Albert van der Horst <albert@spenarnc.xs4all.nl> - 2011-06-25 10:21 +0000

csiph-web