=== ubuntianer83 [n=christia@hlle-4db16c4a.pool.einsundeins.de] has joined #ubuntu-artwork === ubuntianer83 [n=christia@hlle-4db16c4a.pool.einsundeins.de] has left #ubuntu-artwork [] === familyfriendly [n=mmcg069@125-236-128-74.broadband-telecom.global-gateway.net.nz] has joined #ubuntu-artwork === rrittenhouse [n=tad@cpe-76-188-35-66.neo.res.rr.com] has joined #ubuntu-artwork === chuckh [n=someone@ip68-109-65-130.oc.oc.cox.net] has joined #ubuntu-artwork [01:49] hi Troy, I'm going to run through your steps for bzr. Thinking of running it on Edgy. Your run down should still apply pretty closely don't you think? [02:18] troy_s: Well, looks like I'll get it. Right now it's just sitting there doing not much of anything. Maybe it's usually this slow, I guess I wouldn't know. [02:24] sorry [02:25] i only get flagged when you type my full irc name troy_s [02:25] greets by the way chuckh [02:26] Chuckles? [02:26] greetings. Well, lets see. It's sitting at phase 0/4 and has been [02:26] if you get a handle on mastering bzr checkout [02:26] ok [02:26] weird... [02:26] it shouldn't be taking quite that long. [02:27] are you trying that blubuntu sample i sent? [02:27] no, it's been 5 min [02:27] _way_ too long [02:27] ctrl c it... [02:27] lets see if i can resolve the issue... blubuntu? [02:27] at present legacyhuman though I had tried blubuntu and had the same results === klepas [n=klepas@202-161-19-16.dyn.iinet.net.au] has joined #ubuntu-artwork [02:28] weird. [02:28] is fetch showing a progress bar? [02:29] it should show 1/4 with a progress bar. [02:29] yes but it's blank [02:29] 0/4 with a blank bar [02:29] this is on Edgy, would it matter? [02:29] ok... i dont think you require to register your ssh key [02:29] no [02:29] i am on feisty... [02:29] oh crap [02:29] erm [02:29] maybe [02:29] but i doubt it. [02:29] i think i pulled from feisty on edgy etc. [02:30] oh damn [02:30] you might need to issue a bzr init [02:30] as your first go before you get tumbling... [02:30] so try [02:30] just like that [02:30] bzr init [02:30] then the pull [02:30] yeah give it a shot [02:30] waiting [02:30] tell me if it still stalls at 1/4 [02:31] you just recently apt-got bzr right? [02:31] even just getting to that stage takes forever [02:31] so you are toying with the newest repo version i take it. [02:31] it can. [02:31] i don't know what is going on behind the scenes, but it does sometimes take a while. [02:31] got an error. ubuntu directory exists. I'll remove it and try again. [02:31] ah [02:31] yeah just rm-rf it [02:32] in fact, if you are going to bother, you might as well checkout the legacy human then you can apply your patch [02:33] that is what I was thinking of doing. I'm still at 0/4 with a blank progress bar. [02:34] well wtf? [02:34] shouldn't take that long. [02:34] give it a minute then we sort it out. [02:34] usually the network lights blink during that [02:34] are yours? [02:35] well, I can tell the traffic is zip. If they are it's from something else. [02:39] let me test the legacy-human link [02:39] where is the bzr location you are using for it? [02:39] http://bazaar.launchpad.net/~ubuntu-art-pkg/legacyhuman-theme/ubuntu [02:40] I grabbed it off launchpad [02:41] okie trying it... [02:41] nope... leeches right away for me. [02:41] something strange going in at your end. [02:41] in another term, see if anything is in your ~/ubuntu directory [02:42] got an error finally. [02:42] bzr: ERROR: exceptions.AssertionError: [02:42] wow [02:43] that is a problem... i wonder if there are some strange depends -- you just did apt-get install bzr and that was all eh? [02:43] came from python. Let me try another machine. I may have a strange build environment here. [02:43] try removing it then re apt-get it. [02:43] yes... [02:43] very well a python issue! [02:43] i'll be around chuck, going to play a card game with my daughter for a few moments. [02:43] see if you can fix your python issue. [02:43] then i'll show you how to push [02:46] worked on another machine that's more of a default setup [02:46] almost missed it because it was so fast. [02:46] ;) === z_diver [n=chuckh@ip68-109-65-130.oc.oc.cox.net] has joined #ubuntu-artwork [02:56] so chuckh, whilst i am playing, have a peek over the [02:56] structure [02:57] you can also pull like this "bzr checkout " [02:57] ok [02:57] that'll be needed [02:58] troy_s, It's chuck again on the machine with the working bzr install. I've verified the gtkrc works on Fiesty. [02:58] But Legacy Human isn't there anymore. [02:58] ??? [02:59] legacy human isn't in that checkout? [02:59] yeah, but I don't think it's installed by default at least === familyfriendly [n=mmcg069@125-236-128-74.broadband-telecom.global-gateway.net.nz] has left #ubuntu-artwork [] [03:00] it is probalby in extra themes [03:00] needless to say, you can apply your fix [03:00] the checkout worked fine though. [03:00] so what's the best way to go about it. [03:01] it is very simple [03:01] just change the file in question [03:01] bzr add basically will put a full list of files [03:04] troy_s, bzr add ? [03:19] ok [03:19] so back [03:19] lets assume we have dir foobar [03:19] bzr init [03:19] do a bzr whoami to see who you are registered as [03:19] okie? [03:20] is the information correct?, if not, follow the instructions 'bzr whoami 'Joe Blow ' [03:20] okie z_diver ? [03:20] assuming we have say [03:20] ~/foobar [03:20] as your project directory [03:20] with subfiles a, b and c [03:20] bzr will ONLY track [03:20] files added via bzr add [03:21] which means that for an existing branch, you need do nothing UNLESS you are adding a fresh file [03:21] in your case, you will probably just update files for the first bit [03:21] which means that bzr already knows what belongs in that package [03:22] i'm here now [03:24] troy_s, whoami comes out correct, I ran bzr add [03:25] ok [03:25] erm [03:25] you don't need to add it [03:25] because technically it is already part of the download [03:26] follow me? [03:26] k [03:26] you pulled it, so you know that bzr already knows abou tit [03:26] so first thing [03:26] do you have an ssh public key registered at launchpad? [03:26] probably not [03:26] that is the only thing you will require to publish to launchpad's bazaar [03:26] ok... go to your launchpad page [03:27] to generate a key, we'll use ssh keygen [03:27] erm [03:27] ssh-keygen [03:27] MY launchpad page? [03:27] yes [03:28] what is your launchpad logon? [03:28] let me look [03:28] chuck@lagunadata.com [03:28] what is your launchpad id? [03:28] as in launchpad.net/~? [03:28] mine for example, is launchpad.net/~troy-sobotka [03:29] ah got you [03:29] https://launchpad.net/~chuck-lagunadata [03:29] okie? [03:29] so your id right now is set to [03:29] chuck-lagunadata [03:29] okie? [03:29] go there, on the left pane you will see your ssh and gpg keys [03:29] for now, select ssh [03:30] and we will input a key [03:30] the public half [03:31] got it? [03:31] yes [03:31] z_diver: you there yet? [03:31] yep === familyfriendly [n=mmcg069@125-236-128-74.broadband-telecom.global-gateway.net.nz] has joined #ubuntu-artwork [03:31] I've made keys, getting the public [03:31] wow... [03:31] ok [03:31] so just put your public ssh key (id_rsa.pub or whatever from .ssh) [03:33] when you have your published ssh key, let me know [03:34] now when you make a change, you need to issue a commit. this won't do bugger all until you push the changes. [03:34] bzr commit -m "Your full explanation of the commit." [03:34] If you omit the -m, bzr will automatically launch an editor and let you put in a larger comment. [03:34] with? === familyfriendly [n=mmcg069@125-236-128-74.broadband-telecom.global-gateway.net.nz] has left #ubuntu-artwork [] [03:37] troy_s, alright the keys are up there. Do I need to undo the bzr add that I did or will that not cause any harm [03:37] depends [03:37] your bzr add is relative to the directory [03:37] so if you simply re-added the same file [03:37] it shouldn't be an issue [03:37] correct [03:37] there is a bzr list command somewhere [03:37] to see the file listing [03:37] tha'ts what I did [03:37] ok should be ok [03:37] try the push now [03:37] brz pulls up a few [03:37] k [03:37] after a bzr init (already done) [03:38] you do your commit [03:38] with comment [03:38] bzr commit -m 'Blah' [03:38] bzr push sftp://@bazaar.launchpad.net/~// [03:38] and that's it. [03:38] from within the directory [03:38] pretty simple [03:38] yes [03:38] bzr commit from the directory [03:38] then push [03:38] from the root of the directory [03:39] in this case the will match the same one you pulled from [03:39] basically the same address [03:39] if you made some radical changes, you could append -chuck to the branchname for later merging [03:40] and thanks to daniel's automated procedure that him and frank banged out [03:40] every half hour the packages will get built and shipped. [03:41] wow how cool! [03:41] tell me if you are met with success? [03:41] bzr commit gave me an error [03:41] what was the error? [03:41] probably about that double add? [03:41] cannot lock [03:41] try the bzr init [03:41] bzr init [03:41] yes [03:41] woops [03:42] ;) [03:42] wrong window [03:42] it werk? [03:42] new error Error alread a branch [03:43] hmm [03:43] hmm... maybe we can't push direct [03:43] try putting -chuck on it [03:43] and then we can notify daniel [03:43] ok [03:43] it is possible that the mains are locked. [03:43] but i am not certain [03:43] (it might be that daniel needs to permit ax to the mains) [03:44] ok, so do i add gtkrc-chuck or something? [03:44] there might be a merge tool [03:44] no [03:44] just establish your own branch with the changes. [03:44] but let me look into it, [03:44] manning bzr [03:46] for now, let's push to .chuck or -z_diver or something [03:46] and we will get a resolution tomorrow from daniel on how to push direct [03:46] once you push, let me know and I'll see if i can see the revisiosn [03:47] so how should I do that [03:48] offer your commit via pushing [03:48] but push to [03:49] http://bazaar.launchpad.net/~ubuntu-art-pkg/legacyhuman-theme/z_diver [03:49] perhaps [03:49] try that [03:49] troy_s, would it be bzr push [03:49] no it is the fully qualified package name [03:49] erm crap [03:50] obviously with your id on the head instead of the brainded http paste i did [03:50] bzr push sftp://@bazaar.launchpad.net/~// [03:50] that's the full syntax [03:50] so as a guess [03:50] you tried [03:51] bzr push sftp://chuck-lagunadata@bazaar.launchpad.net/~ubuntu-art-pkg/legacyhuman-theme/ubuntu correct? [03:51] lets see [03:51] is that what you tried when you got the 'oops already branch' error? [03:52] ??? [03:52] no. This looks to be working [03:52] in the syntax i just gave? [03:52] darn. mailto:sftp://chuck-lagunadata@bazaar.launchpad.net/~ubuntu-art-pkg/legacyhuman-theme/ubuntu [03:53] mailto? [03:53] wait that's wrong [03:53] wtf? [03:53] no that's how xchat copied your link [03:53] I didn't use it that way. [03:53] hang on [03:53] bzr: ERROR: Parent directory of sftp://chuck-lagunadata@bazaar.launchpad.net/~ubuntu-art-pkg/legacyhuman-theme/ubuntu does not exist. [03:53] bzr push sftp://chuck-lagunadata@bazaar.launchpad.net/~ubuntu-art-pkg/legacyhuman-theme/ubuntu [03:53] erm [03:53] that's the correct errror [03:54] how strange is that. [03:54] it shouldn't realistically be giving that error... [03:54] try the /z_diver instead of ubuntu [03:54] k [03:54] we need to figure out the official pushes issue. [03:55] interesting [03:55] permission denied. I think the lagunadata was correct then, no? [03:57] bzr push sftp://chuck-lagunadata@bazaar.launchpad.net/~ubuntu-art-pkg/legacyhuman-theme/z_diver [03:57] your id wouldn't change [03:57] trying that [03:57] z_diver directory doesn't exist, hmmm [03:58] and the original ubuntu one didn't work? [03:58] from within the local ~/ubuntu [03:58] i'll try again [03:58] dir on your computer? [03:58] yes... i'll try one. [03:58] at this end... [03:58] i know we are damn close as per the instructions [03:58] andreasn -- [03:58] ping [03:58] andreasn -- when you guys push to Tangerine, what is the format syntax for the bzr push command? [03:59] bzr: ERROR: Parent directory of sftp://chuck-lagunadata@bazaar.launchpad.net/~ubuntu-art-pkg/legacyhuman-theme/ubuntu does not exist. [03:59] that is from within ubuntu with the correct id offering the following command. [03:59] chuckh@ubuntu:~/ubuntu$ bzr push sftp://chuck-lagunadata@bazaar.launchpad.net/~ubuntu-art-pkg/legacyhuman-theme/ubuntu [04:00] ok... lets try adding a branch off of it... [04:00] for your revision [04:00] i believe it is bzr help branch [04:00] alright. lookin now [04:02] damn close... in his example he basically created a branch [04:03] but i don't know if we create a branch from the legacyhuman-theme or the full legacyhuman-theme/ubuntu-mybranch [04:03] you have an example handy [04:03] I was going to try the second approach [04:04] i will try one. [04:04] hold on... [04:05] fetching legacy [04:07] so I have downloaded a branch that I called ubuntu-chuckh [04:08] via branch? [04:08] yes [04:08] now I've added my gtkrc to that branch. === Madpilot [n=brian@ubuntu/member/madpilot] has joined #ubuntu-artwork [04:08] verified it's correct [04:09] now can I push that up or is that way too much... [04:09] since I only changed the single file? [04:09] it might be the only way since the offical branch appears locked to me. [04:10] k, I'll try [04:11] it might be working [04:11] woop [04:11] i think it worked [04:11] the push is still to the same directory [04:11] same error that the ubuntu-chuckh branch doesn't exist. [04:12] oh [04:12] bzr push sftp://chuck-lagunadata@bazaar.launchpad.net/~ubuntu-art-pkg/legacyhuman-theme/ubuntu-chuckh [04:12] so that should have been to ubuntu at the end? [04:12] that is what i did [04:12] i did this: [04:13] bzr branch ./troy_s [04:13] then cd into troy_s [04:13] adjusted the NEWS file [04:13] bzr commit -m 'Changed NEWS as a test." [04:13] i can tell I did something wrong. I didn't commit in there. [04:13] then bzr push sftp://troy-sobotka@bazaar.launchpad.net/~ubuntu-art-pkg/legacyhuman-theme/ubuntu [04:14] and it appears to do something [04:14] did it succeed or die? [04:14] because i succeeded but it isn't showing anywhere that i can see. [04:14] mine errored out with the parent directory doesn't exist error [04:14] but let me commit [04:15] try doing the commit using the same syntax i did. [04:18] fer feck sake [04:19] what do you mean. Single quote in front and double behind??? [04:20] anyway, commit seemed to work. Just can't get it to push. still telling me that ERROR: Parent directory of sftp://chuck-lagunadata@bazaar.launchpad.net/~ubuntu-art-pkg/legacyhuman-theme/ubuntu-chuckh does not exist. [04:20] I borked that [04:20] yes the commit is local [04:20] yes i get that too. [04:21] so clearly we have an issue with something we are borking. [04:22] I've tried with simply ubuntu at the end instead of my branch thinking that that might help. To no avail. [04:22] Yes. [04:23] We are close. I have posted a message to Daniel, which will be resolved tomorrow. [04:23] Hopefully we will be able to start the patch fest shortly. [04:23] ;) [04:23] And kill off a large number of the nonsensical 'bugs' [04:23] As they are easy to fix, we just need the write permission or proper syntax. [04:23] It will brighten the mood, i think [04:23] I know for my own branches, this isn't an issue. [04:24] Well... the mood is irrelevant. The main thing is to keep attempting to illustrate that we are on the same side sab is on. [04:24] It will take time, as I originally was very clear in stating. [04:24] I was looking through the bugs though, and noted that a large number, like your gtkrc example, actually had fixes -- just no legwork to push them through. [04:24] by the mood I meant that the art team. It would be nice to have more participation again [04:24] for example, orro had the open folder svg on his site... so i pushed that up to the thread. [04:25] yes. [04:25] as i said, sabdfl simply won't consider design issues until the team is firing on full cylinders. [04:25] of course, everyone seems to forget that prior to edgy we had a grand total of 17 members on launchpad. [04:25] ;) [04:25] how many are there now? [04:26] how many are there now? [04:26] uh [04:26] 202 [04:26] launchpad.net/~ubuntu-art [04:26] that was a good drive then.... [04:26] not to mention all of the stuff that daniel set up with frank over edgy etc. [04:27] (like automated artwork for all of the packages, etc.) [04:27] it was a very frustrating conclusion. [04:27] true. That was a ton of work [04:27] because i tried to make it clear at the beginning [04:27] to sab et al [04:27] that the goal for edgy will _not_ be the destination attained [04:27] it is the foundation work that is the hard part [04:27] and establishing communication with the devs etc [04:28] hell, prior to edgy, we were not even on the bug listing. [04:28] how did you feel we did on that end? [04:28] i was fine [04:28] it is a matter of one part aesthetics, one part design, one part audience [04:28] I know we may have gotten off track a time or two but as far as getting a foundation setup, I though we did great. [04:28] the reality is that we currently have no target audience per - se. the target audience is one person, which is an unfortunate reality. [04:28] yeah it was fine [04:29] the main flaw was sab not stepping in and steering at the various checkpoints, but i don't know if it was clear in the end after he posted his thoughts. frank's article on linux.com was pretty spot on. [04:29] when he was interviewed. [04:29] again though, you can't expect total magic in 4 months [04:30] considering the time, the place we began, etc, it was all quite above the expectation level -- but unfortunately everyone looked at the final. which was silly. [04:30] When he jumps in from time to time we get an idea of his thinking and I know I was usually somewhat surprised at sabs insight. [04:30] well yes... [04:30] at one point i couldn't believe it [04:30] but i was actually arguing about colour theory with him on the phone [04:30] knowing full well that [04:30] i was arguing with someone with zero art / design background [04:30] which was ... strange. [04:30] alas, again, it will take time. [04:31] and perhaps he will need to see the light himself before things will see change. [04:31] we have a good number of very talented people in the crowd [04:31] as is clear from some of the output of the very few who bothered. [04:31] I'm glad to see you're still at it. You produced a lot of neat stuff that didn't get used at all. [04:31] i think the fundamental problem is that we are _not_ following a traditional design approach -- no audience. [04:32] hence you get 'buttons are too thin' 'colors are ugly' etc. [04:32] nothing to check the designs against [04:32] blah [04:32] it matters not [04:32] my only [04:32] and i mean _only_ regret [04:32] is that i actually bothered to try and guess into the sabdfl aesthetic [04:32] had it been my knowledge from the onset, i probably would have just rambled down the road i thought was more appropriate [04:32] right, that's tough to even attempt [04:33] well... especially to a vacant owner. ;) [04:33] no, i remember that and felt it might even be recognized by sab. [04:33] again too, despite the outcome, there were about 300 emails in my box wondering why [04:33] i think we were at about 75% approval despite the unfortunate outcome [04:33] which, considering the circumstance, is completely acceptable. [04:34] especially for a first pass in 3 months effectively. [04:34] had the outcome been more appropriate I think we as a group wouldl be flying still. [04:34] i firmly believe and have faith in ubuntu, so i force myself to keep at it. not suffer from the immature 'sour grapes' approach and pull the bail. [04:34] well... i was letting it stew a bit. [04:34] working on u2 and such. [04:35] now i figure the time is right to really go back to the wheel and get the die hards to learn bzr [04:35] and start building a community that liases with the devs -- even if on a very medial scale. [04:35] oh, yeah, thanks for takign the time with me. [04:35] the core devs are the most important group to touch. [04:35] well bzr is amazingly powerful. [04:35] and relatively easy [04:35] but we need to spread our knoweldge [04:35] get a wiki page up [04:35] and promote the bug quashing once we figure it out [04:36] a wiki would be a good idea. [04:36] the docs could be setup on the launchpad howto with a bzr howto [04:36] specifically geared towards the art team [04:36] how to checkout [04:36] how to update [04:36] how to push [04:36] right, copy and paste just like you did with me. [04:36] it will make daniel's immense workload a little lighter if we can at least push it to the merge point [04:36] yep [04:37] it is really only two commands to pull the sources [04:37] do the work then push it. [04:37] not very hard. [04:37] and seeing as how our first 'success' will be with your gtkrc [04:37] ;) [04:37] it should be good to build out from that. [04:37] its why i contacted you because you actually have work that can fix a bug [04:37] and that is a good start. [04:37] once we get our sea legs, you and i can bang out a wiki page for the art team [04:37] and post to the list [04:38] sure, I'm game for hatt [04:38] 202 folks, at even 10% is still 20 folks banging out bug fixes. [04:38] and _that_ will begin phase two of getting the devs interaction up [04:38] with relatively little pain [04:39] in fact, i dare say that the bulk of those bugs already have fixes either A) in the bug threads, or B) in third party sites like orro's svg [04:39] daniel, for one reason or another, has bumped me onto the desktop bug team, so i can at least order the list a bit. [04:39] Daniel is amazing. He has to be ontop of so much stuff and still do all our bugz too. I think this is a good idea and can help him which in turn turn will get the dev to take note. [04:40] Yes. [04:40] He really has been holding us in the game [04:40] I have a few fixes that I'll have to dig up, and post. Some of them are to my own projects but still like to add them. [04:41] So I think we at least owe it to him to try and take up some of the workload. [04:41] God knows we are all very busy, but ... [04:41] I do what I can considering my slim time. [04:41] Indeed... [04:41] You by the way, would probably have full writes to your theme [04:41] IIRC [04:41] if we think like that the danger is Daniel will and then it's over. [04:41] I might be mistaken, but you can try [04:42] no comment above was about the slim time. [04:43] Exactly. [04:43] Anyways, great to still see you around... [04:43] let's see if we can get the boat back on course. [04:43] baby steps... [04:44] you too. Hang in there... I'll be around and look for you here from time to time [04:44] Let me know what you hear from the devs, please. [04:45] cu === Ubug2 [n=bugbot@ubuntu/bot/ubugtu] has joined #ubuntu-artwork === UbuntuSt1ts [n=StatsBot@bl4-221-125.dsl.telepac.pt] has joined #ubuntu-artwork === PWill [n=paul@cpe-24-208-190-43.columbus.res.rr.com] has joined #ubuntu-artwork === BHSPitMonkey [n=stephen@adsl-65-69-152-153.dsl.rcsntx.swbell.net] has joined #ubuntu-artwork === klepas_ [n=klepas@202-161-2-46.dyn.iinet.net.au] has joined #ubuntu-artwork === familyfriendly [n=mmcg069@125-236-128-74.broadband-telecom.global-gateway.net.nz] has joined #ubuntu-artwork === familyfriendly [n=mmcg069@125-236-128-74.broadband-telecom.global-gateway.net.nz] has left #ubuntu-artwork [] === klepas [n=klepas@202-161-19-16.dyn.iinet.net.au] has joined #ubuntu-artwork === kwwii [n=kwwii@p54954C8A.dip.t-dialin.net] has joined #ubuntu-artwork === klepas_ [n=klepas@202-161-2-46.dyn.iinet.net.au] has joined #ubuntu-artwork === msikma [n=Msikma@s55933ad4.adsl.wanadoo.nl] has joined #ubuntu-artwork === PWill [n=paul@cpe-24-208-190-43.columbus.res.rr.com] has joined #ubuntu-artwork === chuckh [n=someone@ip68-109-65-130.oc.oc.cox.net] has joined #ubuntu-artwork === klepas [n=klepas@202-161-19-16.dyn.iinet.net.au] has joined #ubuntu-artwork === klepas_ [n=klepas@202-161-2-46.dyn.iinet.net.au] has joined #ubuntu-artwork === lapo [n=lapo@host102-254-static.189-82-b.business.telecomitalia.it] has joined #ubuntu-artwork [10:48] hi === klepas_ is now known as klepas === familyfriendly [n=mmcg069@125-236-128-74.broadband-telecom.global-gateway.net.nz] has joined #ubuntu-artwork === lizardking [n=lizardki@87.6.132.215] has joined #ubuntu-artwork [12:02] Hello artworker! === familyfriendly [n=mmcg069@125-236-128-74.broadband-telecom.global-gateway.net.nz] has left #ubuntu-artwork [] [12:12] Someone Have any news from sabdfl 's artwork development? === KaiL [n=KaiL@p548F6B11.dip.t-dialin.net] has joined #ubuntu-artwork === bersace [n=bersace@did75-13-82-243-217-90.fbx.proxad.net] has joined #ubuntu-artwork === klepas_ [n=klepas@202-161-2-46.dyn.iinet.net.au] has joined #ubuntu-artwork === klepas_ is now known as klepas === effraie [n=effraie@jem75-1-82-228-146-152.fbx.proxad.net] has joined #ubuntu-artwork === kwwii_ [n=kwwii@p54956A8B.dip.t-dialin.net] has joined #ubuntu-artwork === TuxCrafter [n=jelle@84-245-7-46.dsl.cambrium.nl] has joined #ubuntu-artwork [03:56] greetings TuxCrafter [03:59] dborg [03:59] Any guess on pixmap support in Lua? [03:59] guess? [03:59] Yes. [03:59] when it's done? [03:59] As in extending the drawing functions of Cairo(?) ? [03:59] yes [03:59] Or at least workable ;) [04:00] I would prefer a 'clean' engine implementation as opposed to me having to kludge with the Pixbuf engine and the TETEAE Lua [04:00] I can't imagine it would be fun getting Pixbuf cooperating nicely. [04:00] I'm not planning to do this yet, it's just a planned possible extension. but it shouldn't be too difficult to add it [04:01] Erk! [04:01] Here is a question [04:01] If I state Lua as the basic widget engine [04:01] and apply it as a blanket [04:02] Do you have an idea how many widgets will trap the bg_image property? [04:02] Compared to say, Mist or the Default? [04:03] I think pretty much all standard widgets (aside from entries, which draw a white background...). it will mostly be custom widgets causing problems [04:03] You would think [04:03] there is no difference, it has nothing to do with the engine [04:03] but the Default actually traps LESS than Mist. [04:03] I thought that... [04:03] huh? [04:03] But I believe that the engine can influence it... [04:03] I must run for now [04:03] I don't see how [04:03] but as an experiment [04:03] try applying [04:04] bg_image [04:04] without specifying a default engine {} clause [04:04] compare the widget output [04:04] in firefox [04:04] or some app [04:04] then apply engine "mist" {} [04:04] you will see what i mean [04:05] I believe it has to do with the switch case structure [04:05] but I might be mistaken [04:05] oh that bg_image you mean. I never used that [04:06] yes i know [04:06] but it is apparently up to the engine to trap it appropriately [04:06] which means in an ideal world [04:06] lua would ;) [04:07] would you mind if i do a test and send you feedback on its implementation? [04:07] dborg [04:08] so with engine "lua" {} [04:08] it looks like it falls back to "Default" [04:08] but, with "mist" the top of firefox is bg_imaged [04:08] yes, mostly [04:08] with Default it isn't [04:08] (as with lua now) [04:08] yikes, don't tell me about firefox ;) [04:08] in an ideal world, we figure out how mist traps it [04:09] mist traps it properly [04:09] in their switch case [04:09] as in, it DOES properly apply the bg_image [04:09] so i suspect that lua might need to add in the same clause [04:09] in order to get proper functionality [04:09] wouldn't it be better to draw the background just once and then make the widgets transparent as possible? [04:09] i have looked at mist's code, but not defaults [04:09] Or that :) [04:09] Whatever works [04:10] The bottom line is that obviously firefox uses some different *widget* that mist captures properly [04:10] and the default doesn't [04:10] (as odd as that seems) [04:10] that's how I have done it before and it will be possible with the lua engine as well. it just fails with widgets who aren't properly transparent (many custom widgets) [04:10] yes [04:11] so is it possible to override that behaviour to force bg_image to behave appropriately in all circum? [04:11] I don't know [04:12] i would buy you a beer if you could make it behave like that [04:12] or at the very least, like mist handles it... (considering the prevalence of FF etc, it is rather mandatory for me) [04:12] what kind of background would you use it for? [04:13] it is somewhere along the lines of the brushed gunmetal of osx, but not cheesy metals. [04:13] its for a far more organic project... [04:13] it appears to be the menu bar [04:13] and the toolbar [04:14] as Thunderbird suffers from the same breaking of bg_image [04:14] but isn't it better to do this kind of thing with one background gradient instead of scaled images? [04:14] (not to mention List Views too... the headers are not applied) [04:14] no, grads can't add the irregularity [04:14] well they can if you use cairo ;) [04:14] ? [04:14] how so? [04:15] and if so, enlighten me. [04:15] i basically need a fundamental texture applied to all widgetry [04:15] consistently [04:15] I mean you can draw the image pattern and then overlay a transparent gradient. I'm quite sure that's how OSX does it. could be very slow though [04:15] right now the implementation is very fast [04:15] using just the bg_image [04:15] the problems are as discussed however [04:16] if mist were perfect, I would use it, but again, it breaks the rules and performs solid fills on things like scrollbar troughs [04:16] etc. [04:16] the default does this properly, but does NOT manage to trap the menubar, toolbar, etc of ff [04:16] (where mist does) [04:16] and frankly, i don't care about speed. [04:16] if it works on a relatively modern computer, it works for me. [04:17] sure [04:18] the main thing is just getting a bloody engine to do the 'right' thing [04:18] and that means having the gtkrc apply the bg_image to _EVERY_ widget, no matter what app [04:18] as in mixing the functionality of default engine with mist [04:18] and we are there. [04:18] which is a simple switch/case statement with the proper constants to the best of my knowledge. [04:19] Hello everyone (need a brake for 15 min) [04:19] well I'm still not convinced that bg_image is all that useful compared to a simple background draw, but it shouldn't be too difficult to slap it behind each drawing function [04:20] I see the problem in xubuntu and probably also ubuntu that users like to see things change like graphical stuff but developers do not support it [04:20] dborg -- i agree... but i think to be a proper engine that that [04:21] TuxCrafter: nature of the beast. users aren't devs however. [04:21] I want to have a voting system for all the dynamical graphical stuff [04:21] yikes [04:21] voting systems are evil :) [04:21] dborg that the base engine should handle the gtkrc defines properly [04:21] you can't design by committee [04:21] no [04:21] you need a solid team [04:22] dborg -- anyways, if you could pull that off, or at least provide a way to draw to _all_ widgets [04:22] i would appreciate the knowledge. [04:22] but they can help make things transparent and let users feel apart of the distribution [04:22] (as in a catch all like bg_image) [04:22] TuxCrafter: matters not [04:22] 'users' is a big term [04:22] with no clearly defined audience, design fails. [04:22] period. [04:22] troy_s: well I'd say it's still up to the engine which options it supports ;) it could have its own background image handling just as well [04:22] you learn that in art and design skool .000001 [04:23] dborg -- sure. i guess then i have to turn it into a request :( [04:23] images are critical ... especially with the newer wave coming down. [04:23] "newer wave"? [04:23] you simply cannot provide the same appearance using simple splines (you could do it somewhat with svg) [04:24] the looks right now are locked into simple line functionality [04:24] I was thinking of a system were people can post a design on a website and with a howto /script how it can be implemented and tested [04:24] and grads [04:24] TuxCrafter: go for it. [04:24] in the ubuntu wiki system [04:24] I was hoping if someone already had made this somewere [04:24] dborg: at any rate, how much effort to implement it in lua? [04:24] TuxCrafter: it is called launchpad [04:25] launchpad is more for bus and request right? [04:25] troy_s: well I'm sure I'll support pixmap textures at some point, what I am not sure about it is the usefulness of bg_image as opposed to rendering a texture once on the window background [04:25] TuxCrafter: it works. but polls will fail. there are two components -- the client (the fellow who calls the ultimate shots) and the audience [04:25] neither cares about polls. [04:26] dborg: i don't mind how it is implemented... (although i would prefer that bg_image did the trick regardless as to how to achieve it) [04:26] dborg and i would very much prefer to use lua [04:26] to show what it can do. [04:26] but how do you measure then if people like it or niot [04:26] TuxCrafter: called focus groups [04:26] TuxCrafter: and they don't work exactly well either [04:27] TuxCrafter: design is a very tricky realm -- it takes people who are educated in the design world (know what trends are moving across _all_ design, etc) with the proper team for execution. [04:27] I am going to do a coarse in people management [04:27] and read some more stuff about opensource management [04:28] sometimes the system is so ineffective that you can just not begin to grasp it :-D [04:28] and i believe ubuntu has the best community system [04:29] a little too good maybe :) [04:29] how does the artwork go in the ubuntu process [04:30] who decide how things looks === dborg_ [n=daniel@e181164223.adsl.alicedsl.de] has joined #ubuntu-artwork [04:32] TuxCrafter: the answer is simple [04:32] TuxCrafter: one person is both the audience and client [04:32] TuxCrafter: sabdfl === dborg___ [n=daniel@e181164223.adsl.alicedsl.de] has joined #ubuntu-artwork [04:32] TuxCrafter: there is no process, just whim [04:32] whim? [04:32] holy crap [04:32] dborg___ what?> [04:32] Mark Shuttleworth [04:33] dborg -- i would buy you a case of your fave liq if you could get textures working [04:33] ;) [04:33] lua very clearly is the future -- teteae -- but we need to show people how this is ture. [04:33] true even [04:33] so no freedom for ubuntu and chaos for xubuntu :-D [04:33] I'll finish it first :P [04:33] TuxCrafter: no... the nature of design in free software still has a lot of 'maturing' to happen [04:34] dborg: you _rock_ === dborg___ is now known as dborg [04:36] TuxCrafter: and, ultimately, the design issues with all of the given distributions have no one to blame but themselves [04:36] heavy on the politicking, and not enough on traditional design theory [04:36] indeed if we look at theory of graphical issues and treds xubuntu needs a lot of work [04:37] well you have one upside -- mr. mak. [04:37] but it ultimately depends on his vision _and_ his ability to implement his change. [04:37] but the not all dev's have that insight [04:37] again, what seems to happen is that the changes are 'half assed' [04:37] because of the political structure [04:38] so what do you advice if we want to add some extra options of graphical work in xubuntu [04:38] if the top of the heap has the ability to call the final shot and give the power to someone they trust, the output _could_ be very good. [04:38] jani is a damn good guy [04:38] he is [04:38] and xub has some pretty good people working on the art/design front [04:38] jub jmak etcetra [04:38] but i think again, it would take someone to really lay down a target audience [04:39] before you can attempt to speak to them [04:39] without a target audience [04:39] you are effectively 'pretending' to appeal to all [04:39] which is pure garbage [04:39] no such creature [04:39] it is like standing up at the united nations and saying 'i love you all' [04:39] indeed thats why I want to let te user be able to choice [04:39] whilst being ignorant that the language being spoken is english for example. [04:39] well users can't choose either [04:40] you must _Clearly_ define your audience [04:40] with a easy way of editing configurations [04:40] otherwise you get what we currently have in ubuntu -- 10000001 different 'opinions' in bug reports [04:40] which is also rubbish [04:40] yes that sucks [04:40] you need to say 'design feature a does not meet the requirements of target audience foobar' [04:41] and on another side of the spectrum you have the 'middle grey' approach [04:41] which is to just barely be adequate [04:41] and keep the complaints down [04:41] which again, is NOT effective design either. [04:42] art and design is, ultimately, a form of communication [04:42] stand out art and design [04:42] communicates a clear message [04:42] _and_ does so in an aesthetically cohesive manner. [04:43] if you don't believe that, feel free to pick up just about any reference book on art / design. [04:43] I think I will specialize myself in these policies to become able to create a effective communication system between different type of users [04:43] to quote but _one_ source: [04:43] "Concept is king" [04:44] "Audience is the force that governs all" [04:44] although just about every reference will have that stated in some manner. [04:44] you forgot over [04:47] I believe it is the power to become able to attract different kind of user to one distributions bye creating easy method of changing complete different type of graphical looks [04:48] but my all my resent experiences learn me this will not become a easy task === klepas [n=klepas@60-242-104-119.tpgi.com.au] has joined #ubuntu-artwork [05:00] TuxCrafter: in theory any distribution affords this. the reality is that _most_ users probably don't want to put in the hours to develop a look. [05:04] troy_s: Yes i agree but when a user is putting time and what to help. He should not be so easily dismissed and say that is idea's are useless. I have seen that happen several times. There should be a clear and democratic system that a user can easily go through with his idea's [05:04] _anyone_ can bikeshed [05:04] democracy does not assure solid design [05:04] nor does dictatorships [05:05] true [05:05] ultimately, there are no easy answers. [05:05] thats also why devs and users are separated [05:06] the best design generally is the byproduct of A) a solid team atmosphere, B) educated participants, C) solid design plan. [05:06] need look no further than the lauded Apple design team [05:07] indeed not a easy subject [05:08] troy_s I have to go further with my work now, and thanks for your insides have something to think about :-D [05:23] I wonder if a sketch of overall design, with all the changes shown, would be more encouraging that just mockups of single features... === coz_ [n=coz_@pool-151-201-27-176.pitt.east.verizon.net] has joined #ubuntu-artwork [05:52] to mods at art.ubuntu.com i am still seeing my name there PLEASE remove all references from the servers i go under coz and cosimo thank you === coz_ [n=coz_@pool-151-201-27-176.pitt.east.verizon.net] has left #ubuntu-artwork ["Leaving"] === TuxCrafter [n=jelle@84-245-7-46.dsl.cambrium.nl] has left #ubuntu-artwork [] [06:07] i wish he woudl quite popping in here as though we are mods. [06:07] TheSheep -- yes. [06:07] TheSheep -- if you mean to an 'outside' person [06:08] hopefully when you are on the 'inside' you have the ability to visualize the issue. [06:08] otherwise you probably shouldn't be on the team. === bersace [n=bersace@did75-13-82-243-217-90.fbx.proxad.net] has joined #ubuntu-artwork [06:38] bersace: greets my brother. [06:47] troy_s: hi bro [06:47] how are you ! [06:47] ? [06:47] good thanks. you? [06:48] quite good [06:48] i saw you did a lot of work in lp [06:49] yeah trying to amp it up a bit. === rrittenhouse [n=tad@cpe-76-188-35-66.neo.res.rr.com] has joined #ubuntu-artwork === TuxCrafter [n=jelle@84-245-7-46.dsl.cambrium.nl] has joined #ubuntu-artwork === TuxCrafter [n=jelle@84-245-7-46.dsl.cambrium.nl] has left #ubuntu-artwork [] === msikma [n=Msikma@s55933ad4.adsl.wanadoo.nl] has joined #ubuntu-artwork === TuxCrafter [n=jelle@84-245-7-46.dsl.cambrium.nl] has joined #ubuntu-artwork [08:49] does somebody now how to install the murrine engine [08:49] never mind [08:49] found the tread === Seveas [n=seveas@ubuntu/member/seveas] has joined #ubuntu-artwork === PingunZ [n=PingunZ@52.6-136-217.adsl-dyn.isp.belgacom.be] has joined #ubuntu-artwork [09:00] !seen fschoep === bersace [n=bersace@did75-13-82-243-217-90.fbx.proxad.net] has joined #ubuntu-artwork === effraie [n=effraie@jem75-1-82-228-146-152.fbx.proxad.net] has joined #ubuntu-artwork === andreasn [n=andreas@h101n1fls31o839.telia.com] has joined #ubuntu-artwork [10:02] pingunz [10:02] no seen [10:02] hey troy_s [10:02] greets. [10:04] how are you m8 ? [10:06] fine thank you pingunz. [10:12] Hey everyone [10:12] greets msikma === familyfriendly [n=mmcg069@125-236-128-74.broadband-telecom.global-gateway.net.nz] has joined #ubuntu-artwork === familyfriendly [n=mmcg069@125-236-128-74.broadband-telecom.global-gateway.net.nz] has left #ubuntu-artwork [] === TuxCrafter [n=jelle@84-245-7-46.dsl.cambrium.nl] has joined #ubuntu-artwork [11:45] hello I have a noob question [11:46] I have installed murrina and the MurrinaGiloucheDuo Theme [11:46] and I want to customisch it [11:46] where do I start :-D [11:46] with config files must I edit? [11:47] gtkrc === TuxCrafter [n=jelle@84-245-7-46.dsl.cambrium.nl] has left #ubuntu-artwork []