|
View:
New views
20 Messages
—
Rating Filter:
Alert me
|
| < Prev | 1 - 2 | Next > |
|
|
|
|
|
Re: Themeing G3Hi Stephen,
We feel that PHP is a bit more accessible than Smarty, especially since WP, Drupal, and several other projects use pure PHP in their templates. I would argue that PHP provides a lower barrier to theming than Smarty does. Drupal does not support Smarty by default. You must download and install a template engine to get Smarty support. It's quite possible that G3 will have a Smarty module at some point, but Smarty support will likely not ship with the core G3 distribution. We talked about the possibility for a color module, but like Smarty, there are no plans to include it in the core distribution at this time. We'll probably opt to document how to clone a theme and alter it's color via CSS. There's a lot to be done to improve our HTML and CSS and relatively ambitious timeline to complete it. - Chad On Oct 26, 2008, at 10:24 PM, Stephen Cupp wrote: > So to write a theme for G3 you need to know HTML, CSS, JS, and PHP? > IMO > that is a pretty high barrier of entry. I know there is nothing you > can > do about HTML, CSS, and JS, but PHP is another story. Smarty is so > much > easier to learn then PHP is. Is there a way to have both like Drupal > does? Also is there plans to have a color module like Drupal's > default > theme has? > > Stephen Cupp > > "Goaltending is a normal job, Sure! How would you like it in your job > if every time you made a mistake, a red light went on over your desk > and > fifteen thousand people stood up and yelled at you?" -Hall of Fame > Goaltender Jacques Plante > > gallery-devel-request@... wrote: > > >> @ Templating >> * Pure PHP >> * Form generation in views > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win > great prizes > Grand prize is a trip for two to an Open Source event anywhere in > the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > __[ g a l l e r y - d e v e l ]_________________________ > > [ list info/archive --> http://gallery.sf.net/lists.php ] > [ gallery info/FAQ/download --> http://gallery.sf.net ] ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ __[ g a l l e r y - d e v e l ]_________________________ [ list info/archive --> http://gallery.sf.net/lists.php ] [ gallery info/FAQ/download --> http://gallery.sf.net ] |
|
|
Re: G3 colorsOn Monday 27 October 2008 00:48:03 Chad Kieffer wrote:
> We'll probably opt to document how to clone a theme and alter > it's color via CSS. I imagine many folks feel that color adjustment is very important to individualization but... In ALA's latest article ( http://www.alistapart.com/articles/progressiveenhancementwithcss ), Aaron Gustafson discusses separation of css into functional units ( e.g. type.css, layout.css, color.css). I think this makes good structural sense. Seems to me this is fine to begin with. If the correct hooks and loops are there, making manipulations available in a GUI can be accomplished if that ever bubbles to the top of the to-do list (which is probably already several volumes long in some folks minds :) -- ----------------------------------------------------------------- | WRWeb Services | http://WRWeb.net | | 1482 Pleasant St. | (603)648-2251 | | Webster, NH, 03303-7613 | 19TBJ8040800540 | ----------------------------------------------------------------- | Web Sites Designed and Supported |Think Locally, Buy Locally! | ----------------------------------------------------------------- ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ __[ g a l l e r y - d e v e l ]_________________________ [ list info/archive --> http://gallery.sf.net/lists.php ] [ gallery info/FAQ/download --> http://gallery.sf.net ] |
|
|
Re: G3 colorsHi,
the only benefit i see for splitting css files is "better" structure. The author says its easier to maintain for example three smaller file than one big file. I do not agree. For example lets say there is a color.css I have .gAdminbar {} I would have it in main.css AND in color.css So i have to switch between two files depending on what i am changing. If there will be "colorpacks" you would need to ship main.css, green_color.css and red_color.css So i don't see a simplification and the structure is not that better. And another reason is, that the client has to do more HTTP requests. See http://developer.yahoo.com/performance/rules.html - Jens Quoting Brandon Sussman <Brandon@...>: > On Monday 27 October 2008 00:48:03 Chad Kieffer wrote: >> We'll probably opt to document how to clone a theme and alter >> it's color via CSS. > > I imagine many folks feel that color adjustment is very important to > individualization but... > > In ALA's latest article ( > http://www.alistapart.com/articles/progressiveenhancementwithcss ), Aaron > Gustafson discusses separation of css into functional units ( e.g. type.css, > layout.css, color.css). I think this makes good structural sense. > > Seems to me this is fine to begin with. If the correct hooks and loops are > there, making manipulations available in a GUI can be accomplished if that > ever bubbles to the top of the to-do list (which is probably already several > volumes long in some folks minds :) > > -- > ----------------------------------------------------------------- > | WRWeb Services | http://WRWeb.net | > | 1482 Pleasant St. | (603)648-2251 | > | Webster, NH, 03303-7613 | 19TBJ8040800540 | > ----------------------------------------------------------------- > | Web Sites Designed and Supported |Think Locally, Buy Locally! | > ----------------------------------------------------------------- > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > __[ g a l l e r y - d e v e l ]_________________________ > > [ list info/archive --> http://gallery.sf.net/lists.php ] > [ gallery info/FAQ/download --> http://gallery.sf.net ] > -- Ich sag mal .... Charisma ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ __[ g a l l e r y - d e v e l ]_________________________ [ list info/archive --> http://gallery.sf.net/lists.php ] [ gallery info/FAQ/download --> http://gallery.sf.net ] |
|
|
Re: G3 colorsOn the basis of that page, here's a wacky idea: noticing that the slowest
part of loading a new gallery page is downloading (in my case) 48 individiual thumbnails why not have gallery pre-build and cache the thumbnails for each page as a single jpg (sprite-like) and repeat it to show the individual images? ----- Original Message ----- From: "Jens A. Tkotz" <jens@...> To: <gallery-devel@...> Sent: Monday, October 27, 2008 3:13 PM Subject: Re: [Gallery-devel] G3 colors Hi, the only benefit i see for splitting css files is "better" structure. The author says its easier to maintain for example three smaller file than one big file. I do not agree. For example lets say there is a color.css I have .gAdminbar {} I would have it in main.css AND in color.css So i have to switch between two files depending on what i am changing. If there will be "colorpacks" you would need to ship main.css, green_color.css and red_color.css So i don't see a simplification and the structure is not that better. And another reason is, that the client has to do more HTTP requests. See http://developer.yahoo.com/performance/rules.html - Jens Quoting Brandon Sussman <Brandon@...>: > On Monday 27 October 2008 00:48:03 Chad Kieffer wrote: >> We'll probably opt to document how to clone a theme and alter >> it's color via CSS. > > I imagine many folks feel that color adjustment is very important to > individualization but... > > In ALA's latest article ( > http://www.alistapart.com/articles/progressiveenhancementwithcss ), Aaron > Gustafson discusses separation of css into functional units ( e.g. > type.css, > layout.css, color.css). I think this makes good structural sense. > > Seems to me this is fine to begin with. If the correct hooks and loops > are > there, making manipulations available in a GUI can be accomplished if > that > ever bubbles to the top of the to-do list (which is probably already > several > volumes long in some folks minds :) > > -- > ----------------------------------------------------------------- > | WRWeb Services | http://WRWeb.net | > | 1482 Pleasant St. | (603)648-2251 | > | Webster, NH, 03303-7613 | 19TBJ8040800540 | > ----------------------------------------------------------------- > | Web Sites Designed and Supported |Think Locally, Buy Locally! | > ----------------------------------------------------------------- > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the > world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > __[ g a l l e r y - d e v e l ]_________________________ > > [ list info/archive --> http://gallery.sf.net/lists.php ] > [ gallery info/FAQ/download --> http://gallery.sf.net ] > -- Ich sag mal .... Charisma ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ __[ g a l l e r y - d e v e l ]_________________________ [ list info/archive --> http://gallery.sf.net/lists.php ] [ gallery info/FAQ/download --> http://gallery.sf.net ] ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ __[ g a l l e r y - d e v e l ]_________________________ [ list info/archive --> http://gallery.sf.net/lists.php ] [ gallery info/FAQ/download --> http://gallery.sf.net ] |
|
|
Re: G3 colorsJens A. Tkotz wrote:
> Hi, > > the only benefit i see for splitting css files is "better" structure. > The author says its easier to maintain for example three smaller file > than one big file. > > I do not agree. > For example lets say there is a color.css > I have .gAdminbar {} > I would have it in main.css AND in color.css > So i have to switch between two files depending on what i am changing. > If there will be "colorpacks" you would need to ship main.css, > green_color.css and red_color.css > So i don't see a simplification and the structure is not that better. Chad and I discussed this a little bit. Really what we're talking about here is how we structure the CSS in the default theme that Gallery ships (right now in Gx, all the CSS is in the default theme). I am not thrilled about it because when I get in there to modify CSS I always get irritated by having to bounce between several files to figure out where to put what. But I defer to Chad/Jakob/Jens on this. > And another reason is, that the client has to do more HTTP requests. > See http://developer.yahoo.com/performance/rules.html I agree. IMO, we should use a css combiner like we do with JS files so that we load all JS/CSS with a single request. -Bharat ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ __[ g a l l e r y - d e v e l ]_________________________ [ list info/archive --> http://gallery.sf.net/lists.php ] [ gallery info/FAQ/download --> http://gallery.sf.net ] |
|
|
Re: G3 colorsAlec Myers wrote:
> On the basis of that page, here's a wacky idea: noticing that the slowest > part of loading a new gallery page is downloading (in my case) 48 > individiual thumbnails why not have gallery pre-build and cache the > thumbnails for each page as a single jpg (sprite-like) and repeat it to show > the individual images? We can definitely sprite all the thumbnails, but that adds complexity in the base case. Instead, we're going to start by changing the security model so that thumbnail images can be loaded directly from disk without PHP. Depending on your system speed this will make thumbnail processing be an order of magnitude faster (or more if you're not using an opcode cache). If that's still not fast enough, we should look into spriting. -Bharat ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ __[ g a l l e r y - d e v e l ]_________________________ [ list info/archive --> http://gallery.sf.net/lists.php ] [ gallery info/FAQ/download --> http://gallery.sf.net ] |
|
|
Re: G3 colorsHi Alec,
We discussed the multiple CSS file approach during the code sprint. Jens brings up good points that I agree with. Although G3 may likely provide css file compression to collect separate css files for combination, this would add an extra level of complexity. I think it's best for now if we stick with a single css file per media type and promote a standard grouping of CSS definitions in that file. We can use comments to identify and explain each group in the file. I don't see how a single file approach would hinder or complicate theme or module driven color changes. - Chad On Oct 27, 2008, at 10:08 AM, "Alec Myers" <alec@...> wrote: > On the basis of that page, here's a wacky idea: noticing that the > slowest > part of loading a new gallery page is downloading (in my case) 48 > individiual thumbnails why not have gallery pre-build and cache the > thumbnails for each page as a single jpg (sprite-like) and repeat it > to show > the individual images? > > ----- Original Message ----- > From: "Jens A. Tkotz" <jens@...> > To: <gallery-devel@...> > Sent: Monday, October 27, 2008 3:13 PM > Subject: Re: [Gallery-devel] G3 colors > > > Hi, > > the only benefit i see for splitting css files is "better" structure. > The author says its easier to maintain for example three smaller file > than one big file. > > I do not agree. > For example lets say there is a color.css > I have .gAdminbar {} > I would have it in main.css AND in color.css > So i have to switch between two files depending on what i am changing. > If there will be "colorpacks" you would need to ship main.css, > green_color.css and red_color.css > So i don't see a simplification and the structure is not that better. > > > And another reason is, that the client has to do more HTTP requests. > See http://developer.yahoo.com/performance/rules.html > > - Jens > > > > Quoting Brandon Sussman <Brandon@...>: > >> On Monday 27 October 2008 00:48:03 Chad Kieffer wrote: >>> We'll probably opt to document how to clone a theme and alter >>> it's color via CSS. >> >> I imagine many folks feel that color adjustment is very important to >> individualization but... >> >> In ALA's latest article ( >> http://www.alistapart.com/articles/progressiveenhancementwithcss ), >> Aaron >> Gustafson discusses separation of css into functional units ( e.g. >> type.css, >> layout.css, color.css). I think this makes good structural sense. >> >> Seems to me this is fine to begin with. If the correct hooks and >> loops >> are >> there, making manipulations available in a GUI can be accomplished >> if >> that >> ever bubbles to the top of the to-do list (which is probably already >> several >> volumes long in some folks minds :) >> >> -- >> ----------------------------------------------------------------- >> | WRWeb Services | http://WRWeb.net | >> | 1482 Pleasant St. | (603)648-2251 | >> | Webster, NH, 03303-7613 | 19TBJ8040800540 | >> ----------------------------------------------------------------- >> | Web Sites Designed and Supported |Think Locally, Buy Locally! | >> ----------------------------------------------------------------- >> >> --- >> --- >> ------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's >> challenge >> Build the coolest Linux based applications with Moblin SDK & win >> great >> prizes >> Grand prize is a trip for two to an Open Source event anywhere in the >> world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> __[ g a l l e r y - d e v e l ]_________________________ >> >> [ list info/archive --> http://gallery.sf.net/lists.php ] >> [ gallery info/FAQ/download --> http://gallery.sf.net ] >> > > > > -- > > Ich sag mal .... Charisma > > --- > ---------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in > the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > __[ g a l l e r y - d e v e l ]_________________________ > > [ list info/archive --> http://gallery.sf.net/lists.php ] > [ gallery info/FAQ/download --> http://gallery.sf.net ] > > > > --- > ---------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win > great prizes > Grand prize is a trip for two to an Open Source event anywhere in > the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > __[ g a l l e r y - d e v e l ]_________________________ > > [ list info/archive --> http://gallery.sf.net/lists.php ] > [ gallery info/FAQ/download --> http://gallery.sf.net ] ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ __[ g a l l e r y - d e v e l ]_________________________ [ list info/archive --> http://gallery.sf.net/lists.php ] [ gallery info/FAQ/download --> http://gallery.sf.net ] |
|
|
Re: G3 colorsI think a user friendly and simple approach to this problem would be to,
AFTER we are done with our single main.css file, to provide another template CSS file that only has the color information. So for somebody that only wants to change the colors of his Gallery (which I agree is probably a common use case), he can take the colors.css, change the colors and use it to override the defaults of the theme. He doesn't even have to clone the theme for this. And it doesn't add any complexity to the default theme. This would require the maintenance of the colors.css stylesheet in addition to the main.css stylesheet. But the effort should be manageable and it would not be a big breakdown if any individual color-style is missing in the colors.css What do people think? --Jakob Chad Kieffer wrote: > Hi Alec, > > We discussed the multiple CSS file approach during the code sprint. > Jens brings up good points that I agree with. Although G3 may likely > provide css file compression to collect separate css files for > combination, this would add an extra level of complexity. > > I think it's best for now if we stick with a single css file per media > type and promote a standard grouping of CSS definitions in that file. > We can use comments to identify and explain each group in the file. > > I don't see how a single file approach would hinder or complicate > theme or module driven color changes. > > - Chad > > On Oct 27, 2008, at 10:08 AM, "Alec Myers" <alec@...> wrote: > >> On the basis of that page, here's a wacky idea: noticing that the >> slowest >> part of loading a new gallery page is downloading (in my case) 48 >> individiual thumbnails why not have gallery pre-build and cache the >> thumbnails for each page as a single jpg (sprite-like) and repeat it >> to show >> the individual images? >> >> ----- Original Message ----- >> From: "Jens A. Tkotz" <jens@...> >> To: <gallery-devel@...> >> Sent: Monday, October 27, 2008 3:13 PM >> Subject: Re: [Gallery-devel] G3 colors >> >> >> Hi, >> >> the only benefit i see for splitting css files is "better" structure. >> The author says its easier to maintain for example three smaller file >> than one big file. >> >> I do not agree. >> For example lets say there is a color.css >> I have .gAdminbar {} >> I would have it in main.css AND in color.css >> So i have to switch between two files depending on what i am changing. >> If there will be "colorpacks" you would need to ship main.css, >> green_color.css and red_color.css >> So i don't see a simplification and the structure is not that better. >> >> >> And another reason is, that the client has to do more HTTP requests. >> See http://developer.yahoo.com/performance/rules.html >> >> - Jens >> >> >> >> Quoting Brandon Sussman <Brandon@...>: >> >>> On Monday 27 October 2008 00:48:03 Chad Kieffer wrote: >>>> We'll probably opt to document how to clone a theme and alter >>>> it's color via CSS. >>> I imagine many folks feel that color adjustment is very important to >>> individualization but... >>> >>> In ALA's latest article ( >>> http://www.alistapart.com/articles/progressiveenhancementwithcss ), >>> Aaron >>> Gustafson discusses separation of css into functional units ( e.g. >>> type.css, >>> layout.css, color.css). I think this makes good structural sense. >>> >>> Seems to me this is fine to begin with. If the correct hooks and >>> loops >>> are >>> there, making manipulations available in a GUI can be accomplished >>> if >>> that >>> ever bubbles to the top of the to-do list (which is probably already >>> several >>> volumes long in some folks minds :) >>> >>> -- >>> ----------------------------------------------------------------- >>> | WRWeb Services | http://WRWeb.net | >>> | 1482 Pleasant St. | (603)648-2251 | >>> | Webster, NH, 03303-7613 | 19TBJ8040800540 | >>> ----------------------------------------------------------------- >>> | Web Sites Designed and Supported |Think Locally, Buy Locally! | >>> ----------------------------------------------------------------- >>> >>> --- >>> --- >>> ------------------------------------------------------------------- >>> This SF.Net email is sponsored by the Moblin Your Move Developer's >>> challenge >>> Build the coolest Linux based applications with Moblin SDK & win >>> great >>> prizes >>> Grand prize is a trip for two to an Open Source event anywhere in the >>> world >>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>> __[ g a l l e r y - d e v e l ]_________________________ >>> >>> [ list info/archive --> http://gallery.sf.net/lists.php ] >>> [ gallery info/FAQ/download --> http://gallery.sf.net ] >>> >> >> >> -- >> >> Ich sag mal .... Charisma >> >> --- >> ---------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's >> challenge >> Build the coolest Linux based applications with Moblin SDK & win great >> prizes >> Grand prize is a trip for two to an Open Source event anywhere in >> the world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> __[ g a l l e r y - d e v e l ]_________________________ >> >> [ list info/archive --> http://gallery.sf.net/lists.php ] >> [ gallery info/FAQ/download --> http://gallery.sf.net ] >> >> >> >> --- >> ---------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's >> challenge >> Build the coolest Linux based applications with Moblin SDK & win >> great prizes >> Grand prize is a trip for two to an Open Source event anywhere in >> the world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> __[ g a l l e r y - d e v e l ]_________________________ >> >> [ list info/archive --> http://gallery.sf.net/lists.php ] >> [ gallery info/FAQ/download --> http://gallery.sf.net ] > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > __[ g a l l e r y - d e v e l ]_________________________ > > [ list info/archive --> http://gallery.sf.net/lists.php ] > [ gallery info/FAQ/download --> http://gallery.sf.net ] ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ __[ g a l l e r y - d e v e l ]_________________________ [ list info/archive --> http://gallery.sf.net/lists.php ] [ gallery info/FAQ/download --> http://gallery.sf.net ] |
|
|
Re: G3 colorsHi Chad,
I'm pretty much +/- 0 on most of these discussions. Whatever you guys choose will be fine. I'm certainly *not* going to waste time caring how the curly brackets are arranged, how many tabs are used for indentation, or what style of capitalisation is used for variable names. I'll leave that to the real programmers ;-) -Alec ----- Original Message ----- From: "Chad Kieffer" <chad@...> To: "Alec Myers" <alec@...> Cc: <gallery-devel@...> Sent: Monday, October 27, 2008 5:08 PM Subject: Re: [Gallery-devel] G3 colors Hi Alec, We discussed the multiple CSS file approach during the code sprint. Jens brings up good points that I agree with. Although G3 may likely provide css file compression to collect separate css files for combination, this would add an extra level of complexity. I think it's best for now if we stick with a single css file per media type and promote a standard grouping of CSS definitions in that file. We can use comments to identify and explain each group in the file. I don't see how a single file approach would hinder or complicate theme or module driven color changes. - Chad On Oct 27, 2008, at 10:08 AM, "Alec Myers" <alec@...> wrote: > On the basis of that page, here's a wacky idea: noticing that the > slowest > part of loading a new gallery page is downloading (in my case) 48 > individiual thumbnails why not have gallery pre-build and cache the > thumbnails for each page as a single jpg (sprite-like) and repeat it > to show > the individual images? > > ----- Original Message ----- > From: "Jens A. Tkotz" <jens@...> > To: <gallery-devel@...> > Sent: Monday, October 27, 2008 3:13 PM > Subject: Re: [Gallery-devel] G3 colors > > > Hi, > > the only benefit i see for splitting css files is "better" structure. > The author says its easier to maintain for example three smaller file > than one big file. > > I do not agree. > For example lets say there is a color.css > I have .gAdminbar {} > I would have it in main.css AND in color.css > So i have to switch between two files depending on what i am changing. > If there will be "colorpacks" you would need to ship main.css, > green_color.css and red_color.css > So i don't see a simplification and the structure is not that better. > > > And another reason is, that the client has to do more HTTP requests. > See http://developer.yahoo.com/performance/rules.html > > - Jens > > > > Quoting Brandon Sussman <Brandon@...>: > >> On Monday 27 October 2008 00:48:03 Chad Kieffer wrote: >>> We'll probably opt to document how to clone a theme and alter >>> it's color via CSS. >> >> I imagine many folks feel that color adjustment is very important to >> individualization but... >> >> In ALA's latest article ( >> http://www.alistapart.com/articles/progressiveenhancementwithcss ), >> Aaron >> Gustafson discusses separation of css into functional units ( e.g. >> type.css, >> layout.css, color.css). I think this makes good structural sense. >> >> Seems to me this is fine to begin with. If the correct hooks and >> loops >> are >> there, making manipulations available in a GUI can be accomplished >> if >> that >> ever bubbles to the top of the to-do list (which is probably already >> several >> volumes long in some folks minds :) >> >> -- >> ----------------------------------------------------------------- >> | WRWeb Services | http://WRWeb.net | >> | 1482 Pleasant St. | (603)648-2251 | >> | Webster, NH, 03303-7613 | 19TBJ8040800540 | >> ----------------------------------------------------------------- >> | Web Sites Designed and Supported |Think Locally, Buy Locally! | >> ----------------------------------------------------------------- >> >> --- >> --- >> ------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's >> challenge >> Build the coolest Linux based applications with Moblin SDK & win >> great >> prizes >> Grand prize is a trip for two to an Open Source event anywhere in the >> world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> __[ g a l l e r y - d e v e l ]_________________________ >> >> [ list info/archive --> http://gallery.sf.net/lists.php ] >> [ gallery info/FAQ/download --> http://gallery.sf.net ] >> > > > > -- > > Ich sag mal .... Charisma > > --- > ---------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in > the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > __[ g a l l e r y - d e v e l ]_________________________ > > [ list info/archive --> http://gallery.sf.net/lists.php ] > [ gallery info/FAQ/download --> http://gallery.sf.net ] > > > > --- > ---------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win > great prizes > Grand prize is a trip for two to an Open Source event anywhere in > the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > __[ g a l l e r y - d e v e l ]_________________________ > > [ list info/archive --> http://gallery.sf.net/lists.php ] > [ gallery info/FAQ/download --> http://gallery.sf.net ] ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ __[ g a l l e r y - d e v e l ]_________________________ [ list info/archive --> http://gallery.sf.net/lists.php ] [ gallery info/FAQ/download --> http://gallery.sf.net ] |
|
|
Re: G3 colorsOn Mon, Oct 27, 2008 at 11:02 AM, Alec Myers <alec@...> wrote: Hi Chad, You can mock all you want, it matters.</cross-thread-interference> - Andy
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ __[ g a l l e r y - d e v e l ]_________________________ [ list info/archive --> http://gallery.sf.net/lists.php ] [ gallery info/FAQ/download --> http://gallery.sf.net ] |
|
|
Re: G3 colorsSounds reasonable to me. Who's responsibility is to to load the sheet?
The G3 framework or the themed's? On Oct 27, 2008, at 12:01 PM, Jakob Hilden <jhild@...> wrote: > I think a user friendly and simple approach to this problem would be > to, > AFTER we are done with our single main.css file, to provide another > template CSS file that only has the color information. So for > somebody > that only wants to change the colors of his Gallery (which I agree is > probably a common use case), he can take the colors.css, change the > colors and use it to override the defaults of the theme. He doesn't > even have to clone the theme for this. And it doesn't add any > complexity to the default theme. > > This would require the maintenance of the colors.css stylesheet in > addition to the main.css stylesheet. But the effort should be > manageable and it would not be a big breakdown if any individual > color-style is missing in the colors.css > > What do people think? > > --Jakob > > > > Chad Kieffer wrote: >> Hi Alec, >> >> We discussed the multiple CSS file approach during the code sprint. >> Jens brings up good points that I agree with. Although G3 may likely >> provide css file compression to collect separate css files for >> combination, this would add an extra level of complexity. >> >> I think it's best for now if we stick with a single css file per >> media >> type and promote a standard grouping of CSS definitions in that >> file. >> We can use comments to identify and explain each group in the file. >> >> I don't see how a single file approach would hinder or complicate >> theme or module driven color changes. >> >> - Chad >> >> On Oct 27, 2008, at 10:08 AM, "Alec Myers" <alec@...> >> wrote: >> >>> On the basis of that page, here's a wacky idea: noticing that the >>> slowest >>> part of loading a new gallery page is downloading (in my case) 48 >>> individiual thumbnails why not have gallery pre-build and cache the >>> thumbnails for each page as a single jpg (sprite-like) and repeat it >>> to show >>> the individual images? >>> >>> ----- Original Message ----- >>> From: "Jens A. Tkotz" <jens@...> >>> To: <gallery-devel@...> >>> Sent: Monday, October 27, 2008 3:13 PM >>> Subject: Re: [Gallery-devel] G3 colors >>> >>> >>> Hi, >>> >>> the only benefit i see for splitting css files is "better" >>> structure. >>> The author says its easier to maintain for example three smaller >>> file >>> than one big file. >>> >>> I do not agree. >>> For example lets say there is a color.css >>> I have .gAdminbar {} >>> I would have it in main.css AND in color.css >>> So i have to switch between two files depending on what i am >>> changing. >>> If there will be "colorpacks" you would need to ship main.css, >>> green_color.css and red_color.css >>> So i don't see a simplification and the structure is not that >>> better. >>> >>> >>> And another reason is, that the client has to do more HTTP requests. >>> See http://developer.yahoo.com/performance/rules.html >>> >>> - Jens >>> >>> >>> >>> Quoting Brandon Sussman <Brandon@...>: >>> >>>> On Monday 27 October 2008 00:48:03 Chad Kieffer wrote: >>>>> We'll probably opt to document how to clone a theme and alter >>>>> it's color via CSS. >>>> I imagine many folks feel that color adjustment is very important >>>> to >>>> individualization but... >>>> >>>> In ALA's latest article ( >>>> http://www.alistapart.com/articles/progressiveenhancementwithcss ), >>>> Aaron >>>> Gustafson discusses separation of css into functional units ( e.g. >>>> type.css, >>>> layout.css, color.css). I think this makes good structural sense. >>>> >>>> Seems to me this is fine to begin with. If the correct hooks and >>>> loops >>>> are >>>> there, making manipulations available in a GUI can be accomplished >>>> if >>>> that >>>> ever bubbles to the top of the to-do list (which is probably >>>> already >>>> several >>>> volumes long in some folks minds :) >>>> >>>> -- >>>> ----------------------------------------------------------------- >>>> | WRWeb Services | http://WRWeb.net | >>>> | 1482 Pleasant St. | (603)648-2251 | >>>> | Webster, NH, 03303-7613 | 19TBJ8040800540 | >>>> ----------------------------------------------------------------- >>>> | Web Sites Designed and Supported |Think Locally, Buy Locally! | >>>> ----------------------------------------------------------------- >>>> >>>> --- >>>> --- >>>> ------------------------------------------------------------------- >>>> This SF.Net email is sponsored by the Moblin Your Move Developer's >>>> challenge >>>> Build the coolest Linux based applications with Moblin SDK & win >>>> great >>>> prizes >>>> Grand prize is a trip for two to an Open Source event anywhere in >>>> the >>>> world >>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>>> __[ g a l l e r y - d e v e l ]_________________________ >>>> >>>> [ list info/archive --> http://gallery.sf.net/lists.php ] >>>> [ gallery info/FAQ/download --> http://gallery.sf.net ] >>>> >>> >>> >>> -- >>> >>> Ich sag mal .... Charisma >>> >>> --- >>> --- >>> ------------------------------------------------------------------- >>> This SF.Net email is sponsored by the Moblin Your Move Developer's >>> challenge >>> Build the coolest Linux based applications with Moblin SDK & win >>> great >>> prizes >>> Grand prize is a trip for two to an Open Source event anywhere in >>> the world >>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>> __[ g a l l e r y - d e v e l ]_________________________ >>> >>> [ list info/archive --> http://gallery.sf.net/lists.php ] >>> [ gallery info/FAQ/download --> http://gallery.sf.net ] >>> >>> >>> >>> --- >>> --- >>> ------------------------------------------------------------------- >>> This SF.Net email is sponsored by the Moblin Your Move Developer's >>> challenge >>> Build the coolest Linux based applications with Moblin SDK & win >>> great prizes >>> Grand prize is a trip for two to an Open Source event anywhere in >>> the world >>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>> __[ g a l l e r y - d e v e l ]_________________________ >>> >>> [ list info/archive --> http://gallery.sf.net/lists.php ] >>> [ gallery info/FAQ/download --> http://gallery.sf.net ] >> >> --- >> --- >> ------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's >> challenge >> Build the coolest Linux based applications with Moblin SDK & win >> great prizes >> Grand prize is a trip for two to an Open Source event anywhere in >> the world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> __[ g a l l e r y - d e v e l ]_________________________ >> >> [ list info/archive --> http://gallery.sf.net/lists.php ] >> [ gallery info/FAQ/download --> http://gallery.sf.net ] > > --- > ---------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win > great prizes > Grand prize is a trip for two to an Open Source event anywhere in > the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > __[ g a l l e r y - d e v e l ]_________________________ > > [ list info/archive --> http://gallery.sf.net/lists.php ] > [ gallery info/FAQ/download --> http://gallery.sf.net ] ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ __[ g a l l e r y - d e v e l ]_________________________ [ list info/archive --> http://gallery.sf.net/lists.php ] [ gallery info/FAQ/download --> http://gallery.sf.net ] |
|
|
Re: G3 colorsThat should have been "themer's" not "themed's" ;)
On Oct 27, 2008, at 12:33 PM, Chad Kieffer <chad@...> wrote: > Sounds reasonable to me. Who's responsibility is to to load the sheet? > The G3 framework or the themed's? > > On Oct 27, 2008, at 12:01 PM, Jakob Hilden <jhild@...> wrote: > >> I think a user friendly and simple approach to this problem would be >> to, >> AFTER we are done with our single main.css file, to provide another >> template CSS file that only has the color information. So for >> somebody >> that only wants to change the colors of his Gallery (which I agree is >> probably a common use case), he can take the colors.css, change the >> colors and use it to override the defaults of the theme. He doesn't >> even have to clone the theme for this. And it doesn't add any >> complexity to the default theme. >> >> This would require the maintenance of the colors.css stylesheet in >> addition to the main.css stylesheet. But the effort should be >> manageable and it would not be a big breakdown if any individual >> color-style is missing in the colors.css >> >> What do people think? >> >> --Jakob >> >> >> >> Chad Kieffer wrote: >>> Hi Alec, >>> >>> We discussed the multiple CSS file approach during the code sprint. >>> Jens brings up good points that I agree with. Although G3 may likely >>> provide css file compression to collect separate css files for >>> combination, this would add an extra level of complexity. >>> >>> I think it's best for now if we stick with a single css file per >>> media >>> type and promote a standard grouping of CSS definitions in that >>> file. >>> We can use comments to identify and explain each group in the file. >>> >>> I don't see how a single file approach would hinder or complicate >>> theme or module driven color changes. >>> >>> - Chad >>> >>> On Oct 27, 2008, at 10:08 AM, "Alec Myers" <alec@...> >>> wrote: >>> >>>> On the basis of that page, here's a wacky idea: noticing that the >>>> slowest >>>> part of loading a new gallery page is downloading (in my case) 48 >>>> individiual thumbnails why not have gallery pre-build and cache the >>>> thumbnails for each page as a single jpg (sprite-like) and repeat >>>> it >>>> to show >>>> the individual images? >>>> >>>> ----- Original Message ----- >>>> From: "Jens A. Tkotz" <jens@...> >>>> To: <gallery-devel@...> >>>> Sent: Monday, October 27, 2008 3:13 PM >>>> Subject: Re: [Gallery-devel] G3 colors >>>> >>>> >>>> Hi, >>>> >>>> the only benefit i see for splitting css files is "better" >>>> structure. >>>> The author says its easier to maintain for example three smaller >>>> file >>>> than one big file. >>>> >>>> I do not agree. >>>> For example lets say there is a color.css >>>> I have .gAdminbar {} >>>> I would have it in main.css AND in color.css >>>> So i have to switch between two files depending on what i am >>>> changing. >>>> If there will be "colorpacks" you would need to ship main.css, >>>> green_color.css and red_color.css >>>> So i don't see a simplification and the structure is not that >>>> better. >>>> >>>> >>>> And another reason is, that the client has to do more HTTP >>>> requests. >>>> See http://developer.yahoo.com/performance/rules.html >>>> >>>> - Jens >>>> >>>> >>>> >>>> Quoting Brandon Sussman <Brandon@...>: >>>> >>>>> On Monday 27 October 2008 00:48:03 Chad Kieffer wrote: >>>>>> We'll probably opt to document how to clone a theme and alter >>>>>> it's color via CSS. >>>>> I imagine many folks feel that color adjustment is very important >>>>> to >>>>> individualization but... >>>>> >>>>> In ALA's latest article ( >>>>> http://www.alistapart.com/articles/ >>>>> progressiveenhancementwithcss ), >>>>> Aaron >>>>> Gustafson discusses separation of css into functional units ( e.g. >>>>> type.css, >>>>> layout.css, color.css). I think this makes good structural sense. >>>>> >>>>> Seems to me this is fine to begin with. If the correct hooks and >>>>> loops >>>>> are >>>>> there, making manipulations available in a GUI can be >>>>> accomplished >>>>> if >>>>> that >>>>> ever bubbles to the top of the to-do list (which is probably >>>>> already >>>>> several >>>>> volumes long in some folks minds :) >>>>> >>>>> -- >>>>> ----------------------------------------------------------------- >>>>> | WRWeb Services | http://WRWeb.net | >>>>> | 1482 Pleasant St. | (603)648-2251 | >>>>> | Webster, NH, 03303-7613 | 19TBJ8040800540 | >>>>> ----------------------------------------------------------------- >>>>> | Web Sites Designed and Supported |Think Locally, Buy Locally! | >>>>> ----------------------------------------------------------------- >>>>> >>>>> --- >>>>> --- >>>>> --- >>>>> ---------------------------------------------------------------- >>>>> This SF.Net email is sponsored by the Moblin Your Move Developer's >>>>> challenge >>>>> Build the coolest Linux based applications with Moblin SDK & win >>>>> great >>>>> prizes >>>>> Grand prize is a trip for two to an Open Source event anywhere in >>>>> the >>>>> world >>>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>>>> __[ g a l l e r y - d e v e l ]_________________________ >>>>> >>>>> [ list info/archive --> http://gallery.sf.net/lists.php ] >>>>> [ gallery info/FAQ/download --> http://gallery.sf.net ] >>>>> >>>> >>>> >>>> -- >>>> >>>> Ich sag mal .... Charisma >>>> >>>> --- >>>> --- >>>> ------------------------------------------------------------------- >>>> This SF.Net email is sponsored by the Moblin Your Move Developer's >>>> challenge >>>> Build the coolest Linux based applications with Moblin SDK & win >>>> great >>>> prizes >>>> Grand prize is a trip for two to an Open Source event anywhere in >>>> the world >>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>>> __[ g a l l e r y - d e v e l ]_________________________ >>>> >>>> [ list info/archive --> http://gallery.sf.net/lists.php ] >>>> [ gallery info/FAQ/download --> http://gallery.sf.net ] >>>> >>>> >>>> >>>> --- >>>> --- >>>> ------------------------------------------------------------------- >>>> This SF.Net email is sponsored by the Moblin Your Move Developer's >>>> challenge >>>> Build the coolest Linux based applications with Moblin SDK & win >>>> great prizes >>>> Grand prize is a trip for two to an Open Source event anywhere in >>>> the world >>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>>> __[ g a l l e r y - d e v e l ]_________________________ >>>> >>>> [ list info/archive --> http://gallery.sf.net/lists.php ] >>>> [ gallery info/FAQ/download --> http://gallery.sf.net ] >>> >>> --- >>> --- >>> ------------------------------------------------------------------- >>> This SF.Net email is sponsored by the Moblin Your Move Developer's >>> challenge >>> Build the coolest Linux based applications with Moblin SDK & win >>> great prizes >>> Grand prize is a trip for two to an Open Source event anywhere in >>> the world >>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>> __[ g a l l e r y - d e v e l ]_________________________ >>> >>> [ list info/archive --> http://gallery.sf.net/lists.php ] >>> [ gallery info/FAQ/download --> http://gallery.sf.net ] >> >> --- >> --- >> ------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's >> challenge >> Build the coolest Linux based applications with Moblin SDK & win >> great prizes >> Grand prize is a trip for two to an Open Source event anywhere in >> the world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> __[ g a l l e r y - d e v e l ]_________________________ >> >> [ list info/archive --> http://gallery.sf.net/lists.php ] >> [ gallery info/FAQ/download --> http://gallery.sf.net ] > > --- > ---------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win > great prizes > Grand prize is a trip for two to an Open Source event anywhere in > the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > __[ g a l l e r y - d e v e l ]_________________________ > > [ list info/archive --> http://gallery.sf.net/lists.php ] > [ gallery info/FAQ/download --> http://gallery.sf.net ] ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ __[ g a l l e r y - d e v e l ]_________________________ [ list info/archive --> http://gallery.sf.net/lists.php ] [ gallery info/FAQ/download --> http://gallery.sf.net ] |
|
|
Re: G3 colorsChad Kieffer wrote:
> That should have been "themer's" not "themed's" ;) > > On Oct 27, 2008, at 12:33 PM, Chad Kieffer <chad@...> wrote: > >> Sounds reasonable to me. Who's responsibility is to to load the sheet? >> The G3 framework or the themed's? Unless we put it in a known place in each theme, it would have to be the theme's responsibility. But that's good, because it allows each themer to decide their theme's layout. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ __[ g a l l e r y - d e v e l ]_________________________ [ list info/archive --> http://gallery.sf.net/lists.php ] [ gallery info/FAQ/download --> http://gallery.sf.net ] |
|
|
Re: G3 colorsAha.
Alec Myers schrieb: > Hi Chad, > > I'm pretty much +/- 0 on most of these discussions. Whatever you guys choose > will be fine. I'm certainly *not* going to waste time caring how the curly > brackets are arranged, how many tabs are used for indentation, or what style > of capitalisation is used for variable names. I'll leave that to the real > programmers ;-) > > -Alec > > > > ----- Original Message ----- > From: "Chad Kieffer" <chad@...> > To: "Alec Myers" <alec@...> > Cc: <gallery-devel@...> > Sent: Monday, October 27, 2008 5:08 PM > Subject: Re: [Gallery-devel] G3 colors > > > Hi Alec, > > We discussed the multiple CSS file approach during the code sprint. > Jens brings up good points that I agree with. Although G3 may likely > provide css file compression to collect separate css files for > combination, this would add an extra level of complexity. > > I think it's best for now if we stick with a single css file per media > type and promote a standard grouping of CSS definitions in that file. > We can use comments to identify and explain each group in the file. > > I don't see how a single file approach would hinder or complicate > theme or module driven color changes. > > - Chad > > On Oct 27, 2008, at 10:08 AM, "Alec Myers" <alec@...> wrote: > >> On the basis of that page, here's a wacky idea: noticing that the >> slowest >> part of loading a new gallery page is downloading (in my case) 48 >> individiual thumbnails why not have gallery pre-build and cache the >> thumbnails for each page as a single jpg (sprite-like) and repeat it >> to show >> the individual images? >> >> ----- Original Message ----- >> From: "Jens A. Tkotz" <jens@...> >> To: <gallery-devel@...> >> Sent: Monday, October 27, 2008 3:13 PM >> Subject: Re: [Gallery-devel] G3 colors >> >> >> Hi, >> >> the only benefit i see for splitting css files is "better" structure. >> The author says its easier to maintain for example three smaller file >> than one big file. >> >> I do not agree. >> For example lets say there is a color.css >> I have .gAdminbar {} >> I would have it in main.css AND in color.css >> So i have to switch between two files depending on what i am changing. >> If there will be "colorpacks" you would need to ship main.css, >> green_color.css and red_color.css >> So i don't see a simplification and the structure is not that better. >> >> >> And another reason is, that the client has to do more HTTP requests. >> See http://developer.yahoo.com/performance/rules.html >> >> - Jens >> >> >> >> Quoting Brandon Sussman <Brandon@...>: >> >>> On Monday 27 October 2008 00:48:03 Chad Kieffer wrote: >>>> We'll probably opt to document how to clone a theme and alter >>>> it's color via CSS. >>> I imagine many folks feel that color adjustment is very important to >>> individualization but... >>> >>> In ALA's latest article ( >>> http://www.alistapart.com/articles/progressiveenhancementwithcss ), >>> Aaron >>> Gustafson discusses separation of css into functional units ( e.g. >>> type.css, >>> layout.css, color.css). I think this makes good structural sense. >>> >>> Seems to me this is fine to begin with. If the correct hooks and >>> loops >>> are >>> there, making manipulations available in a GUI can be accomplished >>> if >>> that >>> ever bubbles to the top of the to-do list (which is probably already >>> several >>> volumes long in some folks minds :) >>> >>> -- >>> ----------------------------------------------------------------- >>> | WRWeb Services | http://WRWeb.net | >>> | 1482 Pleasant St. | (603)648-2251 | >>> | Webster, NH, 03303-7613 | 19TBJ8040800540 | >>> ----------------------------------------------------------------- >>> | Web Sites Designed and Supported |Think Locally, Buy Locally! | >>> ----------------------------------------------------------------- >>> >>> --- >>> --- >>> ------------------------------------------------------------------- >>> This SF.Net email is sponsored by the Moblin Your Move Developer's >>> challenge >>> Build the coolest Linux based applications with Moblin SDK & win >>> great >>> prizes >>> Grand prize is a trip for two to an Open Source event anywhere in the >>> world >>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>> __[ g a l l e r y - d e v e l ]_________________________ >>> >>> [ list info/archive --> http://gallery.sf.net/lists.php ] >>> [ gallery info/FAQ/download --> http://gallery.sf.net ] >>> >> >> >> -- >> >> Ich sag mal .... Charisma >> >> --- >> ---------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's >> challenge >> Build the coolest Linux based applications with Moblin SDK & win great >> prizes >> Grand prize is a trip for two to an Open Source event anywhere in >> the world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> __[ g a l l e r y - d e v e l ]_________________________ >> >> [ list info/archive --> http://gallery.sf.net/lists.php ] >> [ gallery info/FAQ/download --> http://gallery.sf.net ] >> >> >> >> --- >> ---------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's >> challenge >> Build the coolest Linux based applications with Moblin SDK & win >> great prizes >> Grand prize is a trip for two to an Open Source event anywhere in >> the world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> __[ g a l l e r y - d e v e l ]_________________________ >> >> [ list info/archive --> http://gallery.sf.net/lists.php ] >> [ gallery info/FAQ/download --> http://gallery.sf.net ] > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > __[ g a l l e r y - d e v e l ]_________________________ > > [ list info/archive --> http://gallery.sf.net/lists.php ] > [ gallery info/FAQ/download --> http://gallery.sf.net ] ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ __[ g a l l e r y - d e v e l ]_________________________ [ list info/archive --> http://gallery.sf.net/lists.php ] [ gallery info/FAQ/download --> http://gallery.sf.net ] |
|
|
Re: Themeing G3Who is G3 aimed at? Those people that know how to theme in WP and
Drupal will want to run G3 embedded and just want the basic HTML so it doesn't break their WP or Drupal theme. It is my view that decisions like this are made by the developers who didn't wrap their heads around what the users needs are. Unless you are subscribed to this list you have no idea what's going on. Maybe I missed it, but have the developers asked the rest of the community what they want. I haven't seen any polls or forum topics or a survey. When I look through the Theme Development Forum I see questions like "Carbon Theme: changing logo" or "Carbon Theme: how to change the logo link?". Are these the people who are going to think PHP is better then Smarty? Now I'm not trying to be harsh because sometimes I fall into this trap too. Those that know PHP will think a pure PHP themeing system is the best. Those who don't know PHP is another story. I'm also skeptical about the documentation for this new themeing system. As I've said here numerous times I feel that is G2's biggest weak point. Bharat told me he didn't like to write documentation and no amount of wishing is going to change that. He also said he wanted to write G3 in a way so there is not a need for much documentation. Stephen Cupp "Goaltending is a normal job, Sure! How would you like it in your job if every time you made a mistake, a red light went on over your desk and fifteen thousand people stood up and yelled at you?" -Hall of Fame Goaltender Jacques Plante Chad Kieffer wrote: > Hi Stephen, > > We feel that PHP is a bit more accessible than Smarty, especially since > WP, Drupal, and several other projects use pure PHP in their templates. > I would argue that PHP provides a lower barrier to theming than Smarty > does. > > Drupal does not support Smarty by default. You must download and install > a template engine to get Smarty support. It's quite possible that G3 > will have a Smarty module at some point, but Smarty support will likely > not ship with the core G3 distribution. > > We talked about the possibility for a color module, but like Smarty, > there are no plans to include it in the core distribution at this time. > We'll probably opt to document how to clone a theme and alter it's color > via CSS. > > There's a lot to be done to improve our HTML and CSS and relatively > ambitious timeline to complete it. > > - Chad > > On Oct 26, 2008, at 10:24 PM, Stephen Cupp wrote: > >> So to write a theme for G3 you need to know HTML, CSS, JS, and PHP? IMO >> that is a pretty high barrier of entry. I know there is nothing you can >> do about HTML, CSS, and JS, but PHP is another story. Smarty is so much >> easier to learn then PHP is. Is there a way to have both like Drupal >> does? Also is there plans to have a color module like Drupal's default >> theme has? >> >> Stephen Cupp >> >> "Goaltending is a normal job, Sure! How would you like it in your job >> if every time you made a mistake, a red light went on over your desk and >> fifteen thousand people stood up and yelled at you?" -Hall of Fame >> Goaltender Jacques Plante >> >> gallery-devel-request@... wrote: >> >> >>> @ Templating >>> * Pure PHP >>> * Form generation in views >> >> ------------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's >> challenge >> Build the coolest Linux based applications with Moblin SDK & win great >> prizes >> Grand prize is a trip for two to an Open Source event anywhere in the >> world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> __[ g a l l e r y - d e v e l ]_________________________ >> >> [ list info/archive --> http://gallery.sf.net/lists.php ] >> [ gallery info/FAQ/download --> http://gallery.sf.net ] > > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ __[ g a l l e r y - d e v e l ]_________________________ [ list info/archive --> http://gallery.sf.net/lists.php ] [ gallery info/FAQ/download --> http://gallery.sf.net ] |
|
|
Re: G3 colorsWhile most of the current discussions are over my head, there is some in
this that I understand... making it easier for someone like me to play with colours ! That pleases me! - and I expect hundreds of others. The simpler it can be for us to hack themes and colour schemes the better. Gaynor ----- Original Message ----- From: "Jakob Hilden" <jhild@...> To: "Chad Kieffer" <chad@...>; <gallery-devel@...> Sent: Tuesday, October 28, 2008 7:01 AM Subject: Re: [Gallery-devel] G3 colors >I think a user friendly and simple approach to this problem would be to, > AFTER we are done with our single main.css file, to provide another > template CSS file that only has the color information. So for somebody > that only wants to change the colors of his Gallery (which I agree is > probably a common use case), he can take the colors.css, change the > colors and use it to override the defaults of the theme. He doesn't > even have to clone the theme for this. And it doesn't add any > complexity to the default theme. > > This would require the maintenance of the colors.css stylesheet in > addition to the main.css stylesheet. But the effort should be > manageable and it would not be a big breakdown if any individual > color-style is missing in the colors.css > > What do people think? > > --Jakob > > > > Chad Kieffer wrote: >> Hi Alec, >> >> We discussed the multiple CSS file approach during the code sprint. >> Jens brings up good points that I agree with. Although G3 may likely >> provide css file compression to collect separate css files for >> combination, this would add an extra level of complexity. >> >> I think it's best for now if we stick with a single css file per media >> type and promote a standard grouping of CSS definitions in that file. >> We can use comments to identify and explain each group in the file. >> >> I don't see how a single file approach would hinder or complicate >> theme or module driven color changes. >> >> - Chad >> >> On Oct 27, 2008, at 10:08 AM, "Alec Myers" <alec@...> wrote: >> >>> On the basis of that page, here's a wacky idea: noticing that the >>> slowest >>> part of loading a new gallery page is downloading (in my case) 48 >>> individiual thumbnails why not have gallery pre-build and cache the >>> thumbnails for each page as a single jpg (sprite-like) and repeat it >>> to show >>> the individual images? >>> >>> ----- Original Message ----- >>> From: "Jens A. Tkotz" <jens@...> >>> To: <gallery-devel@...> >>> Sent: Monday, October 27, 2008 3:13 PM >>> Subject: Re: [Gallery-devel] G3 colors >>> >>> >>> Hi, >>> >>> the only benefit i see for splitting css files is "better" structure. >>> The author says its easier to maintain for example three smaller file >>> than one big file. >>> >>> I do not agree. >>> For example lets say there is a color.css >>> I have .gAdminbar {} >>> I would have it in main.css AND in color.css >>> So i have to switch between two files depending on what i am changing. >>> If there will be "colorpacks" you would need to ship main.css, >>> green_color.css and red_color.css >>> So i don't see a simplification and the structure is not that better. >>> >>> >>> And another reason is, that the client has to do more HTTP requests. >>> See http://developer.yahoo.com/performance/rules.html >>> >>> - Jens >>> >>> >>> >>> Quoting Brandon Sussman <Brandon@...>: >>> >>>> On Monday 27 October 2008 00:48:03 Chad Kieffer wrote: >>>>> We'll probably opt to document how to clone a theme and alter >>>>> it's color via CSS. >>>> I imagine many folks feel that color adjustment is very important to >>>> individualization but... >>>> >>>> In ALA's latest article ( >>>> http://www.alistapart.com/articles/progressiveenhancementwithcss ), >>>> Aaron >>>> Gustafson discusses separation of css into functional units ( e.g. >>>> type.css, >>>> layout.css, color.css). I think this makes good structural sense. >>>> >>>> Seems to me this is fine to begin with. If the correct hooks and >>>> loops >>>> are >>>> there, making manipulations available in a GUI can be accomplished >>>> if >>>> that >>>> ever bubbles to the top of the to-do list (which is probably already >>>> several >>>> volumes long in some folks minds :) >>>> >>>> -- >>>> ----------------------------------------------------------------- >>>> | WRWeb Services | http://WRWeb.net | >>>> | 1482 Pleasant St. | (603)648-2251 | >>>> | Webster, NH, 03303-7613 | 19TBJ8040800540 | >>>> ----------------------------------------------------------------- >>>> | Web Sites Designed and Supported |Think Locally, Buy Locally! | >>>> ----------------------------------------------------------------- >>>> >>>> --- >>>> --- >>>> ------------------------------------------------------------------- >>>> This SF.Net email is sponsored by the Moblin Your Move Developer's >>>> challenge >>>> Build the coolest Linux based applications with Moblin SDK & win >>>> great >>>> prizes >>>> Grand prize is a trip for two to an Open Source event anywhere in the >>>> world >>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>>> __[ g a l l e r y - d e v e l ]_________________________ >>>> >>>> [ list info/archive --> http://gallery.sf.net/lists.php ] >>>> [ gallery info/FAQ/download --> http://gallery.sf.net ] >>>> >>> >>> >>> -- >>> >>> Ich sag mal .... Charisma >>> >>> --- >>> ---------------------------------------------------------------------- >>> This SF.Net email is sponsored by the Moblin Your Move Developer's >>> challenge >>> Build the coolest Linux based applications with Moblin SDK & win great >>> prizes >>> Grand prize is a trip for two to an Open Source event anywhere in >>> the world >>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>> __[ g a l l e r y - d e v e l ]_________________________ >>> >>> [ list info/archive --> http://gallery.sf.net/lists.php ] >>> [ gallery info/FAQ/download --> http://gallery.sf.net ] >>> >>> >>> >>> --- >>> ---------------------------------------------------------------------- >>> This SF.Net email is sponsored by the Moblin Your Move Developer's >>> challenge >>> Build the coolest Linux based applications with Moblin SDK & win >>> great prizes >>> Grand prize is a trip for two to an Open Source event anywhere in >>> the world >>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>> __[ g a l l e r y - d e v e l ]_________________________ >>> >>> [ list info/archive --> http://gallery.sf.net/lists.php ] >>> [ gallery info/FAQ/download --> http://gallery.sf.net ] >> >> ------------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's >> challenge >> Build the coolest Linux based applications with Moblin SDK & win great >> prizes >> Grand prize is a trip for two to an Open Source event anywhere in the >> world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> __[ g a l l e r y - d e v e l ]_________________________ >> >> [ list info/archive --> http://gallery.sf.net/lists.php ] >> [ gallery info/FAQ/download --> http://gallery.sf.net ] > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the > world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > __[ g a l l e r y - d e v e l ]_________________________ > > [ list info/archive --> http://gallery.sf.net/lists.php ] > [ gallery info/FAQ/download --> http://gallery ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ __[ g a l l e r y - d e v e l ]_________________________ [ list info/archive --> http://gallery.sf.net/lists.php ] [ gallery info/FAQ/download --> http://gallery.sf.net ] |
|
|
Documentation - was Re: Themeing G3I share Stephen's concern about lack of documentation.
I believe good documentation is essential. I know I often have to look up how to do certain things, even things I have been thoroughly familiar with - if I have not done them for a while. Good documentation will hugely reduce the repetitive threads in forums and thus save everyone's time. Unfortunately when I once suggested that some of us less adanced, and not yet to developer stage, might form a writers team, I was told the writers do need to be at the advanced level to fully understand what is/should be happening. So it becomes a rather circular getting nowhere. I still think a writers team could be a good idea. We would need to consult with the core team to check we understood things and that what we wrote was correct etc, but although that would be work for the core team at that stage, it would free them later when the writers could watch the forums, and refer people to the relevant place in documentation. I have found often the information needed is actually in the current documentation, but not easily found. Indexing it all is an important part. This is something I could take part in. Gaynor ----- Original Message ----- From: "Stephen Cupp" <lvthunder@...> To: "Chad Kieffer" <chad@...> Cc: <gallery-devel@...> Sent: Tuesday, October 28, 2008 5:41 PM Subject: Re: [Gallery-devel] Themeing G3 > Who is G3 aimed at? Those people that know how to theme in WP and > Drupal will want to run G3 embedded and just want the basic HTML so it > doesn't break their WP or Drupal theme. > > It is my view that decisions like this are made by the developers who > didn't wrap their heads around what the users needs are. Unless you are > subscribed to this list you have no idea what's going on. Maybe I > missed it, but have the developers asked the rest of the community what > they want. I haven't seen any polls or forum topics or a survey. When > I look through the Theme Development Forum I see questions like "Carbon > Theme: changing logo" or "Carbon Theme: how to change the logo link?". > Are these the people who are going to think PHP is better then Smarty? > Now I'm not trying to be harsh because sometimes I fall into this > trap too. Those that know PHP will think a pure PHP themeing system is > the best. Those who don't know PHP is another story. > > I'm also skeptical about the documentation for this new themeing system. > As I've said here numerous times I feel that is G2's biggest weak > point. Bharat told me he didn't like to write documentation and no > amount of wishing is going to change that. He also said he wanted to > write G3 in a way so there is not a need for much documentation. > > Stephen Cupp > > "Goaltending is a normal job, Sure! How would you like it in your job > if every time you made a mistake, a red light went on over your desk and > fifteen thousand people stood up and yelled at you?" -Hall of Fame > Goaltender Jacques Plante > > Chad Kieffer wrote: >> Hi Stephen, >> >> We feel that PHP is a bit more accessible than Smarty, especially since >> WP, Drupal, and several other projects use pure PHP in their templates. >> I would argue that PHP provides a lower barrier to theming than Smarty >> does. >> >> Drupal does not support Smarty by default. You must download and install >> a template engine to get Smarty support. It's quite possible that G3 >> will have a Smarty module at some point, but Smarty support will likely >> not ship with the core G3 distribution. >> >> We talked about the possibility for a color module, but like Smarty, >> there are no plans to include it in the core distribution at this time. >> We'll probably opt to document how to clone a theme and alter it's color >> via CSS. >> >> There's a lot to be done to improve our HTML and CSS and relatively >> ambitious timeline to complete it. >> >> - Chad >> >> On Oct 26, 2008, at 10:24 PM, Stephen Cupp wrote: >> >>> So to write a theme for G3 you need to know HTML, CSS, JS, and PHP? IMO >>> that is a pretty high barrier of entry. I know there is nothing you can >>> do about HTML, CSS, and JS, but PHP is another story. Smarty is so much >>> easier to learn then PHP is. Is there a way to have both like Drupal >>> does? Also is there plans to have a color module like Drupal's default >>> theme has? >>> >>> Stephen Cupp >>> >>> "Goaltending is a normal job, Sure! How would you like it in your job >>> if every time you made a mistake, a red light went on over your desk and >>> fifteen thousand people stood up and yelled at you?" -Hall of Fame >>> Goaltender Jacques Plante >>> >>> gallery-devel-request@... wrote: >>> >>> >>>> @ Templating >>>> * Pure PHP >>>> * Form generation in views >>> >>> ------------------------------------------------------------------------- >>> This SF.Net email is sponsored by the Moblin Your Move Developer's >>> challenge >>> Build the coolest Linux based applications with Moblin SDK & win great >>> prizes >>> Grand prize is a trip for two to an Open Source event anywhere in the >>> world >>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>> __[ g a l l e r y - d e v e l ]_________________________ >>> >>> [ list info/archive --> http://gallery.sf.net/lists.php ] >>> [ gallery info/FAQ/download --> http://gallery.sf.net ] >> >> > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the > world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > __[ g a l l e r y - d e v e l ]_________________________ > > [ list info/archive --> http://gallery.sf.net/lists.php ] > [ gallery info/FAQ/download --> http://gallery.sf.net ] ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ __[ g a l l e r y - d e v e l ]_________________________ [ list info/archive --> http://gallery.sf.net/lists.php ] [ gallery info/FAQ/download --> http://gallery.sf.net ] |
|
|
Re: Themeing G3Stephen Cupp wrote:
> Who is G3 aimed at? Those people that know how to theme in WP and > Drupal will want to run G3 embedded and just want the basic HTML so it > doesn't break their WP or Drupal theme. > > It is my view that decisions like this are made by the developers who > didn't wrap their heads around what the users needs are. Unless you are > subscribed to this list you have no idea what's going on. Maybe I > missed it, but have the developers asked the rest of the community what > they want. I haven't seen any polls or forum topics or a survey. When > I look through the Theme Development Forum I see questions like "Carbon > Theme: changing logo" or "Carbon Theme: how to change the logo link?". > Are these the people who are going to think PHP is better then Smarty? > Now I'm not trying to be harsh because sometimes I fall into this > trap too. Those that know PHP will think a pure PHP themeing system is > the best. Those who don't know PHP is another story. Stephen, I'm not going to take offense that you're basically saying that I don't understand our user base. I don't think that a poll is an appropriate way to figure out a solution for something like this. We made a measured decision based on a variety of criteria. 1) It's 1 less technology to learn. We expect that themers will know some PHP, or have to learn it. Even with Smarty templates, they still needed to know a *little* PHP. And if they don't know either Smarty or PHP then they need to learn one thing either way. It just needs to be well documented and easy (which is achievable in either case). 2) PHP templates are fast and commonly used. Joomla, Drupal, Wordpress, PHP-Nuke, and others follow this paradigm. This demonstrates that there's a large and thriving base of people who know how to use PHP to create themes. Taking a survey is not the way to make a clear decision. We're doing this for technical reasons and we believe that it'll be at least as easy to understand to the themer as Smarty is. 3) I have personally spent a huge amount of time trying to create a good metaphor for template layers like Smarty on top of our existing system and I've found that this additional layer is slow and confusing. It requires a compilation phase, generates new PHP files off in an unexpected location, leads to permission errors that cause rendering to fail, requires the reader to go off and read and understand the Smarty documentation to do anything more complicated than variable interpolation, and has confusing error messages. 4) Smarty's choice of tag delimiters interfere with two of the most common and basic operations that themers want: using curly braces in CSS and Javascript. So PHP is faster, smaller, better known. > I'm also skeptical about the documentation for this new themeing system. > As I've said here numerous times I feel that is G2's biggest weak > point. Bharat told me he didn't like to write documentation and no > amount of wishing is going to change that. He also said he wanted to > write G3 in a way so there is not a need for much documentation. Ok, I hear what you're saying. But hear this: a new theming system is coming. If you'd like the documentation to be better this time around, how about you take charge of the theming documentation effort and we work together on it? I'll answer every single one of your questions for you in as much detail as you can handle, you are in charge of getting it down in a form that people understand. You'll also be in charge of following through on it and not taking off in the middle of the project. Step up and get involved and you can make a difference here. Otherwise, while I appreciate your skepticism, it's not going to change the outcome. -Bharat ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ __[ g a l l e r y - d e v e l ]_________________________ [ list info/archive --> http://gallery.sf.net/lists.php ] [ gallery info/FAQ/download --> http://gallery.sf.net ] |
|
|
Re: Documentation - was Re: Themeing G3Gaynor McCartney wrote:
> I still think a writers team could be a good idea. We would need to consult > with the core team to check we understood things and that what we wrote was > correct etc, but although that would be work for the core team at that > stage, it would free them later when the writers could watch the forums, and > refer people to the relevant place in documentation. I would be very happy to see a writer's team. I will be happy to explain G3 concepts in detail to anybody who wants to understand and document them. -Bharat ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ __[ g a l l e r y - d e v e l ]_________________________ [ list info/archive --> http://gallery.sf.net/lists.php ] [ gallery info/FAQ/download --> http://gallery.sf.net ] |
| < Prev | 1 - 2 | Next > |
| Free embeddable forum powered by Nabble | Forum Help |