You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm assuming that we'll have some code massaging in addition to the meta-data, do deal with thing like {} in VAST (where Monticello Importer comments out the code and adds an exception stub). Or is the expectation that file-out code is always dialect neutral?
I've started on the port of PDF4Smalltalk 'Values' package from VW to VAST and I'm using it as a test bed for what I think I'll need on the VAST side. That package has few of the namespace and code issues that the PDF and Fonts package have, but it's a good start.
Are we advocating the use of Grease? We've had some discussion on the PDF4Smalltalk forum about the best 'dialect neutral code' technique. I like using Grease to avoid things like #asString variations, but there is a concern that having Grease as a pre-req (too big, perhaps?). My bias is to use Grease, probably because I do a lot of cross-dialect Seaside code (VW & VAST).
The text was updated successfully, but these errors were encountered:
I'm assuming that we'll have some code massaging in addition to the meta-data, do deal with thing like {} in VAST (where Monticello Importer comments out the code and adds an exception stub). Or is the expectation that file-out code is always dialect neutral?
I've started on the port of PDF4Smalltalk 'Values' package from VW to VAST and I'm using it as a test bed for what I think I'll need on the VAST side. That package has few of the namespace and code issues that the PDF and Fonts package have, but it's a good start.
Are we advocating the use of Grease? We've had some discussion on the PDF4Smalltalk forum about the best 'dialect neutral code' technique. I like using Grease to avoid things like #asString variations, but there is a concern that having Grease as a pre-req (too big, perhaps?). My bias is to use Grease, probably because I do a lot of cross-dialect Seaside code (VW & VAST).
The text was updated successfully, but these errors were encountered: