On 02/10/17 15:28, Esteban Lorenzano wrote: >> On 2 Oct 2017, at 15:12, Stephane Ducasse <stepharo.s...@gmail.com> wrote: >> >> I discussed with esteban sooner this summer and we really want to have a >> process >> where people can deploy applications and not just code. >> Now we are not yet there. >> >> Stef >> >> On Sun, Oct 1, 2017 at 9:03 PM, Steven R. Baker <ste...@stevenrbaker.com> >> wrote: >>> Heya folks, >>> >>> [Please jump on any of my statements that sound crazy: use of Spec, >>> other assumptions, etc.] >>> >>> I'm starting an application in Pharo, using Spec. Basically, a GTD >>> application in the spirit of nirvanahq, omnifocus, things, nozbe. The >>> code is working just fine, but I'm left with a lot of questions about >>> how to organize it. >>> >>> First, is there some trick to managing images? Are people using >>> one-per-project, or one-per-computer? All of the above? Anyone using >>> PharoLauncher these days? Other tools? > pharo users tend to prefer one-per-project approach :) > most people uses (or should use) pharo launcher. In fact, we want to make it > the default download, is just that to get it right is complicated :) > > but… pharo launcher is to developers. A final app would require other stuff > to be accomplished (like closing development tools, etc.). > >>> I'm assuming that the current state of the art is Iceberg; where can I >>> find a "This is how you should organize your project using Iceberg" >>> document, blog, book, tutorial, video, or otherwise. > beware: Iceberg is a cvs (like Monticello or git or svn…): it is use to store > code, not to organise your project. > To organise your project you have Metacello. > >>> Once the application is done, I assume I'll want to ship it in a minimal >>> Pharo image. Is there documentation or prior art on this? > this is what is hard :) > I imagine with the headless VMs we are about to finish it will be easier (to > just initiate a window with your app, instead initiate a window with the full > world as now). > but we still require some work. > >>> Finally, is there a way to run and capture keybindings globally? I have >>> one part of my application (a quick-entry window) which I want summoned >>> from a global (OS-wide) hotkey. Has this been done before? Or is it not >>> easy to break the fourth wall, so to speak, and register a global >>> keybinding from inside the VM? > there is a keybindings framework inside pharo, but since you have a lot of > development tools, it becomes hard to use (again, something that can be > solved in the near future, with same approach as before, but not yet). > now, to get the keybindings of the system you will need to install that *in* > the system. > > for mac, for example, you can doit using the ObjC bridge (which does not > works in 64bit images... I’m working on a UFFI replacement, but… guess what? > not yet :P) > and I guess using UFFI you can get that to work on windows and linux? I’m > really don’t know. > > all you ask is *doable*… but not all your requirements are *easily* doable > right now, which is want I want to fix :) I don't mind contributing code and time on these things, as they present real barriers to me. I'm looking for ways to get involved in the community again. :)
-Steven > Esteban > >>> Thanks! >>> >>> -Steven >>> >>> >>> >
