home.social

#cuis — Public Fediverse posts

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

fetched live
  1. Église à #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

  2. Église à #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. Église à #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

  4. Église à #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

  5. 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

  6. 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

  7. 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

  8. 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

  9. 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

  10. 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.

  11. 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.

  12. 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.

  13. 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.

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

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

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

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

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

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

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

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

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

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

  24. 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.

  25. 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.

  26. 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.

  27. 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.

  28. 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.

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

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

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

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

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

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

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

  36. 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

  37. 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

  38. 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

  39. 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

  40. 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

  41. @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

  42. @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

  43. @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

  44. @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

  45. @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,

  46. @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,

  47. @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,

  48. @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,

  49. #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

  50. #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

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

    #HaverSmalltalk #Cuis #CuisSmalltalk #Smalltalk

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

    #HaverSmalltalk #Cuis #CuisSmalltalk #Smalltalk

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

    #HaverSmalltalk #Cuis #CuisSmalltalk #Smalltalk

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

    #HaverSmalltalk #Cuis #CuisSmalltalk #Smalltalk

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

    #HaverSmalltalk #Cuis #CuisSmalltalk #Smalltalk