I would love such an extension.
It would be great if the user would not "know" about internal components
and pages.
Regards,
Norbi
James Carman wrote:
In this case, HiveMind would only be necessary if you wanted to override the
default namespace of the library. Library "authors" should be knowledgeable
enough with HiveMind to at least do a contribution...
<contribution configuration-id="tapestry.Libraries">
<library specification="com/myco/mylibrary.library" />
</contribution>
Something like that.
-----Original Message-----
From: Geoff Longman [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 15, 2006 1:09 PM
To: Tapestry users
Subject: Re: custom namespace
Good God No!
While I love the idea of auto discovery of libraries, every time I see
a quick suggestion to use Hivemind I cringe.
IMO HM is *required* to do too many everyday things in T4. HM should
be relegated to use when the *implementation of the runtime* needs to
be changed or enhanced because a convention doesn't handle a
particular case. A normal everyday user should be able to build
libraries, have full featured ASO's, and build services without ever
writing a line of HM config.
That puts a lot more pressure on the committers to identify the
everyday tasks and find intelligent conventions for users to do
something without writing HM code. That doesn't mean HM is out of the
mix, it's just out of sight and available for those 1% cases where you
just have to make Tap behave differently from the convention. Really,
in a perfect world the Tapestry docs would make no reference to HM
except in an appendix.
end of rant!
Geoff
On 6/15/06, James Carman <[EMAIL PROTECTED]> wrote:
It would be nice if the component libraries could add themselves to the
mix
via a HiveMind contribution. Of course, they would allow "users" to
override their default namespace via a symbol override contribution or
something. That's the way I'd do it.
-----Original Message-----
From: Norbert Sándor [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 15, 2006 12:27 PM
To: Tapestry users
Subject: Re: custom namespace
I use many such component libraries which means that because of this
issue, many libraries must be specified "by hand".
Not a big problem, just tried to avoid it :)
Regards,
Norbi
Geoff Longman wrote:
Yes, that's true. But is that really a problem? Contrib has the same
issue.
Geoff
On 6/15/06, Norbert Sándor <[EMAIL PROTECTED]> wrote:
Thanks!
This means that I must force the user of my component library to define
my library with a fix alias in the .application file.
Regards,
Norbi
Jesse Kuhnert wrote:
You mean like contrib or tacos? I think the namespace name can be
tied
to a
.library file via your .application configuration. (this I'm less
sure
of as
the best solution)
On 6/14/06, Norbert Sándor <[EMAIL PROTECTED]> wrote:
Hi,
By default there are 2 namespaces: framework and application.
How can I define my own, custom namespace?
Regards,
Norbi
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.8.3/362 - Release Date:
2006.06.12.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
