Smalltalk expert having questions related to Vue components #13425
JosefRosenberger
started this conversation in
General Discussions
Replies: 1 comment
-
Vue is a lower-level framework, used to write and combine components. It only provides a very small number of components itself (e.g Transition, KeepAlive). I'm not sure where you read the number of 140 UI components. Vue itself doesn't provide that. There are several component libraries available, written on top of Vue, that should give you what you're looking for. You can find more information about them at: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello all,
I am not (yet) a user of Vue but I'm having a couple of questions, which came up when studying the Vue documentation.
A few words on my background and methodology:
Extremely experienced OOD software architect and lead developer since 1987 (yes, true), first nightmarish in Objective-C, for the last 30 years only in Smalltalk.
I am looking for a UI library, which I can use as low-level tool below my Smalltalk framework having over 10.000 application classes and around 200.000 methods to create complex, appealing and dynamic UIs in the browser.
What I'm missing in the Vue documentation is a detailed listing of all the claimed 140 UI components and their attributes (instance vars). There are just a few examples but no complete list of all and no listing of the UI attributes or examples how they can be initialized.
All UI systems, which I had used or played with in the past (2 x in Smalltalk, Gtk, Sencha EXT JS, which I used for a running prototype) had standardized UI components, widgets, buttons, selection lists, containers and so forth, which were used to assemble a comprehensive UI.
Where are ALL Vue components listed and explained in detail?
I look at the UI totally the OOD way. All possible settings of my UI (currently in Smalltalk) come from various types of descriptors, which exist for all important entities, especially for classes (this includes all DB table settings), attributes (instVars), which includes all lower-level values, also for forms, panes, views and more. I call this "data-driven programming" and I have practiced and enhanced this step-by-step since 1987.
Is it possible to initialize and standardize Vue components this way? In my former Sencha prototype this was quite well possible, but I do not trust this company as they have screwed their customers several times in the past.
I ALSO DO NOT WANT to construct UI components individually one-by-one in this extremely primitive JS "IDE", which I find appalling - and nobody should judge this statement who has no clue of what Smalltalk has been offering since it's first version in 1980!
There exists meanwhile a clever tools to translate Smalltalk code into JavaScript, so that I intend to have my extremely comprehensive and highly productive Smalltalk framework generate (almost?) all of my UI definitions for the browser from Smalltalk definitions in higher abstraction levels similar to what I have achieved for the current Smalltalk UI for the desk-top.
Thank you in advance for your constructive comments
Beta Was this translation helpful? Give feedback.
All reactions