bert at freudenbergs.de
Thu Sep 11 16:17:39 EDT 2008
IIUC the activity would not deal with files but with journal entries.
So you can copy several journal entries into a zipped entry, and you
can unzip entries from a zipped one. This has nothing to do with files
in the home directory (besides, a regular activity cannot write to
home, and read only some of it).
- Bert -
Am 11.09.2008 um 22:12 schrieb Erik Garrison:
> "Bundles" are files. In this case they are compressed files. I'm
> pointing out that if we're going to work with files of this kind we
> should think about working with files of the non-compressed kind.
> The overlap between the Bundle tool and a tool to allow the same
> operations on uncompressed files is pretty large. Note that bundle
> management is usually dealt with in other desktop environments through
> the file browser.
> On Thu, Sep 11, 2008 at 03:57:12PM -0400, Eben Eliason wrote:
>> That's not within the scope of this activity, no. This activity is
>> strictly about viewing and creating bundles.
>> - Eben
>> On Thu, Sep 11, 2008 at 3:01 PM, Erik Garrison <erik at laptop.org>
>>> Would this activity be modified easily to take files from within the
>>> Journal and move them back into the user's /home/, either
>>> compressed or
>>> uncompressed? Call it the File activity.
>>> On Wed, Sep 10, 2008 at 12:49:03AM -0400, Matt Der wrote:
>>>> Hello all,
>>>> I am one of the students who will be working on the Bundle activity
>>>> suggested by Eben Eliason. I understand that the activity should
>>>> designed to manage a variety of archive formats (zip, tar, gz,
>>>> etc.), and it
>>>> should support both the extraction of files from an archive into
>>>> the Journal
>>>> as well as linking a set of entries from the Journal into a
>>>> bundle. Also, I
>>>> see a few additional details are provided in its wiki [
>>>> Is this an active project right now? If not, our team would like
>>>> to start
>>>> working on it soon, but first we are looking for feedback on
>>>> how it should integrate with the Journal, UI particulars, etc.
>>>> If this project is not currently active, we are eager to hear any
>>>> input you might have.
More information about the Devel