Very nice.
Awesome on the zlib too.
What if you make the keyrepeat a boolean in a config file config of some kind?
edit: also, github/bitbucket maybe?
Gspöt - retained GUI lib
- josefnpat
- Inner party member
- Posts: 955
- Joined: Wed Oct 05, 2011 1:36 am
- Location: your basement
- Contact:
Re: Gspöt - formerly Yet another stateful GUI
Missing Sentinel Software | Twitter
FORCIBLY IGNORED.
<leafo> when in doubt delete all of your code
<bartbes> git rm -r *
<bartbes> git commit -m "Fixed all bugs"
<bartbes> git push
FORCIBLY IGNORED.
<leafo> when in doubt delete all of your code
<bartbes> git rm -r *
<bartbes> git commit -m "Fixed all bugs"
<bartbes> git push
Re: Gspöt - formerly Yet another stateful GUI
At least start to versioning the file name would help easily track, delete and compare versions.josefnpat wrote:edit: also, github/bitbucket maybe?
Also perhaps your could merge your shooter bonus to regular demo.
- trubblegum
- Party member
- Posts: 192
- Joined: Wed Feb 22, 2012 10:40 pm
Re: Gspöt - formerly Yet another stateful GUI
I'm very reluctant to add config files etc, for ease-of-use reasons, but I hope I've done one better by asking for element.keyrepeat when setting focus. This change means that you must use gui:focus(id) and gui:unfocus() to set and clear focus. Lookup focus is still at gui.focus
Naturally, Gspot returns to any keyrepeat state set outside of itself when it clears focus.
Also added optional element.updateinterval, which sets a delay for element:update() calls.
The naming convention has me a bit consterned, as I'd rather have element.keyinterval, but consistency with love convention would seem to make for better user-friendly-bility.
Re repository : I think it would be a pretty good idea, but believe it or not, I've never used one before .. would anyone recommend one over the other?
I'm not sure about adding the shooter to the demo .. it's just a silly experiment, really, and I think it would distract from the main purpose of the lib.
Naturally, Gspot returns to any keyrepeat state set outside of itself when it clears focus.
Also added optional element.updateinterval, which sets a delay for element:update() calls.
The naming convention has me a bit consterned, as I'd rather have element.keyinterval, but consistency with love convention would seem to make for better user-friendly-bility.
Re repository : I think it would be a pretty good idea, but believe it or not, I've never used one before .. would anyone recommend one over the other?
I'm not sure about adding the shooter to the demo .. it's just a silly experiment, really, and I think it would distract from the main purpose of the lib.
Re: Gspöt - formerly Yet another stateful GUI
Well, could appear be silly but that don't show exactly how flexible the gui is? Distract of main purpose? I thought you would let people have free choice how to use the library. Or you are saying "you have here a convertible car but you can only use with top on"? I'm pretty sure that if people see a character among all that windows won't forget for what the library was done.trubblegum wrote: I'm not sure about adding the shooter to the demo .. it's just a silly experiment, really, and I think it would distract from the main purpose of the lib.
- trubblegum
- Party member
- Posts: 192
- Joined: Wed Feb 22, 2012 10:40 pm
Re: Gspöt - formerly Yet another stateful GUI
I will consider your words .. for now, enjoy the shiny github goodness, which is my top priority on this project for now.
josefnpat, you are my hero, thank you for showing me the way
josefnpat, you are my hero, thank you for showing me the way
Re: Gspöt - formerly Yet another stateful GUI
Nice to have another gui library.
But what does it better? Whats the difference to EGS, Goo, Gwee, quickie, lQueryUI ?
But what does it better? Whats the difference to EGS, Goo, Gwee, quickie, lQueryUI ?
- josefnpat
- Inner party member
- Posts: 955
- Joined: Wed Oct 05, 2011 1:36 am
- Location: your basement
- Contact:
Re: Gspöt - formerly Yet another stateful GUI
Yay, GitHub. Github Github Github Github...trubblegum wrote:I will consider your words .. for now, enjoy the shiny github goodness, which is my top priority on this project for now.
josefnpat, you are my hero, thank you for showing me the way
One Gui to rule them all? Nothing wrong with a variation, but I don't think it's up to him to compare them all. It might be refreshing if someone took all the gui libs, and wrote a comparative chart on them.SiENcE wrote:Nice to have another gui library.
But what does it better? Whats the difference to EGS, Goo, Gwee, quickie, lQueryUI ?
Missing Sentinel Software | Twitter
FORCIBLY IGNORED.
<leafo> when in doubt delete all of your code
<bartbes> git rm -r *
<bartbes> git commit -m "Fixed all bugs"
<bartbes> git push
FORCIBLY IGNORED.
<leafo> when in doubt delete all of your code
<bartbes> git rm -r *
<bartbes> git commit -m "Fixed all bugs"
<bartbes> git push
Re: Gspöt - formerly Yet another stateful GUI
I think it's hard to say each one is better. All are usually well done, but some have components not avaliable in others. Best way to choose each one is better is test it all and see each one fits better to our desires. It's a question of taste and needs really.SiENcE wrote:Nice to have another gui library.
But what does it better? Whats the difference to EGS, Goo, Gwee, quickie, lQueryUI ?
- trubblegum
- Party member
- Posts: 192
- Joined: Wed Feb 22, 2012 10:40 pm
Re: Gspöt - formerly Yet another stateful GUI
It is completely unique in that it works the way I want it toSiENcE wrote: But what does it better? Whats the difference to EGS, Goo, Gwee, quickie, lQueryUI ?
Take a look at the write-up I just completed over on github, and decide for yourself.
Or, to put it another way : What they said.
- trubblegum
- Party member
- Posts: 192
- Joined: Wed Feb 22, 2012 10:40 pm
Re: Gspöt - formerly Yet another stateful GUI
Just a quick note re something thrown up by the way-back machine
An example of its use would be a blinking button, or an enemy in Gewter which runs its AI every second instead of every frame.
I've gone ahead and included it anyway, as it's a nice little way to do some quick optimising (limited in scope though it may be) dev-side, and I've seen a couple of questions relating to timers and how to create and use one, so why not throw in the functionality?I'm not sure the updateinterval would be used enough to warrant its own per-element setting, especially since there would almost always be an alternate solution using dt.
An example of its use would be a blinking button, or an enemy in Gewter which runs its AI every second instead of every frame.
Who is online
Users browsing this forum: No registered users and 4 guests