Another question...(about WebUser)

> I want to add a new variable to WebUser. I added this :
>
> WebUser>>website
> ^self otherValuesAt: 'website' ifAbsent: [self otherValuesAt: 'website'
> put: '']
>
> WebUser>>website: aString
> self otherValuesAt: 'website' put: aString
>
> in a custom category, so no problem.
>
> But what about views ? I would like to display the new feild in views
> (WebAdminApp>>viewRegistration and
> WebSecurityManagerApp>>userElementForm:).
>
> My first idea was to subclass this apps, and override MyWebSite>>admin
> and MyWebSite>>securityManager.
>
> But if I do it, I need to create empty subclasses of WebAdmin and
> WebSecurityManager too, and I really don't like it. Is there another way
> to do it without creating those empty subclasses ?
>  

> nicolas petton a ?crit :
> > First, I'm sorry for all this questions...
> >  
> Don't worry, you are asking right and useful ones!
> > I want to add a new variable to WebUser. I added this :
> >
> > WebUser>>website
> > ^self otherValuesAt: 'website' ifAbsent: [self otherValuesAt: 'website'
> > put: '']
> >
> > WebUser>>website: aString
> > self otherValuesAt: 'website' put: aString
> >
> > in a custom category, so no problem.
> >
> > But what about views ? I would like to display the new feild in views
> > (WebAdminApp>>viewRegistration and
> > WebSecurityManagerApp>>userElementForm:).
> >
> > My first idea was to subclass this apps, and override MyWebSite>>admin
> > and MyWebSite>>securityManager.
> >
> > But if I do it, I need to create empty subclasses of WebAdmin and
> > WebSecurityManager too, and I really don't like it. Is there another way
> > to do it without creating those empty subclasses ?
> >  
> You are right, better avoid subclassing and rather use extensions. So on
> Squeak, if you have a package MyPackage, add method category *MyPackage
> in class WebUser and that's it! You don't need change any other classes
> in that case, specially not WebSecurityManager etc.

>>> I want to add a new variable to WebUser. I added this :
>>>
>>> WebUser>>website
>>> ^self otherValuesAt: 'website' ifAbsent: [self otherValuesAt: 'website'
>>> put: '']
>>>
>>> WebUser>>website: aString
>>> self otherValuesAt: 'website' put: aString
>>>
>>> in a custom category, so no problem.
>>>
>>> But what about views ? I would like to display the new feild in views
>>> (WebAdminApp>>viewRegistration and
>>> WebSecurityManagerApp>>userElementForm:).
>>>
>>> My first idea was to subclass this apps, and override MyWebSite>>admin
>>> and MyWebSite>>securityManager.
>>>
>>> But if I do it, I need to create empty subclasses of WebAdmin and
>>> WebSecurityManager too, and I really don't like it. Is there another way
>>> to do it without creating those empty subclasses ?
>>>  
>>>      
>> You are right, better avoid subclassing and rather use extensions. So on
>> Squeak, if you have a package MyPackage, add method category *MyPackage
>> in class WebUser and that's it! You don't need change any other classes
>> in that case, specially not WebSecurityManager etc.
>>    
>
> But if I don't suclass, there will be no field for website (in the
> registration form, and update form), right ? I didn't see the code for
> this in WebSecurityManagerApp>>userElementForm: or
> WebAdminApp>>viewRegistration
>  

> Hi Nicolas,
>
> nicolas petton a ?crit :
> >>> I want to add a new variable to WebUser. I added this :
> >>>
> >>> WebUser>>website
> >>> ^self otherValuesAt: 'website' ifAbsent: [self otherValuesAt: 'website'
> >>> put: '']
> >>>
> >>> WebUser>>website: aString
> >>> self otherValuesAt: 'website' put: aString
> >>>
> >>> in a custom category, so no problem.
> >>>
> >>> But what about views ? I would like to display the new feild in views
> >>> (WebAdminApp>>viewRegistration and
> >>> WebSecurityManagerApp>>userElementForm:).
> >>>
> >>> My first idea was to subclass this apps, and override MyWebSite>>admin
> >>> and MyWebSite>>securityManager.
> >>>
> >>> But if I do it, I need to create empty subclasses of WebAdmin and
> >>> WebSecurityManager too, and I really don't like it. Is there another way
> >>> to do it without creating those empty subclasses ?
> >>>  
> >>>      
> >> You are right, better avoid subclassing and rather use extensions. So on
> >> Squeak, if you have a package MyPackage, add method category *MyPackage
> >> in class WebUser and that's it! You don't need change any other classes
> >> in that case, specially not WebSecurityManager etc.
> >>    
> >
> > But if I don't suclass, there will be no field for website (in the
> > registration form, and update form), right ? I didn't see the code for
> > this in WebSecurityManagerApp>>userElementForm: or
> > WebAdminApp>>viewRegistration
> >  
> Then override those methods too with your own ones in your package and
> you'll have the same result but without subclasing.

