Hi Dale, Dne 04. 08. 2012 07:31, piše Dale Henrichs:
> The bigger problem is that I have to have a code base that runs on multiple > platforms while being maintainable, so a "port" to Pharo-2.0 is only a > starting point. In the case of FileTree, which is the real bottleneck there's > a lot code that is written against the FileDirectory API, so there will need > to be significant work to find a way to keep a common code base .... a much > tougher problem, than "just getting it working", it can be solved with time, > but I didn't budget time for an emergency rewrite of FileTree ... today. Just FYI, there is a Sport portability library and by using Sport's SpFilename you have an instantly portable file support over quite a dozen Smalltalks. So, if someone adapt Sport to a new Pharo 2.0 filesystem first .. Best regards Janko -- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si
