[squeak-dev] Files documentation

Mariano Martinez Peck wrote:
> Hi list!
>
> I need to do some things with files (text and binaries), and I would
> need information about creating, deleting, adding, appending, writting
> and so on with them. I look in SBE but I didn't find a chapter about that.
>
> Is somewhere documentation about this?
>
> thanks,
>
> Mariano

The built in File handling is not very elegent, enter, "Rio" File/Drectory

Installer squeaksource project: 'Rio'; install: 'File-Kernel'; install:
'File-Base'.

(and File-Tests for examples)

see also http://wiki.squeak.org/squeak/5929

if you like it, then perhaps you would be kind enough to offer some feedback

best regards

Keith

=========
Class comment from File reads:

Features of File/Directory (née Rio)

File/Directory was inspired by ruby's rio which enables local and remote
files to be used transparently. To achieve this a generic stream copy
function has been developed (aStream copyTo: bStream) and we are able to
expose the working stream of FtpClient so you can stream directly to a
remote file. We also support file archives (zip) as if they were a
filesystem, and transparent streaming to compressed files (gzip).
[transparent streaming to a remote compressed file is still available as
a exercise for the reader to implement ;) ]

File/Directory is a standalone package, it does not use any of the
existing FileDirectory classes. It is separated into File-Kernel and
File-Base, where the former provides a minimal working subset for
KernelImages to access local filesystems.

Local file copying is handled by the fileCopyPlugin if it is present, if
not OSProcess 'cp' is used, and as a last resort a full stream to stream
copyTo: is performed (but this does update modification time).

Remote file upload or download is handled by OSProcess 'ftp' if it is
present. Multiple file transfers are invoked N at a time (where N is
initially 5). Copying from a remote file to another remote file is
handled by the internal stream copy function.

Mariano Martinez Peck wrote:
> David and Keith: Thanks you for your reply.
>
> I will see and try to use RIO. However, what I need to do is very
> simple. I have already add log to SqueakDBX. Till now, the log just
> print in Transcript. The problem is that sometimes I get a
> segmentation fault and I cannot see transcript any more haha. So, I
> would like to be able to log into a log file.
>
> If I think I could give some useful feedback be sure I will let you know.
>
> cheers,
>
> Mariano

Ah! Logging! Why didnt you say so.

We would like to move Squeak to use some form of proper logging
interface, rather than blindly throwing stuff at transcript show. (which
is not thread safe)

The current proposal is "Logging". (Installer install: 'Logging') This
provides a front end to the users choice of available logging
frameworks. Toothpick, and SimpleLog are currently supported.

Documentation: http://installer.pbwiki.com/Logging

regards

Keith

Mariano Martinez Peck wrote:
> Keith: hahahah. I know there was a "Logging" project, but as there
> were few places where to log, I decided to do it by hand. Do you think
> it should be better to do it with it altought I have few places to log ?
>

Definitely.

That is exactly what Logging is there for, so that people are encouraged
to put the log code in their packages without worrying about how the
actual logging is done, timestamped etc. You can let the user choose how
the output is provided/used/managed (e.g. SimpleLog does log file
rotation). The default backend is simply a Null instance (it
should/could be a minimal Transcript Log equivalent to Transcript show:)

There are also utilities for timing events, so you could start a timer
when you send a query and print it when you get the result.

> Just by curious, is Logging something like log4j (sorry, but that's
> what I know :( ?
>
> does Logging use RIO for files ?
>
> thanks,
>
> Mariano

If you load "SimpleLog" (from the gjallar team) this uses Syslog,
transcript, LogMorph or files (not rio, just a basic filestream)

Keith

Hi!

Mariano Martinez Peck wrote:

ok. If you say so, I will try it as soon as I have time and I will let you know my feedback and any question I have with it.

I recommend (of course) using "SimpleLog", and optionally with the
"Logging" frontend from Keith.

SimpleLog was developed in the Gjallar project and it has the following
goodness:

- Simple. :)
- Uses the standard syslog levels.
- Has a UDP based syslog backend. Fast and very useful.
- Has a Morphic viewer which is quite nice and has filtering abilities.
- Has log file rotation.
- Can still log to Transcript but it is protected by a mutex.

If you need to use external monitoring/alarm tools and/or suddenly need
to deploy an app "clustered" then the syslog backend is very nice to
have. Otherwise you end up with one log file per "clustered image" which
is not so nice.

If you use the "Logging" frontend (which I haven't used myself) then you
of course have options to choose backends.

regards, Göran

Hello All,

I need a villainous superpower that I haven't needed before, can anyone
tell me how to achieve this.

I have some code like this:

self send a message to me.
self nextThing.

or

self send a message to me.
A := self nextThing.

What naughty superpower code can I put in to #send that will jump
execution to self nextThing directly?