Carsten wrote:
> .....
>> The point you should be embracing is not to force people to only
>> accept e17's current 'old-fashioned' idea, or your cocky one, or some
>> osx clone, or some gnomic notion, etc... but to empower designers
>> such as yourself with the ability to do more than just show some gif.
>>
>> It's to enable them to easily share such shell-skins so that others may
>> actually try them. It might even be the case that if yours became very
>> popular, then the e17 devs might decide to choose that as (one of)
>> some set of 'official' default shells.
>>
>
> indeed that is a good point. the problem is - your "shell" thing wont do it.
> :)
> what errr... "al" (lets use that as a short name as i can only make out
> anything sensible from the email address... i'll have to call you "squiggles"
> otherwise :) - no - i dont read arabic :)) seems to want is doable via
> extensions (modules) to implement all the specific behaviour he wants.
> specific
> modules already implement similar kinds of behaviour - engage, comp-scale etc.
> what he wants is a unified thing i guess that does it all. great - go make
> it. :) t
Indeed, if he's serious about a Rosa Linux distro of some sort
for which he wants his shell design to be the default, then they should
spend some resources to get someone with enough knowledge of
e17/efl to write a new profile and whatever modules he might need,
which implements just what he wants.
> 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/5120669ecfb29669b7c10st03duc
------------------------------------------------------------------------------
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
