12:51 a.m.
You may have noticed by now that seam-gen has gotten a modest style
upgrade in the trunk. This upgrade is based on "style mods" I have
been maintaining while working on the source code for Seam in Action
(I had to dress up the screenshots for the show). Understand that this
is just a first step in making seam-gen applications look more
presentable, but nonetheless, and important first step.
Below is a list of the enhancements (perhaps something worth blogging about):
1. Added a favicon of the Seam logo
- personally, I think this is the coolest and simplest enhancement
- by the way, we should consider use this favicon for
seamframework.org because I made it transparent
2. Icons for each level of error message (warn, error, info)
3. Stripped the border and background from global messages and fixed
the indenting to accommodate the icons
- the messages were still using the style from the original orange
theme seam-gen projects had
4. Used a RichFaces XCSS resource so that the theme matches the
currently selected RichFaces theme
- I also applied some of the RichFaces gradients to form controls to
make the forms look better (w/ very little CSS)
The only downside of the new theme is that the Visual Editor in
JBossTools doesn't understand the XCSS file (which resides in the
stylesheets directory). Therefore, I left behind the old theme.css and
put an instruction in template.xhtml about switching to the static
theme.css for previews. It would be great if the Visual Editor could
interpret the XCSS file. This opens up so much flexibility for
extending the RichFaces theme.
The commit also came with some other goodies:
1. seam-gen WAR projects now have a consolidated compile target
2. two new targets reexplode and redeploy, which do a clean unexplode
explode or clean undeploy deploy, respectively
3. restart now detects if you have deployed an exploded or packaged
archive and restarts it appropriately (before it bombed if you had a
packaged archive deployed)
4. EAR projects now compile groovy scripts on the classpath (deploying
raw .groovy files requires more research)
5. Added a "head" named insertion in the template.xhtml so that you
can add additional markup in <head> on a per-page basis
6. Global messages now reside in template.xhtml with a Facelets
parameter you can use to turn them off on a per-page basis
7. Changed src/action to src/hot and src/model to src/main
8. Added the view folder to the classpath for tests so that page
actions defined in *.page.xml are invoked during testing (previously
the tests only read the global pages.xml file)
9. Added a javadoc task to the build
10. The default username is admin and the password is blank.
Developers never got to see the failure login scenario out of the box
because we let any credentials through (obviously, with the new
security stuff, we don't even need the authenticator component, but
that is a next step perhaps)
All in all, what these upgrades should do is make your demos of Seam
look just a touch prettier and give you a few more wrenches for
development. There are still plenty of improvements that could be
made.
-Dan
--
Dan Allen
Software consultant | Author of Seam in Action
http://mojavelinux.com
http://mojavelinux.com/seaminaction
NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but don't hear back for more than a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters. Please don't hesitate to resend a message if
you feel that it did not reach my attention.
5:45 a.m.
Got a screenshot?
On Wed, Oct 8, 2008 at 5:51 PM, Dan Allen <dan.j.allen(a)gmail.com> wrote:
You may have noticed by now that seam-gen has gotten a modest style
upgrade in the trunk. This upgrade is based on "style mods" I have
been maintaining while working on the source code for Seam in Action
(I had to dress up the screenshots for the show). Understand that this
is just a first step in making seam-gen applications look more
presentable, but nonetheless, and important first step.
Below is a list of the enhancements (perhaps something worth blogging about):
1. Added a favicon of the Seam logo
- personally, I think this is the coolest and simplest enhancement
- by the way, we should consider use this favicon for
seamframework.org because I made it transparent
2. Icons for each level of error message (warn, error, info)
3. Stripped the border and background from global messages and fixed
the indenting to accommodate the icons
- the messages were still using the style from the original orange
theme seam-gen projects had
4. Used a RichFaces XCSS resource so that the theme matches the
currently selected RichFaces theme
- I also applied some of the RichFaces gradients to form controls to
make the forms look better (w/ very little CSS)
The only downside of the new theme is that the Visual Editor in
JBossTools doesn't understand the XCSS file (which resides in the
stylesheets directory). Therefore, I left behind the old theme.css and
put an instruction in template.xhtml about switching to the static
theme.css for previews. It would be great if the Visual Editor could
interpret the XCSS file. This opens up so much flexibility for
extending the RichFaces theme.
The commit also came with some other goodies:
1. seam-gen WAR projects now have a consolidated compile target
2. two new targets reexplode and redeploy, which do a clean unexplode
explode or clean undeploy deploy, respectively
3. restart now detects if you have deployed an exploded or packaged
archive and restarts it appropriately (before it bombed if you had a
packaged archive deployed)
4. EAR projects now compile groovy scripts on the classpath (deploying
raw .groovy files requires more research)
5. Added a "head" named insertion in the template.xhtml so that you
can add additional markup in <head> on a per-page basis
6. Global messages now reside in template.xhtml with a Facelets
parameter you can use to turn them off on a per-page basis
7. Changed src/action to src/hot and src/model to src/main
8. Added the view folder to the classpath for tests so that page
actions defined in *.page.xml are invoked during testing (previously
the tests only read the global pages.xml file)
9. Added a javadoc task to the build
10. The default username is admin and the password is blank.
Developers never got to see the failure login scenario out of the box
because we let any credentials through (obviously, with the new
security stuff, we don't even need the authenticator component, but
that is a next step perhaps)
All in all, what these upgrades should do is make your demos of Seam
look just a touch prettier and give you a few more wrenches for
development. There are still plenty of improvements that could be
made.
-Dan
--
Dan Allen
Software consultant | Author of Seam in Action
http://mojavelinux.com
http://mojavelinux.com/seaminaction
NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but don't hear back for more than a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters. Please don't hesitate to resend a message if
you feel that it did not reach my attention.
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev
--
Gavin King
gavin.king(a)gmail.com
http://in.relation.to/Bloggers/Gavin
http://hibernate.org
http://seamframework.org
8:44 a.m.
Ah, yes, I forgot to send the screenshots. Here's the eye candy.
Disclaimer: The RichFaces colors don't always line up perfectly. It
was a bit of a game to find the right color to assign to each element.
Of course, it is simple enough to override the colors however you
choose, this is just a starting point.
-Dan
On Wed, Oct 8, 2008 at 11:45 PM, Gavin King <gavin(a)hibernate.org> wrote:
Got a screenshot?
On Wed, Oct 8, 2008 at 5:51 PM, Dan Allen <dan.j.allen(a)gmail.com> wrote:
> You may have noticed by now that seam-gen has gotten a modest style
> upgrade in the trunk. This upgrade is based on "style mods" I have
> been maintaining while working on the source code for Seam in Action
> (I had to dress up the screenshots for the show). Understand that this
> is just a first step in making seam-gen applications look more
> presentable, but nonetheless, and important first step.
>
> Below is a list of the enhancements (perhaps something worth blogging about):
>
> 1. Added a favicon of the Seam logo
> - personally, I think this is the coolest and simplest enhancement
> - by the way, we should consider use this favicon for
> seamframework.org because I made it transparent
> 2. Icons for each level of error message (warn, error, info)
> 3. Stripped the border and background from global messages and fixed
> the indenting to accommodate the icons
> - the messages were still using the style from the original orange
> theme seam-gen projects had
> 4. Used a RichFaces XCSS resource so that the theme matches the
> currently selected RichFaces theme
> - I also applied some of the RichFaces gradients to form controls to
> make the forms look better (w/ very little CSS)
>
> The only downside of the new theme is that the Visual Editor in
> JBossTools doesn't understand the XCSS file (which resides in the
> stylesheets directory). Therefore, I left behind the old theme.css and
> put an instruction in template.xhtml about switching to the static
> theme.css for previews. It would be great if the Visual Editor could
> interpret the XCSS file. This opens up so much flexibility for
> extending the RichFaces theme.
>
> The commit also came with some other goodies:
>
> 1. seam-gen WAR projects now have a consolidated compile target
> 2. two new targets reexplode and redeploy, which do a clean unexplode
> explode or clean undeploy deploy, respectively
> 3. restart now detects if you have deployed an exploded or packaged
> archive and restarts it appropriately (before it bombed if you had a
> packaged archive deployed)
> 4. EAR projects now compile groovy scripts on the classpath (deploying
> raw .groovy files requires more research)
> 5. Added a "head" named insertion in the template.xhtml so that you
> can add additional markup in <head> on a per-page basis
> 6. Global messages now reside in template.xhtml with a Facelets
> parameter you can use to turn them off on a per-page basis
> 7. Changed src/action to src/hot and src/model to src/main
> 8. Added the view folder to the classpath for tests so that page
> actions defined in *.page.xml are invoked during testing (previously
> the tests only read the global pages.xml file)
> 9. Added a javadoc task to the build
> 10. The default username is admin and the password is blank.
> Developers never got to see the failure login scenario out of the box
> because we let any credentials through (obviously, with the new
> security stuff, we don't even need the authenticator component, but
> that is a next step perhaps)
>
> All in all, what these upgrades should do is make your demos of Seam
> look just a touch prettier and give you a few more wrenches for
> development. There are still plenty of improvements that could be
> made.
>
> -Dan
>
> --
> Dan Allen
> Software consultant | Author of Seam in Action
>
> http://mojavelinux.com
> http://mojavelinux.com/seaminaction
>
> NOTE: While I make a strong effort to keep up with my email on a daily
> basis, personal or other work matters can sometimes keep me away
> from my email. If you contact me, but don't hear back for more than a week,
> it is very likely that I am excessively backlogged or the message was
> caught in the spam filters. Please don't hesitate to resend a message if
> you feel that it did not reach my attention.
> _______________________________________________
> seam-dev mailing list
> seam-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/seam-dev
>
--
Gavin King
gavin.king(a)gmail.com
http://in.relation.to/Bloggers/Gavin
http://hibernate.org
http://seamframework.org
--
Dan Allen
Software consultant | Author of Seam in Action
http://mojavelinux.com
http://mojavelinux.com/seaminaction
NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but don't hear back for more than a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters. Please don't hesitate to resend a message if
you feel that it did not reach my attention.
8:45 a.m.
Haha, you may be wondering how I figured out Gavin's birthday. It's
amazing what grep will tell you ;)
-Dan
On Thu, Oct 9, 2008 at 2:44 AM, Dan Allen <dan.j.allen(a)gmail.com> wrote:
Ah, yes, I forgot to send the screenshots. Here's the eye candy.
Disclaimer: The RichFaces colors don't always line up perfectly. It
was a bit of a game to find the right color to assign to each element.
Of course, it is simple enough to override the colors however you
choose, this is just a starting point.
-Dan
On Wed, Oct 8, 2008 at 11:45 PM, Gavin King <gavin(a)hibernate.org> wrote:
> Got a screenshot?
>
> On Wed, Oct 8, 2008 at 5:51 PM, Dan Allen <dan.j.allen(a)gmail.com> wrote:
>> You may have noticed by now that seam-gen has gotten a modest style
>> upgrade in the trunk. This upgrade is based on "style mods" I have
>> been maintaining while working on the source code for Seam in Action
>> (I had to dress up the screenshots for the show). Understand that this
>> is just a first step in making seam-gen applications look more
>> presentable, but nonetheless, and important first step.
>>
>> Below is a list of the enhancements (perhaps something worth blogging about):
>>
>> 1. Added a favicon of the Seam logo
>> - personally, I think this is the coolest and simplest enhancement
>> - by the way, we should consider use this favicon for
>> seamframework.org because I made it transparent
>> 2. Icons for each level of error message (warn, error, info)
>> 3. Stripped the border and background from global messages and fixed
>> the indenting to accommodate the icons
>> - the messages were still using the style from the original orange
>> theme seam-gen projects had
>> 4. Used a RichFaces XCSS resource so that the theme matches the
>> currently selected RichFaces theme
>> - I also applied some of the RichFaces gradients to form controls to
>> make the forms look better (w/ very little CSS)
>>
>> The only downside of the new theme is that the Visual Editor in
>> JBossTools doesn't understand the XCSS file (which resides in the
>> stylesheets directory). Therefore, I left behind the old theme.css and
>> put an instruction in template.xhtml about switching to the static
>> theme.css for previews. It would be great if the Visual Editor could
>> interpret the XCSS file. This opens up so much flexibility for
>> extending the RichFaces theme.
>>
>> The commit also came with some other goodies:
>>
>> 1. seam-gen WAR projects now have a consolidated compile target
>> 2. two new targets reexplode and redeploy, which do a clean unexplode
>> explode or clean undeploy deploy, respectively
>> 3. restart now detects if you have deployed an exploded or packaged
>> archive and restarts it appropriately (before it bombed if you had a
>> packaged archive deployed)
>> 4. EAR projects now compile groovy scripts on the classpath (deploying
>> raw .groovy files requires more research)
>> 5. Added a "head" named insertion in the template.xhtml so that you
>> can add additional markup in <head> on a per-page basis
>> 6. Global messages now reside in template.xhtml with a Facelets
>> parameter you can use to turn them off on a per-page basis
>> 7. Changed src/action to src/hot and src/model to src/main
>> 8. Added the view folder to the classpath for tests so that page
>> actions defined in *.page.xml are invoked during testing (previously
>> the tests only read the global pages.xml file)
>> 9. Added a javadoc task to the build
>> 10. The default username is admin and the password is blank.
>> Developers never got to see the failure login scenario out of the box
>> because we let any credentials through (obviously, with the new
>> security stuff, we don't even need the authenticator component, but
>> that is a next step perhaps)
>>
>> All in all, what these upgrades should do is make your demos of Seam
>> look just a touch prettier and give you a few more wrenches for
>> development. There are still plenty of improvements that could be
>> made.
>>
>> -Dan
>>
>> --
>> Dan Allen
>> Software consultant | Author of Seam in Action
>>
>> http://mojavelinux.com
>> http://mojavelinux.com/seaminaction
>>
>> NOTE: While I make a strong effort to keep up with my email on a daily
>> basis, personal or other work matters can sometimes keep me away
>> from my email. If you contact me, but don't hear back for more than a week,
>> it is very likely that I am excessively backlogged or the message was
>> caught in the spam filters. Please don't hesitate to resend a message if
>> you feel that it did not reach my attention.
>> _______________________________________________
>> seam-dev mailing list
>> seam-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>
>
>
>
> --
> Gavin King
> gavin.king(a)gmail.com
> http://in.relation.to/Bloggers/Gavin
> http://hibernate.org
> http://seamframework.org
>
--
Dan Allen
Software consultant | Author of Seam in Action
http://mojavelinux.com
http://mojavelinux.com/seaminaction
NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but don't hear back for more than a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters. Please don't hesitate to resend a message if
you feel that it did not reach my attention.
--
Dan Allen
Software consultant | Author of Seam in Action
http://mojavelinux.com
http://mojavelinux.com/seaminaction
NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but don't hear back for more than a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters. Please don't hesitate to resend a message if
you feel that it did not reach my attention.
7:22 p.m.
Well you got mine wrong. It's amazing what Facebook will tell you :p
On 9 Oct 2008, at 08:45, Dan Allen wrote:
Haha, you may be wondering how I figured out Gavin's birthday.
It's
amazing what grep will tell you ;)
-Dan
On Thu, Oct 9, 2008 at 2:44 AM, Dan Allen <dan.j.allen(a)gmail.com>
wrote:
> Ah, yes, I forgot to send the screenshots. Here's the eye candy.
>
> Disclaimer: The RichFaces colors don't always line up perfectly. It
> was a bit of a game to find the right color to assign to each
> element.
> Of course, it is simple enough to override the colors however you
> choose, this is just a starting point.
>
> -Dan
>
> On Wed, Oct 8, 2008 at 11:45 PM, Gavin King <gavin(a)hibernate.org>
> wrote:
>> Got a screenshot?
>>
>> On Wed, Oct 8, 2008 at 5:51 PM, Dan Allen <dan.j.allen(a)gmail.com>
>> wrote:
>>> You may have noticed by now that seam-gen has gotten a modest style
>>> upgrade in the trunk. This upgrade is based on "style mods" I have
>>> been maintaining while working on the source code for Seam in
>>> Action
>>> (I had to dress up the screenshots for the show). Understand that
>>> this
>>> is just a first step in making seam-gen applications look more
>>> presentable, but nonetheless, and important first step.
>>>
>>> Below is a list of the enhancements (perhaps something worth
>>> blogging about):
>>>
>>> 1. Added a favicon of the Seam logo
>>> - personally, I think this is the coolest and simplest enhancement
>>> - by the way, we should consider use this favicon for
>>> seamframework.org because I made it transparent
>>> 2. Icons for each level of error message (warn, error, info)
>>> 3. Stripped the border and background from global messages and
>>> fixed
>>> the indenting to accommodate the icons
>>> - the messages were still using the style from the original orange
>>> theme seam-gen projects had
>>> 4. Used a RichFaces XCSS resource so that the theme matches the
>>> currently selected RichFaces theme
>>> - I also applied some of the RichFaces gradients to form controls
>>> to
>>> make the forms look better (w/ very little CSS)
>>>
>>> The only downside of the new theme is that the Visual Editor in
>>> JBossTools doesn't understand the XCSS file (which resides in the
>>> stylesheets directory). Therefore, I left behind the old
>>> theme.css and
>>> put an instruction in template.xhtml about switching to the static
>>> theme.css for previews. It would be great if the Visual Editor
>>> could
>>> interpret the XCSS file. This opens up so much flexibility for
>>> extending the RichFaces theme.
>>>
>>> The commit also came with some other goodies:
>>>
>>> 1. seam-gen WAR projects now have a consolidated compile target
>>> 2. two new targets reexplode and redeploy, which do a clean
>>> unexplode
>>> explode or clean undeploy deploy, respectively
>>> 3. restart now detects if you have deployed an exploded or packaged
>>> archive and restarts it appropriately (before it bombed if you
>>> had a
>>> packaged archive deployed)
>>> 4. EAR projects now compile groovy scripts on the classpath
>>> (deploying
>>> raw .groovy files requires more research)
>>> 5. Added a "head" named insertion in the template.xhtml so that
you
>>> can add additional markup in <head> on a per-page basis
>>> 6. Global messages now reside in template.xhtml with a Facelets
>>> parameter you can use to turn them off on a per-page basis
>>> 7. Changed src/action to src/hot and src/model to src/main
>>> 8. Added the view folder to the classpath for tests so that page
>>> actions defined in *.page.xml are invoked during testing
>>> (previously
>>> the tests only read the global pages.xml file)
>>> 9. Added a javadoc task to the build
>>> 10. The default username is admin and the password is blank.
>>> Developers never got to see the failure login scenario out of the
>>> box
>>> because we let any credentials through (obviously, with the new
>>> security stuff, we don't even need the authenticator component, but
>>> that is a next step perhaps)
>>>
>>> All in all, what these upgrades should do is make your demos of
>>> Seam
>>> look just a touch prettier and give you a few more wrenches for
>>> development. There are still plenty of improvements that could be
>>> made.
>>>
>>> -Dan
>>>
>>> --
>>> Dan Allen
>>> Software consultant | Author of Seam in Action
>>>
>>> http://mojavelinux.com
>>> http://mojavelinux.com/seaminaction
>>>
>>> NOTE: While I make a strong effort to keep up with my email on a
>>> daily
>>> basis, personal or other work matters can sometimes keep me away
>>> from my email. If you contact me, but don't hear back for more
>>> than a week,
>>> it is very likely that I am excessively backlogged or the message
>>> was
>>> caught in the spam filters. Please don't hesitate to resend a
>>> message if
>>> you feel that it did not reach my attention.
>>> _______________________________________________
>>> seam-dev mailing list
>>> seam-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>>
>>
>>
>>
>> --
>> Gavin King
>> gavin.king(a)gmail.com
>> http://in.relation.to/Bloggers/Gavin
>> http://hibernate.org
>> http://seamframework.org
>>
>
>
>
> --
> Dan Allen
> Software consultant | Author of Seam in Action
>
> http://mojavelinux.com
> http://mojavelinux.com/seaminaction
>
> NOTE: While I make a strong effort to keep up with my email on a
> daily
> basis, personal or other work matters can sometimes keep me away
> from my email. If you contact me, but don't hear back for more than
> a week,
> it is very likely that I am excessively backlogged or the message was
> caught in the spam filters. Please don't hesitate to resend a
> message if
> you feel that it did not reach my attention.
>
--
Dan Allen
Software consultant | Author of Seam in Action
http://mojavelinux.com
http://mojavelinux.com/seaminaction
NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but don't hear back for more than
a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters. Please don't hesitate to resend a
message if
you feel that it did not reach my attention.
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev
10:44 p.m.
did'nt someone from this list by the name of dan blast someone mercilessly for a
similar Off Topic question?
while we're on the subject I dont use facebook because one of the qualifying criteria
is your age
so if youre over 40 they CAN legally d(s^r*m)n$t@..
and thus all the wonderful pics of my far flung family i wont be able to see
Thank You
Martin
______________________________________________
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official business of Sender.
This transmission is of a confidential nature and Sender does not endorse distribution to
any party other than intended recipient. Sender does not necessarily endorse content
contained within this transmission.
From: pmuir(a)redhat.com
To: dan.j.allen(a)gmail.com
Subject: Re: [seam-dev] a modest seam-gen style upgrade
Date: Thu, 9 Oct 2008 19:22:48 +0200
CC: seam-dev(a)lists.jboss.org
Well you got mine wrong. It's amazing what Facebook will tell you :p
On 9 Oct 2008, at 08:45, Dan Allen wrote:
> Haha, you may be wondering how I figured out Gavin's birthday. It's
> amazing what grep will tell you ;)
>
> -Dan
>
> On Thu, Oct 9, 2008 at 2:44 AM, Dan Allen <dan.j.allen(a)gmail.com>
> wrote:
>> Ah, yes, I forgot to send the screenshots. Here's the eye candy.
>>
>> Disclaimer: The RichFaces colors don't always line up perfectly. It
>> was a bit of a game to find the right color to assign to each
>> element.
>> Of course, it is simple enough to override the colors however you
>> choose, this is just a starting point.
>>
>> -Dan
>>
>> On Wed, Oct 8, 2008 at 11:45 PM, Gavin King <gavin(a)hibernate.org>
>> wrote:
>>> Got a screenshot?
>>>
>>> On Wed, Oct 8, 2008 at 5:51 PM, Dan Allen <dan.j.allen(a)gmail.com>
>>> wrote:
>>>> You may have noticed by now that seam-gen has gotten a modest style
>>>> upgrade in the trunk. This upgrade is based on "style mods" I
have
>>>> been maintaining while working on the source code for Seam in
>>>> Action
>>>> (I had to dress up the screenshots for the show). Understand that
>>>> this
>>>> is just a first step in making seam-gen applications look more
>>>> presentable, but nonetheless, and important first step.
>>>>
>>>> Below is a list of the enhancements (perhaps something worth
>>>> blogging about):
>>>>
>>>> 1. Added a favicon of the Seam logo
>>>> - personally, I think this is the coolest and simplest enhancement
>>>> - by the way, we should consider use this favicon for
>>>> seamframework.org because I made it transparent
>>>> 2. Icons for each level of error message (warn, error, info)
>>>> 3. Stripped the border and background from global messages and
>>>> fixed
>>>> the indenting to accommodate the icons
>>>> - the messages were still using the style from the original orange
>>>> theme seam-gen projects had
>>>> 4. Used a RichFaces XCSS resource so that the theme matches the
>>>> currently selected RichFaces theme
>>>> - I also applied some of the RichFaces gradients to form controls
>>>> to
>>>> make the forms look better (w/ very little CSS)
>>>>
>>>> The only downside of the new theme is that the Visual Editor in
>>>> JBossTools doesn't understand the XCSS file (which resides in the
>>>> stylesheets directory). Therefore, I left behind the old
>>>> theme.css and
>>>> put an instruction in template.xhtml about switching to the static
>>>> theme.css for previews. It would be great if the Visual Editor
>>>> could
>>>> interpret the XCSS file. This opens up so much flexibility for
>>>> extending the RichFaces theme.
>>>>
>>>> The commit also came with some other goodies:
>>>>
>>>> 1. seam-gen WAR projects now have a consolidated compile target
>>>> 2. two new targets reexplode and redeploy, which do a clean
>>>> unexplode
>>>> explode or clean undeploy deploy, respectively
>>>> 3. restart now detects if you have deployed an exploded or packaged
>>>> archive and restarts it appropriately (before it bombed if you
>>>> had a
>>>> packaged archive deployed)
>>>> 4. EAR projects now compile groovy scripts on the classpath
>>>> (deploying
>>>> raw .groovy files requires more research)
>>>> 5. Added a "head" named insertion in the template.xhtml so
that you
>>>> can add additional markup in <head> on a per-page basis
>>>> 6. Global messages now reside in template.xhtml with a Facelets
>>>> parameter you can use to turn them off on a per-page basis
>>>> 7. Changed src/action to src/hot and src/model to src/main
>>>> 8. Added the view folder to the classpath for tests so that page
>>>> actions defined in *.page.xml are invoked during testing
>>>> (previously
>>>> the tests only read the global pages.xml file)
>>>> 9. Added a javadoc task to the build
>>>> 10. The default username is admin and the password is blank.
>>>> Developers never got to see the failure login scenario out of the
>>>> box
>>>> because we let any credentials through (obviously, with the new
>>>> security stuff, we don't even need the authenticator component, but
>>>> that is a next step perhaps)
>>>>
>>>> All in all, what these upgrades should do is make your demos of
>>>> Seam
>>>> look just a touch prettier and give you a few more wrenches for
>>>> development. There are still plenty of improvements that could be
>>>> made.
>>>>
>>>> -Dan
>>>>
>>>> --
>>>> Dan Allen
>>>> Software consultant | Author of Seam in Action
>>>>
>>>> http://mojavelinux.com
>>>> http://mojavelinux.com/seaminaction
>>>>
>>>> NOTE: While I make a strong effort to keep up with my email on a
>>>> daily
>>>> basis, personal or other work matters can sometimes keep me away
>>>> from my email. If you contact me, but don't hear back for more
>>>> than a week,
>>>> it is very likely that I am excessively backlogged or the message
>>>> was
>>>> caught in the spam filters. Please don't hesitate to resend a
>>>> message if
>>>> you feel that it did not reach my attention.
>>>> _______________________________________________
>>>> seam-dev mailing list
>>>> seam-dev(a)lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>>>
>>>
>>>
>>>
>>> --
>>> Gavin King
>>> gavin.king(a)gmail.com
>>> http://in.relation.to/Bloggers/Gavin
>>> http://hibernate.org
>>> http://seamframework.org
>>>
>>
>>
>>
>> --
>> Dan Allen
>> Software consultant | Author of Seam in Action
>>
>> http://mojavelinux.com
>> http://mojavelinux.com/seaminaction
>>
>> NOTE: While I make a strong effort to keep up with my email on a
>> daily
>> basis, personal or other work matters can sometimes keep me away
>> from my email. If you contact me, but don't hear back for more than
>> a week,
>> it is very likely that I am excessively backlogged or the message was
>> caught in the spam filters. Please don't hesitate to resend a
>> message if
>> you feel that it did not reach my attention.
>>
>
>
>
> --
> Dan Allen
> Software consultant | Author of Seam in Action
>
> http://mojavelinux.com
> http://mojavelinux.com/seaminaction
>
> NOTE: While I make a strong effort to keep up with my email on a daily
> basis, personal or other work matters can sometimes keep me away
> from my email. If you contact me, but don't hear back for more than
> a week,
> it is very likely that I am excessively backlogged or the message was
> caught in the spam filters. Please don't hesitate to resend a
> message if
> you feel that it did not reach my attention.
> _______________________________________________
> seam-dev mailing list
> seam-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/seam-dev
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev
_________________________________________________________________
Get more out of the Web. Learn 10 hidden secrets of Windows Live.
http://windowslive.com/connect/post/jamiethomson.spaces.live.com-Blog-cns...
9:38 p.m.
Thanks, looks good :)
On Thu, Oct 9, 2008 at 1:44 AM, Dan Allen <dan.j.allen(a)gmail.com> wrote:
Ah, yes, I forgot to send the screenshots. Here's the eye candy.
Disclaimer: The RichFaces colors don't always line up perfectly. It
was a bit of a game to find the right color to assign to each element.
Of course, it is simple enough to override the colors however you
choose, this is just a starting point.
-Dan
On Wed, Oct 8, 2008 at 11:45 PM, Gavin King <gavin(a)hibernate.org> wrote:
> Got a screenshot?
>
> On Wed, Oct 8, 2008 at 5:51 PM, Dan Allen <dan.j.allen(a)gmail.com> wrote:
>> You may have noticed by now that seam-gen has gotten a modest style
>> upgrade in the trunk. This upgrade is based on "style mods" I have
>> been maintaining while working on the source code for Seam in Action
>> (I had to dress up the screenshots for the show). Understand that this
>> is just a first step in making seam-gen applications look more
>> presentable, but nonetheless, and important first step.
>>
>> Below is a list of the enhancements (perhaps something worth blogging about):
>>
>> 1. Added a favicon of the Seam logo
>> - personally, I think this is the coolest and simplest enhancement
>> - by the way, we should consider use this favicon for
>> seamframework.org because I made it transparent
>> 2. Icons for each level of error message (warn, error, info)
>> 3. Stripped the border and background from global messages and fixed
>> the indenting to accommodate the icons
>> - the messages were still using the style from the original orange
>> theme seam-gen projects had
>> 4. Used a RichFaces XCSS resource so that the theme matches the
>> currently selected RichFaces theme
>> - I also applied some of the RichFaces gradients to form controls to
>> make the forms look better (w/ very little CSS)
>>
>> The only downside of the new theme is that the Visual Editor in
>> JBossTools doesn't understand the XCSS file (which resides in the
>> stylesheets directory). Therefore, I left behind the old theme.css and
>> put an instruction in template.xhtml about switching to the static
>> theme.css for previews. It would be great if the Visual Editor could
>> interpret the XCSS file. This opens up so much flexibility for
>> extending the RichFaces theme.
>>
>> The commit also came with some other goodies:
>>
>> 1. seam-gen WAR projects now have a consolidated compile target
>> 2. two new targets reexplode and redeploy, which do a clean unexplode
>> explode or clean undeploy deploy, respectively
>> 3. restart now detects if you have deployed an exploded or packaged
>> archive and restarts it appropriately (before it bombed if you had a
>> packaged archive deployed)
>> 4. EAR projects now compile groovy scripts on the classpath (deploying
>> raw .groovy files requires more research)
>> 5. Added a "head" named insertion in the template.xhtml so that you
>> can add additional markup in <head> on a per-page basis
>> 6. Global messages now reside in template.xhtml with a Facelets
>> parameter you can use to turn them off on a per-page basis
>> 7. Changed src/action to src/hot and src/model to src/main
>> 8. Added the view folder to the classpath for tests so that page
>> actions defined in *.page.xml are invoked during testing (previously
>> the tests only read the global pages.xml file)
>> 9. Added a javadoc task to the build
>> 10. The default username is admin and the password is blank.
>> Developers never got to see the failure login scenario out of the box
>> because we let any credentials through (obviously, with the new
>> security stuff, we don't even need the authenticator component, but
>> that is a next step perhaps)
>>
>> All in all, what these upgrades should do is make your demos of Seam
>> look just a touch prettier and give you a few more wrenches for
>> development. There are still plenty of improvements that could be
>> made.
>>
>> -Dan
>>
>> --
>> Dan Allen
>> Software consultant | Author of Seam in Action
>>
>> http://mojavelinux.com
>> http://mojavelinux.com/seaminaction
>>
>> NOTE: While I make a strong effort to keep up with my email on a daily
>> basis, personal or other work matters can sometimes keep me away
>> from my email. If you contact me, but don't hear back for more than a week,
>> it is very likely that I am excessively backlogged or the message was
>> caught in the spam filters. Please don't hesitate to resend a message if
>> you feel that it did not reach my attention.
>> _______________________________________________
>> seam-dev mailing list
>> seam-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>
>
>
>
> --
> Gavin King
> gavin.king(a)gmail.com
> http://in.relation.to/Bloggers/Gavin
> http://hibernate.org
> http://seamframework.org
>
--
Dan Allen
Software consultant | Author of Seam in Action
http://mojavelinux.com
http://mojavelinux.com/seaminaction
NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but don't hear back for more than a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters. Please don't hesitate to resend a message if
you feel that it did not reach my attention.
--
Gavin King
gavin.king(a)gmail.com
http://in.relation.to/Bloggers/Gavin
http://hibernate.org
http://seamframework.org
5671
days inactive
5672
days old
6 comments
4 participants
participants (4)
-
Dan Allen -
Gavin King -
Martin Gainty -
Pete Muir