Storing versioned images in Store

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Storing versioned images in Store

Rich Demers
Smalltalkers,
 
Somewhere along the line, I remember seeing that non-Smalltalk stuff like images and audio files could be stored, with versioning, in Store, but I couldn't find anything in the VW 7.4 Store document about this.  If it is possible, can someone point me to other documentation, along with info on how to reference such info in Store (possibly in an HTML img tag).  If it is not possible, what are other people doing?
 
Rich Demers
 
"To build good systems, build good subsystems!"
Reply | Threaded
Open this post in threaded view
|

Re: Storing versioned images in Store

James Robertson-3
It's possible, but there's no tool interface (yet).  The release notes
cover how to do it

At 11:16 AM 1/17/2006, you wrote:

>Smalltalkers,
>
>Somewhere along the line, I remember seeing that non-Smalltalk stuff like
>images and audio files could be stored, with versioning, in Store, but I
>couldn't find anything in the VW 7.4 Store document about this.  If it is
>possible, can someone point me to other documentation, along with info on
>how to reference such info in Store (possibly in an HTML img tag).  If it
>is not possible, what are other people doing?
>
>Rich Demers
>
>"To build good systems, build good subsystems!"

Reply | Threaded
Open this post in threaded view
|

Re: Storing versioned images in Store

Charles A. Monteiro-2
which is weird since adding an interface should basically amount to  
popping a Dialog file request, behind a button on the Publish dialog.

A while back I used the following snippet which I found along with some of  
my workspace files. It may be exactly what is in the docs.

workspace snippet:

bundle := Store.Registry bundleNamed: 'OCIT - Dev Preferences'.
file := Dialog requestFileName: 'Which file?'.
bundle addFile: file

----------------------
also it seems that one can only associate files to bundles. Also note you  
may want to not provide the full absolute path as is illustrated above. In  
general a relative path would be the way, this was just expedient for what  
I needed to do at the time.

hth,

-Charles



On Tue, 17 Jan 2006 11:19:25 -0500, James Robertson <[hidden email]>  
wrote:

> It's possible, but there's no tool interface (yet).  The release notes  
> cover how to do it
>
> At 11:16 AM 1/17/2006, you wrote:
>> Smalltalkers,
>>
>> Somewhere along the line, I remember seeing that non-Smalltalk stuff  
>> like images and audio files could be stored, with versioning, in Store,  
>> but I couldn't find anything in the VW 7.4 Store document about this.  
>> If it is possible, can someone point me to other documentation, along  
>> with info on how to reference such info in Store (possibly in an HTML  
>> img tag).  If it is not possible, what are other people doing?
>>
>> Rich Demers
>>
>> "To build good systems, build good subsystems!"



--
Charles A. Monteiro

Reply | Threaded
Open this post in threaded view
|

Re: Storing versioned images in Store

Rich Demers
From a quick reading of bundle #addFile: and the methods it uses, it appears
that only a reference to the file's name is kept in Store, and not the
contents of the file.  Am I right about this?

Rich

----- Original Message -----
From: "Charles A. Monteiro" <[hidden email]>
To: "James Robertson" <[hidden email]>; <[hidden email]>
Sent: Tuesday, January 17, 2006 11:53 AM
Subject: Re: Storing versioned images in Store


> which is weird since adding an interface should basically amount to
> popping a Dialog file request, behind a button on the Publish dialog.
>
> A while back I used the following snippet which I found along with some of
> my workspace files. It may be exactly what is in the docs.
>
> workspace snippet:
>
> bundle := Store.Registry bundleNamed: 'OCIT - Dev Preferences'.
> file := Dialog requestFileName: 'Which file?'.
> bundle addFile: file
>
> ----------------------
> also it seems that one can only associate files to bundles. Also note you
> may want to not provide the full absolute path as is illustrated above. In
> general a relative path would be the way, this was just expedient for what
> I needed to do at the time.
>
> hth,
>
> -Charles
>
>
>
> On Tue, 17 Jan 2006 11:19:25 -0500, James Robertson <[hidden email]>
> wrote:
>
>> It's possible, but there's no tool interface (yet).  The release notes
>> cover how to do it
>>
>> At 11:16 AM 1/17/2006, you wrote:
>>> Smalltalkers,
>>>
>>> Somewhere along the line, I remember seeing that non-Smalltalk stuff
>>> like images and audio files could be stored, with versioning, in Store,
>>> but I couldn't find anything in the VW 7.4 Store document about this.
>>> If it is possible, can someone point me to other documentation, along
>>> with info on how to reference such info in Store (possibly in an HTML
>>> img tag).  If it is not possible, what are other people doing?
>>>
>>> Rich Demers
>>>
>>> "To build good systems, build good subsystems!"
>
>
>
> --
> Charles A. Monteiro
>


Reply | Threaded
Open this post in threaded view
|

Re: Storing versioned images in Store

James Robertson-3
The file is stored.  The nasty thing is that it doesn't create paths as
required - so you have to know about the file paths that it wants to
use.  You can test this by loading the bundle SiltSSPFiles (public
Store).  Create this directory structure first:

