Stef,
I agree. It would be great to have more ready to use components. For example, I created a task to control authentication. That could be in place and ready to use or subclass, with optional registration, or in my case, refusal to accept any other than pre-registered users, and (stuff I have yet to do) a UI for an administrator to manage users. The configuration web interface is nice, but it would be nice to have (maybe this is obvious and I simply have yet to see it) examples of programmatically changing configuration. Things that I will hopefully have time to do include an SSL version of Comanche, and idiot-proof setup of Apache for secure sites. Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: [hidden email] Tel: (352) 846-1285 FAX: (352) 392-7029 _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
2008/7/12 Bill Schwab <[hidden email]>:
> Stef, > > I agree. It would be great to have more ready to use components. For > example, I created a task to control authentication. That could be in > place and ready to use or subclass, with optional registration, or in my > case, refusal to accept any other than pre-registered users, and (stuff > I have yet to do) a UI for an administrator to manage users. > > The configuration web interface is nice, but it would be nice to have > (maybe this is obvious and I simply have yet to see it) examples of > programmatically changing configuration. Things that I will hopefully > have time to do include an SSL version of Comanche SSL belongs into Apache not Comanche. Cheers Philippe _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
In reply to this post by Schwab,Wilhelm K
On Jul 12, 2008, at 9:25 PM, Bill Schwab wrote: > Stef, > > I agree. It would be great to have more ready to use components. For > example, I created a task to control authentication. That could be in > place and ready to use or subclass, with optional registration, or > in my > case, refusal to accept any other than pre-registered users, and > (stuff > I have yet to do) a UI for an administrator to manage users. > > The configuration web interface is nice, but it would be nice to have > (maybe this is obvious and I simply have yet to see it) examples of > programmatically changing configuration. Things that I will hopefully > have time to do include an SSL version of Comanche, and idiot-proof > setup of Apache for secure sites. yes. I hope we will have that in our book but I do not have that knowlegde. The problem of the smalltalk community in general is that really few people take the time to write down. > > > Bill > > > > > Wilhelm K. Schwab, Ph.D. > University of Florida > Department of Anesthesiology > PO Box 100254 > Gainesville, FL 32610-0254 > > Email: [hidden email] > Tel: (352) 846-1285 > FAX: (352) 392-7029 > > _______________________________________________ > seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Free forum by Nabble | Edit this page |