Re: I want to build a Tapestry 5 Eclipse plugin editor
My two cents:
- Project setup isn't a particularly big deal for me since I can do
this through Maven. If you do make the plugin create the project,
make sure it is flexible enough to handle projects that already exist
and isn't tied to a specific tapestry release.
- Checkout the paid version of IDEA as it offers some nice code
completion features in the template.
- Loom will let you switch back and forth between the .java and the
corresponding .tml file.
- If you want to create something graphical, I'd take a look at how
the WebObjects editor use to work. You may be able to find a
screenshot somewhere. Basically at the bottom of the page, you had a
list of all the property objects that were available for the page.
You could click on one and see all of its properties and drill down
until you found what you were looking for. Then you could drag that
property and drop it on the editor where you wanted it to appear. I
found it to be very convenient even though it wasn't a full WYSIWYG
environment.
Here are three things that would probably give the biggest
productivity gains in order of importance.
1. Switch between .tml and .java files (Loom does this already). It
would be nice if you could open both the .java and cooresponding .tml
side by side rather than just switching between them.
2. Autocomplete for tapestry built in components. So when you type
:
> Hi guys,
>
> I have been involved in Tapestry for years, usually build my project in
> Eclipse. But I can not find fantastic Eclipse plugin for Taperstry. Now, if
> we use Tapestry 5 to build our web project, it is more convinent, but i
> think there is a good editor for Taperstry 5, Tapestry will be much more
> cool.
>
> So i want to build a Eclipse based editor for Tapestry 5, and build it as an
> Google Summer of Code 2011 project, below is my mainly idea, helping for
> your ideas and feedback. If anyone has interest in it, please let me know,
> Thank you :-)
>
> Features:
>
> 1.Tapestry project feature, such as import tapestry 5 libraries, project
> wizards, add default Tapestry package structure and so on.
>In one word, once we create a Tapestry project, it is created with
> required package structure and web.xml content.
>
> 2.One tapestry page includes one Java class file and one HTML based template
> file. It seems like Microsoft's asp.net in Visual Studio somewhere.
>We can edit the java class file and template file together. So, this
> tool supply a convinent editor for tapestry page. It has design view and
> source view.
>I. source view
>we can edit template file source in this view. and this view supply
> property tips and keyword highlight functions.
>For example, there are attributes "testA" and "testB" in its
> cosspending Java class file. If you want to get the property value, you
> should input "${prop:testA}" in template file,this view will supply auto
> complete function for you after you input "${prop:t}",you can select "testA"
> or "testB".
>
>II.design view
>this view is a more powful HTML editor, we can build it on some open
> souce Eclipse HTML editor. Besides,we can set component's property value in
> this view, add listener for components.
>For example, if we double click a form's submit button named
> "submitButton" in this view, it will add a function
> "onSuccessFromSubmitButton" in its cosspending Java class,this function is
> used to handler form submit action.
>
> 3.supply customization feature for Tapestry page editor. For example, we can
> setup different color for different Java web component in template file.
>
>
> -
> Best Regards
> Gavin Lei (雷银)
> Email: gavingui2...@gmail.com
>
-
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
Should default.css include CSS reset?
http://meyerweb.com/eric/tools/css/reset/ This might help with some of the issues about formatting being off in IE but ok in functional browsers. -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
Re: Should default.css include CSS reset?
+1 from me. Makes plain sense to me. Kalle On Wed, Jan 26, 2011 at 11:05 AM, Howard Lewis Ship wrote: > http://meyerweb.com/eric/tools/css/reset/ > > This might help with some of the issues about formatting being off in > IE but ok in functional browsers. > > -- > Howard M. Lewis Ship > > Creator of Apache Tapestry > > The source for Tapestry training, mentoring and support. Contact me to > learn how I can get you up and productive in Tapestry fast! > > (971) 678-5210 > http://howardlewisship.com > > - > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org > For additional commands, e-mail: dev-h...@tapestry.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
Re: [jira] Closed: (TAP5-409) Localization documentation should be clear that Tapestry (and Java) do not support BOM headers in message catalog files
How do we go about with setting fix versions for documentation now that it's decoupled from the
releases? Do we just leave it out?
On 26.01.2011 21:32, Ulrich Stärk (JIRA) wrote:
[
https://issues.apache.org/jira/browse/TAP5-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ulrich Stärk closed TAP5-409.
-
Resolution: Fixed
Fixed in the documentation wiki at
https://cwiki.apache.org/confluence/display/TAPESTRY/Localization
Localization documentation should be clear that Tapestry (and Java) do not
support BOM headers in message catalog files
---
Key: TAP5-409
URL: https://issues.apache.org/jira/browse/TAP5-409
Project: Tapestry 5
Issue Type: Bug
Affects Versions: 5.0.15, 5.0.16, 5.0.17
Reporter: Borut Bolcina
Assignee: Ulrich Stärk
Attachments: locale-not-working.zip
app.properties has 3 entries:
openid-provider-title=OpenID provider
my-account-link=My account
login-link=Login
index.tml
http://tapestry.apache.org/schema/tapestry_5_0_0.xsd";>
${message:openid-provider-title}
${message:my-account-link} odjava
${message:login-link}
I also have two other lozalized properties files. Depending on the browser
preffered language selection the correct translatinos are displayed - EXCEPT
the first entry, which always falls back to english.
I first noticed this behaviour when playing arounf with EditBean - the
translated labels all worked, well, except the first one. Whichever entry was
the first in the file, that label was not translated.
-
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
Re: Should default.css include CSS reset?
-1 I don't like the idea of dictating designs beyond the standard layout of our components to the users. On 26.01.2011 20:05, Howard Lewis Ship wrote: http://meyerweb.com/eric/tools/css/reset/ This might help with some of the issues about formatting being off in IE but ok in functional browsers. - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
Re: Should default.css include CSS reset?
Well, we do need a solution to some common components (such as Errors) not rendering properly in IE ... and I'd prefer to do something that fixes that problem forever, rather than always having to wonder. That's what a CSS reset does, but I can see the downside of it (a mockup of a page, once converted to T5, might look different). On Wed, Jan 26, 2011 at 12:39 PM, Ulrich Stärk wrote: > -1 > > I don't like the idea of dictating designs beyond the standard layout of our > components to the users. > > On 26.01.2011 20:05, Howard Lewis Ship wrote: >> >> http://meyerweb.com/eric/tools/css/reset/ >> >> This might help with some of the issues about formatting being off in >> IE but ok in functional browsers. >> > > - > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org > For additional commands, e-mail: dev-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
Re: [jira] Closed: (TAP5-409) Localization documentation should be clear that Tapestry (and Java) do not support BOM headers in message catalog files
yes, leave it blank - that's what i remember too.
I guess the only documentation issues that will have
a fix version will be those related to javadocs
On Wed, Jan 26, 2011 at 22:37, Ulrich Stärk wrote:
> How do we go about with setting fix versions for documentation now that it's
> decoupled from the releases? Do we just leave it out?
>
> On 26.01.2011 21:32, Ulrich Stärk (JIRA) wrote:
>>
>> [
>> https://issues.apache.org/jira/browse/TAP5-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>> ]
>>
>> Ulrich Stärk closed TAP5-409.
>> -
>>
>> Resolution: Fixed
>>
>> Fixed in the documentation wiki at
>> https://cwiki.apache.org/confluence/display/TAPESTRY/Localization
>>
>>> Localization documentation should be clear that Tapestry (and Java) do
>>> not support BOM headers in message catalog files
>>>
>>> ---
>>>
>>> Key: TAP5-409
>>> URL: https://issues.apache.org/jira/browse/TAP5-409
>>> Project: Tapestry 5
>>> Issue Type: Bug
>>> Affects Versions: 5.0.15, 5.0.16, 5.0.17
>>> Reporter: Borut Bolcina
>>> Assignee: Ulrich Stärk
>>> Attachments: locale-not-working.zip
>>>
>>>
>>> app.properties has 3 entries:
>>> openid-provider-title=OpenID provider
>>> my-account-link=My account
>>> login-link=Login
>>> index.tml
>>> http://tapestry.apache.org/schema/tapestry_5_0_0.xsd";>
>>>
>>> ${message:openid-provider-title}
>>> >> href="${asset:context:css/iopenid.css}" />
>>>
>>>
>>>
>>> >> t:page="AccountEdit" href="#">${message:my-account-link} >> t:type="actionlink" t:id="logout">odjava
>>>
>>> >> href="#">${message:login-link}
>>>
>>>
>>>
>>>
>>> I also have two other lozalized properties files. Depending on the
>>> browser preffered language selection the correct translatinos are displayed
>>> - EXCEPT the first entry, which always falls back to english.
>>> I first noticed this behaviour when playing arounf with EditBean - the
>>> translated labels all worked, well, except the first one. Whichever entry
>>> was the first in the file, that label was not translated.
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: dev-h...@tapestry.apache.org
>
>
--
Andreas Andreou - andy...@apache.org - http://blog.andyhot.gr
Tapestry PMC / Tacos developer
Open Source / JEE Consulting
-
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
Re: svn commit: r1063860 - in /tapestry/tapestry5/trunk/quickstart/src/main/resources: META-INF/maven/ archetype-resources/src/main/java/components/ archetype-resources/src/main/resources/components/
This is going to be very cool. One thing I noticed too late with the Concrete layout was that form fields rendered very large and ugly ... hopefully this will look better. Has anyone tried this design with a BeanEditForm, Grid or BeanDisplay component? On Wed, Jan 26, 2011 at 12:11 PM, wrote: > Author: uli > Date: Wed Jan 26 20:11:49 2011 > New Revision: 1063860 > > URL: http://svn.apache.org/viewvc?rev=1063860&view=rev > Log: > TAP5-1323: Change Quickstart Template to Match New Site Design > > Thanks to Mark Shead for the patch. > > Added: > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/default.css > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/bg.png > (with props) > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/tapestry.png > (with props) > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/tapestry_s.png > (with props) > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/top-bg.png > (with props) > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/reset.css > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/style.css > Removed: > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img01.jpg > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img02.jpg > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img03.jpg > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img04.jpg > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img05.gif > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img06.gif > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img07.gif > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img08.gif > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img09.gif > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img10.gif > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img11.gif > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img12.gif > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img13.gif > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img14.gif > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img15.gif > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img16.gif > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img17.gif > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img18.gif > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img19.gif > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img20.gif > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/spacer.gif > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/layout.css > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/license.txt > Modified: > > tapestry/tapestry5/trunk/quickstart/src/main/resources/META-INF/maven/archetype-metadata.xml > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/java/components/Layout.java > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/resources/components/Layout.tml > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/resources/pages/About.tml > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/resources/pages/Contact.tml > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/resources/p
Re: Should default.css include CSS reset?
On Wed, 26 Jan 2011 17:05:20 -0200, Howard Lewis Ship wrote: http://meyerweb.com/eric/tools/css/reset/ This might help with some of the issues about formatting being off in IE but ok in functional browsers. +1, as long as there's a symbole to remove or override it. -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
Re: Tapestry subprojects (was: [jira] Commented: (TAP5-1421) Create a standard way to track messages to be presented to the user)
I agree (maybe because that was almost what I suggested, but with different words). :) On Tue, 25 Jan 2011 20:03:04 -0200, Howard Lewis Ship wrote: I think we need to gravitate towards the approach that requires the least amount of coordination and administrative overhead. Maybe it could be different if more of the Tapestry developers were under a single roof, but adding in any kind of overhead tends to tank any attempt at a regular release schedule. I'm comfortable with creating a new module to hold auxiliary components and services, maybe several additional modules. A sexy name for that would be nice, maybe "tapestry-extras". I'm also comfortable with the idea of new modules "incubating" out in the world and being brought into Tapestry once they've solidified. On Tue, Jan 25, 2011 at 1:38 PM, Andreas Andreou wrote: So, in order to go on with adding / accepting new modules / subprojects (such as the cayenne integration module discussed at http://markmail.org/message/5l7xi6srkcfwepeo ) and have a clear vision of how things will be, let me recap the alternatives mentioned here... 1) New modules live in https://svn.apache.org/repos/asf/tapestry/tapestry5/trunk/ Releases are performed for all subprojects at the exact same time (and hence for the same version). This process is what we currently employ and thus requires no further explanation. 2) New modules can be created outside of https://svn.apache.org/repos/asf/tapestry/tapestry5/trunk/ perhaps in https://svn.apache.org/repos/asf/tapestry/tapestry5-module-name. Releases will not have to be performed at the same exact time for all those new subprojects BUT when they do occur they have to use the exact version number of the tapestry core modules they target. The differences in this process are: a) each module gets its own truck, branches and tags. This allows the module to also release versions compatible with older tapestry versions if there's such a need (so tapestry-cayenne can release a 5.2.x version) b) timing of the releases doesn't have to coincide 100% - so, "unfinished" subprojects don't have to stall the rest of the releases. Additionally, it becomes easier to accept "experimental" subprojects c) it might not be possible to guarantee same release numbers in all subprojects - that would result in maintenance and support problems as well as user frustration Now, we haven't run a vote on which to choose as my original intention in this thread was to get a first understanding of what the other devs think on the matter. From the responses, I get that most prefer to keep things as described in 1), so there's no real point in running a vote... but as i said, it's good to see where everyone stands :) Thx. On Fri, Jan 21, 2011 at 19:47, Massimo Lusetti wrote: On Fri, Jan 21, 2011 at 6:47 PM, Massimo Lusetti wrote: On Fri, Jan 21, 2011 at 6:34 PM, Howard Lewis Ship wrote: I also agree; we now have consistent tests to ensure that tapestry-ioc 5.3.7 works with tapestry-core 5.3.7 works with tapestry-spring 5.3.7. If each had its own version, you end up in a situation where you need complex tables to try and guess which version goes with which other. I guess inter-module dependencies may streamline this, but I think it still is more complicated than having a consistent version number. Having a separate release engineering is totally different from version number but I agree with the fact that a precise and consistent dependency management. ... a precise and consistent dependency management have to be present before starting to separate projects. Cheers -- Massimo http://meridio.blogspot.com - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org -- Andreas Andreou - andy...@apache.org - http://blog.andyhot.gr Tapestry PMC / Tacos developer Open Source / JEE Consulting - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, Ars Machina Tecnologia da Informação Ltda. Consultor, desenvolvedor e instrutor em Java, Tapestry e Hibernate Coordenador e professor da Especialização em Engenharia de Software com Ênfase em Java da Faculdade Pitágoras http://www.arsmachina.com.br - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
Re: Should default.css include CSS reset?
+2 about being able to disable it all-together (rather than replacing with something else). Dan Adams Principal Software Engineer iFactory, A Division of RDW Group, Inc. Innovative, inspiring, intelligent interactive solutions for the world’s leading institutions Direct: 617.235.5857 www.ifactory.com @iFactoryBoston From: "Thiago H. de Paula Figueiredo" To: "Tapestry development" , "Howard Lewis Ship" Sent: Wednesday, January 26, 2011 5:47:29 PM Subject: Re: Should default.css include CSS reset? On Wed, 26 Jan 2011 17:05:20 -0200, Howard Lewis Ship wrote: > http://meyerweb.com/eric/tools/css/reset/ > This might help with some of the issues about formatting being off in > IE but ok in functional browsers. +1, as long as there's a symbole to remove or override it. -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
Re: svn commit: r1063860 - in /tapestry/tapestry5/trunk/quickstart/src/main/resources: META-INF/maven/ archetype-resources/src/main/java/components/ archetype-resources/src/main/resources/components/
I'am not using the layout yet but I get this http://twitpic.com/3tp4o1 with default.css and style.css. HTH 2011/1/26 Howard Lewis Ship > This is going to be very cool. One thing I noticed too late with the > Concrete layout was that form fields rendered very large and ugly ... > hopefully this will look better. Has anyone tried this design with a > BeanEditForm, Grid or BeanDisplay component? > > On Wed, Jan 26, 2011 at 12:11 PM, wrote: > > Author: uli > > Date: Wed Jan 26 20:11:49 2011 > > New Revision: 1063860 > > > > URL: http://svn.apache.org/viewvc?rev=1063860&view=rev > > Log: > > TAP5-1323: Change Quickstart Template to Match New Site Design > > > > Thanks to Mark Shead for the patch. > > > > Added: > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/default.css > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/bg.png > (with props) > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/tapestry.png > (with props) > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/tapestry_s.png > (with props) > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/top-bg.png > (with props) > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/reset.css > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/style.css > > Removed: > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img01.jpg > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img02.jpg > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img03.jpg > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img04.jpg > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img05.gif > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img06.gif > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img07.gif > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img08.gif > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img09.gif > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img10.gif > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img11.gif > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img12.gif > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img13.gif > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img14.gif > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img15.gif > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img16.gif > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img17.gif > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img18.gif > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img19.gif > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img20.gif > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/spacer.gif > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/layout.css > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/license.txt > > Modified: > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/META-INF/maven/archetype-metadata.xml > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/java/components/Layout.java > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/resources/components/Layout.tml > > > > tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/resources
Re: Should default.css include CSS reset?
-1 for me as well. ideally tapestry component's css wouldn't change the style of anything outside of that components containers. On Wed, Jan 26, 2011 at 12:39 PM, Ulrich Stärk wrote: > -1 > > I don't like the idea of dictating designs beyond the standard layout of our > components to the users. > > On 26.01.2011 20:05, Howard Lewis Ship wrote: >> >> http://meyerweb.com/eric/tools/css/reset/ >> >> This might help with some of the issues about formatting being off in >> IE but ok in functional browsers. >> > > - > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org > For additional commands, e-mail: dev-h...@tapestry.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
Re: I want to build a Tapestry 5 Eclipse plugin editor
Hi Mark,
Thank you for your reply, that is what in my mind :-)
As we know, Tapestry focus on components, each page is made up of many
compoents. This development model like Visual Studio very much, if we
develop C# asp.net application, each page is made up of a .aspx file and a
.cs file, and Visual Studio supply a editor for us to edit these two files
together, we can easily transfer between these two files, even we can not
feel that they are two files. Page property view is also a necessary part of
this editor. This design model help me much when i was developing
asp.netapplication.
Tapestry focus on components too, i think Java open source community should
supply such a convinent development environment like Visual Studio for
Tapestry, this will improve develop feeling, help us much. So i want to
finish a editor for Tapestry
在 2011年1月27日 上午12:35，Mark 写道：
> My two cents:
>
> - Project setup isn't a particularly big deal for me since I can do
> this through Maven. If you do make the plugin create the project,
> make sure it is flexible enough to handle projects that already exist
> and isn't tied to a specific tapestry release.
>
> - Checkout the paid version of IDEA as it offers some nice code
> completion features in the template.
>
> - Loom will let you switch back and forth between the .java and the
> corresponding .tml file.
>
> - If you want to create something graphical, I'd take a look at how
> the WebObjects editor use to work. You may be able to find a
> screenshot somewhere. Basically at the bottom of the page, you had a
> list of all the property objects that were available for the page.
> You could click on one and see all of its properties and drill down
> until you found what you were looking for. Then you could drag that
> property and drop it on the editor where you wanted it to appear. I
> found it to be very convenient even though it wasn't a full WYSIWYG
> environment.
>
> Here are three things that would probably give the biggest
> productivity gains in order of importance.
>
> 1. Switch between .tml and .java files (Loom does this already). It
> would be nice if you could open both the .java and cooresponding .tml
> side by side rather than just switching between them.
>
> 2. Autocomplete for tapestry built in components. So when you type
> with the required parameters listed. (There is a how to for setting
> this up using the schema and the .jsp editor, but it didn't seem to
> work for me last time I tried it.)
>
> 3. Autocomplete for custom components. I think there is a how to, to
> create a schema to do this using the .jsp editor as well, but I didn't
> have any luck with it during the brief time I played with it.
>
> 4. Autocomplete of properties from the .java page when editing the
> .tml file. When it is setup correctly IDEA does a reasonable job of
> this.
>
> 5. Some type of drag and drop to put properties from the .java file
> into the .tml file. (Could be a GUI, but wouldn't have to be.)
>
> At least those are my thoughts on what would be the most useful features.
>
> Mark
>
> 2011/1/26 Gavin Lei :
> > Hi guys,
> >
> > I have been involved in Tapestry for years, usually build my project in
> > Eclipse. But I can not find fantastic Eclipse plugin for Taperstry. Now,
> if
> > we use Tapestry 5 to build our web project, it is more convinent, but i
> > think there is a good editor for Taperstry 5, Tapestry will be much more
> > cool.
> >
> > So i want to build a Eclipse based editor for Tapestry 5, and build it as
> an
> > Google Summer of Code 2011 project, below is my mainly idea, helping for
> > your ideas and feedback. If anyone has interest in it, please let me
> know,
> > Thank you :-)
> >
> > Features:
> >
> > 1.Tapestry project feature, such as import tapestry 5 libraries, project
> > wizards, add default Tapestry package structure and so on.
> >In one word, once we create a Tapestry project, it is created with
> > required package structure and web.xml content.
> >
> > 2.One tapestry page includes one Java class file and one HTML based
> template
> > file. It seems like Microsoft's asp.net in Visual Studio somewhere.
> >We can edit the java class file and template file together. So, this
> > tool supply a convinent editor for tapestry page. It has design view and
> > source view.
> >I. source view
> >we can edit template file source in this view. and this view
> supply
> > property tips and keyword highlight functions.
> >For example, there are attributes "testA" and "testB" in its
> > cosspending Java class file. If you want to get the property value, you
> > should input "${prop:testA}" in template file,this view will supply
> auto
> > complete function for you after you input "${prop:t}",you can select
> "testA"
> > or "testB".
> >
> >II.design view
> >this view is a more powful HTML editor, we can build it on some
> open
> > souce Eclipse HTML editor. Besides,we can set component's property value
> in
> > thi
Re: I want to build a Tapestry 5 Eclipse plugin editor
Gavin, Your plans are quite ambitious and your efforts will be very much appreciated by Tapestry users if you can accomplish even a few of your goals. In terms of priorities, I agree with Mark's list. Also: I hope you'll use the Apache License 2.0 I started developing a more modest Tapestry-Eclipse plugin myself a month ago. I haven't made enough progress yet to show anybody, but if you happen to not start on yours for a month or two then please check back with me to see if I have anything decent to give you as a starting point. My approach also combines the editing of tml and java source (and component message catalogs, too), but only as separate editor "pages" (tabs at the bottom of the editor) rather than in a fancy graphical drag-and-drop editor. 2011/1/26 Gavin Lei : > Hi Mark, > > Thank you for your reply, that is what in my mind :-) > > As we know, Tapestry focus on components, each page is made up of many > compoents. This development model like Visual Studio very much, if we > develop C# asp.net application, each page is made up of a .aspx file and a > .cs file, and Visual Studio supply a editor for us to edit these two files > together, we can easily transfer between these two files, even we can not > feel that they are two files. Page property view is also a necessary part of > this editor. This design model help me much when i was developing > asp.netapplication. > > Tapestry focus on components too, i think Java open source community should > supply such a convinent development environment like Visual Studio for > Tapestry, this will improve develop feeling, help us much. So i want to > finish a editor for Tapestry > > 在 2011年1月27日 上午12:35，Mark 写道： > >> My two cents: >> >> - Project setup isn't a particularly big deal for me since I can do >> this through Maven. If you do make the plugin create the project, >> make sure it is flexible enough to handle projects that already exist >> and isn't tied to a specific tapestry release. >> >> - Checkout the paid version of IDEA as it offers some nice code >> completion features in the template. >> >> - Loom will let you switch back and forth between the .java and the >> corresponding .tml file. >> >> - If you want to create something graphical, I'd take a look at how >> the WebObjects editor use to work. You may be able to find a >> screenshot somewhere. Basically at the bottom of the page, you had a >> list of all the property objects that were available for the page. >> You could click on one and see all of its properties and drill down >> until you found what you were looking for. Then you could drag that >> property and drop it on the editor where you wanted it to appear. I >> found it to be very convenient even though it wasn't a full WYSIWYG >> environment. >> >> Here are three things that would probably give the biggest >> productivity gains in order of importance. >> >> 1. Switch between .tml and .java files (Loom does this already). It >> would be nice if you could open both the .java and cooresponding .tml >> side by side rather than just switching between them. >> >> 2. Autocomplete for tapestry built in components. So when you type >> > with the required parameters listed. (There is a how to for setting >> this up using the schema and the .jsp editor, but it didn't seem to >> work for me last time I tried it.) >> >> 3. Autocomplete for custom components. I think there is a how to, to >> create a schema to do this using the .jsp editor as well, but I didn't >> have any luck with it during the brief time I played with it. >> >> 4. Autocomplete of properties from the .java page when editing the >> .tml file. When it is setup correctly IDEA does a reasonable job of >> this. >> >> 5. Some type of drag and drop to put properties from the .java file >> into the .tml file. (Could be a GUI, but wouldn't have to be.) >> >> At least those are my thoughts on what would be the most useful features. >> >> Mark >> >> 2011/1/26 Gavin Lei : >> > Hi guys, >> > >> > I have been involved in Tapestry for years, usually build my project in >> > Eclipse. But I can not find fantastic Eclipse plugin for Taperstry. Now, >> if >> > we use Tapestry 5 to build our web project, it is more convinent, but i >> > think there is a good editor for Taperstry 5, Tapestry will be much more >> > cool. >> > >> > So i want to build a Eclipse based editor for Tapestry 5, and build it as >> an >> > Google Summer of Code 2011 project, below is my mainly idea, helping for >> > your ideas and feedback. If anyone has interest in it, please let me >> know, >> > Thank you :-) >> > >> > Features: >> > >> > 1.Tapestry project feature, such as import tapestry 5 libraries, project >> > wizards, add default Tapestry package structure and so on. >> >In one word, once we create a Tapestry project, it is created with >> > required package structure and web.xml content. >> > >> > 2.One tapestry page includes one Java class file and one HTML based >> template >> > file. It seems lik
Re: I want to build a Tapestry 5 Eclipse plugin editor
Hi Bob, It seems that you have started you job for months, what do you have yet ? May be we can discuss details here. When i search "Tapestry eclipse plunge" in google, we can get lots of result and get some editor, but they are all not perfect, or even not avaiable, so, i think a editor which can improve Tapertry development progress is really needed 在 2011年1月27日 上午10:26，Bob Harner 写道： > Gavin, > > Your plans are quite ambitious and your efforts will be very much > appreciated by Tapestry users if you can accomplish even a few of your > goals. > > In terms of priorities, I agree with Mark's list. > > Also: I hope you'll use the Apache License 2.0 > > I started developing a more modest Tapestry-Eclipse plugin myself a > month ago. I haven't made enough progress yet to show anybody, but if > you happen to not start on yours for a month or two then please check > back with me to see if I have anything decent to give you as a > starting point. My approach also combines the editing of tml and java > source (and component message catalogs, too), but only as separate > editor "pages" (tabs at the bottom of the editor) rather than in a > fancy graphical drag-and-drop editor. > > 2011/1/26 Gavin Lei : > > Hi Mark, > > > > Thank you for your reply, that is what in my mind :-) > > > > As we know, Tapestry focus on components, each page is made up of many > > compoents. This development model like Visual Studio very much, if we > > develop C# asp.net application, each page is made up of a .aspx file and > a > > .cs file, and Visual Studio supply a editor for us to edit these two > files > > together, we can easily transfer between these two files, even we can not > > feel that they are two files. Page property view is also a necessary part > of > > this editor. This design model help me much when i was developing > > asp.netapplication. > > > > Tapestry focus on components too, i think Java open source community > should > > supply such a convinent development environment like Visual Studio for > > Tapestry, this will improve develop feeling, help us much. So i want to > > finish a editor for Tapestry > > > > 在 2011年1月27日 上午12:35，Mark 写道： > > > >> My two cents: > >> > >> - Project setup isn't a particularly big deal for me since I can do > >> this through Maven. If you do make the plugin create the project, > >> make sure it is flexible enough to handle projects that already exist > >> and isn't tied to a specific tapestry release. > >> > >> - Checkout the paid version of IDEA as it offers some nice code > >> completion features in the template. > >> > >> - Loom will let you switch back and forth between the .java and the > >> corresponding .tml file. > >> > >> - If you want to create something graphical, I'd take a look at how > >> the WebObjects editor use to work. You may be able to find a > >> screenshot somewhere. Basically at the bottom of the page, you had a > >> list of all the property objects that were available for the page. > >> You could click on one and see all of its properties and drill down > >> until you found what you were looking for. Then you could drag that > >> property and drop it on the editor where you wanted it to appear. I > >> found it to be very convenient even though it wasn't a full WYSIWYG > >> environment. > >> > >> Here are three things that would probably give the biggest > >> productivity gains in order of importance. > >> > >> 1. Switch between .tml and .java files (Loom does this already). It > >> would be nice if you could open both the .java and cooresponding .tml > >> side by side rather than just switching between them. > >> > >> 2. Autocomplete for tapestry built in components. So when you type > >> >> with the required parameters listed. (There is a how to for setting > >> this up using the schema and the .jsp editor, but it didn't seem to > >> work for me last time I tried it.) > >> > >> 3. Autocomplete for custom components. I think there is a how to, to > >> create a schema to do this using the .jsp editor as well, but I didn't > >> have any luck with it during the brief time I played with it. > >> > >> 4. Autocomplete of properties from the .java page when editing the > >> .tml file. When it is setup correctly IDEA does a reasonable job of > >> this. > >> > >> 5. Some type of drag and drop to put properties from the .java file > >> into the .tml file. (Could be a GUI, but wouldn't have to be.) > >> > >> At least those are my thoughts on what would be the most useful > features. > >> > >> Mark > >> > >> 2011/1/26 Gavin Lei : > >> > Hi guys, > >> > > >> > I have been involved in Tapestry for years, usually build my project > in > >> > Eclipse. But I can not find fantastic Eclipse plugin for Taperstry. > Now, > >> if > >> > we use Tapestry 5 to build our web project, it is more convinent, but > i > >> > think there is a good editor for Taperstry 5, Tapestry will be much > more > >> > cool. > >> > > >> > So i want to build a Eclipse based editor for Tapestry 5,
Re: svn commit: r1063860 - in /tapestry/tapestry5/trunk/quickstart/src/main/resources: META-INF/maven/ archetype-resources/src/main/java/components/ archetype-resources/src/main/resources/components/
Looks exactly as it should, or am I missing something? Uli On 27.01.2011 01:03, françois facon wrote: I'am not using the layout yet but I get this http://twitpic.com/3tp4o1 with default.css and style.css. HTH 2011/1/26 Howard Lewis Ship This is going to be very cool. One thing I noticed too late with the Concrete layout was that form fields rendered very large and ugly ... hopefully this will look better. Has anyone tried this design with a BeanEditForm, Grid or BeanDisplay component? On Wed, Jan 26, 2011 at 12:11 PM, wrote: Author: uli Date: Wed Jan 26 20:11:49 2011 New Revision: 1063860 URL: http://svn.apache.org/viewvc?rev=1063860&view=rev Log: TAP5-1323: Change Quickstart Template to Match New Site Design Thanks to Mark Shead for the patch. Added: tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/default.css tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/bg.png (with props) tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/tapestry.png (with props) tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/tapestry_s.png (with props) tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/top-bg.png (with props) tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/reset.css tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/style.css Removed: tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img01.jpg tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img02.jpg tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img03.jpg tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img04.jpg tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img05.gif tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img06.gif tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img07.gif tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img08.gif tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img09.gif tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img10.gif tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img11.gif tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img12.gif tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img13.gif tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img14.gif tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img15.gif tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img16.gif tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img17.gif tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img18.gif tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img19.gif tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/img20.gif tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/images/spacer.gif tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/layout.css tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/webapp/layout/license.txt Modified: tapestry/tapestry5/trunk/quickstart/src/main/resources/META-INF/maven/archetype-metadata.xml tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/java/components/Layout.java tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/resources/components/Layout.tml tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resources/src/main/resources/pages/About.tml tapestry/tapestry5/trunk/quickstart/src/main/resources/archetype-resourc