source
         css
                 images

and then load the bundle.  You should see all the ssp/css files used by the
blog server.

At 02:05 PM 1/17/2006, you wrote:

> From a quick reading of bundle #addFile: and the methods it uses, it
> appears that only a reference to the file's name is kept in Store, and
> not the contents of the file.  Am I right about this?
>
>Rich
>
>----- Original Message ----- From: "Charles A. Monteiro" <[hidden email]>
>To: "James Robertson" <[hidden email]>; <[hidden email]>
>Sent: Tuesday, January 17, 2006 11:53 AM
>Subject: Re: Storing versioned images in Store
>
>
>>which is weird since adding an interface should basically amount to
>>popping a Dialog file request, behind a button on the Publish dialog.
>>
>>A while back I used the following snippet which I found along with some
>>of my workspace files. It may be exactly what is in the docs.
>>
>>workspace snippet:
>>
>>bundle := Store.Registry bundleNamed: 'OCIT - Dev Preferences'.
>>file := Dialog requestFileName: 'Which file?'.
>>bundle addFile: file
>>
>>----------------------
>>also it seems that one can only associate files to bundles. Also note you
>>may want to not provide the full absolute path as is illustrated above.
>>In general a relative path would be the way, this was just expedient for
>>what I needed to do at the time.
>>
>>hth,
>>
>>-Charles
>>
>>
>>
>>On Tue, 17 Jan 2006 11:19:25 -0500, James Robertson <[hidden email]> wrote:
>>
>>>It's possible, but there's no tool interface (yet).  The release notes
>>>cover how to do it
>>>
>>>At 11:16 AM 1/17/2006, you wrote:
>>>>Smalltalkers,
>>>>
>>>>Somewhere along the line, I remember seeing that non-Smalltalk stuff
>>>>like images and audio files could be stored, with versioning, in Store,
>>>>but I couldn't find anything in the VW 7.4 Store document about this.
>>>>If it is possible, can someone point me to other documentation, along
>>>>with info on how to reference such info in Store (possibly in an HTML
>>>>img tag).  If it is not possible, what are other people doing?
>>>>
>>>>Rich Demers
>>>>
>>>>"To build good systems, build good subsystems!"
>>
>>
>>
>>--
>>Charles A. Monteiro
>

Reply | Threaded
Open this post in threaded view
|

Re: Storing versioned images in Store

Charles A. Monteiro-2
In reply to this post by Rich Demers
incorrect,

the contents of the file are definitely stored in StORE , no pundle  
intended :) , okay that's pretty corny but in the mood today,

the file contents are stored as binary i.e. BLOB, for one I know because I  
have tried it and have pointed to the same repository from different boxes  
and it will download the file, again it will try to recreate the file on  
the path it stored so full paths are generally not good.

-Charles


On Tue, 17 Jan 2006 14:05:28 -0500, Rich Demers <[hidden email]> wrote:

>> From a quick reading of bundle #addFile: and the methods it uses, it  
>> appears
> that only a reference to the file's name is kept in Store, and not the  
> contents of the file.  Am I right about this?
>
> Rich
>
> ----- Original Message ----- From: "Charles A. Monteiro"  
> <[hidden email]>
> To: "James Robertson" <[hidden email]>; <[hidden email]>
> Sent: Tuesday, January 17, 2006 11:53 AM
> Subject: Re: Storing versioned images in Store
>
>
>> which is weird since adding an interface should basically amount to  
>> popping a Dialog file request, behind a button on the Publish dialog.
>>
>> A while back I used the following snippet which I found along with some  
>> of my workspace files. It may be exactly what is in the docs.
>>
>> workspace snippet:
>>
>> bundle := Store.Registry bundleNamed: 'OCIT - Dev Preferences'.
>> file := Dialog requestFileName: 'Which file?'.
>> bundle addFile: file
>>
>> ----------------------
>> also it seems that one can only associate files to bundles. Also note  
>> you may want to not provide the full absolute path as is illustrated  
>> above. In general a relative path would be the way, this was just  
>> expedient for what I needed to do at the time.
>>
>> hth,
>>
>> -Charles
>>
>>
>>
>> On Tue, 17 Jan 2006 11:19:25 -0500, James Robertson <[hidden email]>  
>> wrote:
>>
>>> It's possible, but there's no tool interface (yet).  The release notes  
>>> cover how to do it
>>>
>>> At 11:16 AM 1/17/2006, you wrote:
>>>> Smalltalkers,
>>>>
>>>> Somewhere along the line, I remember seeing that non-Smalltalk stuff  
>>>> like images and audio files could be stored, with versioning, in  
>>>> Store, but I couldn't find anything in the VW 7.4 Store document  
>>>> about this. If it is possible, can someone point me to other  
>>>> documentation, along with info on how to reference such info in Store  
>>>> (possibly in an HTML img tag).  If it is not possible, what are other  
>>>> people doing?
>>>>
>>>> Rich Demers
>>>>
>>>> "To build good systems, build good subsystems!"
>>
>>
>>
>> -- Charles A. Monteiro
>>
>



--
Charles A. Monteiro