Nicolas Roard wrote:
On 4/4/07, Isaiah Beerbower <[EMAIL PROTECTED]> wrote:
Hello all!
[snip]
I propose (please tell me if this is a stupid idea) that we have
services be, well, services. Instead of using a bundle they would be
similar to an application, but not an application. If I am correct,
applications get their behavior from the NSApplication class. I propose
we create our own class (EtoileService) and a new function
(EtoileServiceMain) to start the run loop. This way we could define our
own behavior for services. EtoileService would have some sort of
integration with NSDocument (or, probably, EtoileDocument) to give the
document oriented behavior.
[snip]
Please critique my ideas without mercy!
Well, for start, services (in the gnustep sense) ARE applications, not
bundles.
And I don't see why we would get rid of applications and have only
bundles -- applications are useful, they run in separate process :-)
If you read my email correctly (or maybe I was confusing?) you would see
that I was saying services should be application like. I know that all
services are currently applications, my suggestion was to create our own
"NSApplication" class so as to give the services a standard behavior. My
idea had nothing to do with making services into bundles, quite the
contrary!
Now, that does NOT mean that our "applications" will behave as
isolated as current desktop applications do -- to the contrary ! and
they will likely not be really similar to "current applications". But
I don't see why technically we should get rid of them.
Our services will be document based, will they not? Almost everything
you do on the computer writes to or reads from a document; why not treat
it that way?
Basically what you are proposing is awfully close to the architecture
we already have :)
(and yes, services are described already in a plist, etc ;-)
I didn't say they didn't! (deep breath) I suggested adding a NEW plist
file describing what settings a service has and how they should be
edited. All settings could then be changed by opening the settings
document with a preferences editor. The preferences editor would look
for a settings plist in the service which would tell it how to edit the
settings in the user's settings file (i.e. in ~/GNUstep/Defaults, or
wherever they are, I forget).
I'm not sure about the "let's get rid of prefrences panels" -- it
seems to me more an etymologic change (let's call them preferences
documents!) than a real technical change.
I'm not just changing the name! I'm actually treating the preferences
like other documents!
On adding more "pickers" it's a good idea. Not sure about a calculator
one, but a date/time picker would be neat, yes. Other "pickers" idea ?
A character picker would be nice. A language picker could also be nice.
The calculator idea is to replace a *normal* desktop calculator, and put
it in a floating window, where it belongs. It could be seen as a "number
picker".
Please reply,
Isaiah Beerbower
(ps: I didn't answer to david's mail -- but basically I entirely agree
with him, files are bad. The only problem I have is how long will it
takes us to do it, and what should we do in the meantime)
NOTE: That's not just David. That is a discussion between several people
from the chat room. If you haven't read the actual discussion (and I'm
not saying that its bad if you haven't) it might be the cause of you
misunderstanding my email. The ideas here were additions to what was
discussed there.
_______________________________________________
Etoile-discuss mailing list
Etoile-discuss@gna.org
https://mail.gna.org/listinfo/etoile-discuss