Mailing List Archive: 49091 messages
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search

[REBOL] Re: How to print a document

From: petr:krenzelok:trz:cz at: 12-Jun-2001 21:16

----- Original Message ----- From: "Holger Kruse" <[holger--rebol--com]> To: <[rebol-list--rebol--com]> Sent: Tuesday, June 12, 2001 6:28 PM Subject: [REBOL] Re: How to print a document
> On Tue, Jun 12, 2001 at 10:44:23AM +0200, Petr Krenzelok wrote: > > Hi, > > > > so, I know how do you feel. I complained the same some time ago here.
> > helped, as RT told us there is no easy multiplatform solution to
printing. But
> > message to RT - who cares? ;-): > > Sigh...
Although I don't know what "sigh" means, I seem to upset you? :-)
> Petr, I wish you would not always take the REBOL feature set so > personally.
And that's the question. I have probably slight problem in what I say and what do I feel. I feel currently no angry towards anything RT does. And in real (howdy Jeff :-) I already stated that I feel VERY comfort with direction RT took in last two or three months ... Holger - at the end of my message I offered solution - use html output ...
> We get a LOT of requests. Some of them make sense, others don't. > Some are easy to implement, others are not. Some have cross-platform > issues, others don't. Our time is limited and just because your favorite > feature does not make it into the next release does not mean we are
> the request or ignoring you. Please be patient.
Ah, that's not about some kind of "my" feature - I remember earlier discussions re printing and I do also remember Carl's word in /Express conference - offered solution was - there will be no direct printing support, use .html. So I tried to offer the view, showing that even in current versions of Rebol, there are some multiplatform issues (e.g. not all features supported by BeOS or Elate as mentioned in docs ...)
> You still need to catch any errors in 'insert though because it is > possible for a sound to be incompatible with a sound card or driver, > or for the sound hardware driver to be busy.
I can understand this one ...
> > I don't understand why it is not solved > > the save way as security box dialog - it just asks for persmission. > > Because it is not a permission issue. It is an issue of being ABLE to > do something or not (which is determined by the system setup), not of > being ALLOWED to do something (which is controlled by the user).
but that's exactly something I wanted to argue upon. Being able to throw ('insert) something into the port is something which belongs to script level.What is more strange is being unable to open sound port only because someone does not use unlocked version. I thought that in such case, we should not push ppl to take care in the script level. That's why I mentioned security dialog - it was meant just as an example. I thought that user would be notified in the beginning that he/she doesn't use unlocked version, but nothing more. Sound system is - or is not available, "sigh" :-) Why should we put special conditions in our source code because of normal vs /Pro version?
> > Maybe it > > could be solved that way too? If I don't have sound card in my comp,
apps using
> > sound capabilities don't probably require special versions :-) > > They don't. App writers need to decide which versions of REBOL they want
> support. If you want to run in less functional environments you need to be > prepared to handle that.
See above - we are not talking less functional environments here. Not from OS side of view at least ...
> Sound is no different than any other non-Core feature, > such as encryption, HTTPS, database support etc.
... maybe you are right here, above mentioned features are mostly special features of Command, and will not probably be used in demos, daily user/hobby tasks, etc.
> > I hope that once component system evolves further, these issues will get > > resolved ... > > It is not an issue of components but of run-time errors. There is no way > you can catch ALL possible run-time incompatibilities and errors just by > declaration. Some errors cannot be predicted and can only be detected when > a feature is used. For instance in Unix you often do not have mixers (or
> are not configured or enabled), so you have to deal with the possibility
> SOME sounds cannot be played if at the time the sound is played the
> is used by another program. Windows does not have that problem.
Why there is not one and only OS, perfect one, which would solve everything? Time for RT to bring us one :-) -pekr-