webtek-devel

Re: [Webtek-devel] test

[max d. <pro...@gm...>]

reply test

On May 23, 2008, at 1:02 PM, max demmelbauer wrote:

> test
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Webtek-devel mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webtek-devel

[Webtek-devel] Inheritance hierarchies for Model objects

[Adrian S. <adr...@gm...>]

I have two types of User and they have significantly different attributes.
On the other hand, they have a number of attributes in common (e.g.
username/passwords), the users can log in over the same login form (so
usernames must be unique across both types of user), etc.
 
Instinctively, the natural way to model this would be an inheritance
hierarchy, i.e.

*	a "User" model class with the id, username, password attributes
*	"AdministratorUser" and "AdvisorUser" (from my application) which
extend "User" and have their further attributes

The "User" superclass would need to have some kind of findByUsername method
which would return an instance of one of the concrete classes, depending on
which type of user was found.
 
Is there any support for anything like this in WebTek?
 
(If not - no problem! - it's only a small application, so I can easily use
another solution, such as placing all the attributes in one single "User"
class/table which covers both cases.)

[Webtek-devel] Package hierarchies for Pages and Models

[Adrian S. <adr...@gm...>]

The project I am intending to construct with WebTek has quite a few screens.
Is it possible to have some kind of hierarchy such as:
 
MyApp::Page::Foo::Bar
 
or must all pages be directly under the Page directory, i.e.
 
MyApp::Page::Bar
 
What about model classes? (Although in my app I only have 3-4 database
tables, so it's not really an issue.)

[Webtek-devel] Breadcrumbs

[Adrian S. <adr...@gm...>]

Is there any facility for supporting "Breadcrumbs", for example 

Root Page > All profiles > Profile 'x' > Edit Data

I would imagine following features being necessary for a breadcrumbs system:

*	It would make sense to use the Parent concept already in WebTek to
build the breadcrumbs (as opposed to e.g. having the breadcrumb parent/child
relationship external in a config file or something)
*	As "Edit Data"-type screens are implemented with WebTek actions, and
as they are represented by adding e.g. /edit onto the URL, it would also
make sense to add them to the breadcrumbs
*	Obviously the breadcrumbs would be linked to the pages they
represent
*	Breadcrumbs should be able to support data for example "Profile 'x'"
for the particular profile that's being viewed.
*	Text localizable
*	Maybe an obscure point, but I think it'd be cool if the last point,
e.g. "Edit Data" above, could be missed out. That way breadcrumbs would just
be ".... Profile 'x' >" and the actual text of "Edit Data" could be the main
heading of the page.

If there is no such system, then I would be happy to build such a system.

*	I imagine the best place would be in a "module"
*	For example exposing a new tag such as <% breadcrumbs %> which is
implemented by the Root page of the module
*	In order to follow the convention in WebTek that "templates are in
control" i.e. they suck the data out of the pages with macros (as opposed to
pages populating dumb templates by setting e.g. $-variables), I would create
a "breadcrumb.tpl" in each Page class.
*	This could include a <% message %> for localization
*	Or any other attribute for example <% name %>. In the example above.
if the "ProfileView" page (for "Profile 'x'") uses a Profile model, and that
model has a "name" attribute.
	
*	Formatting done over CSS, i.e. not really a concern of the
breadcrumb system. Following "programming by convention", the CSS styles
would have fixed names e.g. "breadcrumbItem" which could be styled.

[Webtek-devel] Session variables are scalars?

[Adrian S. <adr...@gm...>]

In the latest tutorial, you remember the logged-in user by setting a
variable on the session, using:

session->user(request->user)

What objects are involved here? I assume that:

*	The "request" has a special attribute which is the http-auth user
being submitted with the http request? And that that's a string?
*	The "session" is able to store only scalar/string attributes.
Looking at the table definition of "session", that would seem to be the
case.

Assuming that one is implementing an authorization system based on Users who
are stored in the database, and not using HTTP authentication, should one

*	set e.g. the user_id in the session, or
*	set the whole user object as a session attribute, and the session
persistence system takes care of extracitng the user_id from the user
object?

[Webtek-devel] **Message you sent blocked by our bulk email filter**

[Barracuda S. F. <pos...@co...>]

Your message to: web...@re...
was blocked by our Spam Firewall. The email you sent with the following subject has NOT BEEN DELIVERED:

Subject: When Snacks Attack!‏

[Webtek-devel] **Message you sent blocked by our bulk email filter**

[Barracuda S. F. <pos...@co...>]

WW91ciBtZXNzYWdlIHRvOiB3ZWJ0ZWNoc2VtQHJlbGl1cy5uZXQKd2FzIGJs
b2NrZWQgYnkgb3VyIFNwYW0gRmlyZXdhbGwuIFRoZSBlbWFpbCB5b3Ugc2Vu
dCB3aXRoIHRoZSBmb2xsb3dpbmcgc3ViamVjdCBoYXMgTk9UIEJFRU4gREVM
SVZFUkVEOgoKU3ViamVjdDogTWFya2V0IFVzYQoK