[library] fLUIds - A love-imgui API wrap for simplicity

[milk]

love-imgui API wrap for simplicity, inspired by LaTeX TikZ node positioning.
Depends on love-imgui: https://github.com/slages/love-imgui , you'll need to compile the binaries or use the ones provided on that GitHub link.

As you can see by the love-imgui example, it's pretty, well, ugly un-manageable to say the least, I made this lib to solve that problem.
This library simplifies the usage of love-imgui so that you can use it in a neat OO fashion, with some helpers of course.

Documentation: https://github.com/twentytwoo/fLUIds

Essentially;

Code: Select all

  drawable = function() imgui.Text("Hello World!") end

  window_1 = fluids.Window("Window 1", drawable, {10, 10, 300, 200})
  window_2 = fluids.Window("Window 2", drawable, {0, 0, 100, 50})

  window_2:setAlign({"below of", "right"}, window_1)
  
  -- Or a nameless window
  fluids.Window("I am stored nowhere - spooky", drawable, {10, 20, 30, 40}, {"NoTitleBar"}) 

(drawable is different in the picture shown, but the same concept)

2017-11-02-200639_1366x768_scrot.png (13.74 KiB) Viewed 11899 times

To be a nice person I've decided to renamed the library from succ to fLUIds - fL(ove-imgui)U(ser)I(interface)ds

[Tjakka5]

Sadly I don't see how this library should help make GUI's made with Imgui "less ugly".
I find writing a GUI in an immediate way very easy and flexible.

With this however, you still need to store your variables somewhere. Where that location may be is not "fixed" by your library, so that "problem" still persists. Maybe even made worse.

On top of that, you now also need to create, keep track of, and sometimes destroy a window. Just unnecessary work by something that could be done as easy as:

Code: Select all

if myGuiIsOpen and Imgui.Begin("My GUI") then
  -- Do stuff
end; Imgui.End()

So then the only feature I see is being able to put windows next to each other in different ways.
However, I can't think of any situation that I would want that.
If I want a GUI with a weirdly aligned layout, I'd just use Imgui's child system.

I also don't understand the library name.

A term for fellatio.

Im not agains't "Love related" library names, as long as they make sense. This just seems like it was named "succ" for the sake of naming a library that.

[brogrammer]

Im not agains't "Love related" library names, as long as they make sense.

you from the library name police?

[Tjakka5]

Im not agains't "Love related" library names, as long as they make sense.

you from the library name police?

There have been numerous discussions about "Love" related naming of libraries. The general opinion is that they should either have a reason to be called that, or even just not be called that at all.

There have been multiple libraries posted here with sexual names without any reason. (Off the top of my head I know "Nut", "Moan", "Lovetoys")

And a few that make actual sense, even taking some thought to 'get': Love Bone, HC.

Either way, naming your library "Succ" (Which is also used as a meme) just for the sake of naming that is tasteless and childish in my opinion, and should be considered to be changed.


That comment about the name was only a small part of my critique, and should not be the focus of this thread.

[brogrammer]

people create and share things and are free to give them a name of their choice. they don't have to make sense and they don't require your approval. imma write a lib named FÜCK just to spite you and your entitlement lol

[zorg]

Children please, if i were to stoop to such levels, i'd say that both of you should go and do the proverbial library name action

In any case, why stop people from trying to make a library work as they would rather see it work?

If they enjoy retained mode more, instead of an immediate mode solution, while still using the same library that actually is somewhat decent, even if only for tinkering, in löve where the selection of working UI-s isn't the top type of lib being worked on, then why stop them?

[milk]

Sadly I don't see how this library should help make GUI's made with Imgui "less ugly".
I find writing a GUI in an immediate way very easy and flexible.

With this however, you still need to store your variables somewhere. Where that location may be is not "fixed" by your library, so that "problem" still persists. Maybe even made worse.

The love-imgui example shows windows being opened and closed with arbitrary booleans...

Code: Select all

local showTestWindow = false
local showAnotherWindow = false

if showTestWindow ...

If you were to have a debug system with over 100 booleans to specify if a window should be opened or closed it'd get a bit ridiculous. All this lib does is manage windows. This would also mount up in your love.update() wherein you would have >100 imgui.Begin()'s, contrasted with a single succ.Update()/succ.Draw()

On top of that, you now also need to create, keep track of, and sometimes destroy a window. Just unnecessary work...

Also, windows are stored in succ.clients - you don't even need to need to define a variable for a window, you could just call succ.Window() on its own in love.load() ..., defining vars is just so you can run the succ methods, (e.g. :setAlign, :destroy)

So then the only feature I see is being able to put windows next to each other in different ways.
However, I can't think of any situation that I would want that.
If I want a GUI with a weirdly aligned layout, I'd just use Imgui's child system.

Maybe not for you, but I've known a few people I've talked to that liked the idea of window positioning the way this lib does, most people simply want make things quickly and without any headaches, not spend ages reading through the imgui documentation which is loaded into c++ file

I also don't understand the library name.

A term for fellatio.

Im not agains't "Love related" library names, as long as they make sense. This just seems like it was named "succ" for the sake of naming a library that.

I put almost no thought into the name, no need to get your panties in a bunch because you're some kind of celibate , you can just as easily change it by changing the require name.

At the end of the day it's just your opinion man, if you don't like the lib thats fine, you do you

[yetneverdone]

Oh, why changed the name?

[milk]

Oh, why changed the name?

because succ wasn't exactly subtle, at least fLUIds kind of makes sense ... fL(ove-imgui)(U)ser(Interface)ds
and because people's feefee's

[yintercept]

Just want to say thanks for the library, been a breeze working with it. Thanks again.