> Le vendredi 26 octobre 2007 ? 13:44 +0200, Janko Miv?ek a ?crit :
>  
>> Hi Nicolas,
>>
>> nicolas petton a ?crit :
>>    
>>>>> I want to add a new variable to WebUser. I added this :
>>>>>
>>>>> WebUser>>website
>>>>> ^self otherValuesAt: 'website' ifAbsent: [self otherValuesAt: 'website'
>>>>> put: '']
>>>>>
>>>>> WebUser>>website: aString
>>>>> self otherValuesAt: 'website' put: aString
>>>>>
>>>>> in a custom category, so no problem.
>>>>>
>>>>> But what about views ? I would like to display the new feild in views
>>>>> (WebAdminApp>>viewRegistration and
>>>>> WebSecurityManagerApp>>userElementForm:).
>>>>>
>>>>> My first idea was to subclass this apps, and override MyWebSite>>admin
>>>>> and MyWebSite>>securityManager.
>>>>>
>>>>> But if I do it, I need to create empty subclasses of WebAdmin and
>>>>> WebSecurityManager too, and I really don't like it. Is there another way
>>>>> to do it without creating those empty subclasses ?
>>>>>  
>>>>>      
>>>>>          
>>>> You are right, better avoid subclassing and rather use extensions. So on
>>>> Squeak, if you have a package MyPackage, add method category *MyPackage
>>>> in class WebUser and that's it! You don't need change any other classes
>>>> in that case, specially not WebSecurityManager etc.
>>>>    
>>>>        
>>> But if I don't suclass, there will be no field for website (in the
>>> registration form, and update form), right ? I didn't see the code for
>>> this in WebSecurityManagerApp>>userElementForm: or
>>> WebAdminApp>>viewRegistration
>>>  
>>>      
>> Then override those methods too with your own ones in your package and
>> you'll have the same result but without subclasing.
>>    
>
> Thank you Janko for your answers.
> But if I do it, there will be another problem: this will be applied to
> all AIDASites.
>
> I have another idea, but I don't know how to do. I would like to
> subclass WebSecurityManagerApp but without subclassing
> WebSecurityManager. But is there a way to set a custom app to an object
> (an app with a different name)? Something like:
> UrlResolver defaultUrl: '/admin.html' forObject: admin app: MyAdminApp
>
>  

> nicolas petton a ?crit :
> > Le vendredi 26 octobre 2007 ? 13:44 +0200, Janko Miv?ek a ?crit :
> >  
> >> Hi Nicolas,
> >>
> >> nicolas petton a ?crit :
> >>    
> >>>>> I want to add a new variable to WebUser. I added this :
> >>>>>
> >>>>> WebUser>>website
> >>>>> ^self otherValuesAt: 'website' ifAbsent: [self otherValuesAt: 'website'
> >>>>> put: '']
> >>>>>
> >>>>> WebUser>>website: aString
> >>>>> self otherValuesAt: 'website' put: aString
> >>>>>
> >>>>> in a custom category, so no problem.
> >>>>>
> >>>>> But what about views ? I would like to display the new feild in views
> >>>>> (WebAdminApp>>viewRegistration and
> >>>>> WebSecurityManagerApp>>userElementForm:).
> >>>>>
> >>>>> My first idea was to subclass this apps, and override MyWebSite>>admin
> >>>>> and MyWebSite>>securityManager.
> >>>>>
> >>>>> But if I do it, I need to create empty subclasses of WebAdmin and
> >>>>> WebSecurityManager too, and I really don't like it. Is there another way
> >>>>> to do it without creating those empty subclasses ?
> >>>>>  
> >>>>>      
> >>>>>          
> >>>> You are right, better avoid subclassing and rather use extensions. So on
> >>>> Squeak, if you have a package MyPackage, add method category *MyPackage
> >>>> in class WebUser and that's it! You don't need change any other classes
> >>>> in that case, specially not WebSecurityManager etc.
> >>>>    
> >>>>        
> >>> But if I don't suclass, there will be no field for website (in the
> >>> registration form, and update form), right ? I didn't see the code for
> >>> this in WebSecurityManagerApp>>userElementForm: or
> >>> WebAdminApp>>viewRegistration
> >>>  
> >>>      
> >> Then override those methods too with your own ones in your package and
> >> you'll have the same result but without subclasing.
> >>    
> >
> > Thank you Janko for your answers.
> > But if I do it, there will be another problem: this will be applied to
> > all AIDASites.
> >
> > I have another idea, but I don't know how to do. I would like to
> > subclass WebSecurityManagerApp but without subclassing
> > WebSecurityManager. But is there a way to set a custom app to an object
> > (an app with a different name)? Something like:
> > UrlResolver defaultUrl: '/admin.html' forObject: admin app: MyAdminApp
> >
> >  
> That's interesting idea and also a problem which needs to be solved
> somehow. To solve most generally I would start with some object to App
> map and add it to AIDASite, maybe in settings. Then I'd just extend
> method Object>>webApp to look in this map too. What do you think?

