Hello, Thanks fro the replies.
I think my first question was a little fuzzy. I think what I need to do as change the question.
If for example I have a seaside web app and users need to create an account. Now, for each user I create an object, say an instance of class Users, which has instance variables such as name and address. So the new user puts in their detail such as name, address, telephone number and then click register. How should (not what) the system name this object. What I'm confused about is I don't know how may users the system will have have do I name all the user object; I can't call them all aUser . If the first user gets an object named user1 how do I create another instance of User named user2 or What about If I want to use one of the input field as part of the name of the object?
The example below may make it clear what I mean
10 timesRepeat: [ x := 1 asString. ''the value of x can be any string object" user"how do I add x to be part off the name so I end up with variable named user1 user2 ... " := User new. x := x + x.]
Darren
On May 23, 2007, at 16:37 , Darren White wrote:
Hello, Thanks fro the replies.
I think my first question was a little fuzzy. I think what I need to do as change the question.
If for example I have a seaside web app and users need to create an account. Now, for each user I create an object, say an instance of class Users, which has instance variables such as name and address. So the new user puts in their detail such as name, address, telephone number and then click register. How should (not what) the system name this object. What I'm confused about is I don't know how may users the system will have have do I name all the user object; I can't call them all aUser . If the first user gets an object named user1 how do I create another instance of User named user2 or What about If I want to use one of the input field as part of the name of the object?
The example below may make it clear what I mean
10 timesRepeat: [ x := 1 asString. ''the value of x can be any string object" user"how do I add x to be part off the name so I end up with variable named user1 user2 ... " := User new. x := x + x.]
There is a cool thing called a "collection" that can hold as many users as you want:
users := OrderedCollection new. 10 timesRepeat: [users add: User new].
And later you can access an individual user like this:
users at: 2
users at: 5
- Bert -
On May 23, 2007, at 17:16 , Bert Freudenberg wrote:
On May 23, 2007, at 16:37 , Darren White wrote:
Hello, Thanks fro the replies.
I think my first question was a little fuzzy. I think what I need to do as change the question.
If for example I have a seaside web app and users need to create an account. Now, for each user I create an object, say an instance of class Users, which has instance variables such as name and address. So the new user puts in their detail such as name, address, telephone number and then click register. How should (not what) the system name this object. What I'm confused about is I don't know how may users the system will have have do I name all the user object; I can't call them all aUser . If the first user gets an object named user1 how do I create another instance of User named user2 or What about If I want to use one of the input field as part of the name of the object?
The example below may make it clear what I mean
10 timesRepeat: [ x := 1 asString. ''the value of x can be any string object" user"how do I add x to be part off the name so I end up with variable named user1 user2 ... " := User new. x := x + x.]
There is a cool thing called a "collection" that can hold as many users as you want:
users := OrderedCollection new. 10 timesRepeat: [users add: User new].
And later you can access an individual user like this:
users at: 2
users at: 5
Also, there is another kind of collection named dictionary that allows to use objects other than integers (like strings) to be the key:
users := Dictionary new. 1 to: 10 do: [:i | users at: ('user', i asString) put: (User new)]
(I added parens for clarity, they're not necessary in this case)
Retrieval goes like this:
users at: 'user5'
Cheers,
- Bert -
Following Bert, the key used to access the dictionary could also be the instance variable 'name' of the User. So, if you now that names are unique, you can write:
users := Dictionary new. names := #('Fred' 'Julia' 'Oliver' 'Martha'). names do: [:aName | | aUser | aUser := User new. aUser name: aName. users at: aUser name put: aUser]. ^users at: 'Fred'
Of course, if you further change the name of a user, users will get messy... (users at: 'Fred') name: 'John'. ^users at: 'Fred'.
User 'John' is still registeered at key 'Fred'...
How to update the Dictionary would be another lesson.
If names are not unique, but you still want to access by name, no problem, you can well make a Dictionary where each entry is a collection of users sharing same name...
usersByName := Dictionary new. names := #('Fred' 'Julia' 'Oliver' 'Martha' 'Fred'). names do: [:aName | | aUser | aUser := User new. aUser name: aName. (usersByName at: aUser name ifAbsentPut: [OrderedCollection new]) add: aUser]. ^usersByName at: 'Fred'
Then i guesse you will have a birthdate coupled to the name or other kind of ID to differentiate your users...
After learning a bit of the Collection subclasses, you will see that you can program as you think.
Nicolas
Bert Freudenberg a écrit :
On May 23, 2007, at 17:16 , Bert Freudenberg wrote:
On May 23, 2007, at 16:37 , Darren White wrote:
Hello, Thanks fro the replies.
I think my first question was a little fuzzy. I think what I need to do as change the question.
If for example I have a seaside web app and users need to create an account. Now, for each user I create an object, say an instance of class Users, which has instance variables such as name and address. So the new user puts in their detail such as name, address, telephone number and then click register. How should (not what) the system name this object. What I'm confused about is I don't know how may users the system will have have do I name all the user object; I can't call them all aUser . If the first user gets an object named user1 how do I create another instance of User named user2 or What about If I want to use one of the input field as part of the name of the object?
The example below may make it clear what I mean
10 timesRepeat: [ x := 1 asString. ''the value of x can be any string object" user"how do I add x to be part off the name so I end up with variable named user1 user2 ... " := User new. x := x + x.]
There is a cool thing called a "collection" that can hold as many users as you want:
users := OrderedCollection new. 10 timesRepeat: [users add: User new].And later you can access an individual user like this:
users at: 2 users at: 5Also, there is another kind of collection named dictionary that allows to use objects other than integers (like strings) to be the key:
users := Dictionary new. 1 to: 10 do: [:i | users at: ('user', i asString) put: (User new)](I added parens for clarity, they're not necessary in this case)
Retrieval goes like this:
users at: 'user5'Cheers,
- Bert -
On Wed, 2007-05-23 at 15:37 +0100, Darren White wrote:
Hello, Thanks fro the replies.
I think my first question was a little fuzzy. I think what I need to do as change the question.
If for example I have a seaside web app and users need to create an account. Now, for each user I create an object, say an instance of class Users, which has instance variables such as name and address. So the new user puts in their detail such as name, address, telephone number and then click register. How should (not what) the system name this object. What I'm confused about is I don't know how may users the system will have have do I name all the user object; I can't call them all aUser . If the first user gets an object named user1 how do I create another instance of User named user2 or What about If I want to use one of the input field as part of the name of the object?
The example below may make it clear what I mean
10 timesRepeat: [ x := 1 asString. ''the value of x can be any string object" user"how do I add x to be part off the name so I end up with variable named user1 user2 ... " := User new. x := x + x.]
Why not using a collection for this. If I understand you right, you just need a bunch of user objects. If you think you need some kind of index just use an OrderedCollection.
users := OrderedCollection new. 10 timeRepeat: [ users add: User new. ]
Then you have even the chance to access them by index
firstUser := users at: 1
hope this helps,
Norbert
Hello Darren,
DW> 10 timesRepeat: [ DW> x := 1 asString. DW> ''the value of x can be any string object" DW> user"how do I add x to be part off the name so I end up with DW> variable named user1 user2 ... " := User new. DW> x := x + x.]
if I don't misunderstand you, you want to put your users in a subclass of Collection, first guess is OrderedCollection. There is no need to have a single variable with a unique name for each user.
So up to now I don't understand why the system should name the object.
Is it a possibility to say:
users := OrderedCollection new.
Then a user enters his details in an instance of class User and you put it into the collection users by:
newUser := User new. user name: .... "to add the name to the new user"
users add: newUser. "to stuff this user into the collection of users"
Collection and subclasses offer methods like:
users select: [:eachUser | eachUser name = 'willi']
to give you a collection of all users named 'willi'.
If this points in the right direction read up on collections and their enumeration methods.
Else hope for someone to understand you better or clarify your intentions for me :-))
Cheers
Herbert mailto:herbertkoenig@gmx.net
beginners@lists.squeakfoundation.org
-
Bert Freudenberg -
Darren White -
Herbert König -
nicolas cellier -
Norbert Hartl