not to be offensive, but I don't really like this site design all that much...... It looks old... and dare I say a sf project page? sorry, but the current one looks better imo.--Ian "Inc" Caldwell
On 9/9/07, andres <[EMAIL PROTECTED]> wrote: > > El Sunday 09 September 2007 11:36:53 Andreas Volz escribió: > > Not bad. But the current design is also not bad. If I remember correct > > the E website engine is very flexible. Perhaps you're able to create a > > changeable stylesheet. Many websites have this. > Nah, I don't think is worth it, I made another design because I don't like > several decisions made with the current one, like using tables for laying > out > options that break when slightly bigger fonts are used or putting a BIG > piece > of the logo (with no function) occupying like 50% of the screen, etc. > > But rather than having a lengthy discussion about this I prefer to present > my > perspectives with my alternative "don't decorate, communicate, focus on > content, buzzword compliant 2.0" style that it's up to the developers to > follow or not. > > > But I think more important than style is content! The current content > > is... hm... "a bit raw in some parts". Perhaps you better spend time > > into improving the website content. :-? > > > I disagree, if I was a new user and went into the main page of the > official > website I would have a hard time finding the great (and updated!) articles > about EWL hosted in the wiki. > > Bad or disorganized design nullifies good contents almost completely (I'm > not > calling the current design bad or disorganized, this is a general > statement). > > Besides, as I said in my first mail, I do have some suggestions for > content > layout that could be applied regardless of the chosen design and I'm > writting > content as I can, look Z_en_coder up in the wiki. > I'm just worried about most users not knowing my articles in the wiki even > exist. > > But I'm writting content, for example, I'm currently half-way (in my local > mirror of the wiki) to a comprehensive application development with Edje > article, including not only standard EDC code and C API, but an > introduction > to evas, ecore, ecore_evas and how they relate to edje, the python and > ruby > APIs and the ruby based Redact compiler (+ Corrected versions of all code > examples I happen to come across while studying this). > > But as I said, its the developer's call, if they are interested in using a > design like this I can work on it further and implement it once we are all > satisfied, or I can just continue to write wiki articles. > > > > right menu: > > > http://img523.imageshack.us/my.php?image=ewebrightwt0.png > > > > I don't like this. There's no visual line between menu end and text > > start. > > > > regards > > Andreas > > > > ------------------------------------------------------------ > ------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2005. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > enlightenment-devel mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > enlightenment-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- --Inc www.inc-omplete.org www.inc-corporate.org ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