>>> I have another idea, but I don't know how to do. I would like to
>>> subclass WebSecurityManagerApp but without subclassing
>>> WebSecurityManager. But is there a way to set a custom app to an object
>>> (an app with a different name)? Something like:
>>> UrlResolver defaultUrl: '/admin.html' forObject: admin app: MyAdminApp
>>>      
>> That's interesting idea and also a problem which needs to be solved
>> somehow. To solve most generally I would start with some object to App
>> map and add it to AIDASite, maybe in settings. Then I'd just extend
>> method Object>>webApp to look in this map too. What do you think?
>>    
>
> I think it's a very good idea :) This way it would easier to extend
> existing models and apps, without overriding existing methods. If you
> want I can do it (at least I can try).

> nicolas petton a ?crit :
> >>> I have another idea, but I don't know how to do. I would like to
> >>> subclass WebSecurityManagerApp but without subclassing
> >>> WebSecurityManager. But is there a way to set a custom app to an object
> >>> (an app with a different name)? Something like:
> >>> UrlResolver defaultUrl: '/admin.html' forObject: admin app: MyAdminApp
> >>>      
> >> That's interesting idea and also a problem which needs to be solved
> >> somehow. To solve most generally I would start with some object to App
> >> map and add it to AIDASite, maybe in settings. Then I'd just extend
> >> method Object>>webApp to look in this map too. What do you think?
> >>    
> >
> > I think it's a very good idea :) This way it would easier to extend
> > existing models and apps, without overriding existing methods. If you
> > want I can do it (at least I can try).
> Yes, just try it, then we'll finish together. Another place for map can
> beWebStyle, but that class is already overloaded ...

> Le vendredi 26 octobre 2007 ? 16:28 +0200, Janko Miv?ek a ?crit :
>  
>> nicolas petton a ?crit :
>>    
>>>>> I have another idea, but I don't know how to do. I would like to
>>>>> subclass WebSecurityManagerApp but without subclassing
>>>>> WebSecurityManager. But is there a way to set a custom app to an object
>>>>> (an app with a different name)? Something like:
>>>>> UrlResolver defaultUrl: '/admin.html' forObject: admin app: MyAdminApp
>>>>>      
>>>>>          
>>>> That's interesting idea and also a problem which needs to be solved
>>>> somehow. To solve most generally I would start with some object to App
>>>> map and add it to AIDASite, maybe in settings. Then I'd just extend
>>>> method Object>>webApp to look in this map too. What do you think?
>>>>    
>>>>        
>>> I think it's a very good idea :) This way it would easier to extend
>>> existing models and apps, without overriding existing methods. If you
>>> want I can do it (at least I can try).
>>>      
>> Yes, just try it, then we'll finish together. Another place for map can
>> beWebStyle, but that class is already overloaded ...
>>    
>
> I tried it, and it seems to work fine.
>
> Object>>webAppFor: aSession
> | webApp |
> aSession isNil ifTrue: [^nil].
> webApp := aSession webAppFor: self.
> webApp notNil ifTrue: [^webApp].
> webApp := self firstSessionFromStack site mappings at: self ifAbsent:
> [].
> webApp ifNil: [webApp := WebApplication newFor: self on: aSession]
> ifNotNil: [webApp observee: self; session: aSession; postInitialize].
> "I know, it's uggly, but it works !"
> webApp notNil ifTrue: [aSession addWebApp: webApp for: self].
> ^webApp
>
>
> AIDASite>>mappings
> ^self settings at: #mappings ifAbsentPut: [Dictionary new].
>
>
> AIDASite>>mapApp: aWebApplication for: anObject
> self mappings at: anObject put: aWebApplication
>
>
> Then in my AIDASite subclass:
>
> admin
> ^self systemServices
> at: #Admin
> ifAbsent: [ |admin|
> admin := WebAdmin new.
> self mapApp: MyWebAdminApp new for: admin.
> self addSystemService: admin named: #Admin.
> self urlResolver defaultURL: '/admin.html' forObject: self admin.
> ^self admin].
>
>