Ha.. nearly suggested that one (a few pages back) given you have a good SDL background.

EDIT: however, most pups don't ship with SDL as standard. I did it in slacko for a bit more functionality ootb, at not a huge cost in terms of bloat._________________Puppy Linux Blog - contact me for access

Ha.. nearly suggested that one (a few pages back) given you have a good SDL background.

EDIT: however, most pups don't ship with SDL as standard. I did it in slacko for a bit more functionality ootb, at not a huge cost in terms of bloat.

I wrote an SDL engine a few years back but it became one of those projects that never gets finished for one reason or another (Tetravex works though as long as you stay away from the unfinished high score entry) and I've been thinking about recycling it Anyway, just an idea I've got whizzing around.

Yeah, I liked having the full SDL monty with Slacko 5.5 because normally what I do is download all the SDL source packages and dependencies and create my own pets but I was mostly spared that, which was nice. It was in fact the default presence of those libraries that got me thinking.

What other lightweight toolkits does Puppy include? I've got flsynclient so there must be fltk I guess. I don't really know much about it. I'm just thinking out loud.

Just a short catchup :
Have compiled gtkdialog-0.7.20-21-r83 from bk sources and 0.8.2 from google code
on Puppy derivate having gtk-2.16.1 :
svg icons don't work for me , showing the icon for not available ( paper with X ) .

Path to the svg is there and inscapelite opens and shows shows the created svg .

hmmm, it works on Puppeee, though the build is slightly different. Can someone on 4.3.1 check? I think Ttuuxxx updated the gtk on Puppies, and forgot SVG support or something because I've had other problems with tray applets on Puppies in the past.

And it's true , runtt21 used a 432 devx by ttuuxxx for Macpup Foxy 3 . Opera 2 has gtk2-14.7 but i have put in the 16.1 from F3 so geany shows the delete icon-button in the find entry line . Will check things out !

Cheers !

EDIT:
Have compiled 0.8.2 with the 14.7 default gtk-2 libraries of Puppy-4.3.1 and svg works now for latest woof2 partview . technosaurus, thank you very much !
/EDIT

Working with pMusic 4, I have met some issues with the latest gtkdialog. I wouldn't call them bugs as things may work as expected. On the other hand, I see no reason for not mention, and maybe one or two could easily be 'fixed'.

vbox / hboxIf scrollable="true". I am not able to get use of space-expand="true" space-fill="true" to expand width.
I have to use <window width-request="300">, but this a not the best solution if someone uses a longer NLS-string.

Improving my template for a right-click menu, I wanted to add a frame. But the <frame> widget is both not complete (always a gap for label), and takes a lot of place since I am not able to set spacing, I looked at the scrollable vbox. This one accepts both spacing and different shadow-types...

This is basically how the right-click menu looks like. Here is scrollable set to true, so window won't expand to show the complete label.

Using a scrollable vbox is of course not necessary here, but a ordinary vbox won't let me set a frame. It seems to me that the option Shadow-type only works if scrollable="true".

tree
One of the major improvements in pMusic 4, is the switching from table to tree widget and the usage of multiple selection. This gives many new features when it comes to track/playlists/file managing. This has lead to a simpler workflow. and it is looking all good. What is a bit awkward, is that hover-selection can't be combined with a selection-mode

With multiple selection activated (selection-mode="3"), selecting a list-item is activated after the signal="button-press-event", and the right-click menu is shown by that signal. This is logic, because else the selection would be deactivated when right-click. BUT! this means that the user has to first click on an item, and then click another time to show the menu. If hover-selection was possible to combine with selection-mode this would work as other gtk-apps. This would also allow drag and drop internally in any gtkdialog app. ( Am I dreaming... ) Drag and drop works in the pMusic playlist, but only because multiple-selection isn't activated and hover-selection="true".

Switching from <table> to <tree> has been easy with the latest updates of gtkdialog. In fact most stuff works better with the tree widget. But I have met one tiny issue. To force the scrollbar to top I clear:tree before refresh:tree. This is a nice 'trick', but works only for the hscrollbar. Strangely the clear command does NOT reset vertical scrollbar.

I'll have a look at these issues soon, a bit at a time because I've got other things to do at the moment.

I have noticed that the GtkLabel text in the <text> widget is being rendered differently in gtk3 but I'm testing the examples and then researching any issues/differences and I've haven't reached "t" yet.

[EDIT] @simargl: I think you're just assuming wrongly regarding the justify property: justify is relative to the other lines within the same widget; the xalign property is what you want -- the examples/text/text_advanced and examples/text/text_attributes demonstrate both of these.

...
vbox / hboxIf scrollable="true". I am not able to get use of space-expand="true" space-fill="true" to expand width.
I have to use <window width-request="300">, but this a not the best solution if someone uses a longer NLS-string.

Improving my template for a right-click menu, I wanted to add a frame. But the <frame> widget is both not complete (always a gap for label), and takes a lot of place since I am not able to set spacing, I looked at the scrollable vbox. This one accepts both spacing and different shadow-types...
...
Using a scrollable vbox is of course not necessary here, but a ordinary vbox won't let me set a frame. It seems to me that the option Shadow-type only works if scrollable="true".
...

Making a vbox scrollable packs it inside a GtkViewport inside a GtkScrolledWindow and that's it. It does what you would expect it to such as expanding to accommodate its contents and adding scrollbars if it becomes bigger than the viewport that you're looking through. shadow-type does indeed only affect the GtkViewport.

The frame widget is flawed because all of the empty space within the tag becomes the label. I'm sure the original author thought it was a good idea at the time but it means that you can't set GtkFrame properties. Also it automatically has a vbox placed within it and of course you can't set its properties either. Anyway, even though without a label the border is unbroken, there's a top margin.

You could try h/vseparators I just tried it and if you set the spacing to 0 then they connect at the corners.

[EDIT] Actually forget the separator idea -- it'll drive you insane I was just playing with an eventbox with a border inside an eventbox with a dark background which is great but it's theme dependent. Also gtk3 requires the interior eventbox to have a background colour set which again is theme dependent.

Regards,
ThunorLast edited by thunor on Thu 02 May 2013, 11:19; edited 1 time in total

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum