Re: Using fluido once available
On Sun, Dec 23, 2012 at 3:11 AM, Martin Gainty mgai...@hotmail.com wrote: Matt/Christian which mobile configuration are you testing on? Basically you can test it with just making Chrome/fFirefox etc small in width. Besides, you can use: Opera Mobile Emu: http://de.opera.com/developer/tools/mobile/ Ripple: http://incubator.apache.org/projects/ripple.html The Android SDK has an emu, and XCode too. I personally add Android 2.3 devices to the list of above Merry x-mas! Cheers Christian Frohe Weihnachten Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. From: grobme...@gmail.com Date: Sat, 22 Dec 2012 17:35:55 +0100 Subject: Re: Using fluido once available To: dev@struts.apache.org It doesnt look like it (looked into the css code) I will patch it after xmas Thanks! On Sat, Dec 22, 2012 at 5:29 PM, Matt Raible m...@raibledesigns.com wrote: Just noticed the new site doesn't look great on mobile. Is Bootstrap's responsive CSS included in the theme? Screenshot at: http://flickr.com/photos/mraible/8296526787/ On Dec 22, 2012, at 11:19, Christian Grobmeier grobme...@gmail.com wrote: On Sat, Dec 22, 2012 at 5:00 PM, Lukasz Lenart lukaszlen...@apache.org wrote: 2012/12/21 Lukasz Lenart lukaszlen...@apache.org: Almost forget about that, but I think we have silent consensus here, so I'm going to finish releasing 2.3.8 and then I'll merge and release the new website :-) New website is out - kudos to Christian! Well, and to all the other people who left countless comments, patched it, merged it and so on :-) Anyway I've noticed that we should use fluido for the Struts2 subsite as well - it looks a bit old-fashioned compering to main site ;-) Agreed! And I already found a few minor things to fix (hovering buttons looks not so good and so on) Cheers merry xmax too! Christian Cheers Merry Christmas! -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
RE: Using fluido once available
I was hoping you would say Android which is easy to test since Manfreds maven-android-plugin is now available does anyone have iPhone SDK so we can incorporate testing on iPhone into the pom? if not where does one acquire iPhone SDK? Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. From: grobme...@gmail.com Date: Sun, 23 Dec 2012 12:11:19 +0100 Subject: Re: Using fluido once available To: dev@struts.apache.org On Sun, Dec 23, 2012 at 3:11 AM, Martin Gainty mgai...@hotmail.com wrote: Matt/Christian which mobile configuration are you testing on? Basically you can test it with just making Chrome/fFirefox etc small in width. Besides, you can use: Opera Mobile Emu: http://de.opera.com/developer/tools/mobile/ Ripple: http://incubator.apache.org/projects/ripple.html The Android SDK has an emu, and XCode too. I personally add Android 2.3 devices to the list of above Merry x-mas! Cheers Christian Frohe Weihnachten Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. From: grobme...@gmail.com Date: Sat, 22 Dec 2012 17:35:55 +0100 Subject: Re: Using fluido once available To: dev@struts.apache.org It doesnt look like it (looked into the css code) I will patch it after xmas Thanks! On Sat, Dec 22, 2012 at 5:29 PM, Matt Raible m...@raibledesigns.com wrote: Just noticed the new site doesn't look great on mobile. Is Bootstrap's responsive CSS included in the theme? Screenshot at: http://flickr.com/photos/mraible/8296526787/ On Dec 22, 2012, at 11:19, Christian Grobmeier grobme...@gmail.com wrote: On Sat, Dec 22, 2012 at 5:00 PM, Lukasz Lenart lukaszlen...@apache.org wrote: 2012/12/21 Lukasz Lenart lukaszlen...@apache.org: Almost forget about that, but I think we have silent consensus here, so I'm going to finish releasing 2.3.8 and then I'll merge and release the new website :-) New website is out - kudos to Christian! Well, and to all the other people who left countless comments, patched it, merged it and so on :-) Anyway I've noticed that we should use fluido for the Struts2 subsite as well - it looks a bit old-fashioned compering to main site ;-) Agreed! And I already found a few minor things to fix (hovering buttons looks not so good and so on) Cheers merry xmax too! Christian Cheers Merry Christmas! -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org -- http
Re: Using fluido once available
Martin, On Sun, Dec 23, 2012 at 4:42 PM, Martin Gainty mgai...@hotmail.com wrote: I was hoping you would say Android which is easy to test since Manfreds maven-android-plugin is now available does anyone have iPhone SDK so we can incorporate testing on iPhone into the pom? if not where does one acquire iPhone SDK? you can test for iPhone with XCode. It has an Emulator included not only for iPad but also for iPhone versions. It has a cost of 4$ in the App-Store. But honestly I am confused - with the mentioned plug you would create apk files. Currently we have only discussed how the web page looks on mobile browsers. Do you want to create some kind of app out of it? Cheers Christian Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. From: grobme...@gmail.com Date: Sun, 23 Dec 2012 12:11:19 +0100 Subject: Re: Using fluido once available To: dev@struts.apache.org On Sun, Dec 23, 2012 at 3:11 AM, Martin Gainty mgai...@hotmail.com wrote: Matt/Christian which mobile configuration are you testing on? Basically you can test it with just making Chrome/fFirefox etc small in width. Besides, you can use: Opera Mobile Emu: http://de.opera.com/developer/tools/mobile/ Ripple: http://incubator.apache.org/projects/ripple.html The Android SDK has an emu, and XCode too. I personally add Android 2.3 devices to the list of above Merry x-mas! Cheers Christian Frohe Weihnachten Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. From: grobme...@gmail.com Date: Sat, 22 Dec 2012 17:35:55 +0100 Subject: Re: Using fluido once available To: dev@struts.apache.org It doesnt look like it (looked into the css code) I will patch it after xmas Thanks! On Sat, Dec 22, 2012 at 5:29 PM, Matt Raible m...@raibledesigns.com wrote: Just noticed the new site doesn't look great on mobile. Is Bootstrap's responsive CSS included in the theme? Screenshot at: http://flickr.com/photos/mraible/8296526787/ On Dec 22, 2012, at 11:19, Christian Grobmeier grobme...@gmail.com wrote: On Sat, Dec 22, 2012 at 5:00 PM, Lukasz Lenart lukaszlen...@apache.org wrote: 2012/12/21 Lukasz Lenart lukaszlen...@apache.org: Almost forget about that, but I think we have silent consensus here, so I'm going to finish releasing 2.3.8 and then I'll merge and release the new website :-) New website is out - kudos to Christian! Well, and to all the other people who left countless comments, patched it, merged it and so on :-) Anyway I've noticed that we should use fluido for the Struts2 subsite as well - it looks a bit old-fashioned compering to main site ;-) Agreed! And I already found a few minor things to fix (hovering buttons looks not so good and so on) Cheers merry xmax too! Christian Cheers Merry Christmas! -- Łukasz + 48 606 323 122 http://www.lenart.org.pl
RE: Using fluido once available
Christian makes a Good Point It would make sense to stick with Emulators I am envisioning: EmulatorMode first (to achieve a smooth integration into pom) and get all the distro's builtnew suite of test-cases to flesh out rendering issues such as what Matt saw APK distro's (the real deal) would come after Emulator distros are built and test-cases have been run are there sites where one can acquire (APK-Emulator) versions of XCode? Thanks, Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. From: grobme...@gmail.com Date: Sun, 23 Dec 2012 20:37:03 +0100 Subject: Re: Using fluido once available To: dev@struts.apache.org Martin, On Sun, Dec 23, 2012 at 4:42 PM, Martin Gainty mgai...@hotmail.com wrote: I was hoping you would say Android which is easy to test since Manfreds maven-android-plugin is now available does anyone have iPhone SDK so we can incorporate testing on iPhone into the pom? if not where does one acquire iPhone SDK? you can test for iPhone with XCode. It has an Emulator included not only for iPad but also for iPhone versions. It has a cost of 4$ in the App-Store. But honestly I am confused - with the mentioned plug you would create apk files. Currently we have only discussed how the web page looks on mobile browsers. Do you want to create some kind of app out of it? Cheers Christian Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. From: grobme...@gmail.com Date: Sun, 23 Dec 2012 12:11:19 +0100 Subject: Re: Using fluido once available To: dev@struts.apache.org On Sun, Dec 23, 2012 at 3:11 AM, Martin Gainty mgai...@hotmail.com wrote: Matt/Christian which mobile configuration are you testing on? Basically you can test it with just making Chrome/fFirefox etc small in width. Besides, you can use: Opera Mobile Emu: http://de.opera.com/developer/tools/mobile/ Ripple: http://incubator.apache.org/projects/ripple.html The Android SDK has an emu, and XCode too. I personally add Android 2.3 devices to the list of above Merry x-mas! Cheers Christian Frohe Weihnachten Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce
Re: Using fluido once available
2012/12/21 Lukasz Lenart lukaszlen...@apache.org: Almost forget about that, but I think we have silent consensus here, so I'm going to finish releasing 2.3.8 and then I'll merge and release the new website :-) New website is out - kudos to Christian! Anyway I've noticed that we should use fluido for the Struts2 subsite as well - it looks a bit old-fashioned compering to main site ;-) Cheers Merry Christmas! -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
On Sat, Dec 22, 2012 at 5:00 PM, Lukasz Lenart lukaszlen...@apache.org wrote: 2012/12/21 Lukasz Lenart lukaszlen...@apache.org: Almost forget about that, but I think we have silent consensus here, so I'm going to finish releasing 2.3.8 and then I'll merge and release the new website :-) New website is out - kudos to Christian! Well, and to all the other people who left countless comments, patched it, merged it and so on :-) Anyway I've noticed that we should use fluido for the Struts2 subsite as well - it looks a bit old-fashioned compering to main site ;-) Agreed! And I already found a few minor things to fix (hovering buttons looks not so good and so on) Cheers merry xmax too! Christian Cheers Merry Christmas! -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
Just noticed the new site doesn't look great on mobile. Is Bootstrap's responsive CSS included in the theme? Screenshot at: http://flickr.com/photos/mraible/8296526787/ On Dec 22, 2012, at 11:19, Christian Grobmeier grobme...@gmail.com wrote: On Sat, Dec 22, 2012 at 5:00 PM, Lukasz Lenart lukaszlen...@apache.org wrote: 2012/12/21 Lukasz Lenart lukaszlen...@apache.org: Almost forget about that, but I think we have silent consensus here, so I'm going to finish releasing 2.3.8 and then I'll merge and release the new website :-) New website is out - kudos to Christian! Well, and to all the other people who left countless comments, patched it, merged it and so on :-) Anyway I've noticed that we should use fluido for the Struts2 subsite as well - it looks a bit old-fashioned compering to main site ;-) Agreed! And I already found a few minor things to fix (hovering buttons looks not so good and so on) Cheers merry xmax too! Christian Cheers Merry Christmas! -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
It doesnt look like it (looked into the css code) I will patch it after xmas Thanks! On Sat, Dec 22, 2012 at 5:29 PM, Matt Raible m...@raibledesigns.com wrote: Just noticed the new site doesn't look great on mobile. Is Bootstrap's responsive CSS included in the theme? Screenshot at: http://flickr.com/photos/mraible/8296526787/ On Dec 22, 2012, at 11:19, Christian Grobmeier grobme...@gmail.com wrote: On Sat, Dec 22, 2012 at 5:00 PM, Lukasz Lenart lukaszlen...@apache.org wrote: 2012/12/21 Lukasz Lenart lukaszlen...@apache.org: Almost forget about that, but I think we have silent consensus here, so I'm going to finish releasing 2.3.8 and then I'll merge and release the new website :-) New website is out - kudos to Christian! Well, and to all the other people who left countless comments, patched it, merged it and so on :-) Anyway I've noticed that we should use fluido for the Struts2 subsite as well - it looks a bit old-fashioned compering to main site ;-) Agreed! And I already found a few minor things to fix (hovering buttons looks not so good and so on) Cheers merry xmax too! Christian Cheers Merry Christmas! -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
RE: Using fluido once available
Matt/Christian which mobile configuration are you testing on? Frohe Weihnachten Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. From: grobme...@gmail.com Date: Sat, 22 Dec 2012 17:35:55 +0100 Subject: Re: Using fluido once available To: dev@struts.apache.org It doesnt look like it (looked into the css code) I will patch it after xmas Thanks! On Sat, Dec 22, 2012 at 5:29 PM, Matt Raible m...@raibledesigns.com wrote: Just noticed the new site doesn't look great on mobile. Is Bootstrap's responsive CSS included in the theme? Screenshot at: http://flickr.com/photos/mraible/8296526787/ On Dec 22, 2012, at 11:19, Christian Grobmeier grobme...@gmail.com wrote: On Sat, Dec 22, 2012 at 5:00 PM, Lukasz Lenart lukaszlen...@apache.org wrote: 2012/12/21 Lukasz Lenart lukaszlen...@apache.org: Almost forget about that, but I think we have silent consensus here, so I'm going to finish releasing 2.3.8 and then I'll merge and release the new website :-) New website is out - kudos to Christian! Well, and to all the other people who left countless comments, patched it, merged it and so on :-) Anyway I've noticed that we should use fluido for the Struts2 subsite as well - it looks a bit old-fashioned compering to main site ;-) Agreed! And I already found a few minor things to fix (hovering buttons looks not so good and so on) Cheers merry xmax too! Christian Cheers Merry Christmas! -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
Chrome on iOS 6 / iPhone 4s. On Dec 22, 2012, at 9:11 PM, Martin Gainty mgai...@hotmail.com wrote: Matt/Christian which mobile configuration are you testing on? Frohe Weihnachten Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. From: grobme...@gmail.com Date: Sat, 22 Dec 2012 17:35:55 +0100 Subject: Re: Using fluido once available To: dev@struts.apache.org It doesnt look like it (looked into the css code) I will patch it after xmas Thanks! On Sat, Dec 22, 2012 at 5:29 PM, Matt Raible m...@raibledesigns.com wrote: Just noticed the new site doesn't look great on mobile. Is Bootstrap's responsive CSS included in the theme? Screenshot at: http://flickr.com/photos/mraible/8296526787/ On Dec 22, 2012, at 11:19, Christian Grobmeier grobme...@gmail.com wrote: On Sat, Dec 22, 2012 at 5:00 PM, Lukasz Lenart lukaszlen...@apache.org wrote: 2012/12/21 Lukasz Lenart lukaszlen...@apache.org: Almost forget about that, but I think we have silent consensus here, so I'm going to finish releasing 2.3.8 and then I'll merge and release the new website :-) New website is out - kudos to Christian! Well, and to all the other people who left countless comments, patched it, merged it and so on :-) Anyway I've noticed that we should use fluido for the Struts2 subsite as well - it looks a bit old-fashioned compering to main site ;-) Agreed! And I already found a few minor things to fix (hovering buttons looks not so good and so on) Cheers merry xmax too! Christian Cheers Merry Christmas! -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
+1 Lukasz Lenart lukaszlen...@apache.org schrieb: What do you think, should we release the new website ? I would like to merge Christian changes back to trunk and release it. Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org -- Sent from my mobile phone
Re: Using fluido once available
2012/12/21 Rene Gielen gie...@it-neering.net: +1 Almost forget about that, but I think we have silent consensus here, so I'm going to finish releasing 2.3.8 and then I'll merge and release the new website :-) Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
What do you think, should we release the new website ? I would like to merge Christian changes back to trunk and release it. Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
On Wed, Dec 19, 2012 at 10:44 PM, Lukasz Lenart lukaszlen...@apache.org wrote: What do you think, should we release the new website ? I would like to merge Christian changes back to trunk and release it. I am fine with it - release often and early, some wise man once said. Surely will could work on the website forever Of course ym opinion is biased :-) Cheers Christian Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
On Mon, Dec 3, 2012 at 12:41 AM, Martin Cooper mfncoo...@gmail.com wrote: We have an official Twitter account - @TheApacheStruts - which we use to spread news about Struts and to interact with our community. Just like @TheASF, @TheApacheTomcat or @ApacheJames. On Facebook, there is as well a page voluntarily maintained by Struts PMC members, called Struts2 Users. Objective: spreading and dispatching news, interacting with the community. Currently 1400+ likes aka followers. See: https://www.facebook.com/apachestruts On G+, there is again an page voluntarily maintained by Struts PMC members, called Apache Struts. Objective: spreading and dispatching news, interacting with the community. Currently more than 3700 people are following. See: https://plus.google.com/+ApacheStruts/posts See also on G+: Apache Software Foundation, Apache TomEE The idea is to link this pages to our site just like we did with the twitter account in the branch (and other Apache projects do as well on their front page). So how is this supporting commercial enterprises? One could argue that we are using (free) services of commercial companies, yes. We do that all the time at Apache. I fail to see how this is promoting Twitter, Google or Facebook as companies. If 100 other companies came along and asked us to put links to their sites on our site, would we do it? If not, why not? Would we be selective, or add anyone who asked? If the former, what are the criteria? Why isn't LinkedIn in the same group as the special three we've chosen to advertise? Because we are free to chose our tools. If volunteers he want to maintain FB, G+ and Twitter and link to the accounts there, it is fine. It is a service to our users, because they can read news in the tools of their choice. If the project choses LinkedIn as another tool, we should link it as well. Criteria is: does the PMC want to use the tool? Yes - link. No - no link. Similar to maven: we use maven because we like it. If the Gradle team would ask us to support Gradle, what would we say? Ironically, the latter two are getting prominent ASF support since they are platinum sponsors: http://apache.org/foundation/thanks.html Sponsorship does *not* buy favours. That's very explicit. And that is also why there is a specific, foundation-central, and non-project-specific thank you page. I don't see what Sponsorship has something to do with our toolset. Linking to Struts related resources on Twitter, G+ or Facebook is as much of a support for commercial enterprises as linking to Struts Sourceforge is or Struts GitHub would be - free community resources offered and hosted free of charge by a commercial enterprise like SourceForge and GitHub. Once we've checked with our legal people, and this usage has been approved by them, I'll be fine with it. Until then, I'm very conscious that the ASF is legally a charity, and is subject to losing that status if we don't abide by the rules. So I would rather ask the question and get the official answer than discover that we were responsible for the ASF losing its status over an assumption we made. There was an e-mail from Simone Tripodi to the Board mailing list (11.01.2011). Shane Cucuru responded and it was very clear to me that projects are free to use the social media they want. We just need to take care on the branding, be able to let other PMC members access these tools and to make clear, if the channel does speak on the projects behalf or not. Maybe I don't get the issue right, but imho this whole discussion is just about one question: can we link to our Twitter/Facebook/G+ channel or not. And given the fact we are allowed to use these tools, why should we not be allowed to link to them? Cheers Christian -- Martin Cooper - René -- Martin Cooper [...] -- René Gielen http://twitter.com/rgielen - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
On Tue, Nov 27, 2012 at 11:51 PM, Rene Gielen rgie...@apache.org wrote: Am 28.11.12 06:14, schrieb Martin Cooper: On Tue, Nov 27, 2012 at 1:55 PM, Johannes Geppert jo...@apache.org wrote: It looks there is a broad agreement related to the projects links and the Roadmap FAQ. So i have dropped it from the site. Also I have added a Facebook and G+ Integration beside the Twitter Integration. Looks like this is our current News Section. ;-) Why are we supporting commercial enterprises from our site? As a 501(c)3 organisation, are we allowed to do that? We have an official Twitter account - @TheApacheStruts - which we use to spread news about Struts and to interact with our community. Just like @TheASF, @TheApacheTomcat or @ApacheJames. On Facebook, there is as well a page voluntarily maintained by Struts PMC members, called Struts2 Users. Objective: spreading and dispatching news, interacting with the community. Currently 1400+ likes aka followers. See: https://www.facebook.com/apachestruts On G+, there is again an page voluntarily maintained by Struts PMC members, called Apache Struts. Objective: spreading and dispatching news, interacting with the community. Currently more than 3700 people are following. See: https://plus.google.com/+ApacheStruts/posts See also on G+: Apache Software Foundation, Apache TomEE The idea is to link this pages to our site just like we did with the twitter account in the branch (and other Apache projects do as well on their front page). So how is this supporting commercial enterprises? One could argue that we are using (free) services of commercial companies, yes. We do that all the time at Apache. I fail to see how this is promoting Twitter, Google or Facebook as companies. If 100 other companies came along and asked us to put links to their sites on our site, would we do it? If not, why not? Would we be selective, or add anyone who asked? If the former, what are the criteria? Why isn't LinkedIn in the same group as the special three we've chosen to advertise? Ironically, the latter two are getting prominent ASF support since they are platinum sponsors: http://apache.org/foundation/thanks.html Sponsorship does *not* buy favours. That's very explicit. And that is also why there is a specific, foundation-central, and non-project-specific thank you page. Linking to Struts related resources on Twitter, G+ or Facebook is as much of a support for commercial enterprises as linking to Struts Sourceforge is or Struts GitHub would be - free community resources offered and hosted free of charge by a commercial enterprise like SourceForge and GitHub. Once we've checked with our legal people, and this usage has been approved by them, I'll be fine with it. Until then, I'm very conscious that the ASF is legally a charity, and is subject to losing that status if we don't abide by the rules. So I would rather ask the question and get the official answer than discover that we were responsible for the ASF losing its status over an assumption we made. -- Martin Cooper - René -- Martin Cooper [...] -- René Gielen http://twitter.com/rgielen - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
2012/11/28 Christian Grobmeier grobme...@gmail.com: I think a people.a.o user directory would do the trick. You mean to deploy it to my home directory at people.a.o ? Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
On Fri, Nov 30, 2012 at 7:03 PM, Lukasz Lenart lukaszlen...@apache.org wrote: 2012/11/28 Christian Grobmeier grobme...@gmail.com: I think a people.a.o user directory would do the trick. You mean to deploy it to my home directory at people.a.o ? Yes. I mean, its just for testing Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
Am 27.11.12 22:55, schrieb Johannes Geppert: It looks there is a broad agreement related to the projects links and the Roadmap FAQ. So i have dropped it from the site. Also I have added a Facebook and G+ Integration beside the Twitter Integration. Looks like this is our current News Section. ;-) On the bottom of our Welcome Page are some Books like Starting with Struts2 linked. But this Links returns only a blank page to me. Does anybody know the right Link? Good point - this is pretty much outdated. The correct link for Ian's mini book is http://www.infoq.com/minibooks/starting-struts2 But given that there are a couple of books around now, we might want to consider adding a Books page. As for Struts 2, there are even more books to mention than those found in the Struts section of the Apache Bookstore: Roughley: Starting Struts 2, InfoQ Brown, Davis, Stanlick: Struts 2 in Action, Manning Newton: Apache Struts Web Application Development, Packt Roughley: Practical Apache Struts 2 Web 2.0 Projects, Apress Kurniawan; Struts 2 Design and Programming: A Tutorial, BrainySoftware Johannes [...] -- René Gielen http://twitter.com/rgielen - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
Hi, Do we have a place where we can deploy a pre-release version of site to test it ? Maybe just to struts.a.o/next ? Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
On Wed, Nov 28, 2012 at 8:57 PM, Lukasz Lenart lukaszlen...@apache.org wrote: Do we have a place where we can deploy a pre-release version of site to test it ? Maybe just to struts.a.o/next ? I think a people.a.o user directory would do the trick. Cheers Christian Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
Indeed it looks a bit awkward having trunk/branches besides forms/legacy. But it just indicates that the latter directories seem to be misplaced so far. I'd suggest moving the contents of legacy to ../archive, and introduce a new folder ../resources where we move the forms directory to. - René Am 22.11.12 13:27, schrieb Lukasz Lenart: 2012/11/22 Lukasz Lenart lukaszlen...@apache.org: 2012/11/22 Christian Grobmeier grobme...@gmail.com: eh couldnt wait and have started.. but one question. The folders legacy and forms, are they part of the site and need to be moved to trunk or can they remain where they currently are? I think they can stay where they are now. At some point we should clean up a bit the repo - move forms to some legal folder and remove legacy Martin and Rene please correct me if I'm wrong. Kind regards -- René Gielen http://twitter.com/rgielen - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
I applied the moves suggested in my former mail. Am 27.11.12 16:08, schrieb Rene Gielen: Indeed it looks a bit awkward having trunk/branches besides forms/legacy. But it just indicates that the latter directories seem to be misplaced so far. I'd suggest moving the contents of legacy to ../archive, and introduce a new folder ../resources where we move the forms directory to. - René Am 22.11.12 13:27, schrieb Lukasz Lenart: 2012/11/22 Lukasz Lenart lukaszlen...@apache.org: 2012/11/22 Christian Grobmeier grobme...@gmail.com: eh couldnt wait and have started.. but one question. The folders legacy and forms, are they part of the site and need to be moved to trunk or can they remain where they currently are? I think they can stay where they are now. At some point we should clean up a bit the repo - move forms to some legal folder and remove legacy Martin and Rene please correct me if I'm wrong. Kind regards -- René Gielen IT-Neering.net Saarstrasse 100, 52062 Aachen, Germany Tel: +49-(0)241-4010770 Fax: +49-(0)241-4010771 Cel: +49-(0)163-2844164 http://twitter.com/rgielen - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
Changing it to footer div class=row span12 Apache Struts, Struts, Apache, the Apache feather logo, and the Apache Struts project logos are trademarks of The Apache Software Foundation. /div /footer imo looks more appropriate - there still seems to be some css weirdness though... Am 26.11.12 23:28, schrieb Johannes Geppert: p#169; 2005-2011 The Apache Software Foundation - Apache Struts, Struts, Apache, the Apache feather logo, and the Apache Struts project logos are trademarks of The Apache Software Foundation./p -- René Gielen IT-Neering.net Saarstrasse 100, 52062 Aachen, Germany Tel: +49-(0)241-4010770 Fax: +49-(0)241-4010771 Cel: +49-(0)163-2844164 http://twitter.com/rgielen - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
Am 26.11.12 22:41, schrieb Martin Cooper: On Mon, Nov 26, 2012 at 12:41 PM, Lukasz Lenart lukaszlen...@apache.orgwrote: 2012/11/25 Johannes Geppert jo...@apache.org: What others think about shrinking a little bit the menu and some Content? +1 :-) Depends on what you mean by shrink. We have people (e.g. Link, very recently) who don't seem to be able to find stuff on our menu, so making it smaller will not help at all. On the other hand, reducing the number of items would undoubtedly help. I have to admit that the sheer amount of information both in the main menu and certain pages is what it makes hard for me to find something - even given that I'm involved with the site for some years now. While e.g. it is educative to hear about mailing list policies first, the actual information how to subscribe is buried under piles of letters ... and most of nowadays users seem to have an attention span not lasting longer than three paragraphs before they give up reading. At least the mailing list moderation experience seems to indicate that. Basically I think that careful reduction and hierarchical organization of information helps to succeed getting our messages between our site reader's ears. That said, reducing the main menu would be good first step in my opinion. 1.) The Roadmap FAQ is really outdated! We can update it, delete it or reference it to the current Struts3 Wiki Page I think we can remove that page, even if we plan S3 there is not too much to write - Struts 2 done better :-) A roadmap can be very useful, but it needs people committed to maintaining it. I think Ted was probably the only one who did this for an extended period. We should just remove it if we don't have something useful to say. +1 - unless there is valid maintained content, we should remove the roadmap FAQ. If at a later point we want to add up to date roadmap information again, we might consider to call it simply Roadmap rather than Roadmap FAQ. 2.) What is the mining of the Project Minutes ? Last update is from 2008! I think it would be nice to put here Reports to the ASF Board which Rene prepares, it's important to see what's going on with the project, thus will overtake Roadmap FAQ The board minutes are a matter of public record, and are always published. See: http://www.apache.org/foundation/board/calendar.html It's not easy to find the Struts reports in that (e.g. you need to know our schedule), so I'd be okay with re-publishing, if we think we'll keep it up to date. But we should copy from the board minutes, rather than our list, to be sure we capture accurately what the board accepted. I'm not sure if the board level reports - in this particular form - are of widespread interest, neither do they replace well maintained news content. Given that we had to implement a solution to automatically extract the content from the approved reports, as Martin stated, I wonder if this is worth the effort. A news section with targeted information bits might be a more relevant way to go, as long at it is well maintained. E.g., I could imagine snippets like - Struts Users Facebook Site hits 1.000.000 likes - Struts Downloads peeked with the release of 4.0.1 - Externally maintained Struts 2 BootQueryNateStrap-Plugin version 9.8.7 released - Appfuse 20.12 now with Struts2 LiquidDiamondAngular Theme support baked in - ApacheCon NA 2015 to feature five Struts 4 talks - John Doe has written an interesting blog post on Configuration over Convention in Struts 4 As for the noteworthy stuff assembled into the quarterly board report, I could volunteer to add a rehash-and-update-site workflow at around the time the report is submitted. But I think more voluntary help would be needed to keep such a news stream relevant. If we go for adding approved board reports, the Development-Minutes section would have to be filled with life again. If not, we should consider removing it. 3.) Maybe we can create on Page for the Related and Similar Projects? This would make the Menu much more cleaner. +1 Frankly, I think we should drop related and similar projects. There is no meaningful determination of what does, or does not, make it into either list. +1 as well - besides, the linked Apache projects seems to have nothing alike any more (at least Wicket / Tapestry last time I checked). I'd vote to drop - Related Projects - Similar Projects - Java 5 for Struts 1 (Strecks) 4.) The Link to Our Blogs looks also really outdated! Last Entry is from 2008. http://people.apache.org/~rubys/planet/struts/ We can add few new, like your :-) That planet link is long-obsolete. See instead: http://blogs.apache.org/ Since there isn't too much going on regarding Struts even at blogs.a.o, I'm in favor for dropping the Our Blogs link. 5.) Is the Struts Sourceforge active? Never heard about it. http://struts.sourceforge.net/ I've been using it some times ago, but not any more but I
Re: Using fluido once available
determination of what does, or does not, make it into either list. +1 as well - besides, the linked Apache projects seems to have nothing alike any more (at least Wicket / Tapestry last time I checked). I'd vote to drop - Related Projects - Similar Projects - Java 5 for Struts 1 (Strecks) 4.) The Link to Our Blogs looks also really outdated! Last Entry is from 2008. http://people.apache.org/~rubys/planet/struts/ We can add few new, like your :-) That planet link is long-obsolete. See instead: http://blogs.apache.org/ Since there isn't too much going on regarding Struts even at blogs.a.o, I'm in favor for dropping the Our Blogs link. 5.) Is the Struts Sourceforge active? Never heard about it. http://struts.sourceforge.net/ I've been using it some times ago, but not any more but I think it should stay :-) Yeah, it should stay. It's where we can point non-committers to check in Struts-related code, if they so wish. Hmm - diving a bit into http://struts.sourceforge.net/, frankly it looks like a zombie to me. All Getting Involved - Repository links (CVS) I tried were broken. Is there any recent activity? Wouldn't it be better to link https://github.com/apache/struts2 instead? It should at least be linked in addition. Additional thoughts: - we should not only incorporate the twitter button but also G+ and Facebook buttons pointing to the respective Struts pages. - Development-Source Code and Development-Source Repository should be merged - dropping pages does not necessarily mean removing them - as for historic reference (and bookmarks), those pages might still be deployed but no longer referenced from the menu -- Martin Cooper Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: [hidden email]http://user/SendEmail.jtp?type=nodenode=5711187i=2 For additional commands, e-mail: [hidden email]http://user/SendEmail.jtp?type=nodenode=5711187i=3 -- René Gielen http://twitter.com/rgielen - To unsubscribe, e-mail: [hidden email]http://user/SendEmail.jtp?type=nodenode=5711187i=4 For additional commands, e-mail: [hidden email]http://user/SendEmail.jtp?type=nodenode=5711187i=5 -- If you reply to this email, your message will be added to the discussion below: http://struts.1045723.n5.nabble.com/Using-fluido-once-available-tp4998141p5711187.html To unsubscribe from Using fluido once available, click herehttp://struts.1045723.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=4998141code=am9nZXBAYXBhY2hlLm9yZ3w0OTk4MTQxfC0xNDI4NDU4NDU5 . NAMLhttp://struts.1045723.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml - web: http://www.jgeppert.com twitter: http://twitter.com/jogep -- View this message in context: http://struts.1045723.n5.nabble.com/Using-fluido-once-available-tp4998141p5711194.html Sent from the Struts - Dev mailing list archive at Nabble.com.
Re: Using fluido once available
, the Development-Minutes section would have to be filled with life again. If not, we should consider removing it. 3.) Maybe we can create on Page for the Related and Similar Projects? This would make the Menu much more cleaner. +1 Frankly, I think we should drop related and similar projects. There is no meaningful determination of what does, or does not, make it into either list. +1 as well - besides, the linked Apache projects seems to have nothing alike any more (at least Wicket / Tapestry last time I checked). I'd vote to drop - Related Projects - Similar Projects - Java 5 for Struts 1 (Strecks) 4.) The Link to Our Blogs looks also really outdated! Last Entry is from 2008. http://people.apache.org/~rubys/planet/struts/ We can add few new, like your :-) That planet link is long-obsolete. See instead: http://blogs.apache.org/ Since there isn't too much going on regarding Struts even at blogs.a.o, I'm in favor for dropping the Our Blogs link. 5.) Is the Struts Sourceforge active? Never heard about it. http://struts.sourceforge.net/ I've been using it some times ago, but not any more but I think it should stay :-) Yeah, it should stay. It's where we can point non-committers to check in Struts-related code, if they so wish. Hmm - diving a bit into http://struts.sourceforge.net/, frankly it looks like a zombie to me. All Getting Involved - Repository links (CVS) I tried were broken. Is there any recent activity? Wouldn't it be better to link https://github.com/apache/struts2 instead? It should at least be linked in addition. Additional thoughts: - we should not only incorporate the twitter button but also G+ and Facebook buttons pointing to the respective Struts pages. - Development-Source Code and Development-Source Repository should be merged - dropping pages does not necessarily mean removing them - as for historic reference (and bookmarks), those pages might still be deployed but no longer referenced from the menu -- Martin Cooper Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: [hidden email] http://user/SendEmail.jtp?type=nodenode=5711187i=2 For additional commands, e-mail: [hidden email] http://user/SendEmail.jtp?type=nodenode=5711187i=3 -- René Gielen http://twitter.com/rgielen - To unsubscribe, e-mail: [hidden email] http://user/SendEmail.jtp?type=nodenode=5711187i=4 For additional commands, e-mail: [hidden email] http://user/SendEmail.jtp?type=nodenode=5711187i=5 -- If you reply to this email, your message will be added to the discussion below: http://struts.1045723.n5.nabble.com/Using-fluido-once-available-tp4998141p5711187.html To unsubscribe from Using fluido once available, click here http://struts.1045723.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=4998141code=am9nZXBAYXBhY2hlLm9yZ3w0OTk4MTQxfC0xNDI4NDU4NDU5 . NAML http://struts.1045723.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml - web: http://www.jgeppert.com twitter: http://twitter.com/jogep -- View this message in context: http://struts.1045723.n5.nabble.com/Using-fluido-once-available-tp4998141p5711194.html Sent from the Struts - Dev mailing list archive at Nabble.com.
Re: Using fluido once available
2012/11/28 Martin Cooper mart...@apache.org: Why are we supporting commercial enterprises from our site? As a 501(c)3 organisation, are we allowed to do that? Hmmm we should ask somebody as I have no idea how it works in US. Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
Am 28.11.12 06:14, schrieb Martin Cooper: On Tue, Nov 27, 2012 at 1:55 PM, Johannes Geppert jo...@apache.org wrote: It looks there is a broad agreement related to the projects links and the Roadmap FAQ. So i have dropped it from the site. Also I have added a Facebook and G+ Integration beside the Twitter Integration. Looks like this is our current News Section. ;-) Why are we supporting commercial enterprises from our site? As a 501(c)3 organisation, are we allowed to do that? We have an official Twitter account - @TheApacheStruts - which we use to spread news about Struts and to interact with our community. Just like @TheASF, @TheApacheTomcat or @ApacheJames. On Facebook, there is as well a page voluntarily maintained by Struts PMC members, called Struts2 Users. Objective: spreading and dispatching news, interacting with the community. Currently 1400+ likes aka followers. See: https://www.facebook.com/apachestruts On G+, there is again an page voluntarily maintained by Struts PMC members, called Apache Struts. Objective: spreading and dispatching news, interacting with the community. Currently more than 3700 people are following. See: https://plus.google.com/+ApacheStruts/posts See also on G+: Apache Software Foundation, Apache TomEE The idea is to link this pages to our site just like we did with the twitter account in the branch (and other Apache projects do as well on their front page). So how is this supporting commercial enterprises? One could argue that we are using (free) services of commercial companies, yes. We do that all the time at Apache. I fail to see how this is promoting Twitter, Google or Facebook as companies. Ironically, the latter two are getting prominent ASF support since they are platinum sponsors: http://apache.org/foundation/thanks.html Linking to Struts related resources on Twitter, G+ or Facebook is as much of a support for commercial enterprises as linking to Struts Sourceforge is or Struts GitHub would be - free community resources offered and hosted free of charge by a commercial enterprise like SourceForge and GitHub. - René -- Martin Cooper [...] -- René Gielen http://twitter.com/rgielen - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
2012/11/25 Johannes Geppert jo...@apache.org: What others think about shrinking a little bit the menu and some Content? +1 :-) 1.) The Roadmap FAQ is really outdated! We can update it, delete it or reference it to the current Struts3 Wiki Page I think we can remove that page, even if we plan S3 there is not too much to write - Struts 2 done better :-) 2.) What is the mining of the Project Minutes ? Last update is from 2008! I think it would be nice to put here Reports to the ASF Board which Rene prepares, it's important to see what's going on with the project, thus will overtake Roadmap FAQ 3.) Maybe we can create on Page for the Related and Similar Projects? This would make the Menu much more cleaner. +1 4.) The Link to Our Blogs looks also really outdated! Last Entry is from 2008. http://people.apache.org/~rubys/planet/struts/ We can add few new, like your :-) 5.) Is the Struts Sourceforge active? Never heard about it. http://struts.sourceforge.net/ I've been using it some times ago, but not any more but I think it should stay :-) Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
On Mon, Nov 26, 2012 at 12:41 PM, Lukasz Lenart lukaszlen...@apache.orgwrote: 2012/11/25 Johannes Geppert jo...@apache.org: What others think about shrinking a little bit the menu and some Content? +1 :-) Depends on what you mean by shrink. We have people (e.g. Link, very recently) who don't seem to be able to find stuff on our menu, so making it smaller will not help at all. On the other hand, reducing the number of items would undoubtedly help. 1.) The Roadmap FAQ is really outdated! We can update it, delete it or reference it to the current Struts3 Wiki Page I think we can remove that page, even if we plan S3 there is not too much to write - Struts 2 done better :-) A roadmap can be very useful, but it needs people committed to maintaining it. I think Ted was probably the only one who did this for an extended period. We should just remove it if we don't have something useful to say. 2.) What is the mining of the Project Minutes ? Last update is from 2008! I think it would be nice to put here Reports to the ASF Board which Rene prepares, it's important to see what's going on with the project, thus will overtake Roadmap FAQ The board minutes are a matter of public record, and are always published. See: http://www.apache.org/foundation/board/calendar.html It's not easy to find the Struts reports in that (e.g. you need to know our schedule), so I'd be okay with re-publishing, if we think we'll keep it up to date. But we should copy from the board minutes, rather than our list, to be sure we capture accurately what the board accepted. 3.) Maybe we can create on Page for the Related and Similar Projects? This would make the Menu much more cleaner. +1 Frankly, I think we should drop related and similar projects. There is no meaningful determination of what does, or does not, make it into either list. 4.) The Link to Our Blogs looks also really outdated! Last Entry is from 2008. http://people.apache.org/~rubys/planet/struts/ We can add few new, like your :-) That planet link is long-obsolete. See instead: http://blogs.apache.org/ 5.) Is the Struts Sourceforge active? Never heard about it. http://struts.sourceforge.net/ I've been using it some times ago, but not any more but I think it should stay :-) Yeah, it should stay. It's where we can point non-committers to check in Struts-related code, if they so wish. -- Martin Cooper Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
@Christian The Footer must be inside of an Element, like this: footerp#169; 2005-2011 The Apache Software Foundation - Apache Struts, Struts, Apache, the Apache feather logo, and the Apache Struts project logos are trademarks of The Apache Software Foundation./p/footer But when I try this, I got two footer texts. The one from Fluido Skin and the defined. Johannes # web: http://www.jgeppert.com twitter: http://twitter.com/jogep 2012/11/26 Martin Cooper-2 [via Struts] ml-node+s1045723n5711179...@n5.nabble.com On Mon, Nov 26, 2012 at 12:41 PM, Lukasz Lenart [hidden email]http://user/SendEmail.jtp?type=nodenode=5711179i=0wrote: 2012/11/25 Johannes Geppert [hidden email]http://user/SendEmail.jtp?type=nodenode=5711179i=1: What others think about shrinking a little bit the menu and some Content? +1 :-) Depends on what you mean by shrink. We have people (e.g. Link, very recently) who don't seem to be able to find stuff on our menu, so making it smaller will not help at all. On the other hand, reducing the number of items would undoubtedly help. 1.) The Roadmap FAQ is really outdated! We can update it, delete it or reference it to the current Struts3 Wiki Page I think we can remove that page, even if we plan S3 there is not too much to write - Struts 2 done better :-) A roadmap can be very useful, but it needs people committed to maintaining it. I think Ted was probably the only one who did this for an extended period. We should just remove it if we don't have something useful to say. 2.) What is the mining of the Project Minutes ? Last update is from 2008! I think it would be nice to put here Reports to the ASF Board which Rene prepares, it's important to see what's going on with the project, thus will overtake Roadmap FAQ The board minutes are a matter of public record, and are always published. See: http://www.apache.org/foundation/board/calendar.html It's not easy to find the Struts reports in that (e.g. you need to know our schedule), so I'd be okay with re-publishing, if we think we'll keep it up to date. But we should copy from the board minutes, rather than our list, to be sure we capture accurately what the board accepted. 3.) Maybe we can create on Page for the Related and Similar Projects? This would make the Menu much more cleaner. +1 Frankly, I think we should drop related and similar projects. There is no meaningful determination of what does, or does not, make it into either list. 4.) The Link to Our Blogs looks also really outdated! Last Entry is from 2008. http://people.apache.org/~rubys/planet/struts/ We can add few new, like your :-) That planet link is long-obsolete. See instead: http://blogs.apache.org/ 5.) Is the Struts Sourceforge active? Never heard about it. http://struts.sourceforge.net/ I've been using it some times ago, but not any more but I think it should stay :-) Yeah, it should stay. It's where we can point non-committers to check in Struts-related code, if they so wish. -- Martin Cooper Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: [hidden email]http://user/SendEmail.jtp?type=nodenode=5711179i=2 For additional commands, e-mail: [hidden email]http://user/SendEmail.jtp?type=nodenode=5711179i=3 -- If you reply to this email, your message will be added to the discussion below: http://struts.1045723.n5.nabble.com/Using-fluido-once-available-tp4998141p5711179.html To unsubscribe from Using fluido once available, click herehttp://struts.1045723.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=4998141code=am9nZXBAYXBhY2hlLm9yZ3w0OTk4MTQxfC0xNDI4NDU4NDU5 . NAMLhttp://struts.1045723.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml - web: http://www.jgeppert.com twitter: http://twitter.com/jogep -- View this message in context: http://struts.1045723.n5.nabble.com/Using-fluido-once-available-tp4998141p5711180.html Sent from the Struts - Dev mailing list archive at Nabble.com.
Re: Using fluido once available
Thanks for starting the branch Christian! What others think about shrinking a little bit the menu and some Content? 1.) The Roadmap FAQ is really outdated! We can update it, delete it or reference it to the current Struts3 Wiki Page 2.) What is the mining of the Project Minutes ? Last update is from 2008! 3.) Maybe we can create on Page for the Related and Similar Projects? This would make the Menu much more cleaner. 4.) The Link to Our Blogs looks also really outdated! Last Entry is from 2008. http://people.apache.org/~rubys/planet/struts/ 5.) Is the Struts Sourceforge active? Never heard about it. http://struts.sourceforge.net/ Johannes # web: http://www.jgeppert.com twitter: http://twitter.com/jogep 2012/11/23 Christian Grobmeier [via Struts] ml-node+s1045723n5711154...@n5.nabble.com On Thu, Nov 22, 2012 at 1:26 PM, Lukasz Lenart [hidden email]http://user/SendEmail.jtp?type=nodenode=5711154i=0 wrote: 2012/11/22 Christian Grobmeier [hidden email]http://user/SendEmail.jtp?type=nodenode=5711154i=1: eh couldnt wait and have started.. but one question. The folders legacy and forms, are they part of the site and need to be moved to trunk or can they remain where they currently are? I think they can stay where they are now. At some point we should clean up a bit the repo - move forms to some legal folder and remove legacy I just committed the fluido things! :-) http://svn.apache.org/repos/asf/struts/site/branches/site2fluidomigration The usual mvn site should do the trick. I saw the footer from site.xml is ignored. Its still showing the old one, which is not good from branding perspective. Hopefully I find a way to improve it. Or somebody else Cheers - To unsubscribe, e-mail: [hidden email]http://user/SendEmail.jtp?type=nodenode=5711154i=2 For additional commands, e-mail: [hidden email]http://user/SendEmail.jtp?type=nodenode=5711154i=3 -- If you reply to this email, your message will be added to the discussion below: http://struts.1045723.n5.nabble.com/Using-fluido-once-available-tp4998141p5711154.html To unsubscribe from Using fluido once available, click herehttp://struts.1045723.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=4998141code=am9nZXBAYXBhY2hlLm9yZ3w0OTk4MTQxfC0xNDI4NDU4NDU5 . NAMLhttp://struts.1045723.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml - web: http://www.jgeppert.com twitter: http://twitter.com/jogep -- View this message in context: http://struts.1045723.n5.nabble.com/Using-fluido-once-available-tp4998141p5711160.html Sent from the Struts - Dev mailing list archive at Nabble.com.
Re: Using fluido once available
On Thu, Nov 22, 2012 at 1:26 PM, Lukasz Lenart lukaszlen...@apache.org wrote: 2012/11/22 Christian Grobmeier grobme...@gmail.com: eh couldnt wait and have started.. but one question. The folders legacy and forms, are they part of the site and need to be moved to trunk or can they remain where they currently are? I think they can stay where they are now. At some point we should clean up a bit the repo - move forms to some legal folder and remove legacy I just committed the fluido things! :-) http://svn.apache.org/repos/asf/struts/site/branches/site2fluidomigration The usual mvn site should do the trick. I saw the footer from site.xml is ignored. Its still showing the old one, which is not good from branding perspective. Hopefully I find a way to improve it. Or somebody else Cheers - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
Christian could you prepare a patch for what have you done so far ? I would like update the main webpage with the new look :-) Even if not everything is perfect it would nice to show people a movement and expect theirs feedback. Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
Hi, oh i almost forgot about that. I have it on my disk, currently pointing to: https://svn.apache.org/repos/asf/struts/site it has not been updated with the recent developments. I am willing to help. In order to do so, would it be better to make a new site-branch? i could then try to merge my stuff, relocate, and commit to the new branch. Then we might be able to tweak it until it fits. Cheers Christian On Thu, Nov 22, 2012 at 12:04 PM, Lukasz Lenart lukaszlen...@apache.org wrote: Christian could you prepare a patch for what have you done so far ? I would like update the main webpage with the new look :-) Even if not everything is perfect it would nice to show people a movement and expect theirs feedback. Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
2012/11/22 Christian Grobmeier grobme...@gmail.com: I have it on my disk, currently pointing to: https://svn.apache.org/repos/asf/struts/site it has not been updated with the recent developments. I am willing to help. In order to do so, would it be better to make a new site-branch? i could then try to merge my stuff, relocate, and commit to the new branch. Then we might be able to tweak it until it fits. Maybe move the current source to trunk (trunk need to be created) and add your version under branch (as well have to be created) so at the end we will have a common Svn layout https://svn.apache.org/repos/asf/struts/site/ |-- trunk |-- branches Kind regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
On Thu, Nov 22, 2012 at 12:58 PM, Lukasz Lenart lukaszlen...@apache.org wrote: 2012/11/22 Christian Grobmeier grobme...@gmail.com: I have it on my disk, currently pointing to: https://svn.apache.org/repos/asf/struts/site it has not been updated with the recent developments. I am willing to help. In order to do so, would it be better to make a new site-branch? i could then try to merge my stuff, relocate, and commit to the new branch. Then we might be able to tweak it until it fits. Maybe move the current source to trunk (trunk need to be created) and add your version under branch (as well have to be created) so at the end we will have a common Svn layout https://svn.apache.org/repos/asf/struts/site/ |-- trunk |-- branches Makes sense. Let's do it like that. I have made a local update on what I have, its just a few conflicts. I surely can deal with them. Today is a bit tight as I am giving a talk on Dartlang, but I will do that tomorrow Cheers Kind regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
On Thu, Nov 22, 2012 at 1:06 PM, Christian Grobmeier grobme...@gmail.com wrote: On Thu, Nov 22, 2012 at 12:58 PM, Lukasz Lenart lukaszlen...@apache.org wrote: 2012/11/22 Christian Grobmeier grobme...@gmail.com: I have it on my disk, currently pointing to: https://svn.apache.org/repos/asf/struts/site it has not been updated with the recent developments. I am willing to help. In order to do so, would it be better to make a new site-branch? i could then try to merge my stuff, relocate, and commit to the new branch. Then we might be able to tweak it until it fits. Maybe move the current source to trunk (trunk need to be created) and add your version under branch (as well have to be created) so at the end we will have a common Svn layout https://svn.apache.org/repos/asf/struts/site/ |-- trunk |-- branches eh couldnt wait and have started.. but one question. The folders legacy and forms, are they part of the site and need to be moved to trunk or can they remain where they currently are? - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
2012/11/22 Christian Grobmeier grobme...@gmail.com: eh couldnt wait and have started.. but one question. The folders legacy and forms, are they part of the site and need to be moved to trunk or can they remain where they currently are? I think they can stay where they are now. At some point we should clean up a bit the repo - move forms to some legal folder and remove legacy Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
2012/11/22 Lukasz Lenart lukaszlen...@apache.org: 2012/11/22 Christian Grobmeier grobme...@gmail.com: eh couldnt wait and have started.. but one question. The folders legacy and forms, are they part of the site and need to be moved to trunk or can they remain where they currently are? I think they can stay where they are now. At some point we should clean up a bit the repo - move forms to some legal folder and remove legacy Martin and Rene please correct me if I'm wrong. Kind regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
2011/11/29 Christian Grobmeier grobme...@gmail.com: Hello all, here is a new draft: http://code.grobmeier.de/struts-draft-v3/ Looks nice :-) * Lukasz mentioned the content is fixed size. This is now fixed (fluid) :-). We run again into the doxia problems, but i have worked around them. Is it possible to have a top limit ? eg. 1024px ? ;-) * Lukasz mentioned the heading are not good at all (the same as the first sentence of the following paragraph) Can be easily improved, but it can stay as is now * Next links on the bottom: i think they are pretty useless. After the frontpage the next link is showing the downloads. It should lead through a tutorial, not the standard menu of the page. And it stops on the Kickstart FAQ. I highly doubt the sense of this link and would like to remove them for sake of minimalism, but of course it is up to you. I have left it in until this is discussed. I can live with discussing them after the first patch +1 * Text. It is way to much text on the front page. On the frontpage should be less txt, pointing you to the detail pages. Frontpage is to guide you through the site. Imho this is not the case. The current information should go into another page, the front page should only contain a teaser and a link to this section Maybe just reduce the lines of the text and the rest move to separate pages * Search: yes or no? I would not use it anyway because I don't like that google styled search. Martin expressed similar. How do others think? I never used it, so +1 * Remove announcements page? This page is not cared very well. Of course this is no styling issue, but while we are at it, we could remove it. The other chance is to care about the page. What you mean by that ? Each time a new release is promoted we put info to the announcements page, IMHO it should stay as is, it shows clearly what's happened * Release notes cannot be found easily. Martin said it is in the first section, but I actually mean this page: http://struts.apache.org/downloads.html I could not find the release notes of prior releases easily. There is this changes maven plugin which generates a simple page of changes: http://logging.apache.org/log4php/changes-report.html I found it pretty hard to check what changed in which version (and what probably broke in which version) Disagree, you can select given version which leads you to download section and there you have a link to release notes, which are something more than just list of fixed issues http://struts.apache.org/2.2.3.1/docs/version-notes-2231.html Most of the discuss items can be discussed later. I think i have started to many things with the fluido update. Now I have left most as it was before, with a few exceptions. If you agree to v3, I can look through the other pages if there needs to be something done and create a patch. After the patch we can discuss the other items, if you like. +1 Kind regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ Warszawa JUG conference - Confitura http://confitura.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
Hi all, I would have liked to be more involved in that discussion, but unfortunately I have been very busy. So, sorry in advance if I will miss something. First I would like to say that: 1. the new site looks very good 2. as Martin already said and according with the stats [1], struts website attracts every day many users, so we cannot ignore accessibility. * added color for visited links. I don't like them, but Martin explained it might be useful for voice commands. No clue about it, this can be discussed later if other people don't like it (like me) Regarding the visit link, I don't like them too, but we should take into consideration people with a cognitive disability or brain injury, visited link may reduce the memory load. An useful link [2] [1] http://people.apache.org/~vgritsenko/stats/projects/struts [2] http://www.w3.org/WAI/UA/WD-UAAG10-20010126/uaag10.html#tech-special-highlight Twitter :http://www.twitter.com/m_cucchiara G+ :https://plus.google.com/107903711540963855921 Linkedin:http://www.linkedin.com/in/mauriziocucchiara Maurizio Cucchiara
Re: Using fluido once available
It's very hard to think that next link provides a good tour of the struts features (I'm pretty sure it got lost over the years), and then what features should it describe: Struts 2 or Struts 1? If there is one thing that I have never considered clean on the website is the S1-S2 distinction. I think that it is very hard to the new user understanding where they are going to go. IMO the first page should provide to the user, the chose of one of the two paths before anything else. Twitter :http://www.twitter.com/m_cucchiara G+ :https://plus.google.com/107903711540963855921 Linkedin:http://www.linkedin.com/in/mauriziocucchiara Maurizio Cucchiara On 29 November 2011 10:32, Christian Grobmeier grobme...@gmail.com wrote: * Next links on the bottom: i think they are pretty useless. After the frontpage the next link is showing the downloads. It should lead through a tutorial, not the standard menu of the page. And it stops on the Kickstart FAQ. I highly doubt the sense of this link and would like to remove them for sake of minimalism, but of course it is up to you. I have left it in until this is discussed. I can live with discussing them after the first patch
Re: Using fluido once available
On Wed, Nov 30, 2011 at 11:18 AM, Maurizio Cucchiara mcucchi...@apache.org wrote: It's very hard to think that next link provides a good tour of the struts features (I'm pretty sure it got lost over the years), and then what features should it describe: Struts 2 or Struts 1? If there is one thing that I have never considered clean on the website is the S1-S2 distinction. I think that it is very hard to the new user understanding where they are going to go. IMO the first page should provide to the user, the chose of one of the two paths before anything else. Very much +1. It confused me too when I started with Struts 2 (i have used Struts 1 ages ago). I have currently no idea, but how can we cooperate on our ideas? Is there a Struts Sandbox for non-committer access with asf account? Cheers Twitter :http://www.twitter.com/m_cucchiara G+ :https://plus.google.com/107903711540963855921 Linkedin :http://www.linkedin.com/in/mauriziocucchiara Maurizio Cucchiara On 29 November 2011 10:32, Christian Grobmeier grobme...@gmail.com wrote: * Next links on the bottom: i think they are pretty useless. After the frontpage the next link is showing the downloads. It should lead through a tutorial, not the standard menu of the page. And it stops on the Kickstart FAQ. I highly doubt the sense of this link and would like to remove them for sake of minimalism, but of course it is up to you. I have left it in until this is discussed. I can live with discussing them after the first patch -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
Hello, On Wed, Nov 30, 2011 at 10:32 AM, Maurizio Cucchiara mcucchi...@apache.org wrote: 1. the new site looks very good 2. as Martin already said and according with the stats [1], struts website attracts every day many users, so we cannot ignore accessibility. this was actually not my intention and I agree of course :-) * added color for visited links. I don't like them, but Martin explained it might be useful for voice commands. No clue about it, this can be discussed later if other people don't like it (like me) Regarding the visit link, I don't like them too, but we should take into consideration people with a cognitive disability or brain injury, visited link may reduce the memory load. An useful link [2] They are already in with v3 of the site. Probably you don#t see it, because it is only one page. But if you click on the links directly beyond the hero section it should show you the visited color Cheers Christian [1] http://people.apache.org/~vgritsenko/stats/projects/struts [2] http://www.w3.org/WAI/UA/WD-UAAG10-20010126/uaag10.html#tech-special-highlight Twitter :http://www.twitter.com/m_cucchiara G+ :https://plus.google.com/107903711540963855921 Linkedin :http://www.linkedin.com/in/mauriziocucchiara Maurizio Cucchiara -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
2011/11/30 Łukasz Lenart lukasz.len...@googlemail.com: * Lukasz mentioned the content is fixed size. This is now fixed (fluid) :-). We run again into the doxia problems, but i have worked around them. Is it possible to have a top limit ? eg. 1024px ? ;-) Oh dear - your ideas :-) But actually there is a chance as I just googled: http://www.css4you.de/max-width.html It should work with that. Will give it a try later * Text. It is way to much text on the front page. On the frontpage should be less txt, pointing you to the detail pages. Frontpage is to guide you through the site. Imho this is not the case. The current information should go into another page, the front page should only contain a teaser and a link to this section Maybe just reduce the lines of the text and the rest move to separate pages +1. Maurizio might have some ideas on that * Remove announcements page? This page is not cared very well. Of course this is no styling issue, but while we are at it, we could remove it. The other chance is to care about the page. What you mean by that ? Each time a new release is promoted we put info to the announcements page, IMHO it should stay as is, it shows clearly what's happened http://struts.apache.org/announce.html I know what you mean now - I didn't see the go to announcments 2010, 2009 etc links I thought there was only one entry on it. I step back from my opinion here. Lets leave it as it is now * Release notes cannot be found easily. Martin said it is in the first section, but I actually mean this page: http://struts.apache.org/downloads.html I could not find the release notes of prior releases easily. There is this changes maven plugin which generates a simple page of changes: http://logging.apache.org/log4php/changes-report.html I found it pretty hard to check what changed in which version (and what probably broke in which version) Disagree, you can select given version which leads you to download section and there you have a link to release notes, which are something more than just list of fixed issues From struts.apache.org I clicked to relases: http://struts.apache.org/downloads.html Then I choose version 2.2.1: http://struts.apache.org/2.2.1/index.html And I still don't see the release notes. What am I missing? Cheers Christian -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
2011/11/30 Christian Grobmeier grobme...@gmail.com: * Release notes cannot be found easily. Martin said it is in the first section, but I actually mean this page: http://struts.apache.org/downloads.html I could not find the release notes of prior releases easily. There is this changes maven plugin which generates a simple page of changes: http://logging.apache.org/log4php/changes-report.html I found it pretty hard to check what changed in which version (and what probably broke in which version) Disagree, you can select given version which leads you to download section and there you have a link to release notes, which are something more than just list of fixed issues From struts.apache.org I clicked to relases: http://struts.apache.org/downloads.html Then I choose version 2.2.1: http://struts.apache.org/2.2.1/index.html And I still don't see the release notes. What am I missing? You're talking about the Prior releases and I was talking about GA releases [1] ;-) If so, you're right, maybe adding a link to Release Notes would solve the problem. [1] http://struts.apache.org/download.cgi#struts2231 Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ Warszawa JUG conference - Confitura http://confitura.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
2011/11/30 Łukasz Lenart lukasz.len...@googlemail.com: 2011/11/30 Christian Grobmeier grobme...@gmail.com: * Release notes cannot be found easily. Martin said it is in the first section, but I actually mean this page: http://struts.apache.org/downloads.html I could not find the release notes of prior releases easily. There is this changes maven plugin which generates a simple page of changes: http://logging.apache.org/log4php/changes-report.html I found it pretty hard to check what changed in which version (and what probably broke in which version) Disagree, you can select given version which leads you to download section and there you have a link to release notes, which are something more than just list of fixed issues From struts.apache.org I clicked to relases: http://struts.apache.org/downloads.html Then I choose version 2.2.1: http://struts.apache.org/2.2.1/index.html And I still don't see the release notes. What am I missing? You're talking about the Prior releases and I was talking about GA releases [1] ;-) If so, you're right, maybe adding a link to Release Notes would solve the problem. [1] http://struts.apache.org/download.cgi#struts2231 Ah understood! Yes I think the release notes links should be added to this page: http://struts.apache.org/downloads.html Cheers Christian Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ Warszawa JUG conference - Confitura http://confitura.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
Hello all, here is a new draft: http://code.grobmeier.de/struts-draft-v3/ Here are the CHANGES (I will try to make this e-mail as short as possible but refer to some items of Martins post below): * Dave said, the hero-unit font is huge and Martin complained on the hero unit as to big in total. I reduced the size of font and unit itself * Latest Struts 1.3.x release is included in the hero unit too as Martin asked for * Lukasz mentioned the content is fixed size. This is now fixed (fluid) :-). We run again into the doxia problems, but i have worked around them. The problems with big/small screens as explained by Martin should be gone too * Updated the content of the hero unit to Lukasz suggestion * added Next link on the bottom again (see discussion below) * added color for visited links. I don't like them, but Martin explained it might be useful for voice commands. No clue about it, this can be discussed later if other people don't like it (like me) * removed search. Martin mentioned probably is nobody searching the site like this. I didn't find a good place to integrate it. LEFT FOR DISCUSSION: * Lukasz mentioned the heading are not good at all (the same as the first sentence of the following paragraph) * Next links on the bottom: i think they are pretty useless. After the frontpage the next link is showing the downloads. It should lead through a tutorial, not the standard menu of the page. And it stops on the Kickstart FAQ. I highly doubt the sense of this link and would like to remove them for sake of minimalism, but of course it is up to you. I have left it in until this is discussed. I can live with discussing them after the first patch * Text. It is way to much text on the front page. On the frontpage should be less txt, pointing you to the detail pages. Frontpage is to guide you through the site. Imho this is not the case. The current information should go into another page, the front page should only contain a teaser and a link to this section * Search: yes or no? I would not use it anyway because I don't like that google styled search. Martin expressed similar. How do others think? * Remove announcements page? This page is not cared very well. Of course this is no styling issue, but while we are at it, we could remove it. The other chance is to care about the page. * Release notes cannot be found easily. Martin said it is in the first section, but I actually mean this page: http://struts.apache.org/downloads.html I could not find the release notes of prior releases easily. There is this changes maven plugin which generates a simple page of changes: http://logging.apache.org/log4php/changes-report.html I found it pretty hard to check what changed in which version (and what probably broke in which version) * Branding: I just mention it for completeness. The page should be improved with that, I will look into it. Not an styling issue, but should be done. Most of the discuss items can be discussed later. I think i have started to many things with the fluido update. Now I have left most as it was before, with a few exceptions. If you agree to v3, I can look through the other pages if there needs to be something done and create a patch. After the patch we can discuss the other items, if you like. Cheers Christian On Tue, Nov 29, 2011 at 6:04 AM, Martin Cooper mfncoo...@gmail.com wrote: On Sun, Nov 27, 2011 at 6:04 AM, Christian Grobmeier grobme...@gmail.com wrote: Hello Martin, On Sun, Nov 27, 2011 at 3:57 AM, Martin Cooper mfncoo...@gmail.com wrote: On Sat, Nov 26, 2011 at 2:51 PM, Christian Grobmeier I have added a hero section. A what? This is the first huge section, showing what the page is about. Like here: http://incubator.apache.org/directmemory/ Unfortunately I needed to remove the h2, h3 etc to make this work because of a doxia bug. It seems it is already fixed in trunk, so I think we can leave it now and replace it later. (the bug replaces h2 with div class=sectonh2... - this kills everything) I'd say the missing h2, h3, et al, is a showstopper. OK, then we can't use fluido now, except we add anything in sequence (like it is today). This is terrible to read imho and so the question is if we need to wait for a new doxia release then. The updated version you posted is better. The headings are important. Just bolding text doesn't provide for accessibility, and doesn't provide screen readers the means to navigate through the page. We need to be mindful, with a framework as popular as Struts, that we are addressing the needs of all readers, so accessibility is very important. I think we should make the text somehow smaller if possible. It is very much too read and probably we should just have a teaser on the the various paragraphs. I disagree. The Recent Releases section needs to come back to the top, where it is prominent for the majority of existing users, who are returning for the latest update. The
Re: Using fluido once available
On Sun, Nov 27, 2011 at 6:04 AM, Christian Grobmeier grobme...@gmail.com wrote: Hello Martin, On Sun, Nov 27, 2011 at 3:57 AM, Martin Cooper mfncoo...@gmail.com wrote: On Sat, Nov 26, 2011 at 2:51 PM, Christian Grobmeier I have added a hero section. A what? This is the first huge section, showing what the page is about. Like here: http://incubator.apache.org/directmemory/ Unfortunately I needed to remove the h2, h3 etc to make this work because of a doxia bug. It seems it is already fixed in trunk, so I think we can leave it now and replace it later. (the bug replaces h2 with div class=sectonh2... - this kills everything) I'd say the missing h2, h3, et al, is a showstopper. OK, then we can't use fluido now, except we add anything in sequence (like it is today). This is terrible to read imho and so the question is if we need to wait for a new doxia release then. The updated version you posted is better. The headings are important. Just bolding text doesn't provide for accessibility, and doesn't provide screen readers the means to navigate through the page. We need to be mindful, with a framework as popular as Struts, that we are addressing the needs of all readers, so accessibility is very important. I think we should make the text somehow smaller if possible. It is very much too read and probably we should just have a teaser on the the various paragraphs. I disagree. The Recent Releases section needs to come back to the top, where it is prominent for the majority of existing users, who are returning for the latest update. The remainder of the page is designed for those new to Struts, and there needs to be enough meat right there on the home page to hold their interest and entice them to stay on the site, rather than just provide a bunch of links and hope they'll click on one. I didn't mean smaller in terms of font size, sorry for being unclear. Neither did I. :-) Actually the news section is on top right and very prominent to me. Struts has an Announcements page were everything is detail. This page is pretty useless if we write nearly everything on the frontpage. In addtion there are release notes. There are 3 different pages containing similar information. I don't think this is good and should be streamlined. The front page serves two sets of primary readers. Number one is the people who are looking for the latest update of the framework. That is why release notes is top and center on the existing site. Struts is so well known now that updates is *the* most needed information. Number two is introductory text for people new to Struts - just enough information for them to get oriented about the framework and understand where they need to go next. Everybody outside these two groups is on the way to somewhere else when they come to the front page. In addition, the current news on the front page are from 2008 two times and one from 2011. So... the 2008 news are not really helpful to anybody. I would remove them or keep them on the annoucments page if necessary. I agree with you about the 2.0.14 release. I expect it's still there just because nobody got around to removing it. The 1.3.10 release needs to stay because there are tens of thousands of people using Struts 1 in production, and they still need to be able to see what the latest release of that is, even if we think it's really old. In addtion, we should use some kind of news format. Like: 10.12.2001 Struts 2.2.3.1 released This release contains a security fix. See: Release Note And so on. I mean: date, short headline, short content (just one sentence) and the link to the release notes. For releases, that's exactly what Recent Releases is for, and that's why it should be at the top. Other announcements are on the Announcements page, linked from the menu. As mentioned it is on top (right). Only if you have a large screen *and* you dedicate that large screen to your browser window. See more below. Announcements page contains only the 2011 release. And recent releases cotains 2008 releases. Not very recent. See above. So - what do you think abou it? I see some significant issues with the sample home page: * The dark menu bar thing at the top wraps in a weird way, and starts to cover up the logos, which looks really bad. (And it's not obvious that it's a wrapping issue unless you have enough real estate to resize and avoid the wrap.) There are also weird garbage artifacts when you work with this menu bar. Given that it provides no additional functionality, is very ugly, and doesn't work well, I'd recommend scrapping it. This dark menu bar is called topbar in fludio terms. It is pretty easy to disable it and I have no problems with doing that. Basically it contains the same link as on the left side. I have left it in b/c many people seem to like that nowadays. Anyway, I am with you and remove it. Btw, the covering of the logo is b/c the topbar is fixed position. This
Re: Using fluido once available
Hello Martin, On Sun, Nov 27, 2011 at 3:57 AM, Martin Cooper mfncoo...@gmail.com wrote: On Sat, Nov 26, 2011 at 2:51 PM, Christian Grobmeier I have added a hero section. A what? This is the first huge section, showing what the page is about. Like here: http://incubator.apache.org/directmemory/ Unfortunately I needed to remove the h2, h3 etc to make this work because of a doxia bug. It seems it is already fixed in trunk, so I think we can leave it now and replace it later. (the bug replaces h2 with div class=sectonh2... - this kills everything) I'd say the missing h2, h3, et al, is a showstopper. OK, then we can't use fluido now, except we add anything in sequence (like it is today). This is terrible to read imho and so the question is if we need to wait for a new doxia release then. I think we should make the text somehow smaller if possible. It is very much too read and probably we should just have a teaser on the the various paragraphs. I disagree. The Recent Releases section needs to come back to the top, where it is prominent for the majority of existing users, who are returning for the latest update. The remainder of the page is designed for those new to Struts, and there needs to be enough meat right there on the home page to hold their interest and entice them to stay on the site, rather than just provide a bunch of links and hope they'll click on one. I didn't mean smaller in terms of font size, sorry for being unclear. Actually the news section is on top right and very prominent to me. Struts has an Announcements page were everything is detail. This page is pretty useless if we write nearly everything on the frontpage. In addtion there are release notes. There are 3 different pages containing similar information. I don't think this is good and should be streamlined. In addition, the current news on the front page are from 2008 two times and one from 2011. So... the 2008 news are not really helpful to anybody. I would remove them or keep them on the annoucments page if necessary. In addtion, we should use some kind of news format. Like: 10.12.2001 Struts 2.2.3.1 released This release contains a security fix. See: Release Note And so on. I mean: date, short headline, short content (just one sentence) and the link to the release notes. For releases, that's exactly what Recent Releases is for, and that's why it should be at the top. Other announcements are on the Announcements page, linked from the menu. As mentioned it is on top (right). Announcements page contains only the 2011 release. And recent releases cotains 2008 releases. Not very recent. So - what do you think abou it? I see some significant issues with the sample home page: * The dark menu bar thing at the top wraps in a weird way, and starts to cover up the logos, which looks really bad. (And it's not obvious that it's a wrapping issue unless you have enough real estate to resize and avoid the wrap.) There are also weird garbage artifacts when you work with this menu bar. Given that it provides no additional functionality, is very ugly, and doesn't work well, I'd recommend scrapping it. This dark menu bar is called topbar in fludio terms. It is pretty easy to disable it and I have no problems with doing that. Basically it contains the same link as on the left side. I have left it in b/c many people seem to like that nowadays. Anyway, I am with you and remove it. Btw, the covering of the logo is b/c the topbar is fixed position. This is what Gmail and those kind of apps do today, I think this is the reason why it has been brought into bootstrap. Well, i remove it. * There's a huge waste of space with just Apache Struts in a big font, one sentence, and two buttons. Given that this is right below both the ASF logo, at top left, and the Struts logo, at top right, this serves no function and just takes up space - and prime real estate, at that - and forces everyone to scroll to get to anything useful. This is the hero unit. Actually I disagree. It gives you the chance to see at one glance what it is about and leads you to the most important links: technic primer and downloads. I don't know what your monitor size is, but I don't have to scroll. Anyway this is a matter of taste, if others don't like it, I can remove it of course. * The column width does not increase as I resize my browser window. Yet I'm forced to resize the window to get the menu to render properly. Can you explain whcih browser size you are using? And which menu does not render - the topbar or the sidebar? Probably this will explain why you say the recents news are not on top, because they move down if the browser is to small. * We need proper headings (as mentioned above) rather than the random first words in a section in a big bold font. Section titles are chosen for meaning. As there is nobody parsing this site I wonder why this is so important for the moment when it looks the same. Of
Re: Using fluido once available
Hello Martin (and others), I have made an update based on your comments (and mine): http://code.grobmeier.de/struts-draft-v2/ Looks better for you now? Cheers On Sun, Nov 27, 2011 at 3:04 PM, Christian Grobmeier grobme...@gmail.com wrote: Hello Martin, On Sun, Nov 27, 2011 at 3:57 AM, Martin Cooper mfncoo...@gmail.com wrote: On Sat, Nov 26, 2011 at 2:51 PM, Christian Grobmeier I have added a hero section. A what? This is the first huge section, showing what the page is about. Like here: http://incubator.apache.org/directmemory/ Unfortunately I needed to remove the h2, h3 etc to make this work because of a doxia bug. It seems it is already fixed in trunk, so I think we can leave it now and replace it later. (the bug replaces h2 with div class=sectonh2... - this kills everything) I'd say the missing h2, h3, et al, is a showstopper. OK, then we can't use fluido now, except we add anything in sequence (like it is today). This is terrible to read imho and so the question is if we need to wait for a new doxia release then. I think we should make the text somehow smaller if possible. It is very much too read and probably we should just have a teaser on the the various paragraphs. I disagree. The Recent Releases section needs to come back to the top, where it is prominent for the majority of existing users, who are returning for the latest update. The remainder of the page is designed for those new to Struts, and there needs to be enough meat right there on the home page to hold their interest and entice them to stay on the site, rather than just provide a bunch of links and hope they'll click on one. I didn't mean smaller in terms of font size, sorry for being unclear. Actually the news section is on top right and very prominent to me. Struts has an Announcements page were everything is detail. This page is pretty useless if we write nearly everything on the frontpage. In addtion there are release notes. There are 3 different pages containing similar information. I don't think this is good and should be streamlined. In addition, the current news on the front page are from 2008 two times and one from 2011. So... the 2008 news are not really helpful to anybody. I would remove them or keep them on the annoucments page if necessary. In addtion, we should use some kind of news format. Like: 10.12.2001 Struts 2.2.3.1 released This release contains a security fix. See: Release Note And so on. I mean: date, short headline, short content (just one sentence) and the link to the release notes. For releases, that's exactly what Recent Releases is for, and that's why it should be at the top. Other announcements are on the Announcements page, linked from the menu. As mentioned it is on top (right). Announcements page contains only the 2011 release. And recent releases cotains 2008 releases. Not very recent. So - what do you think abou it? I see some significant issues with the sample home page: * The dark menu bar thing at the top wraps in a weird way, and starts to cover up the logos, which looks really bad. (And it's not obvious that it's a wrapping issue unless you have enough real estate to resize and avoid the wrap.) There are also weird garbage artifacts when you work with this menu bar. Given that it provides no additional functionality, is very ugly, and doesn't work well, I'd recommend scrapping it. This dark menu bar is called topbar in fludio terms. It is pretty easy to disable it and I have no problems with doing that. Basically it contains the same link as on the left side. I have left it in b/c many people seem to like that nowadays. Anyway, I am with you and remove it. Btw, the covering of the logo is b/c the topbar is fixed position. This is what Gmail and those kind of apps do today, I think this is the reason why it has been brought into bootstrap. Well, i remove it. * There's a huge waste of space with just Apache Struts in a big font, one sentence, and two buttons. Given that this is right below both the ASF logo, at top left, and the Struts logo, at top right, this serves no function and just takes up space - and prime real estate, at that - and forces everyone to scroll to get to anything useful. This is the hero unit. Actually I disagree. It gives you the chance to see at one glance what it is about and leads you to the most important links: technic primer and downloads. I don't know what your monitor size is, but I don't have to scroll. Anyway this is a matter of taste, if others don't like it, I can remove it of course. * The column width does not increase as I resize my browser window. Yet I'm forced to resize the window to get the menu to render properly. Can you explain whcih browser size you are using? And which menu does not render - the topbar or the sidebar? Probably this will explain why you say the recents news are not on top, because they move down if the browser is to
Re: Using fluido once available
Hello Christian, thank you for the preview, the new Site looks really clean and nice. So +1 from me to change the struts2 site layout. This morning I see the first preview with my mobile opera browser and I've got some trouble with black top navigation bar. Johannes - web: http://www.jgeppert.com twitter: http://twitter.com/jogep -- View this message in context: http://struts.1045723.n5.nabble.com/Using-fluido-once-available-tp4998141p5027047.html Sent from the Struts - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
Johannes, thanks. I have removed the black top bar here: http://code.grobmeier.de/struts-draft-v2 Can you check with this browser if you like that version better? Cheers Christian On Sun, Nov 27, 2011 at 8:16 PM, Johannes Geppert jo...@apache.org wrote: Hello Christian, thank you for the preview, the new Site looks really clean and nice. So +1 from me to change the struts2 site layout. This morning I see the first preview with my mobile opera browser and I've got some trouble with black top navigation bar. Johannes - web: http://www.jgeppert.com twitter: http://twitter.com/jogep -- View this message in context: http://struts.1045723.n5.nabble.com/Using-fluido-once-available-tp4998141p5027047.html Sent from the Struts - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
The top headline for 2.2.3.1 GA is *huge* in Chrome/Linux. http://imgur.com/v3fFN [image: huge.png] On Sun, Nov 27, 2011 at 2:28 PM, Christian Grobmeier grobme...@gmail.comwrote: Johannes, thanks. I have removed the black top bar here: http://code.grobmeier.de/struts-draft-v2 Can you check with this browser if you like that version better? Cheers Christian On Sun, Nov 27, 2011 at 8:16 PM, Johannes Geppert jo...@apache.org wrote: Hello Christian, thank you for the preview, the new Site looks really clean and nice. So +1 from me to change the struts2 site layout. This morning I see the first preview with my mobile opera browser and I've got some trouble with black top navigation bar. Johannes - web: http://www.jgeppert.com twitter: http://twitter.com/jogep -- View this message in context: http://struts.1045723.n5.nabble.com/Using-fluido-once-available-tp4998141p5027047.html Sent from the Struts - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
First of all, nice work :-) 2011/11/27 Christian Grobmeier grobme...@gmail.com: I'd say the missing h2, h3, et al, is a showstopper. OK, then we can't use fluido now, except we add anything in sequence (like it is today). This is terrible to read imho and so the question is if we need to wait for a new doxia release then. Sorry, but I really don't get it, where is the problem ? The page looks awesome and I don't see any problems with missing h2, h3, etc. I didn't mean smaller in terms of font size, sorry for being unclear. Actually the news section is on top right and very prominent to me. Struts has an Announcements page were everything is detail. This page is pretty useless if we write nearly everything on the frontpage. In addtion there are release notes. There are 3 different pages containing similar information. I don't think this is good and should be streamlined. In addition, the current news on the front page are from 2008 two times and one from 2011. So... the 2008 news are not really helpful to anybody. I would remove them or keep them on the annoucments page if necessary. The news section is ok, the only problem I see is that the main section is fixed sized and doesn't look good on a huge screen (24 compared to 15). Is it possible to change that ? * There's a huge waste of space with just Apache Struts in a big font, one sentence, and two buttons. Given that this is right below both the ASF logo, at top left, and the Struts logo, at top right, this serves no function and just takes up space - and prime real estate, at that - and forces everyone to scroll to get to anything useful. This is the hero unit. Actually I disagree. It gives you the chance to see at one glance what it is about and leads you to the most important links: technic primer and downloads. I don't know what your monitor size is, but I don't have to scroll. Anyway this is a matter of taste, if others don't like it, I can remove it of course. I'll say just to mix the both version, v1 with v2, like below Apache Struts The latest production release of Struts 2 is Struts 2.2.3.1 [_point to release notes_], which was promoted to General Availability (or Ready for Primetime) on 7 September 2011. Struts 2.2.3.1 includes important security fixes. All developers are strongly encouraged to update existing Struts 2 applications to Struts 2.2.3.1. | Download | | Read more | * We need proper headings (as mentioned above) rather than the random first words in a section in a big bold font. Section titles are chosen for meaning. As there is nobody parsing this site I wonder why this is so important for the moment when it looks the same. Of course I would like to have proper h2 etc too, but then fluido is not possible as explained above (or we use sequential paragraphs) I'd say, v1 looks better for me, in two cases the heading is the same as beginning of the sentence. If we don't have a good heading, v1 approach is better. * Visited links are not coloured differently from unvisited ones. Thats a feature of bootstrap. I have already had this discussion on the incubator ml. I don't like have the colors changed. But others seem to like it. If you would like that, please name me a color which you would like to see for visited links and I will use it. The same here, I really prefer sites without colour changes for the visited pages. I open the same pages many times and after some time they look the same - all the links are visited now ;) And we don't change the content that often to have visited links so important. Overall, it looks pretty and trendy, but actual usability has gone down the tubes and is pretty awful. I'd personally prefer to see us stick with what we have unless the usability can be brought back to at least what we have now. Usability is far more important than pretty or trendy. OK actually the current page is not very usable for me because: - way to much text on it - search is somewhere hidden on the bottom - no easy way to get to the downloads - outdated news - news do not differ in design from other text - everything to plain for my eyes - Announcments page does contain less information the recent releases box on frontpage - Release notes are not found easily (actually I am still searching while typing) - the page flow with the next links somewhere on the bottom is broken when you reach the Kickstart FAQ. Or is this intended? Usability is important, but changing the layout is far more important to show that the project is still alive. Redeploying a new version doesn't change much, just some numbers and dates. Changing layout says “We will always be there for you” ;-) And usability can be improved over time. I would say, do for it, redeploying a new site is 1 simpler than releasing a new version of Struts 2 ;-) Kind regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ Warszawa JUG conference - Confitura http://confitura.pl/
Re: Using fluido once available
Hello all, today fluido 1.0 came out. Here is my first draft (similar to Maurizios): http://code.grobmeier.de/struts-draft-v1/ (just one page) I have added a hero section. Unfortunately I needed to remove the h2, h3 etc to make this work because of a doxia bug. It seems it is already fixed in trunk, so I think we can leave it now and replace it later. (the bug replaces h2 with div class=sectonh2... - this kills everything) I think we should make the text somehow smaller if possible. It is very much too read and probably we should just have a teaser on the the various paragraphs. In addtion, we should use some kind of news format. Like: 10.12.2001 Struts 2.2.3.1 released This release contains a security fix. See: Release Note And so on. I mean: date, short headline, short content (just one sentence) and the link to the release notes. So - what do you think abou it? Cheers Christian On Wed, Nov 16, 2011 at 6:43 PM, Maurizio Cucchiara mcucchi...@apache.org wrote: Just for the record looks like Simone has already moved out of the sandbox the plugin https://svn.apache.org/repos/asf/maven/skins/trunk/maven-fluido-skin/ Anyway I would like to see a kind of refresh on struts website, you can count on my help. Twitter :http://www.twitter.com/m_cucchiara G+ :https://plus.google.com/107903711540963855921 Linkedin :http://www.linkedin.com/in/mauriziocucchiara Maurizio Cucchiara On 16 November 2011 17:47, Maurizio Cucchiara mcucchi...@apache.org wrote: Hi Christian, I have done some tests a couple of weeks ago, IIRC there was some issue using the fluido plugin. For what concern the website, consider that struts website root resides, as you noticed before, belong the following path http://svn.apache.org/repos/asf/struts/site/ Here there is the S2 website (nothing more than a single page :) ) http://svn.apache.org/repos/asf/struts/struts2/trunk/src/site/ And the third one, is used by the Confluence export plugin (I'm pretty sure, though I could be wrong) With that saying, I published the fluido verson of struts website http://people.apache.org/~mcucchiara/struts/www/ Let's see the first impressions (for example I just realized that fluido doesn't provide the links to S1, S2 on top bar). Twitter :http://www.twitter.com/m_cucchiara G+ :https://plus.google.com/107903711540963855921 Linkedin :http://www.linkedin.com/in/mauriziocucchiara Maurizio Cucchiara On 16 November 2011 16:50, Christian Grobmeier grobme...@gmail.com wrote: Hey folks, I have contributed a little to the efford of Simone Tripodi to create a maven skin called fluido. It is based on the great bootstrap css framework. Here is an example: http://people.apache.org/~simonetripodi/ Simone has proposed to move this skin now to maven proper (currently in sandbox) and all participants are working straight to a release. Now, if there is an interest (and I think so) I volunteer to migrate the Struts website to this new skin, once it is available. Would be nice to hear some opinions and maybe some wishes if there are any before I start to do the work. For reference, here is the Bootstrap website: http://twitter.github.com/bootstrap/ I have found this repository which could be skinned: http://svn.apache.org/repos/asf/struts/site/ Here is some more http://svn.apache.org/repos/asf/struts/struts2/trunk/src/site/ http://svn.apache.org/repos/asf/struts/struts2/trunk/core/src/site/ I am not sure about these sites - how are they used? It seems esp the second link has something to do with Confluence. Am I missing anything else? Cheers, Christian -- http://www.grobmeier.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
On Sat, Nov 26, 2011 at 2:51 PM, Christian Grobmeier grobme...@gmail.com wrote: Hello all, today fluido 1.0 came out. Here is my first draft (similar to Maurizios): http://code.grobmeier.de/struts-draft-v1/ (just one page) I have added a hero section. A what? Unfortunately I needed to remove the h2, h3 etc to make this work because of a doxia bug. It seems it is already fixed in trunk, so I think we can leave it now and replace it later. (the bug replaces h2 with div class=sectonh2... - this kills everything) I'd say the missing h2, h3, et al, is a showstopper. I think we should make the text somehow smaller if possible. It is very much too read and probably we should just have a teaser on the the various paragraphs. I disagree. The Recent Releases section needs to come back to the top, where it is prominent for the majority of existing users, who are returning for the latest update. The remainder of the page is designed for those new to Struts, and there needs to be enough meat right there on the home page to hold their interest and entice them to stay on the site, rather than just provide a bunch of links and hope they'll click on one. In addtion, we should use some kind of news format. Like: 10.12.2001 Struts 2.2.3.1 released This release contains a security fix. See: Release Note And so on. I mean: date, short headline, short content (just one sentence) and the link to the release notes. For releases, that's exactly what Recent Releases is for, and that's why it should be at the top. Other announcements are on the Announcements page, linked from the menu. So - what do you think abou it? I see some significant issues with the sample home page: * The dark menu bar thing at the top wraps in a weird way, and starts to cover up the logos, which looks really bad. (And it's not obvious that it's a wrapping issue unless you have enough real estate to resize and avoid the wrap.) There are also weird garbage artifacts when you work with this menu bar. Given that it provides no additional functionality, is very ugly, and doesn't work well, I'd recommend scrapping it. * There's a huge waste of space with just Apache Struts in a big font, one sentence, and two buttons. Given that this is right below both the ASF logo, at top left, and the Struts logo, at top right, this serves no function and just takes up space - and prime real estate, at that - and forces everyone to scroll to get to anything useful. * The column width does not increase as I resize my browser window. Yet I'm forced to resize the window to get the menu to render properly. * We need proper headings (as mentioned above) rather than the random first words in a section in a big bold font. Section titles are chosen for meaning. * The release information at the bottom is in a super-narrow column for no apparent reason, again forcing me to scroll unnecessarily. * The Next link, leading to the sequence running through our pages, is missing completely. * Visited links are not coloured differently from unvisited ones. Overall, it looks pretty and trendy, but actual usability has gone down the tubes and is pretty awful. I'd personally prefer to see us stick with what we have unless the usability can be brought back to at least what we have now. Usability is far more important than pretty or trendy. -- Martin Cooper Cheers Christian On Wed, Nov 16, 2011 at 6:43 PM, Maurizio Cucchiara mcucchi...@apache.org wrote: Just for the record looks like Simone has already moved out of the sandbox the plugin https://svn.apache.org/repos/asf/maven/skins/trunk/maven-fluido-skin/ Anyway I would like to see a kind of refresh on struts website, you can count on my help. Twitter :http://www.twitter.com/m_cucchiara G+ :https://plus.google.com/107903711540963855921 Linkedin :http://www.linkedin.com/in/mauriziocucchiara Maurizio Cucchiara On 16 November 2011 17:47, Maurizio Cucchiara mcucchi...@apache.org wrote: Hi Christian, I have done some tests a couple of weeks ago, IIRC there was some issue using the fluido plugin. For what concern the website, consider that struts website root resides, as you noticed before, belong the following path http://svn.apache.org/repos/asf/struts/site/ Here there is the S2 website (nothing more than a single page :) ) http://svn.apache.org/repos/asf/struts/struts2/trunk/src/site/ And the third one, is used by the Confluence export plugin (I'm pretty sure, though I could be wrong) With that saying, I published the fluido verson of struts website http://people.apache.org/~mcucchiara/struts/www/ Let's see the first impressions (for example I just realized that fluido doesn't provide the links to S1, S2 on top bar). Twitter :http://www.twitter.com/m_cucchiara G+ :https://plus.google.com/107903711540963855921 Linkedin :http://www.linkedin.com/in/mauriziocucchiara Maurizio Cucchiara On 16 November 2011 16:50, Christian
Re: Using fluido once available
@Christian very nice idea I would love to see it on the main page @Maurizio the site looks astonished, I would like to go for it, but I don't know if we need a vote (I think not ;-) Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ Warszawa JUG conference - Confitura http://confitura.pl/ 2011/11/16 Christian Grobmeier grobme...@gmail.com: On Wed, Nov 16, 2011 at 6:43 PM, Maurizio Cucchiara mcucchi...@apache.org wrote: Just for the record looks like Simone has already moved out of the sandbox the plugin Yes, he notified me via twitter hehe :-) And of course I am following the maven dev list currently. https://svn.apache.org/repos/asf/maven/skins/trunk/maven-fluido-skin/ Anyway I would like to see a kind of refresh on struts website, you can count on my help. Cool thanks. I will take a look at your work and together we might bring it to fly. Cheers Twitter :http://www.twitter.com/m_cucchiara G+ :https://plus.google.com/107903711540963855921 Linkedin :http://www.linkedin.com/in/mauriziocucchiara Maurizio Cucchiara On 16 November 2011 17:47, Maurizio Cucchiara mcucchi...@apache.org wrote: Hi Christian, I have done some tests a couple of weeks ago, IIRC there was some issue using the fluido plugin. For what concern the website, consider that struts website root resides, as you noticed before, belong the following path http://svn.apache.org/repos/asf/struts/site/ Here there is the S2 website (nothing more than a single page :) ) http://svn.apache.org/repos/asf/struts/struts2/trunk/src/site/ And the third one, is used by the Confluence export plugin (I'm pretty sure, though I could be wrong) With that saying, I published the fluido verson of struts website http://people.apache.org/~mcucchiara/struts/www/ Let's see the first impressions (for example I just realized that fluido doesn't provide the links to S1, S2 on top bar). Twitter :http://www.twitter.com/m_cucchiara G+ :https://plus.google.com/107903711540963855921 Linkedin :http://www.linkedin.com/in/mauriziocucchiara Maurizio Cucchiara On 16 November 2011 16:50, Christian Grobmeier grobme...@gmail.com wrote: Hey folks, I have contributed a little to the efford of Simone Tripodi to create a maven skin called fluido. It is based on the great bootstrap css framework. Here is an example: http://people.apache.org/~simonetripodi/ Simone has proposed to move this skin now to maven proper (currently in sandbox) and all participants are working straight to a release. Now, if there is an interest (and I think so) I volunteer to migrate the Struts website to this new skin, once it is available. Would be nice to hear some opinions and maybe some wishes if there are any before I start to do the work. For reference, here is the Bootstrap website: http://twitter.github.com/bootstrap/ I have found this repository which could be skinned: http://svn.apache.org/repos/asf/struts/site/ Here is some more http://svn.apache.org/repos/asf/struts/struts2/trunk/src/site/ http://svn.apache.org/repos/asf/struts/struts2/trunk/core/src/site/ I am not sure about these sites - how are they used? It seems esp the second link has something to do with Confluence. Am I missing anything else? Cheers, Christian -- http://www.grobmeier.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org -- http://www.grobmeier.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Using fluido once available
Hey folks, I have contributed a little to the efford of Simone Tripodi to create a maven skin called fluido. It is based on the great bootstrap css framework. Here is an example: http://people.apache.org/~simonetripodi/ Simone has proposed to move this skin now to maven proper (currently in sandbox) and all participants are working straight to a release. Now, if there is an interest (and I think so) I volunteer to migrate the Struts website to this new skin, once it is available. Would be nice to hear some opinions and maybe some wishes if there are any before I start to do the work. For reference, here is the Bootstrap website: http://twitter.github.com/bootstrap/ I have found this repository which could be skinned: http://svn.apache.org/repos/asf/struts/site/ Here is some more http://svn.apache.org/repos/asf/struts/struts2/trunk/src/site/ http://svn.apache.org/repos/asf/struts/struts2/trunk/core/src/site/ I am not sure about these sites - how are they used? It seems esp the second link has something to do with Confluence. Am I missing anything else? Cheers, Christian -- http://www.grobmeier.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
Hi Christian, I have done some tests a couple of weeks ago, IIRC there was some issue using the fluido plugin. For what concern the website, consider that struts website root resides, as you noticed before, belong the following path http://svn.apache.org/repos/asf/struts/site/ Here there is the S2 website (nothing more than a single page :) ) http://svn.apache.org/repos/asf/struts/struts2/trunk/src/site/ And the third one, is used by the Confluence export plugin (I'm pretty sure, though I could be wrong) With that saying, I published the fluido verson of struts website http://people.apache.org/~mcucchiara/struts/www/ Let's see the first impressions (for example I just realized that fluido doesn't provide the links to S1, S2 on top bar). Twitter :http://www.twitter.com/m_cucchiara G+ :https://plus.google.com/107903711540963855921 Linkedin :http://www.linkedin.com/in/mauriziocucchiara Maurizio Cucchiara On 16 November 2011 16:50, Christian Grobmeier grobme...@gmail.com wrote: Hey folks, I have contributed a little to the efford of Simone Tripodi to create a maven skin called fluido. It is based on the great bootstrap css framework. Here is an example: http://people.apache.org/~simonetripodi/ Simone has proposed to move this skin now to maven proper (currently in sandbox) and all participants are working straight to a release. Now, if there is an interest (and I think so) I volunteer to migrate the Struts website to this new skin, once it is available. Would be nice to hear some opinions and maybe some wishes if there are any before I start to do the work. For reference, here is the Bootstrap website: http://twitter.github.com/bootstrap/ I have found this repository which could be skinned: http://svn.apache.org/repos/asf/struts/site/ Here is some more http://svn.apache.org/repos/asf/struts/struts2/trunk/src/site/ http://svn.apache.org/repos/asf/struts/struts2/trunk/core/src/site/ I am not sure about these sites - how are they used? It seems esp the second link has something to do with Confluence. Am I missing anything else? Cheers, Christian -- http://www.grobmeier.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
Just for the record looks like Simone has already moved out of the sandbox the plugin https://svn.apache.org/repos/asf/maven/skins/trunk/maven-fluido-skin/ Anyway I would like to see a kind of refresh on struts website, you can count on my help. Twitter :http://www.twitter.com/m_cucchiara G+ :https://plus.google.com/107903711540963855921 Linkedin :http://www.linkedin.com/in/mauriziocucchiara Maurizio Cucchiara On 16 November 2011 17:47, Maurizio Cucchiara mcucchi...@apache.org wrote: Hi Christian, I have done some tests a couple of weeks ago, IIRC there was some issue using the fluido plugin. For what concern the website, consider that struts website root resides, as you noticed before, belong the following path http://svn.apache.org/repos/asf/struts/site/ Here there is the S2 website (nothing more than a single page :) ) http://svn.apache.org/repos/asf/struts/struts2/trunk/src/site/ And the third one, is used by the Confluence export plugin (I'm pretty sure, though I could be wrong) With that saying, I published the fluido verson of struts website http://people.apache.org/~mcucchiara/struts/www/ Let's see the first impressions (for example I just realized that fluido doesn't provide the links to S1, S2 on top bar). Twitter :http://www.twitter.com/m_cucchiara G+ :https://plus.google.com/107903711540963855921 Linkedin :http://www.linkedin.com/in/mauriziocucchiara Maurizio Cucchiara On 16 November 2011 16:50, Christian Grobmeier grobme...@gmail.com wrote: Hey folks, I have contributed a little to the efford of Simone Tripodi to create a maven skin called fluido. It is based on the great bootstrap css framework. Here is an example: http://people.apache.org/~simonetripodi/ Simone has proposed to move this skin now to maven proper (currently in sandbox) and all participants are working straight to a release. Now, if there is an interest (and I think so) I volunteer to migrate the Struts website to this new skin, once it is available. Would be nice to hear some opinions and maybe some wishes if there are any before I start to do the work. For reference, here is the Bootstrap website: http://twitter.github.com/bootstrap/ I have found this repository which could be skinned: http://svn.apache.org/repos/asf/struts/site/ Here is some more http://svn.apache.org/repos/asf/struts/struts2/trunk/src/site/ http://svn.apache.org/repos/asf/struts/struts2/trunk/core/src/site/ I am not sure about these sites - how are they used? It seems esp the second link has something to do with Confluence. Am I missing anything else? Cheers, Christian -- http://www.grobmeier.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Using fluido once available
On Wed, Nov 16, 2011 at 6:43 PM, Maurizio Cucchiara mcucchi...@apache.org wrote: Just for the record looks like Simone has already moved out of the sandbox the plugin Yes, he notified me via twitter hehe :-) And of course I am following the maven dev list currently. https://svn.apache.org/repos/asf/maven/skins/trunk/maven-fluido-skin/ Anyway I would like to see a kind of refresh on struts website, you can count on my help. Cool thanks. I will take a look at your work and together we might bring it to fly. Cheers Twitter :http://www.twitter.com/m_cucchiara G+ :https://plus.google.com/107903711540963855921 Linkedin :http://www.linkedin.com/in/mauriziocucchiara Maurizio Cucchiara On 16 November 2011 17:47, Maurizio Cucchiara mcucchi...@apache.org wrote: Hi Christian, I have done some tests a couple of weeks ago, IIRC there was some issue using the fluido plugin. For what concern the website, consider that struts website root resides, as you noticed before, belong the following path http://svn.apache.org/repos/asf/struts/site/ Here there is the S2 website (nothing more than a single page :) ) http://svn.apache.org/repos/asf/struts/struts2/trunk/src/site/ And the third one, is used by the Confluence export plugin (I'm pretty sure, though I could be wrong) With that saying, I published the fluido verson of struts website http://people.apache.org/~mcucchiara/struts/www/ Let's see the first impressions (for example I just realized that fluido doesn't provide the links to S1, S2 on top bar). Twitter :http://www.twitter.com/m_cucchiara G+ :https://plus.google.com/107903711540963855921 Linkedin :http://www.linkedin.com/in/mauriziocucchiara Maurizio Cucchiara On 16 November 2011 16:50, Christian Grobmeier grobme...@gmail.com wrote: Hey folks, I have contributed a little to the efford of Simone Tripodi to create a maven skin called fluido. It is based on the great bootstrap css framework. Here is an example: http://people.apache.org/~simonetripodi/ Simone has proposed to move this skin now to maven proper (currently in sandbox) and all participants are working straight to a release. Now, if there is an interest (and I think so) I volunteer to migrate the Struts website to this new skin, once it is available. Would be nice to hear some opinions and maybe some wishes if there are any before I start to do the work. For reference, here is the Bootstrap website: http://twitter.github.com/bootstrap/ I have found this repository which could be skinned: http://svn.apache.org/repos/asf/struts/site/ Here is some more http://svn.apache.org/repos/asf/struts/struts2/trunk/src/site/ http://svn.apache.org/repos/asf/struts/struts2/trunk/core/src/site/ I am not sure about these sites - how are they used? It seems esp the second link has something to do with Confluence. Am I missing anything else? Cheers, Christian -- http://www.grobmeier.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org -- http://www.grobmeier.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org