You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Viktor Szathmary <ph...@gmail.com> on 2005/03/28 18:37:04 UTC
[ANN] Tacos Library 2005-03-27
Hi,
a new release of the Tacos Component Library is available at:
http://tacos.sourceforge.net/
The Tacos Tree component offers a better alternative to contrib:Tree.
It has improved usability and the development API is simple and straightforward.
Personally, my brain always twisted in a knot when using contrib:Tree,
not to mention the time it took to make it work with acceptable
usability. Tacos Tree addresses this by making things almost as easy
as a Foreach. It also provides important end-user usability
improvements (ie. pixel-precise positioning).
Check out the live demo at:
http://tacos.mine.nu:8080/tacos-demo/
There's also a supplier file available for the Tapestry Palette
Eclipse plugin. Add it via Window -> Preferences -> Tapestry Palette
-> Remote Libraries: http://tacos.sourceforge.net/supplier-tacos.xml
Comments, suggestions, bug reports and other contributions are
welcome. In the future I'm hoping to add more components.
btw, does anyone have a copy of the TapDoc XSL somewhere? I would like
to use it for component documentation, but it's no longer available at
the original site. I see it's used on t-deli.com, so Mindbridge might
have a copy :)
Regards,
Viktor
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: [ANN] Tacos Library 2005-03-27
Posted by Andreas Andreou <an...@di.uoa.gr>.
Well done viktor!
- Since i'll be working on creating some ajax components (even though
others have beat me to it),
I think that the tree component will really benefit from a possible ajax
integration (i.e. have the javascript call
a listener method).
- The Tacos project is surely a well known tapestry components project,
but would you mind also adding it
to the TapestryForums.com site?
- I also need the TapDoc XSL to generate docs for my components... Can
we have it posted somewhere?
I don't know if the forums allow posting files...
Respect,
Andreas
Viktor Szathmary wrote:
>Hi,
>
>a new release of the Tacos Component Library is available at:
>
>http://tacos.sourceforge.net/
>
>The Tacos Tree component offers a better alternative to contrib:Tree.
>It has improved usability and the development API is simple and straightforward.
>
>Personally, my brain always twisted in a knot when using contrib:Tree,
>not to mention the time it took to make it work with acceptable
>usability. Tacos Tree addresses this by making things almost as easy
>as a Foreach. It also provides important end-user usability
>improvements (ie. pixel-precise positioning).
>
>Check out the live demo at:
>
>http://tacos.mine.nu:8080/tacos-demo/
>
>There's also a supplier file available for the Tapestry Palette
>Eclipse plugin. Add it via Window -> Preferences -> Tapestry Palette
>-> Remote Libraries: http://tacos.sourceforge.net/supplier-tacos.xml
>
>Comments, suggestions, bug reports and other contributions are
>welcome. In the future I'm hoping to add more components.
>
>btw, does anyone have a copy of the TapDoc XSL somewhere? I would like
>to use it for component documentation, but it's no longer available at
>the original site. I see it's used on t-deli.com, so Mindbridge might
>have a copy :)
>
>Regards,
> Viktor
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: [ANN] Tacos Library 2005-03-27
Posted by Viktor Szathmary <ph...@gmail.com>.
hi,
yes, i wish there was a concept of a component instance in tapestry
(well, you can retrieve components but their state is not estabilished
until render and is reused if you have multiple of them).. right now
this is the closest i could get.. the tree state parameter is
optional, you only need to provide a binding if you need external
control - even then you can leave it null: the component will
initialize it to a new HashSet in that case.
i found that in practice this is Good Enough(tm).. i would be
interested to learn if there's a more elegant way of doing this with
tapestry :)
viktor
On Tue, 29 Mar 2005 17:10:37 +0200, Vjeran Marcinko <vj...@tis.hr> wrote:
> Hi Victor.
>
> I'm pretty impressed with simplicity of tacos:Tree, it looks much more
> elegantly solved than contrib:Tree, but I think this external interface
> (current TreeManager) has to be defined a bit more clearly.
> If you take a look at file tree example, you will see that "state" parameter
> of Tree component (java.util.Set) is defined solely for purpose of creation
> of convenience class - TreeManager. It seems awkward way, since I wanted to
> avoid seeing this Set because I'm happy with default value (HashSet).
> Actually, if we forget about Tapestry, and think only in terms of OO -
> IContentProvider, IKeyProvider and state Set, are dependencies for Tree
> component. Some are optional (for eg. state Set), and are creaed internally
> as default values (HashSet), which is great, and everything is clear.
> Difficulty is that when Tree component is instantiated, it would be best to
> fetch this Tree instance somehow and cast it to ITreeManager (or whatever
> name) since that is interface that we use for external manipulation. But
> obviously this fetching and casting is ugly (I guess it could be acomplished
> by getComponent("..."), but I'm not so sure, and it is ugly...).
>
> I don't see best solution yet ...I guess it needs some more thinking about
> how to design this... :-(
>
> ----- Original Message -----
> From: "Viktor Szathmary" <ph...@gmail.com>
> To: "Vjeran Marcinko" <vj...@tis.hr>
> Cc: "Tapestry users" <ta...@jakarta.apache.org>
> Sent: Tuesday, March 29, 2005 4:42 PM
> Subject: Re: [ANN] Tacos Library 2005-03-27
>
> > hi,
> >
> > indeed, the ITreeManager is not really needed anymore. It used to be
> > coupled with the tree state (set of expanded keys), but since it also
> > needs the content/keyProviders to do its job, i decided it's better to
> > separate them (so those don't get serialized in session state). the
> > tree itself creates a TreeManager instances when doing expand/close.
> > of course it could perform the same operations directly on the set...
> > i'll clean it up a bit more for the next release...
>
> --
> No virus found in this outgoing message.
> Checked by AVG Anti-Virus.
> Version: 7.0.308 / Virus Database: 266.8.4 - Release Date: 27.3.2005
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: [ANN] Tacos Library 2005-03-27
Posted by Vjeran Marcinko <vj...@tis.hr>.
Hi Victor.
I'm pretty impressed with simplicity of tacos:Tree, it looks much more
elegantly solved than contrib:Tree, but I think this external interface
(current TreeManager) has to be defined a bit more clearly.
If you take a look at file tree example, you will see that "state" parameter
of Tree component (java.util.Set) is defined solely for purpose of creation
of convenience class - TreeManager. It seems awkward way, since I wanted to
avoid seeing this Set because I'm happy with default value (HashSet).
Actually, if we forget about Tapestry, and think only in terms of OO -
IContentProvider, IKeyProvider and state Set, are dependencies for Tree
component. Some are optional (for eg. state Set), and are creaed internally
as default values (HashSet), which is great, and everything is clear.
Difficulty is that when Tree component is instantiated, it would be best to
fetch this Tree instance somehow and cast it to ITreeManager (or whatever
name) since that is interface that we use for external manipulation. But
obviously this fetching and casting is ugly (I guess it could be acomplished
by getComponent("..."), but I'm not so sure, and it is ugly...).
I don't see best solution yet ...I guess it needs some more thinking about
how to design this... :-(
----- Original Message -----
From: "Viktor Szathmary" <ph...@gmail.com>
To: "Vjeran Marcinko" <vj...@tis.hr>
Cc: "Tapestry users" <ta...@jakarta.apache.org>
Sent: Tuesday, March 29, 2005 4:42 PM
Subject: Re: [ANN] Tacos Library 2005-03-27
> hi,
>
> indeed, the ITreeManager is not really needed anymore. It used to be
> coupled with the tree state (set of expanded keys), but since it also
> needs the content/keyProviders to do its job, i decided it's better to
> separate them (so those don't get serialized in session state). the
> tree itself creates a TreeManager instances when doing expand/close.
> of course it could perform the same operations directly on the set...
> i'll clean it up a bit more for the next release...
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.8.4 - Release Date: 27.3.2005
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: [ANN] Tacos Library 2005-03-27
Posted by Viktor Szathmary <ph...@gmail.com>.
hi,
indeed, the ITreeManager is not really needed anymore. It used to be
coupled with the tree state (set of expanded keys), but since it also
needs the content/keyProviders to do its job, i decided it's better to
separate them (so those don't get serialized in session state). the
tree itself creates a TreeManager instances when doing expand/close.
of course it could perform the same operations directly on the set...
i'll clean it up a bit more for the next release...
viktor
On Tue, 29 Mar 2005 14:03:05 +0200, Vjeran Marcinko <vj...@tis.hr> wrote:
> BTW, the TreeManager is just a support/convenience class for external
> manipulation with tree data and state, right? It's not actually used by the
> Tree component itself ?
> If above is correct, I don't see exactly a need for ITreeManager
> interface...
>
> -Vjeran
>
> --
> No virus found in this outgoing message.
> Checked by AVG Anti-Virus.
> Version: 7.0.308 / Virus Database: 266.8.4 - Release Date: 27.3.2005
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: [ANN] Tacos Library 2005-03-27
Posted by Vjeran Marcinko <vj...@tis.hr>.
BTW, the TreeManager is just a support/convenience class for external
manipulation with tree data and state, right? It's not actually used by the
Tree component itself ?
If above is correct, I don't see exactly a need for ITreeManager
interface...
-Vjeran
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.8.4 - Release Date: 27.3.2005
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: [ANN] Tacos Library 2005-03-27
Posted by Viktor Szathmary <ph...@gmail.com>.
hi,
here's a bit of history. The current contrib:Tree was written by
mindbridge and tzvetelin and incubated around 2002 under the Tacos
project. Then it was moved to the apache tapestry project as
contrib:Tree.
The current Tacos tree that I wrote is a completely different, brand
new codebase that is not compatible with contrib:Tree - as such, not a
drop-in replacement but an easy-to-use alternative.
viktor
On Mon, 28 Mar 2005 20:53:53 +0200, Vjeran Marcinko <vj...@tis.hr> wrote:
> Hmmm... I guess I was wrong, but I thought that contrib:Tree has become from
> Tacos Tree?
> Any chances that qualities of this component will be incorporated into
> contrib:Tree because it's nice to have best of breed component by default
> inside the framework? Or they are too different for that?
>
> ----- Original Message -----
> From: "Viktor Szathmary" <ph...@gmail.com>
> To: <ta...@jakarta.apache.org>
> Sent: Monday, March 28, 2005 6:37 PM
> Subject: [ANN] Tacos Library 2005-03-27
>
> > Hi,
> >
> > a new release of the Tacos Component Library is available at:
> >
> > http://tacos.sourceforge.net/
> >
> > The Tacos Tree component offers a better alternative to contrib:Tree.
> > It has improved usability and the development API is simple and
> straightforward.
> >
> > Personally, my brain always twisted in a knot when using contrib:Tree,
> > not to mention the time it took to make it work with acceptable
> > usability. Tacos Tree addresses this by making things almost as easy
> > as a Foreach. It also provides important end-user usability
> > improvements (ie. pixel-precise positioning).
> >
> > Check out the live demo at:
> >
> > http://tacos.mine.nu:8080/tacos-demo/
> >
> > There's also a supplier file available for the Tapestry Palette
> > Eclipse plugin. Add it via Window -> Preferences -> Tapestry Palette
> > -> Remote Libraries: http://tacos.sourceforge.net/supplier-tacos.xml
> >
> > Comments, suggestions, bug reports and other contributions are
> > welcome. In the future I'm hoping to add more components.
> >
> > btw, does anyone have a copy of the TapDoc XSL somewhere? I would like
> > to use it for component documentation, but it's no longer available at
> > the original site. I see it's used on t-deli.com, so Mindbridge might
> > have a copy :)
> >
> > Regards,
> > Viktor
>
> --
> No virus found in this outgoing message.
> Checked by AVG Anti-Virus.
> Version: 7.0.308 / Virus Database: 266.8.4 - Release Date: 27.3.2005
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: [ANN] Tacos Library 2005-03-27
Posted by Vjeran Marcinko <vj...@tis.hr>.
Hmmm... I guess I was wrong, but I thought that contrib:Tree has become from
Tacos Tree?
Any chances that qualities of this component will be incorporated into
contrib:Tree because it's nice to have best of breed component by default
inside the framework? Or they are too different for that?
----- Original Message -----
From: "Viktor Szathmary" <ph...@gmail.com>
To: <ta...@jakarta.apache.org>
Sent: Monday, March 28, 2005 6:37 PM
Subject: [ANN] Tacos Library 2005-03-27
> Hi,
>
> a new release of the Tacos Component Library is available at:
>
> http://tacos.sourceforge.net/
>
> The Tacos Tree component offers a better alternative to contrib:Tree.
> It has improved usability and the development API is simple and
straightforward.
>
> Personally, my brain always twisted in a knot when using contrib:Tree,
> not to mention the time it took to make it work with acceptable
> usability. Tacos Tree addresses this by making things almost as easy
> as a Foreach. It also provides important end-user usability
> improvements (ie. pixel-precise positioning).
>
> Check out the live demo at:
>
> http://tacos.mine.nu:8080/tacos-demo/
>
> There's also a supplier file available for the Tapestry Palette
> Eclipse plugin. Add it via Window -> Preferences -> Tapestry Palette
> -> Remote Libraries: http://tacos.sourceforge.net/supplier-tacos.xml
>
> Comments, suggestions, bug reports and other contributions are
> welcome. In the future I'm hoping to add more components.
>
> btw, does anyone have a copy of the TapDoc XSL somewhere? I would like
> to use it for component documentation, but it's no longer available at
> the original site. I see it's used on t-deli.com, so Mindbridge might
> have a copy :)
>
> Regards,
> Viktor
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.8.4 - Release Date: 27.3.2005
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org