On Sat, Nov 11, 2017 at 6:58 PM, Викентий Потапов <vikenti.pota...@gmail.com> wrote: > Well, i've got very extensive feedback for i18n of applications, there are > few solutions i can use, despite there is no united way embedded into pharo > view on application design. That's ok, i can do something for my one taste (i > prefer it to be a part of SPEC framework or something like this). > > Another stumbling block is application deployment. I've heard about some > "Launcher" but ... what is it? what it does? where to get it?
the launcher is an application to manage your images and development. You can find it at - http://files.pharo.org/platform/launcher/ (do not use blessed but the latest version of your platform) we should promote this tool better > In Cincom VW deployment means: > - get rid of all we don't use in image. > - test image for successful run > - delete all sources (hide it from disassembler) Until recently in Pharo it was not possible to remove the compiler. Now we can create an image without the compiler. We have to continue > - lock\hide all excessive menus, tools or any backdoor to launch Smalltalk > IDE or execute smaltalk code presented as text. - You should remove and provide something as s replacement for the UnhandledException defaultAction else you get the debugger. Now you application should use exception. For the menu, check the pragma <WorldMenu> > - pack image and VM together with specified name of main executable. For this you should use bash or bat files. > > What can i do with Pharo? Does it have unified method to deploy pharo > applications? I didn't find that method, and i ought to do some messy stuff > "by hand". > > It will be very useful to do some steps in that direction. I want Pharo to be > comfortable tool for application development. Like Delphi or C++ (where i > came from but don't want to get get back to, after Smalltalk any other > platform seems imperfect for me). We want the same but we are not yet there. I want APPLICATIONS not just code loaded into Pharo. > > Faithfully yours, Vikenti Potapov. > >
