Oh and btw, the problem that I see with using e's current
notion of "profile" as a means to define such a shell-skin
bundle, is that the current notion of a profile is either too small
if you mean just the config data file, or too big if you mean
the entire directory.
    As Cedric succinctly described, you want something that holds
enought config data for whatever gadgets/modules it uses, plus
edje groups for themes of those gadgets, wallpapers, cursors, etc.
and it's all one file that you can choose to apply to a given screen
or set of virtual desktops.

    I just don't see how you can easily use the current notion of profile
to enable this - perhaps use some derivative of the config data part
(minus aspects that you don't want included like passwds, and any
other stuff that doesn't deal with what the shell-skin notion conforms to).


> ....
>> he problem is you're trying to go the next level... which is "what id
>> there are 50 designers all with awesome ideas - how do they package them up 
>> and
>> give them to people". that's your shell thing. and as such all of these are 
>> in
>> fact large blobs of logic (code) and so are not readily portable and 
>> shippable.
>> the best that can be done is offer a module and then alongside a profile that
>> enables it and configures it. the module cant sensibly ship with the profile
>> because it is not "just data". :)
>>
>>   
>>     
>
>     It depends on what one considers a "shell-skin" to mean.
> If you mean it to contain e17 C modules then you could have
> issues with that.
>     However, it doesn't have to mean that... One can do a lot
> with just packaging a desktop config of existing gadgets/modules,
> plus wallpapers, plus gadget themes, etc... and it would define
> a good notion of such a thing.
>     If it needs to depend on specific C modules that are not part of some
> distribution say, then those would have to be downloaded separately.
> However, one can imagine e17 jscripted modules that could do a lot
> of the basic kinds of functionality, much as edje, and that could be
> part of the shell-theme bundle.
>
>     The overwhelming majority of people's shell customizations
> does not involve writing new C modules... just selecting, theming,
> and positioning existing ones. And again, any requirements on
> having some particular C module around would be just that - go and get
> module blingo over at this link here as the cool-blingo shell-theme
> uses that.
>
>
>   
>> so right now all of this is possible, but in 2 parts. make a module, then a
>> profile to configure it. :) i know i don't have the time to do ui experiments
>> myself. i'd rather not have some grand unified module here either but just
>> specific features you can turn on and off provided by a range of modules, 
>> not a
>> single one. so you can take and configure just one of the elements you like 
>> not
>> not have to take the rest. :)
>>   
>>     
>     Yes, you can do that (make e17 C modules and make profiles using 
> those, etc).
> But this is more something that distros or other organizations would 
> do... not for
> skinners/themers or just users who like to do their own desktop 
> customizations.
>     As above, this latter is more like selecting some set of existing 
> gadgets/modules,
> some config for placing them here and there, some themes for the 
> gadgets, maybe
> some matching wallpaper, cursor, ... those kinds of things (I would tend 
> to not include
> normal e17 themes as part of that since those already have their own 
> system, and you
> can just say that the shell-skin cool-blingo looks best if used with the 
> default e17 theme).
>
>     You know Cedric wants to do this kind of thing via the exchange 
> site, and it's just
> a matter of formalizing what to include/exclude, writing a managing 
> module for it, etc..
> much as is the case with the current themes/wallpaper/splash subsystems.
>
>   

____________________________________________________________
How to Sleep Like a Rock
Obey this one natural trick to fall asleep and stay asleep all night.
http://thirdpartyoffers.juno.com/TGL3141/5120b027a6f5f3021658cst01duc

------------------------------------------------------------------------------
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to