Logo And other component changes in themes [ Was 5.0 theme ]
Here you go Kieran... Keep in mind this is a completely cheesy mockup and NOT my idea of a great UI solution. It is merely an illustration to hopefully convey a point. http://occy.net/tmp/Change_Logo-mockup-1.png http://occy.net/tmp/Change_Logo-mockup-2.png Trae PS. I changed the subject, as this seems like a fork of the original discussion. But an important one nonetheless. On 9/26/06, Kieran Lal <kieran@civicspacelabs.org> wrote:
On Sep 26, 2006, at 6:35 AM, Trae McCombs wrote:
Hmmm, I just had an interesting idea...
How about a mock-up/Wireframe?
Kieran
-- Trae McCombs || http://occy.net/ Founder - Themes.org // Linux.com
Op dinsdag 26 september 2006 17:30, schreef Trae McCombs:
Here you go Kieran...
Keep in mind this is a completely cheesy mockup and NOT my idea of a great UI solution. It is merely an illustration to hopefully convey a point.
You can achieve all this already with microcontent module Bèr -- [ Bèr Kessels | Drupal services www.webschuur.com ] Nieuwsartikelen, of weblog.: http://help.sympal.nl/nieuwsartikelen_of_weblog Written while listening to Paul McCartney by Scissor Sisters on Ta-Dah!
On 9/26/06, Bèr Kessels <ber@webschuur.com> wrote:
Op dinsdag 26 september 2006 17:30, schreef Trae McCombs:
Here you go Kieran...
Keep in mind this is a completely cheesy mockup and NOT my idea of a great UI solution. It is merely an illustration to hopefully convey a point.
You can achieve all this already with microcontent module
Perhaps I didn't quote enough of the original conversation... The point is that it is difficult to change the default Drupal logo on the default theme. We are not assuming people are computer geniuses here. The people we are worried about, or concerned with, are people who either value thier time, or are novices. Would you be suggesting that this microcontent module gets included in core? Bèr
-- [ Bèr Kessels | Drupal services www.webschuur.com ]
Nieuwsartikelen, of weblog.: http://help.sympal.nl/nieuwsartikelen_of_weblog
Written while listening to Paul McCartney by Scissor Sisters on Ta-Dah!
-- Trae McCombs || http://occy.net/ Founder - Themes.org // Linux.com
Op dinsdag 26 september 2006 20:29, schreef Trae McCombs:
The point is that it is difficult to change the default Drupal logo on the default theme. We are not assuming people are computer geniuses here. The people we are worried about, or concerned with, are people who either value thier time, or are novices.
Would you be suggesting that this microcontent module gets included in core?
no. Its just that i'd like to point out that code for all this is already out there. It requires you to make all the "stuff" blocks though. Nodes even. Title/slogan is a node, footer is a node, mission is a node, etceteras. And they appear as blocks too. if you have the permissions to change anything, you get a little "edit" link with it. nearly 40% of the code in that module is to circumvent stuff in core. So I guess incorporating the *functionality* is not that hard. But that is going to take ages of talk, I am afraid. Too many people don't like the idea of their logo being a node, or the mission being a node. And of blocks being nodes. etc. Bèr
On Sep 26, 2006, at 12:52 PM, Bèr Kessels wrote:
Too many people don't like the idea of their logo being a node, or the mission being a node. And of blocks being nodes. etc.
actually, part of what you're talking about is exactly what killes is proposing as a solution to some nasty i18n issues (you can't t() the value of the site slogan, since it just lives in the variables table, so there's currently no good way to have a language-appropriate slogan)... -dww
Derek Wright wrote:
On Sep 26, 2006, at 12:52 PM, Bèr Kessels wrote:
Too many people don't like the idea of their logo being a node, or the mission being a node. And of blocks being nodes. etc.
actually, part of what you're talking about is exactly what killes is proposing as a solution to some nasty i18n issues (you can't t() the value of the site slogan, since it just lives in the variables table, so there's currently no good way to have a language-appropriate slogan)...
More precisely, I've been talking about removing strings that contain stuff you'd want to translate from the variables table. Putting them into a node was one option. The variables table should only contain numbers and strings that get used internally. Cheers, Gerhard
On Fri, 29 Sep 2006, Gerhard Killesreiter wrote:
More precisely, I've been talking about removing strings that contain stuff you'd want to translate from the variables table. Putting them into a node was one option. The variables table should only contain numbers and strings that get used internally.
"Stuff you'd want to translate" is a broad topic. Date formats and the first day of the week are generally subject to "translation", but are very much variables. Yes, site mission or footer is a nice candidate for being a node. The first day of the week setting might not be. I am wondering what other options were considered. Gabor
Gabor Hojtsy wrote:
On Fri, 29 Sep 2006, Gerhard Killesreiter wrote:
More precisely, I've been talking about removing strings that contain stuff you'd want to translate from the variables table. Putting them into a node was one option. The variables table should only contain numbers and strings that get used internally.
"Stuff you'd want to translate" is a broad topic. Date formats and the first day of the week are generally subject to "translation", but are very much variables. Yes, site mission or footer is a nice candidate for being a node. The first day of the week setting might not be. I am wondering what other options were considered.
None, this was the result of a ten minute discussion. :p Cheers, Gerhard
Gerhard Killesreiter wrote:
Gabor Hojtsy wrote:
On Fri, 29 Sep 2006, Gerhard Killesreiter wrote:
More precisely, I've been talking about removing strings that contain stuff you'd want to translate from the variables table. Putting them into a node was one option. The variables table should only contain numbers and strings that get used internally.
"Stuff you'd want to translate" is a broad topic. Date formats and the first day of the week are generally subject to "translation", but are very much variables. Yes, site mission or footer is a nice candidate for being a node. The first day of the week setting might not be. I am wondering what other options were considered.
None, this was the result of a ten minute discussion. :p
Also: Didn't we agree a while ago that date formats should be part of the UI string translations? Cheers, Gerhard
Trae McCombs wrote:
On 9/26/06, *Bèr Kessels* <ber@webschuur.com <mailto:ber@webschuur.com>> wrote:
Op dinsdag 26 september 2006 17:30, schreef Trae McCombs: > Here you go Kieran... > > Keep in mind this is a completely cheesy mockup and NOT my idea of a great > UI solution. It is merely an illustration to hopefully convey a point.
You can achieve all this already with microcontent module
Perhaps I didn't quote enough of the original conversation...
The point is that it is difficult to change the default Drupal logo on the default theme. We are not assuming people are computer geniuses here. The people we are worried about, or concerned with, are people who either value thier time, or are novices.
Would you be suggesting that this microcontent module gets included in core?
Regardless of Bèr's intention, I wouldn't have known about microcontent module if he didn't mention it.
On 27 Sep 2006, at 01:28, sime wrote:
The point is that it is difficult to change the default Drupal logo on the default theme. We are not assuming people are computer geniuses here. The people we are worried about, or concerned with, are people who either value thier time, or are novices. Would you be suggesting that this microcontent module gets included in core?
Regardless of Bèr's intention, I wouldn't have known about microcontent module if he didn't mention it.
Agreed. The goal should be to make it easier in _core_ ... :) -- Dries Buytaert :: http://www.buytaert.net/
Op woensdag 27 september 2006 08:43, schreef Dries Buytaert:
Regardless of Bèr's intention, I wouldn't have known about microcontent module if he didn't mention it.
Agreed. The goal should be to make it easier in _core_ ...
The idea was indeed to raise some awareness. Ideally we would use some (big part) of the code in microcontent, or else some of the concepts (everythnig should have this little 'edit' link in your screen). I hoped by telling the world about microcontent again, in this thread, those people working on the core solution, can be helped :). I won't have the resoucres/time to make microcontent into a core patch myself, but I am willing to help, if people need to know details about microcontent. It might speed up stuff. Bèr -- [ Bèr Kessels | Drupal services www.webschuur.com ]
participants (7)
-
Bèr Kessels -
Derek Wright -
Dries Buytaert -
Gabor Hojtsy -
Gerhard Killesreiter -
sime -
Trae McCombs