tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tapestry-...@jakarta.apache.org
Subject [Jakarta Tapestry Wiki] Updated: WishList
Date Fri, 16 Jul 2004 20:06:08 GMT
   Date: 2004-07-16T13:06:08
   Editor: JoelTrunick <joel.trunick@webifysolutions.com>
   Wiki: Jakarta Tapestry Wiki
   Page: WishList
   URL: http://wiki.apache.org/jakarta-tapestry/WishList

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -1,3 +1,7 @@
+How about a Tapestry Context? I've built one for our projects, it sets the Visit into ThreadLocal.
This way, helper classes don't have to pass around the Visit. The extended BasePage implements
IPageListener and sets (and unsets) the Visit. Classes that control web flow can grab it themselves.
You could also put HttpRequest in it for implementing Portal support (this was mentioned in
HLS's post as problematic). Probably all of a 30 minute job.
+
+A supported tag in the html, jwcid="id@CopyOf" would be nice. We put all component definitions
in our .page files (as everyone should) to separate HTML development from Java development.
However, we typically need at least a couple of copies of links etc., and having such a tag
would be much cleaner than all the alias components that blindly make more ids with a number
tacked on the end!
+
  * Make Tapestry pages somehow "compileable", adding support for this for ANT and so on.
I'm going to make Ognl 3.0 generate java code (Dmitriy Kiriy, KiriyDmitriy at yandex.ru)
  * Better/easier support for invalidating session commonly needed for log out action. Or
at least some method for reinstantiation of visit object and forgetting all pages. 
 SteveGibson: Is this difficult - ["FrequentlyAskedQuestions/LogoutLink"]
@@ -12,12 +16,15 @@
     {{{ The cool thing is that once Tapestry is integrated with Hivemind you can add services
with all kinds
 of interesting functionality, like continuations or Spring-like transaction support. 
 In fact I believe that the current Tapestry services themselves (like Asset, Action, Page,
etc) are 
-going to become Hivemind services. }}}
+going to become Hivemind services. }}}  (- Why not Spring support as well - Joel)
  * Add runtime exception logging through commons-logging *along* with displaying them on
Exception page. Exception page is nice during development, but insufficient for deployment
since I cannot go through let's say file logs and see what happened badly yesterday. This
additional logging should not be performed inside default exception page class, since user
could specify his own exception page and forget to implement logging inside new class.
+    (Note by Joel: We used a production page with a hidden link to reveal the error message,
Tapestry doesn't need to be extended for this)
  * Add skinning functionality (add skin string to html search, i.e. file_skin_EN_US.html)
+     (- This was discussed on the forum, skinning would be great (and relatively easy to
add I would think), but this probably isn't the best way to go about it. - Joel)
  * Listener methods that take actual typed parameters rather than having to pull them from
service parameters
  * Cleaner URL's, to really help with ["J2EESecurity"]
  * Easier testability of Tapestry pages/components
+      - Static validation would be nice.
  * Fix for security hole in asset service
  * Allow simpler validation - for example, bypass invoking listener method and return to
same page if validation errors occur
  * Better support for hot deploy, allowing new page and component templates/specifications
to be picked up at runtime.  WebOGNL has a timestamp dependency check, which would be nice
to borrow from.
@@ -25,7 +32,7 @@
  * For component beans, add a set-static-property type of capability, instead of shoehorning
in a string using an expression setter.
  * Unified the way to process validation, make all form components support displayName property
and be able to support validator. Let the FieldLabel highlight the label automatically when
the field is required.
  * It would be great if there was a way to carry through form parameters.  Say I have pages
A and B.  B is a general purpose page used to lookup information.  It should be possible to
navigate from  A to B back to A and keep the form parameters of that were set in A.  At the
moment you would need to make B record the values in hidden fields then submit them back to
A or use persistent properties.  It would be great to be able to automatically pass these
parameters along without making B explicitly aware of A's parameters since B might be used
in other contexts.  Hope that makes sense.  It's hard to explain.
- * Allow use of "id" attribute instead of "jwcid", so that templates are truly pure HTML.
 Perhaps even make the scheme for tagging the binding name flexible.
+ * Allow use of "id" attribute instead of "jwcid", so that templates are truly pure HTML.
 Perhaps even make the scheme for tagging the binding name flexible. 
  * The biggest issue I have had (and have seen a lot others have) is with pleasing the rewind
cycle. The rewind has to be completely transparent which means we should by default make all
form elements serialize their state in hidden fields and allow the user to opt out.
  * Get ride of page specifications - I've got 13 pages, all listed in App.application, all
with Page.page files with just one line: <page-specification class="app.Page"/>. Perhaps
I use anonymous components too much, and page-specifications would be needed for more complex
pages, but it'd be great for trivial pages not to have to jump through these hoops and instead
get auto-looked up by package (e.g. put app.pages.* in App.application as an auto-lookup package)
 

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


Mime
View raw message