Jump to content

Duma

Members
  • Content count

    2376
  • Joined

  • Last visited

  • Days Won

    53

Duma last won the day on February 4 2016

Duma had the most liked content!

Community Reputation

242 Excellent

About Duma

  • Rank
    Artist
  • Birthday 08/03/1989

Contact Methods

  • Website URL
    http://www.pimpmylinux.wordpress.com

Profile Information

  • Gender
    Male
  • Location
    Rivalta (TO) - Italia
  1. Anyone want to help me with a Bodhi Logo?

    The file comes from the original logo and carries back a lot of unused definitions. I've delete all the bloat code and now you should see all clean and flat colored
  2. Anyone want to help me with a Bodhi Logo?

    https://www.dropbox.com/s/rxe72ju8e2r921m/SimpleBodhi.svg Here's for you!
  3. Theme fixing

    The theme was create by Luca De Marini (Artpulse, OpenGEU, etc etc) with buttons on the left, I've only recompiled keeping its concept. It was choosen in the Theme poll I launched because it's with buttons on the left, even if a lot of people uses buttons on the right... For editing a thing like that on this theme is something very hard, but, of course, possible. We have to create new pixmaps and rewrite entirely the border code. No panic, by the way, it's possible and I hope to be more free in the middle of April, sorry but for Easter and spring I have a lots of things to do. I can try to do this and write a simple tutorial here, but as you have all understood, I can't be sure for the time I use to do this A good theme could have different Border style and you can, via software at the moment, set the favorite border style. So in SWAMI I suppose it could be something not so hard, because the configuration is already possible in E, am I wrong, Jeff? For SimplEx I've create left and right buttoned border style, so I've imagined to explain quickly how to set as default a style: As you know there's 4 kind of window: default, dialog (mainly a default without iconify), noresize, noresize_dialog For "default" window style it's possible to set the default style using Settings -> Looks -> Border (or something similar, I'm not in Moksha at the moment) For other style I suppose it's possible using the "Remeber..." option: it has a flag about border style. So you can set, at the moment, a default style for all the kind of windows. Of course a theme should have inside the different window style. So it's a themer duty
  4. Theme fixing

    So it was the mouse_events things I wrote last tuesday?
  5. Theming for Moksha

    If you want to port an existing gtk theme, consider a theme that also have a gtk3 version. Otherwise you will do a lot of yob for an uncomplete work. Have you checked if your bamboo theme has a gtk3 version?
  6. Theming for Moksha

    I try to encourage every attempt to theme creation with my support and my experience. At the moment I don't have time to write a comprensive guide to make themes, I'm sorry about that . Reading documentation could be an useful start point. I've used a lot of "#define" on Radiance theme, so it could be a little more complicated to read as theme, maybe starting with Dark theme could be better. Do you have any scratch or mokup of your ideas? What Jeff said (and this is what make Moksha Themes unique) is the elementary part of the theme. To make this I suggest to start decompiling the Elementary Dark theme. The sintax is pretty similar to EDJE themes . It won't be easy, but I encourage you to start because we need more themers!! :D Feel free to ask if you have doubt, of course.
  7. Moksha on PCLinuxOS

    It seems that also PCLinuxOS, the another Enlightened distro, has tried Moksha and try to bake an ISO: Check it here: http://www.pclinuxos.com/forum/index.php/topic,136027.0.html
  8. Let me describe for you tasks.edc file from default theme, would you? you can find two groups - "e/modules/tasks/item" and "e/modules/tasks/item_vert" -: the first manages the widget for horizontal layout, the second one for the vertical layout. Easy . Dig into the "e/modules/tasks/item" you can find all these parts, ordered from the background and go until the foreground: "sel_shadow", an image (this file: "shadow_rounded_horiz" ). Nothing particular to say: it has the mouse_events: 0; option. Useful because on this part mouse doesn't send signals. "glow" ( glow_small.png). The blue glows that appear when a task is selected. Note that it has three state. A state named "default" (all the parts must have it), a state named "visible" and a state named "hilighted". the inherit: "default" 0.0 option on the top two state means: "Hey copy all the setting from "default" 0.0 state, exept from the following". So what it changes from "default", "visible" and "hilighted"? The color that will be multiplied on the image layer.On "default" the 4 layer of the glow.png image will be multiplied for 255 (on a 0-255 scale, so it's the 1, multiplying for 1 make a number equal to itself ) 255 255 and 0. Note the last one is the alpha channel, so the alpha layer (the transparency layer) will be multiplied for 0, will be make it transparency. On "visible" alpha channel will be multiplied for 128, semitransparency! On "hilighted" alpha channel will be multiplied for 255, full solid colors! How glow part swithches between all the states? It uses the programs on line 289-303: program { signal: "e,state,unfocused"; source: "e"; action: STATE_SET "default" 0.0; target: "clip"; target: "sel_clip"; target: "glow"; } program { signal: "e,state,focused"; source: "e"; action: STATE_SET "hilighted" 0.0; transition: DECELERATE 0.2; target: "glow"; after: "focus2"; } program { name: "focus2"; action: STATE_SET "visible" 0.0; transition: SINUSOIDAL 0.3; target: "glow"; } The first program is triggered by the signal "e,state,unfocused": when a window gets unfocused, the program do the action STATE_SET "default", so changes the state of the TARGET parts to "default" 0.0. The second program is triggered by the signal "e,state,focused": when a window gets focused, the program on 0.2 seconds change the state of TARGET part "glow" to "hilighted" and on 0,3 second to "visible", to get a blinking effect. Note the "after" option on the second program, after it does its action, launch the program named "focus2", the third. "sel_base" ( vgrad_med_dark.png), the base of the task button. Note the clip_to option that refers to a "sel_clip" part. "Clipping" a part to another makes something similar at multiplying the two parts. The RGBA channels (and other state like visible) of the part clipped will be multiplied by the RGBA channels of the "clip_to" part (in this case, sel_clip). "sel_bevel" ( bevel_out.png), parts the compose the base of the task button, the "bevel effect". Also clipped by "sel_clip" part. "sel_label" a text part that display the name of the selected window. Two states: default and clicked. You see the change of color between the two states (mainly the color1: (the base), color2 and color3 point to shadow and border of the text - change only the alpha channel.). Also clipped by "sel_clip" part I'll suspend the sequence of the parts to focus your attention on "sel_clip" part, the last one (line 248): part { name: "sel_clip"; type: RECT; description { state: "default" 0.0; rel1.offset: -20 -20; rel2.offset: 19 19; visible: 0; } description { state: "selected" 0.0; inherit: "default" 0.0; visible: 1; } description { state: "iconic" 0.0; inherit: "default" 0.0; visible: 0; } } three states: "default", "selected" and "iconic": this part it's just a RECTangle (you'll see the type part) that is visible only on selected state. And the switch of "selected" state is managed by programs on lines 283-289 (syntax similar to the programs showed before). So when a window gets focused, all the part clipped to "select" gets visible and when a window gets unfocused or iconified the part gets invisible, because "default" and "iconic" state of "sel_clip" part is with "visible: 0". "base", it has two state "default" and "clicked" and it change its image between the two states ( button_normal.png for normal state and button_clicked.png for clicked state. Notice the changes of gradient and dimension.) the change of state is managed by the following program: program { signal: "mouse,down,1"; source: "event"; action: STATE_SET "clicked" 0.0; target: "base"; target: "e.text.label"; target: "sel_label"; } program { signal: "mouse,up,1"; source: "event"; action: STATE_SET "default" 0.0; target: "base"; target: "e.text.label"; target: "sel_label"; } what events triggered these programs: the mouse click on "event" part. If the button 1 of the mouse goes down (you press the button!), changes the state to clicked, when the button 1 of the mouse turns up (you release the button!) the state goes "default". the target of these programs are 3: "base", "e.text.label" and "sel_label". Notice that base part is clipped by a clip part named "clip" (see on line 233) that is visible on state "default" and "iconic", but invisible on state "selected". When a button goes selected, all the parts clipped by clip disappear and appear all the part clipped to "sel_clip", and vice versa, of course. "e.text.label". a text part that display the name of the window. It turns between a default state and an "iconic", for iconified window. The iconic has a less bright colors (all the RGB channel multiplied for 21 on a scale 0-255) "icon" and "icon2" are SPACER parts: it manages the sapce to let for the icon. That is different if the task is "default", with only icon ("icon_only" state) or only text ("text_only" state). "icon_clip" a part that make all the parts clipped by it semitransparent when it gets to the state "iconic". Mainly the Icon. "bar" the glow blue bar horizontal_separated_bar_glow.png that appear on selected tasks. In fact it is clipped by "sel_clip": it hasn't a state that make it visible when window gets focused. "sel_clip" will do it for it. "e.swallow.icon". The icon part. It's a SWALLOW because it take the source of the image from an external source. It is not on the EDJ theme. States "bounces" refers to the bounce effect that you see if your window send notifications: the icon starts bounces changing its position (rel1 and rel2 option change the position of the top-left and bottom-right conrers). "event" part: un invisible RECTANGLE used to catch all the mouse click event. "sel_shine" the shine of selected tasks ( -it's visible on dark background-). Clipped to "sel_clip", works exacly like "bar" part. After that you will se "clip" and "sel_clip" part, discussed before. I hope to point you in right direction for your theming work. This is just an overview of the code, but if you have specific question please ask. You have to edit not only "base" part, but also all the part clipped to "sel_clip". Have you done it?
  9. Evolution email in Bodhi 3.1.1

    I use evolution mail, even if it carry a lot of bloath from gnome, if I correctly remember. There's other GTK3 client mail, like Geary (from the fancy mac wannabe designers of Elementary ), if you like to try
  10. Congratulation mbert! I hope you will continue with theming (ELEMENTARY porting needs you! ). Feel free to ask if you need more support!
  11. making unfocussed windows again transparent in bodhi 3.1.0

    A similar topic has been discussed here, by the way on old E17 (or E19) was possible to manage opacity through Color Settings because the compositing effects were managed by E theme. Now compositing is on the lovely hands of Ecomorph. Or you can also try other compiste manager, like compton.
  12. A program that compare file that I've used is meld. I suggest it because you can also edit and save the file. By the way, here's a quick and dirty piece of code that you can add to your "e/fileman/default/window/main" group: parts (insert as lasts): part { name: "e.swallow.favorites"; type: SWALLOW; description { state: "default" 0.0; align: 0. 1.0; rel1.offset: 4 4; rel1.to: "region"; rel2.offset: 4 -5; rel2.relative: 0.0 1.0; rel2.to: "region"; fixed: 1 0; } } part { name: "e.swallow.content"; type: SWALLOW; description { state: "default" 0.0; rel1.offset: 4 4; rel1.to: "region"; rel2.offset: -5 -5; rel2.to: "region"; align: 1.0 1.0; } description { state: "fav" 0.0; inherit: "default" 0.0; rel1.relative: 1.0 0.0; rel1.to_x: "e.swallow.favorites"; } } part { name: "e.swallow.toolbar"; type: SWALLOW; description { state: "default" 0.0; } description { state: "tb_top" 0.0; align: 0.5 0.0; rel1.offset: 4 4; // XXX: this is a bug workaround. should be -4 4; rel2.offset: -9 4; rel2.relative: 1.0 0.0; fixed: 0 1; } description { state: "tb_bottom" 0.0; align: 0.5 1.0; rel1.offset: 4 -5; rel1.relative: 0.0 1.0; // XXX: this is a bug workaround. should be -4 -5; rel2.offset: -9 -5; fixed: 0 1; } } part { name: "region"; type: SPACER; description { state: "default" 0.0; } description { state: "tb_top" 0.0; inherit: "default" 0.0; rel1.relative: 0.0 1.0; rel1.to_y: "e.swallow.toolbar"; } description { state: "tb_bottom" 0.0; inherit: "default" 0.0; rel2.relative: 1.0 0.0; rel2.to_y: "e.swallow.toolbar"; } description { state: "tb_left" 0.0; inherit: "default" 0.0; rel1.relative: 1.0 0.0; rel1.to_x: "e.swallow.toolbar"; } description { state: "tb_right" 0.0; inherit: "default" 0.0; rel2.relative: 0.0 1.0; rel2.to_x: "e.swallow.toolbar"; } } and programs program { signal: "e,favorites,enabled"; source: "e"; action: STATE_SET "fav" 0.0; target: "e.swallow.content"; } program { signal: "e,favorites,disabled"; source: "e"; action: STATE_SET "default" 0.0; target: "e.swallow.content"; } program { signal: "e,toolbar,left"; source: "e"; action: STATE_SET "tb_left" 0.0; target: "e.swallow.toolbar"; target: "region"; } program { signal: "e,toolbar,right"; source: "e"; action: STATE_SET "tb_right" 0.0; target: "e.swallow.toolbar"; target: "region"; } program { signal: "e,toolbar,top"; source: "e"; action: STATE_SET "tb_top" 0.0; target: "e.swallow.toolbar"; target: "region"; } program { signal: "e,toolbar,bottom"; source: "e"; action: STATE_SET "tb_bottom" 0.0; target: "e.swallow.toolbar"; target: "region"; } program { signal: "e,toolbar,disabled"; source: "e"; action: STATE_SET "default" 0.0; target: "e.swallow.toolbar"; target: "region"; } Let me know!
  13. Moksha Themes...

    Hi guys! I've assumed that the SimplEx EDJ part of the theme is complete (maybe it lacks a couple of barely used modules, so I can add it later) and I've moved on to extend the SimplEx to ELEMENTARY! As I've done for all my theme, when I start with a ELM porting, I share with bother you with the first widget: Action Slider!! Probably I'll take a looooooot of time to end all this theme, so feel free to take the latest version on my Github page, if you are impatient!
  14. Request: port of old E16 themes (like blue steel)

    Porting the blingbling theme is a goal that I have, but I don't know when I'll have enough time to spend on this.
  15. Compare your fileman.edc file with one taken from a decompiled e20 themes. There's some differences that you have to do.
×