On Thursday, 11 March 2021 at 10:59:11 UTC, Mark Lagodych wrote:
> I've got an idea of a small GUI library as a pet project. What easy-to-type, short and nice name you can suggest? I can also use a shortened form (for instance, if the lib is called "kaleidoscope", i can use only "kd").
>
> I've come up with these ones so far:
> - Mango (is it already used?)
> - Rowan (i like it; could be shorten to "rw")
> - Feijoa (complicated, however, could be shorten to nice "fj")
> - Pumpkin (also could be "pmk")
>
> Why fruit? Well, that are just my names. You don't have to mention fruit.
>
> Any beautiful words associated with Mars?

Is Ares taken? 🤔

AresUI

On Thursday, 11 March 2021 at 15:54:49 UTC, Mark Lagodych wrote:
>
> My goal is to create something like Qt. Big, usable and aesthetic (in terms of code)

Then the name should reflect the desired attributes: Big, Aestheic, Usable

BAU

if we turn Usable into Easy it becomes

BAE

aka the acronym for Before Anyone Else.

So I'd says BAE UI.

On Thursday, 11 March 2021 at 17:03:38 UTC, Guillaume Piolat wrote:
>
> So I'd says BAE UI.

Of course the name's already taken: https://github.com/nkpgardose/bae-ui

On Thursday, 11 March 2021 at 16:36:00 UTC, Imperatorn wrote:
> On Thursday, 11 March 2021 at 10:59:11 UTC, Mark Lagodych wrote:
>> Any beautiful words associated with Mars?
> Is Ares taken? 🤔
> AresUI

Yes, unfortunately :(.

On Thursday, 11 March 2021 at 10:59:11 UTC, Mark Lagodych wrote:
> I've got an idea of a small GUI library as a pet project. What easy-to-type, short and nice name you can suggest? I can also use a shortened form (for instance, if the lib is called "kaleidoscope", i can use only "kd").
>
> I've come up with these ones so far:
> - Mango (is it already used?)
> - Rowan (i like it; could be shorten to "rw")
> - Feijoa (complicated, however, could be shorten to nice "fj")
> - Pumpkin (also could be "pmk")
>
> Why fruit? Well, that are just my names. You don't have to mention fruit.
>
> Any beautiful words associated with Mars?

Will Jupiter be OK? Or Saturn?

On Saturday, 13 March 2021 at 23:51:21 UTC, Mark Lagodych wrote:
> On Thursday, 11 March 2021 at 10:59:11 UTC, Mark Lagodych wrote:
>> I've got an idea of a small GUI library as a pet project. What easy-to-type, short and nice name you can suggest? I can also use a shortened form (for instance, if the lib is called "kaleidoscope", i can use only "kd").
>>
>> I've come up with these ones so far:
>> - Mango (is it already used?)
>> - Rowan (i like it; could be shorten to "rw")
>> - Feijoa (complicated, however, could be shorten to nice "fj")
>> - Pumpkin (also could be "pmk")
>>
>> Why fruit? Well, that are just my names. You don't have to mention fruit.
>>
>> Any beautiful words associated with Mars?
>
> Will Jupiter be OK? Or Saturn?

- Olympus Mons, the largest volcano

- Valles Marineris, one of the largest canyons in the Solar System

- a large amount of underground ice in the Utopia Planitia region

- the vast upland region Tharsis

Tharsis UI 😎
Naming sux 😔

On Sunday, 14 March 2021 at 07:35:11 UTC, Imperatorn wrote:
> - the vast upland region Tharsis
> Tharsis UI 😎

Tharsis UI is the best! Thanks 😊
＼(^o^)／

On Thursday, 11 March 2021 at 15:54:49 UTC, Mark Lagodych wrote:
> My goal is to create something like Qt. Big, usable and aesthetic (in terms of code)

A word of warning. Every now and again a developer stumbles into these forums, eyes blinking in the glare of D's clean lines and meta-programming power, and says "I'm going to reimplement Qt in D". It's a huge job that one person can't do on their own. I urge you to get a realistic expectation in place before starting. Which parts of Qt would you focus on first? Also, which platform (windows, linux, macos)?

On Sunday, 14 March 2021 at 11:47:59 UTC, Abdulhaq wrote:
> I urge you to get a realistic expectation in place before starting. Which parts of Qt would you focus on first? Also, which platform (windows, linux, macos)?

My roadmap is:

1. Create a framework with event-driven programming and a nice OOP entry point. (Reimplantation of QApplication class and event-flavoured C++).

2. Create a module called "platform". It will be a middle-level abstract interface to a system API. No pretty widget class hierarchy/string translations/advanced resource loading. Plain functions for creating, destroying, modifying widgets and some capabilities of drawing with OpenGL or whatever.
Porting my library to a new platform might be as simple/hard as reimplementing "platform.d"

I target:
- easy use of both native and owner-drawn gui
- easy use of native features (system notifications (as a sort of message boxes), window transparency, drag-and-drop)
- Linux and Windows because I have them installed on my PC

3. Pretty widget class hierarchy that basically just glues up high-level (1) and middle-level (2) parts of the library.

I target:
- high extensibility (what about implementation of QML? MsExcel-like widget? Syntax highlighting in TextEdit? I probably won't do that, but I'll leave an opportunity for somebody else)
- string translations, theming.

-----------------------
That's all for now about how I feel Tharsis will be done.

On 15/03/2021 12:57 PM, Mark Lagodych wrote:
> 2. Create a module called "platform". It will be a middle-level abstract interface to a system API. No pretty widget class hierarchy/string translations/advanced resource loading. Plain functions for creating, destroying, modifying widgets and some capabilities of drawing with OpenGL or whatever.
> Porting my library to a new platform might be as simple/hard as reimplementing "platform.d"

That is going to be a massive module.

See: https://github.com/Devisualization/spew