home.social

#cuis — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #cuis, aggregated by home.social.

  1. Chắc chắn rồi, đây là bài đăng dành cho bạn:

    Ở TPHCM, Đồng Nai có một loại rau mọc dại, không cần chăm sóc nhưng lại trở thành đặc sản trứ danh! 🌿

    Từng được coi là món "cứu đói" của những ngày khó khăn, giờ đây chúng lại nổi tiếng với độ giòn sần sật, hương vị thơm ngon khó cưỡng.

    Sinh trưởng tự nhiên, chỉ việc hái về và chế biến thành những món ăn dân dã nhưng đậm đà tình quê. Bạn có đoán ra đó là loại rau gì không? 😉

    #DacSan #RauMocDai #TPHCM #DongNai #AmThucViet #StreetFoodVietnam #Cuis

  2. Eglise à #Cuis (#Marne) Construction XVe siècle, XVIe siècle, XVIIe siècle, XVIIIe siècle. Eglise : classement par arrêté du 29 janvier 1902.
    Suite 👉 monumentum.fr/monument-histori
    #Patrimoine #MonumentHistorique
    Photo CC-BY-SA 4.0 : Garitan

  3. Smalltalk (Cuis)

    Yes I have install #cuis on my system works great because smalltalk is its own VM. I like #smalltalk and #cuis is a great way to learn.

  4. @drgeo This is soooo cool!
    I am temped to port #Haver to the #Cuis rolling release, just to be able to use it.

  5. @drgeo Does this mean, we soon will have a PDF editor for #Cuis ?

  6. I managed to write a grammar for #Cuis version 7.0. It can parse the 30001 methods in the development image of my Earley-parser, but I do not know, whether it created the right language structures aka. syntax trees.

    Needless to say, that it needs #Haver to be executed.

  7. @alvarmaciel would you know how to modify the clock in #Squeak or #Cuis #Smalltalk to not show seconds?

  8. @vidak May one point out that #Haver is decidedly *not a fork* of #Cuis. It is implemented on top of the current Cuis version.

  9. I love class definitions using the module system #Haver provides.

    Enter the definition shown in the first picture, with proper settings your class will be bound in a module, as shown in the second picture.

    #HaverSmalltalk
    #Cuis

  10. Alas #Cuis has a bug in it's ZIP file package. This code snippet does not terminate:

    (z1 := ZipArchive new) zipFileComment: 'ZIP test'.
    z1
    addFile: SourceFiles first fileEntry as: 'f1';
    writeToFileNamed: 'test.zip';
    close.

    See:
    lists.cuis.st/mailman/archives

  11. @vidak Communication wise: nothing ;)

    Concerning #Smalltalk I created an extension of #Cuis called #Haver .
    Documentation and release builds are outdated, but that can be changed.

    Take a look at: haver.klix.ch

  12. @vidak Cool! I thought about using #HaverSmalltalk (eat your own dogfood) or #CuisSmalltalk. After all #Cuis has builtin vector-graphics with a #TrueType engine implemented in Smalltalk,

  13. #Unicode Input by #AsciArt

    I just added experimental support for converting ASCII-art character pictures to Unicode code points to #Haver.

    Every input starting with "\." and followed by a recognized picture is replaced by a corresponding Unicode code point (or, more exactly, its glyph).

    #Cuis
    #CuisSmalltalk
    #HaverSmalltalk

  14. #Unicode Input by #AsciArt

    I just added experimental support for converting ASCII-art character pictures to Unicode code points to #Haver.

    Every input starting with "\." and followed by a recognized picture is replaced by a corresponding Unicode code point (or, more exactly, its glyph).

    #Cuis
    #CuisSmalltalk
    #HaverSmalltalk

  15. #Haver now has persistent work spaces which persist the source code and the bound variables.

    #HaverSmalltalk #Cuis #CuisSmalltalk #Smalltalk

  16. @drgeo Pointed to an 13 year old interview with @juanvuletich
    saying:

    «It is a must to read, and we can say that the heading to the Cuis' objectives have been maintained in most part.

    For me the most dominant aspect of Cuis is that it is an enabler.»

    It totally agree!

    #Cuis #CuisSmalltalk #Smalltalk

    See:
    clubsmalltalk.org/2010/07/juan

  17. @Conornash That's interesting!
    I did a complete round trip:
    Started with Smalltalk/V for MDOS in the late 80s. Used the same #Smalltalk on Windows and OS/2 in the early 90s. Used C++ for the rest of that decade. Then switched to #Python as a substitute for Smalltalk. Used #Squeak and #Pharo for private projects. Finally came back to #Cuis around 2015. After some discussion I started my own Cuis-based Smalltalk called #Haver​.

  18. @Conornash That is why I gave up using #Pharo​.

    There are oodles of packages looking useful. Once you want to use one them, you soon discover that exactly this package stopped being useful, because it does not work or even load with newer Pharo versions. (Backward compatibility is for wimps!)

    #Cuis is IMHO a much better alternative!

  19. @CyDeFect Well .. If there are too many nested and too deeply morphs, #Cuis spends a long time to do complete the layout process.

  20. What does an immersive #morphic look like? What would you build with it? #smalltalk #squeak #pharo #cuis

  21. Oh shit, I just discovered why Squeak's and Cuis​' break-point implementations are exception based. 'Break on entry' on a #drawOn:-method leads to a new debugger every time a morph is displayed.

    #CuisSmalltalk #Squeak #Cuis

  22. @drgeo I see no difference. I suppose you can export the "scan" from #Cuis as #SVG​, can't you?

    #CuisSmalltalk

  23. Semantic actions make the grammar considerably longer, but we can still make good use of Unicode arrows (⇑) provided #Cuis​' Unicode handling.

    #Haver #HaverSmalltalk #CuisSmalltalk