Looking forward to G2... can't wait.
I thought I give you guys a tip for designing the new interface of the Gallery. 'A List Apart' features a great and easy to understand article on how to design a fluid thumbnail-interface. With this technique, there is no more need for(ugly nested) tables.
Here is the link:
<!-- BBCode Start --><A HREF="http://www.alistapart.com/stories/practicalcss/" TARGET="_blank">[ALA] "Tables are dead"</A><!-- BBCode End -->
Posts: 7994
Thanks for the link. I read through it; it looks pretty cool. I'm not sure how well using a CSS only interface will mesh with CMS based systems when we embed Gallery into systems like PostNuke, etc, but it's an interesting concept.
The nice thing about G2 is that the entire system will be templated and themeable so even though we're using tables for G2.0 (at least we are at the moment) it will be possible to create a whole redesign of the HTML and CSS for the app to move away from using CSS without changing a line of PHP.
Posts: 9
I'm glad to hear you like the article, and that you even consider using it.
Your theme-implementation sounds REALLY great. I wish you all the best for G2 and the other projects in your life, bharat. I understand from several sources on this site that you have other things to think about besides Gallery :- )
PS: I signed myself up to help with the Dutch translations, but never got an answer. My (spammable) emailadres is artifexcollect @ hotmail.com
Posts: 7994
Heh yeah I've been a bit busy lately. But I'm trying to keep working on G2 a little bit every day and constructive criticism from all sides is useful! Download a G2 snapshot and take a look at the way that I implemented themes and templates and let me know what you think.
Excellent. The easiest way to do it is to just read the docs/LOCALIZING document and follow its directions. Send us updates to the Dutch translations at any time and we'll commit them to the tree. Thanks!
Posts: 332
Just a note on CSS vs. Table. Many applications use both. The table to loosely structure the page into head, body, footer and then use the <div> for content within the sections.
By using both methods, I found gives the greatest control over how the different styles behave in different browsers.
Think of it this way. The table is a room in a house. The Div is the entertainment center (with all the components) on wheels and can be moved anywhere within the room with little effort using CSS.
I have taken Gallery 1.3.3 and implemented several CSS style tags within the table structure. I can now change the graphics and color of the tables at ease. BUT I cannot change the tables themselves dynamically (width/height/margin etc). You can do this if you have Div tags instead of tables.
Another thing that is wonderful about DIV is that it makes the code which resides inside it modular. In other words if the [login/logout] code was contained in a div(or set of divs) then I could move it to the header of my site with ease. I wouldn't have to worry if I'd forgotten a piece of code as everything inside the set of DIV tags would be for a specific purpose.
I'll take a look at G2 next chance I get.
:smile:
Jade
<!-- BBCode Start --><A HREF="http://pownuke.com/galleryskins" TARGET="_blank">Gallery Skins</A><!-- BBCode End -->