Creating class with empty Catagory!
Yes, this could definitely be inmproved. An idea would be a dialog with a pre-filled class definition that has useful defaults. This way when demoing, you can just accept the empty and nevertheless a class is created just by pressing âokâ in this dialog.
On 08 Sep 2015, at 11:28, Volkert <volkert@komponentenwerkstatt.de> wrote:
Would it be nicer to open a Altert box?
BW, Volkert
<gabhajcb.png>
Marcus I would simply not put empty we have unpackaged let us use it by default. The empty category is a bad idea and we should address it because many people are getting burned.
Yes, this could definitely be inmproved. An idea would be a dialog with a pre-filled class definition that has useful defaults. This way when demoing, you can just accept the empty and nevertheless a class is created just by pressing âokâ in this dialog.
On 08 Sep 2015, at 11:28, Volkert <volkert@komponentenwerkstatt.de> wrote:
Would it be nicer to open a Altert box?
BW, Volkert
<gabhajcb.png>
On Tue, Sep 8, 2015 at 5:28 PM, Volkert <volkert@komponentenwerkstatt.de> wrote:
Would it be nicer to open a Alert box?
Yes. Now maybe it should not be done directly from here... SlotClassBuilder >> category: aCategory aCategory isEmpty ifTrue: [ InvalidPackageName signal: 'The Category should not be empty' ]. category := aCategory ...since that might(?) introduce a dependency from the kernel to the UI. But maybe further down the stack in one of... PackageTreeNautilusUI(AbstractNautilusUI) >> compileAClassFrom: aString notifying: aController >> compileSource: aText notifying: aController there could be an error handler. Would you like to have a go at it? cheers -ben
participants (4)
-
Ben Coman -
Marcus Denker -
stepharo -
Volkert