letlang
Glimmer
letlang | Glimmer | |
---|---|---|
12 | 24 | |
157 | 514 | |
- | - | |
7.9 | 8.2 | |
4 months ago | 3 months ago | |
Rust | Ruby | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
letlang
-
Letlang — Roadblocks and how to overcome them - My programming language targeting Rust
That works for any types (except the functional types), and even the generic ones. During code generation, I create structs that implement the Type trait.
-
A new milestone for Letlang (targeting Rust) - Effect Handlers
As stated on the website ( https://letlang.dev ), Letlang is a general-purpose language.
-
Writing a simple Lisp interpreter in Rust
Author here, the article is more about how Rust and its ecosystem are nice tools for language designers rather than the beauty of Lisp.
The crates listed in that article are the ones I use for my compiler: https://letlang.dev
Lisp was only chosen as a way to demonstrate the power of those crates and Rust features. A kind of way of justifying my choices for Letlang.
It's not "you should do it like this" but "you can do it like this".
-
Ask HN: Possible? Faster than C, simpler than Python, safer than Rust
"Faster than C", I saw people write C code slower than a Python equivalent. So I have to admit, I don't know what it means for a language to be fast, because it depends on the algorithm being implemented.
---
"simpler than Python", what does "simple" mean?
Simple design? Python's design is very complex (take a look at "Crimes with Python's pattern matching" < https://www.hillelwayne.com/post/python-abc/ > for example), on the other hand, assembly languages, or Lisp, or Forth, have a very simple design.
Simple as in "easy to use"? Rust is easy, write code, fix what the compiler tells you you did wrong. Joke aside, Go is quite easy to use and while I personally don't like this language, I get why it replaced Python in a lot of use cases.
Also, once you get used to the OTP framework, Erlang/Elixir/Gleam/any beam language are quite easy to use and have less footguns than Python.
---
"safer than Rust" is too vague. Is it memory safety? type safety? thread safety? cosmic ray safety? A mix of all of that?
Let's guess you meant "memory safety". All languages with a Garbage Collector are "memory safe".
---
On a semi-unrelated note, I've been working on https://letlang.dev
It's a language inspired by Erlang/Elixir (same concurrency model) that compiles to Rust code (the runtime use tokio). It is immutable, have no Garbage Collector thanks to Rust semantics, and dynamically typed.
I haven't run any benchmark (it's not even finished, I've been working on the specification before continuing the implementation), but I guess it could be slower than a rock.
---
For some recommendations, have you looked at Zig? Nim? Hare?
https://ziglang.org/
-
Syntax for defining algebraic data types
In my language (Letlang), I use the keyword class with structural pattern matching and optionally a predicate. Types (or rather, classes) can be combined with logical operators &, |, !:
-
Erlang's not about lightweight processes and message passing
Not sure this is what GP is talking about but to implement the actor model in https://letlang.dev I use tokio.
-
Features you've removed from your lang? Why did you put them in, why did you take them out?
In the early drafts of Letlang, I had the goal to add an equation solver. I got rid of that because:
-
What features would you want in a new programming language?
I'm working on a programming language inspired by erlang and which compiles to Rust: https://letlang.dev
-
Six programming languages I’d like to see
For a contract based language and a "really dynamically typed language", I'm working on https://letlang.dev
And it's because I haven't thought yet about how to do static type checking with such a feature.
I haven't got any time to work on it in the past few weeks, and I'm the only dev (would really love some help). So, it will be ready when it will be ready :P
-
Hello Letlang! My programming language targeting Rust
I use Rust generators to implement them, a rudimentary example: https://github.com/linkdd/letlang/blob/main/letlang_runtime/src/utils/entrypoint.rs
Glimmer
-
Ruby vs. Python comes down to the for loop (2021)
Glimmer is a award winning GUI Toolkit for ruby which supports every major platform (gtk, qt, wxwidgets, swt, swing, java fx, etc), it can also output as SVG or CSS: https://github.com/AndyObtiva/glimmer
- Shoes makes building little graphical programs for Mac, Windows, Linux simple
-
What would an ideal language for teaching new programmers be like?
Here's the github for the glimmer GUI library . https://github.com/AndyObtiva/glimmer
-
Emerging Rust GUIs in a WASM world
I don't quite understand why you would need to only create a web application. I see the future much more similar to like what glimmer (but in ruby https://github.com/AndyObtiva/glimmer) is doing. Write once, run verywhere.
- The "preferred" way to develop GTK applications
-
Two probably-controversial ideas for new widgets for desktop Linux, please give feedback
Personally I'd love to have a "meta-DSL" that can describe widgets and functionality without being tied to a specific language. A bit like glimmer: https://github.com/AndyObtiva/glimmer however had unified for as many possible languages out there, and not tied to a specific language per se.
-
GTK or Qt from a user point of view
Qt is probably the more sophisticated toolkit, but GTK has a few things going. I love its language support + CSS. I wrote tons of ruby-gtk3 apps and hopefully ruby-gtk4 soon. No such thing exists for qt (ruby-qt died years ago). I actually write in a mostly GUI agnostic manner; andy pushed this to a new level though: https://github.com/AndyObtiva/glimmer
-
Glimmer DSL for SWT Table Cell Data-Binding of Background/Foreground/Font/Image
# From: https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/docs/reference/GLIMMER_SAMPLES.md#hello-table require 'glimmer-dsl-swt' class HelloTable class BaseballGame class << self attr_accessor :selected_game def all_playoff_games @all_playoff_games ||= { 'NLDS' => [ new(Time.new(2037, 10, 6, 12, 0), 'Chicago Cubs', 'Milwaukee Brewers', 'Free Bobblehead'), new(Time.new(2037, 10, 7, 12, 0), 'Chicago Cubs', 'Milwaukee Brewers'), new(Time.new(2037, 10, 8, 12, 0), 'Milwaukee Brewers', 'Chicago Cubs'), new(Time.new(2037, 10, 9, 12, 0), 'Milwaukee Brewers', 'Chicago Cubs'), new(Time.new(2037, 10, 10, 12, 0), 'Milwaukee Brewers', 'Chicago Cubs', 'Free Umbrella'), new(Time.new(2037, 10, 6, 18, 0), 'Cincinnati Reds', 'St Louis Cardinals', 'Free Bobblehead'), new(Time.new(2037, 10, 7, 18, 0), 'Cincinnati Reds', 'St Louis Cardinals'), new(Time.new(2037, 10, 8, 18, 0), 'St Louis Cardinals', 'Cincinnati Reds'), new(Time.new(2037, 10, 9, 18, 0), 'St Louis Cardinals', 'Cincinnati Reds'), new(Time.new(2037, 10, 10, 18, 0), 'St Louis Cardinals', 'Cincinnati Reds', 'Free Umbrella'), ], 'ALDS' => [ new(Time.new(2037, 10, 6, 12, 0), 'New York Yankees', 'Boston Red Sox', 'Free Bobblehead'), new(Time.new(2037, 10, 7, 12, 0), 'New York Yankees', 'Boston Red Sox'), new(Time.new(2037, 10, 8, 12, 0), 'Boston Red Sox', 'New York Yankees'), new(Time.new(2037, 10, 9, 12, 0), 'Boston Red Sox', 'New York Yankees'), new(Time.new(2037, 10, 10, 12, 0), 'Boston Red Sox', 'New York Yankees', 'Free Umbrella'), new(Time.new(2037, 10, 6, 18, 0), 'Houston Astros', 'Cleveland Indians', 'Free Bobblehead'), new(Time.new(2037, 10, 7, 18, 0), 'Houston Astros', 'Cleveland Indians'), new(Time.new(2037, 10, 8, 18, 0), 'Cleveland Indians', 'Houston Astros'), new(Time.new(2037, 10, 9, 18, 0), 'Cleveland Indians', 'Houston Astros'), new(Time.new(2037, 10, 10, 18, 0), 'Cleveland Indians', 'Houston Astros', 'Free Umbrella'), ], 'NLCS' => [ new(Time.new(2037, 10, 12, 12, 0), 'Chicago Cubs', 'Cincinnati Reds', 'Free Towel'), new(Time.new(2037, 10, 13, 12, 0), 'Chicago Cubs', 'Cincinnati Reds'), new(Time.new(2037, 10, 14, 12, 0), 'Cincinnati Reds', 'Chicago Cubs'), new(Time.new(2037, 10, 15, 18, 0), 'Cincinnati Reds', 'Chicago Cubs'), new(Time.new(2037, 10, 16, 18, 0), 'Cincinnati Reds', 'Chicago Cubs'), new(Time.new(2037, 10, 17, 18, 0), 'Chicago Cubs', 'Cincinnati Reds'), new(Time.new(2037, 10, 18, 12, 0), 'Chicago Cubs', 'Cincinnati Reds', 'Free Poncho'), ], 'ALCS' => [ new(Time.new(2037, 10, 12, 12, 0), 'Houston Astros', 'Boston Red Sox', 'Free Towel'), new(Time.new(2037, 10, 13, 12, 0), 'Houston Astros', 'Boston Red Sox'), new(Time.new(2037, 10, 14, 12, 0), 'Boston Red Sox', 'Houston Astros'), new(Time.new(2037, 10, 15, 18, 0), 'Boston Red Sox', 'Houston Astros'), new(Time.new(2037, 10, 16, 18, 0), 'Boston Red Sox', 'Houston Astros'), new(Time.new(2037, 10, 17, 18, 0), 'Houston Astros', 'Boston Red Sox'), new(Time.new(2037, 10, 18, 12, 0), 'Houston Astros', 'Boston Red Sox', 'Free Poncho'), ], 'World Series' => [ new(Time.new(2037, 10, 20, 18, 0), 'Chicago Cubs', 'Boston Red Sox', 'Free Baseball Cap'), new(Time.new(2037, 10, 21, 18, 0), 'Chicago Cubs', 'Boston Red Sox'), new(Time.new(2037, 10, 22, 18, 0), 'Boston Red Sox', 'Chicago Cubs'), new(Time.new(2037, 10, 23, 18, 0), 'Boston Red Sox', 'Chicago Cubs'), new(Time.new(2037, 10, 24, 18, 0), 'Boston Red Sox', 'Chicago Cubs'), new(Time.new(2037, 10, 25, 18, 0), 'Chicago Cubs', 'Boston Red Sox'), new(Time.new(2037, 10, 26, 18, 0), 'Chicago Cubs', 'Boston Red Sox', 'Free World Series Polo'), ] } end def playoff_type @playoff_type ||= 'World Series' end def playoff_type=(new_playoff_type) @playoff_type = new_playoff_type self.schedule=(all_playoff_games[@playoff_type]) self.selected_game = schedule.first unless selected_game.nil? end def playoff_type_options all_playoff_games.keys end def schedule @schedule ||= all_playoff_games[playoff_type] end def schedule=(new_schedule) @schedule = new_schedule end end include Glimmer include Glimmer::DataBinding::ObservableModel TEAM_BALLPARKS = { 'Boston Red Sox' => 'Fenway Park', 'Chicago Cubs' => 'Wrigley Field', 'Cincinnati Reds' => 'Great American Ball Park', 'Cleveland Indians' => 'Progressive Field', 'Houston Astros' => 'Minute Maid Park', 'Milwaukee Brewers' => 'Miller Park', 'New York Yankees' => 'Yankee Stadium', 'St Louis Cardinals' => 'Busch Stadium', } ATTRIBUTES = [:game_date, :game_time, :home_team, :away_team, :ballpark, :promotion] ATTRIBUTES_BACKGROUND = ATTRIBUTES.map {|attribute| "#{attribute}_background"} ATTRIBUTES_FOREGROUND = ATTRIBUTES.map {|attribute| "#{attribute}_foreground"} ATTRIBUTES_FONT = ATTRIBUTES.map {|attribute| "#{attribute}_font"} ATTRIBUTES_IMAGE = ATTRIBUTES.map {|attribute| "#{attribute}_image"} attr_accessor *([:booked, :date_time] + ATTRIBUTES + ATTRIBUTES_BACKGROUND + ATTRIBUTES_FOREGROUND + ATTRIBUTES_FONT + ATTRIBUTES_IMAGE) alias booked? booked def initialize(date_time, home_team, away_team, promotion = 'N/A') self.date_time = date_time self.home_team = home_team self.away_team = away_team self.promotion = promotion self.ballpark_image = [File.expand_path('hello_table/baseball_park.png', __dir__), width: 20, height: 20] self.booked = false observe(self, :date_time) do |new_value| notify_observers(:game_time) end end def home_team=(home_team_value) if home_team_value != away_team @home_team = home_team_value self.ballpark = TEAM_BALLPARKS[@home_team] end end def away_team=(away_team_value) if away_team_value != home_team @away_team = away_team_value end end def date Date.new(date_time.year, date_time.month, date_time.day) end def time Time.new(0, 1, 1, date_time.hour, date_time.min, date_time.sec, '+00:00') end def game_date date_time.strftime("%m/%d/%Y") end def game_time date_time.strftime("%I:%M %p") end def home_team_options TEAM_BALLPARKS.keys end def away_team_options TEAM_BALLPARKS.keys end def ballpark_options [TEAM_BALLPARKS[@home_team], TEAM_BALLPARKS[@away_team]] end def to_s "#{home_team} vs #{away_team} at #{ballpark} on #{game_date} #{game_time}" end def book! self.booked = true self.background = :dark_green self.foreground = :white self.font = {style: :italic} "Thank you for booking #{to_s}" end # Sets background for all attributes def background=(color) self.game_date_background = color self.game_time_background = color self.home_team_background = color self.away_team_background = color self.ballpark_background = color self.promotion_background = color end # Sets foreground for all attributes def foreground=(color) self.game_date_foreground = color self.game_time_foreground = color self.home_team_foreground = color self.away_team_foreground = color self.ballpark_foreground = color self.promotion_foreground = color end # Sets font for all attributes def font=(font_properties) self.game_date_font = font_properties self.game_time_font = font_properties self.home_team_font = font_properties self.away_team_font = font_properties self.ballpark_font = font_properties self.promotion_font = font_properties end end include Glimmer::UI::CustomShell before_body do Display.app_name = 'Hello, Table!' end body { shell { grid_layout text 'Hello, Table!' background_image File.expand_path('hello_table/baseball_park.png', __dir__) image File.expand_path('hello_table/baseball_park.png', __dir__) label { layout_data :center, :center, true, false text 'BASEBALL PLAYOFF SCHEDULE' background :transparent if OS.windows? foreground rgb(94, 107, 103) font name: 'Optima', height: 38, style: :bold } combo(:read_only) { layout_data :center, :center, true, false selection <=> [BaseballGame, :playoff_type] font height: 14 } table(:editable) { |table_proxy| layout_data :fill, :fill, true, true table_column { text 'Game Date' width 150 sort_property :date # ensure sorting by real date value (not `game_date` string specified in items below) editor :date_drop_down, property: :date_time } table_column { text 'Game Time' width 150 sort_property :time # ensure sorting by real time value (not `game_time` string specified in items below) editor :time, property: :date_time } table_column { text 'Ballpark' width 180 editor :none } table_column { text 'Home Team' width 150 editor :combo, :read_only # read_only is simply an SWT style passed to combo widget } table_column { text 'Away Team' width 150 editor :combo, :read_only # read_only is simply an SWT style passed to combo widget } table_column { text 'Promotion' width 150 # default text editor is used here } # This is a contextual pop up menu that shows up when right-clicking table rows menu { menu_item { text 'Book' on_widget_selected do book_selected_game end } } # Data-bind table items (rows) to a model collection (BaseballGame.schedule), # mapping columns in declaration order to row model properties (attributes) # By convention, every column property can be accompanied by extra properties # with the following suffixes: `_background`, `_foreground`, `_font`, and `_image` # For example, for `game_date`, model could also implement these related properties: # `game_date_background`, `game_date_foreground`, `game_date_font`, `game_date_image` # That is done in order to let the table widget set extra properties if needed. items <=> [BaseballGame, :schedule, column_properties: [:game_date, :game_time, :ballpark, :home_team, :away_team, :promotion]] # Data-bind table selection selection <=> [BaseballGame, :selected_game] # Default initial sort property sort_property :date # Sort by these additional properties after handling sort by the column the user clicked additional_sort_properties :date, :time, :home_team, :away_team, :ballpark, :promotion on_key_pressed do |key_event| book_selected_game if key_event.keyCode == swt(:cr) end } button { text 'Book Selected Game' layout_data :center, :center, true, false font height: 14 enabled <= [BaseballGame, 'selected_game.booked', on_read: ->(value) { value == false }] on_widget_selected do book_selected_game end } } } def book_selected_game return if BaseballGame.selected_game.booked? message_box { text 'Baseball Game Booked!' message BaseballGame.selected_game.book! }.open end end HelloTable.launch
-
_why's Estate
The other project, which is a bit more akin to Shoes, is the glimmer suite. https://github.com/AndyObtiva/glimmer
-
The Third Gosu Game Jam kicks off in just a few days on August 14th. Cast your votes to determine the theme!
One day glimmer will support gosu apps! (For those not knowing glimmer, here is a promo link: https://github.com/AndyObtiva/glimmer; it's not my project but Andy is cool so there you go - gosu is also great, though I don't fully understand why it were to be limited solely to games rather than also support GUI-like elements. Buttons it already supports, input-fields too. Needs more GUI functionality.)
What are some alternatives?
zigself - An implementation of the Self programming language in Zig
Shoes - Shoes 4 : the next version of Shoes
scenebuilder - Scene Builder is a visual, drag 'n' drop, layout tool for designing JavaFX application user interfaces.
Humanizer - Very simple captcha with Rails 3 & 4 & 5 & 6 & 7 support
cells - A Common Lisp implementation of the dataflow programming paradigm
glimmer-dsl-libui - Glimmer DSL for LibUI - Prerequisite-Free Ruby Desktop Development Cross-Platform Native GUI Library - The Quickest Way From Zero To GUI - If You Liked Shoes, You'll Love Glimmer! - No need to pre-install any prerequisites. Just install the gem and have platform-independent GUI that just works on Mac, Windows, and Linux.
power-fx-host-samples - Samples for hosting Power Fx engine.
glimmer-dsl-swt - Glimmer DSL for SWT (JRuby Desktop Development Cross-Platform Native GUI Framework) - The Quickest Way From Zero To GUI - If You Liked Shoes, You'll Love Glimmer!
impulse - Impossible Dev Tools for React and Tailwind
glimmer-dsl-tk - Glimmer DSL for Tk (Ruby Tk Desktop Development GUI Library)
halo - An experimental graph-based meta programming language
qtbindings - An easy to install gem version of the Ruby bindings to Qt