hi, ah, those are correct presenters/applications. if you want to make a gtk application at a point you need to configure it (hence CrGtkConfiguration). CrApplicationStarter is because in different platforms you may have different ways of start the application (for example macOS may need a system menu... which anyway so far I have been unable to do, but still ;) )
the other extensions were for needs of the application but indeed some of them may arrive (and some of them already this) to vanilla spec (firstResponder is now "defaultKeyboardFocus", for example...). this application is one of the ones I use to test concepts that may or may not make their path to vanilla Spec :) Esteban On May 11 2021, at 7:30 pm, mark.odonoghue.2...@gmail.com wrote: > Hi Esteban > > I’m new and may be wrong and apologise if so … ! > It just looked like the Crono package has a few things I didn’t expect : > CrApplicationStarter > CrGtkConfiguration > > CrWindowConfiguration > > SpPresenter extension firstResponder > > SpWindowPresenter extensions (2) > > These ‘Cr’ classes seem to have some more general purpose behaviours that > other SpApplications could use? > And I would have thought the Gtk configuration would be outside Crono too? > Also, presumably the extensions are candidates for repackaging outside/above > Crono ….? > This may be just a naming and packaging thing rather than any criticism of > design. > > In summary, as a simple consumer of the framework there was (some) surprising > detail in the Crono package and classes that didn’t seem relevant to any new > application I would be writing. > Hence I would have hoped not to have to clone these details (or even deal > with them…). > Does that sound fair? - or do I have the wrong end of the stick !! > > > Cheers > Mark
